Methodology
The training does not start by teaching a tool. It starts by mapping what your team currently does, then builds new habits into the gaps that are actually causing friction.
Before any module begins, teams complete a short audit of their current recurring meetings, documentation locations and messaging habits. This gives the facilitator a concrete picture of where the team is losing time, rather than working from assumptions about what "good async communication" should look like.
The audit typically takes one working session to complete and produces a simple map: which meetings exist, what each one is meant to accomplish, and where documentation currently lives, if it lives anywhere consistent at all.
Module one is built around a simple test applied to every piece of team communication: could this be written instead of said out loud, and would it be better if it were?
Templates for status updates, decision proposals and handoff notes, designed so a reader in a different timezone can act on them without waiting for a live explanation.
Explicit agreements about how quickly different types of messages need a reply, replacing the unspoken expectation that everything gets answered immediately.
A clear route for moving something from async discussion to a live conversation when it genuinely needs one, so async-first does not become async-only.
A handoff format used at the end of a working day so the next person picking up the task does not need a call to understand where things stand.
Module two treats documentation as a system with categories, not a single dumping ground. Teams learn to separate reference material that rarely changes from decision logs that capture why a choice was made, and from working notes that are expected to go stale.
Participants restructure an existing piece of their own documentation during the session, so the exercise produces something usable immediately rather than a hypothetical example.
Module three works through four steps applied to every recurring meeting a team currently holds.
Write down, in one sentence, what the meeting is supposed to produce. Meetings without a written purpose are the first candidates for removal.
Check whether the stated purpose could be met by a written update, a shared document, or an async decision thread instead.
For meetings that genuinely need real-time discussion, build a shorter agenda that starts with the decision to be made, not a status recap.
Every meeting that remains ends with a written decision or action list, so it feeds documentation instead of disappearing once the call ends.
A mix of formats reflects the async-first principle the program teaches.
Reading, examples and templates completed individually or in small groups, on each participant's own schedule.
Shorter facilitated sessions focused on applying that module's material to the team's real workflows.
A running written thread where participants can ask the facilitator questions between sessions.
A short follow-up check-in after the program ends, to see how new habits are settling into daily work.
Facilitators adjust pacing and examples based on the audit results from the first session. A team already using structured documentation but drowning in status meetings spends more time in the meeting redesign module. A team with the opposite problem spends more time on documentation architecture.
The program stays informational and practical throughout. It does not promise a specific outcome, and it does not require a particular tool stack to work through the material.
Reach out and describe your current tools and meeting load. We can talk through which modules matter most for your situation.
Talk to Us