How Our Engineering Team Communicates Asynchronously Through Writing
Blog post from WorkOS
The Engineering team at WorkOS uses asynchronous communication through writing in Threads to make product decisions and maintain transparency. They aim for asynchronous communication to save time from meetings, ensure transparent decision-making, and leave a record for future reference. They propose guidelines on when to create a Thread, where to create it, requesting responses, what to include in a Thread, conveying status, coming to decisions, handling disagreements, and completing Threads. The team uses emojis to indicate the status of a proposal and follows different decision-making processes for irreversible and reversible decisions. They also encourage thoughtful disagreement and scheduling calls if needed.
No tracked trend matches for this post yet.
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.