4 ms·
I’m running engineering at a small startup that’s full remote, it’s working fine for us. Don’t agree that remote work means you can’t have dynamic communication
by presentation 3y ago
I’m running engineering at a small startup that’s full remote, it’s working fine for us. Don’t agree that remote work means you can’t have dynamic communication. It just means you need to choose the right employees and have an higher bar of alignment on how you work and communicate.
Don’t hire people who don’t value synchronous communication. People who want all communication to be async and don’t plan to respond promptly to messages (like the work/life balance crowd on HN) will not produce a dynamic team because that’s not the strong point of async communication.
Do quick calls when text conversation gets too long, build a team where you can expect people to actually make an effort to show up to the calls. For us we also have strategy calls with video regularly (but not too frequently), and make sure everyone is aligned to the plan and concerns are resolved before building. Make sure the team understands that for anything where they are unsure what to do or have any ambiguity around requirements, that they proactively ping the right people.
Doesn’t mean you need to be on all the time and that async communication is not valuable, but you need everyone to know when it is and isn’t the right way to go. So long as people are making a best effort to value communication speed it works out.
Hire people who are motivated enough to form opinions, and confident enough to say they really think. Most people are not invested in their work, or not invested in the problem space enough to bother making the mental and research effort to form valid opinions on your problem space. This is fine for when things just need to get done (not everyone on the team needs to be a decision maker), but foster those who are ready to invest. Make it clear it’s a good thing if they do form opinions and are willing to express their doubts about the strategy to others/leadership.
For us we also have very clear owners of different aspects of our operations and product. Someone will make the final decisions on those aspects. This doesn’t mean they make all choices, they can choose to defer to someone they trust to make the call. But someone needs to be clearly responsible, and others need to know that if a conversation is not resolving that they can pull the right person in to resolve it efficiently. People need to agree to disagree at some point once those responsible make a choice.
This general approach works for us, people don’t tend to hate their managers if they understand why choices are made, feel that their concerns are heard, and are aligned ideologically with the approach and way of working. But it does require choosing the right people and setting a higher bar for yourself on alignment.
- theonething 3y ago> Don’t hire people who don’t value synchronous communication. People who want all communication to be async and don’t plan to respond promptly to messages (like the work/life balance crowd on HN) will not produce a dynamic team because that’s not the strong point of async communication. Basecamp has always been remote and asynchronous and they seem to be doing well.
- cosmodisk 3y agoDon't hire people who can't put two coherent sentences together in an email. I've seen many many of such types. They are tragedy in remote environments.
- hiepph 3y agoAgree. Writing communication is essential, and might have more influence than speaking communication, in a remote working environment. The whole OSS movement has been built on this.
- presentation 3y agoOP is talking about fast moving startups in an ambiguous environment, async is good but optimizing utilization doesn’t help if you’re going in the wrong direction. My point isn’t “don’t value async work” it is “don’t not value sync work”
- j4yav 3y agoAsync teams achieve dynamic results through multi-threading, not being really good at dropping everything else to do one thing at a time really well.
- presentation 3y agoYa but OP is asking about startups in an ambiguous environment. I think that works well when you’re more steady state.