Go async-first with your team
Use the filters below to find async-first methods that are relevant to your team. For detailed articles, check out the blog.
Technical design docs
Technical design docs are an efficient way to communicate about software architecture and technical solutions. These docs precede an architectural decision record. They benefit from detail, though brevity is an important consideration too.
Feature breakdown documents
Feature breakdown documents serve as a single resource to catalogue all information about a feature. As the team enhances the feature, this document becomes a single source of truth about it.
Idea papers
Idea papers allow you to nurture fresh ideas by articulating them clearly. People can use this as a reference to share feedback and enrich the idea. Decision making is also easier if everyone can understand the idea well.
Avoid communication blasts
A single line message that you send to 200 people isn’t a single line message anymore. It’s a 200-line message. Instead, “shrink the blast radius”.
Target your conversations
Limit chat conversations only to those necessary to the discussion.
React, don’t respond
In the spirit of limiting messages, use emoji reactions where possible, instead of responding to a message.
Limit the number of messages
It’s ok to write longer chat messages! Save everyone the extra notifications.
Make the task-board the central communication tool
Most project management tools allow you to define a workflow for your team and visualise that workflow as a task board. Your task board should be the source of truth for all the work your team is up to.