3 ms·
Even within remote companies there are distinctions between the way different teams practice remote. For example, a lot of companies that transitioned to remote
by zuhayeer 5y ago
Even within remote companies there are distinctions between the way different teams practice remote. For example, a lot of companies that transitioned to remote out of necessity come from the perspective of copy / pasting in-office activities online (ie meetings, happy hours, etc) whereas natively remote companies think about things from a more original and untethered view (async, writing, Looms). Be careful to spot the difference when joining a company.
- woodpanel 5y agoPlease, would love to hear more about your point about "(async, writing, Looms)" :-) I'd just had the pleasure to work at a unicorn which started during the pandemic, but for whatever reason wanted to open actual offices mid-term. The result being that some teams were working more async-y than others. And I immediatly felt, there's a need to explore how to sync teams in an async way, including many yet-to-exist tech-solutions. So please, elaborate!
- zuhayeer 5y agoThe GitLab Handbook is a great start. They have an awesome guide to remote work: https://about.gitlab.com/company/culture/all-remote/guide/ https://about.gitlab.com/company/culture/all-remote/guide/ Strong written communication is a given, but they have some good advice here: https://about.gitlab.com/company/culture/all-remote/effective-communication/ https://about.gitlab.com/company/culture/all-remote/effectiv... If you aren't familiar, Loom (https://www.loom.com/ https://www.loom.com/) is a great tool for screen recordings and narrations to explain things asynchronously without having to book time with someone else. Particularly useful if you have a distributed team across the world. And also neat that it can be indexed like a document if someone has a similar query in the future, they can find this video instead of having to message you.