Ben Balter
@benbalter
@benbalter
Remote work requires communicating more, less frequently, because async communication involves less frequent, but richer communication. There is less talking about the work and more doing it, allowing the system to optimize for throughput and flow. https://ben.balter.com/2023/08/04/remote-work-communicate-more-with-less/
❗ Heads up! This Tweet is archived and here for historical purposes. It may no longer be accurate or reflect my views. Proceed at your own risk.
If you enjoyed this tweet, you might also enjoy:
- Recently new to remote work culture? There's a lot more to it than not w...
- In light of today's announcement, a reminder that Slack DMs are not emai...
- Why should your team work asynchronously? Async is the key to remote wor...
- Come work with me and help make the software industry safer and more wel...
- I missed it when it was first published, but just as true today, @sm_deb...
- 15 rules for communicating at @GitHub http://ben.balter.com/2014/11/06/r...
- Any good resources out there along the lines of "Blogging for Dummies"? ...
- Are there any open source form builders out there with an active communi...
- The way you communicate via issues/PRs is very different than the way yo...
- Talked a bit on how remote work requires an async-first culture. https:/...
- Any DC-based WordPress folks looking for work? Ideally a WordPress shop,...