Blueprint library
Communication · Startups
Communication Operating Models
A blueprint library for startup People leaders. Pick the edition that fits how your team actually works.
Most async → Most real-time
No single right way
How your team communicates depends on how distributed you are, how much your hours overlap, and how you like to work. This isn't one blueprint, it's a set of editions for different operating models, built on a shared foundation.
A shared spine (the parts that are true on every model) plus per-paradigm editions (which only swap the deltas). Maintain the spine once; the editions inherit it.
The six communication modes
The tools exist regardless of how sync-heavy you are
The "where should this go?" decision flow
The routing logic is universal; only the defaults shift
The scenario playbook
What "good" looks like per scenario is stable
Anti-patterns & the cross-tool workflow
Buried decisions and pointless meetings are bad everywhere
"Write decisions down somewhere findable"
The one rule no model escapes
The spectrum
Four operating models from most async to most real-time. Click to explore an edition.
Pick your model
Answer five questions about your org. Mostly one column → that's your edition. Split down the middle → we recommend the more-async option; it's easier to add sync than to claw it back.
1.How wide is your time-zone spread?
2.Daily real-time overlap between people?
3.Where do people work?
4.Cultural preference?
5.Should a decision ever be made live?
0 of 5 answered
Most async → Most real-time
Async-First edition
Where we sit: Async-First
We're remote-first across a handful of time zones with some overlap. Writing is our default operating mode because we're rarely all online at once, and because it's more inclusive. We escalate to live conversation only when the task truly calls for it, and we always leave an async path for anyone who can't be there.
Working across time zones
- ·Assume the other person is offline. Write self-contained messages: context, the ask, the deadline, and the link.
- ·No decision is made live without an async window. Share the proposal first, give a fair window for input, then confirm.
- ·Record meetings and broadcasts by default, someone is usually missing.
- ·Protect overlap hours for genuinely sync needs; don't burn them on status updates.
- ·Rotate meeting times fairly so the same region isn't always taking the 6am or 10pm call.
- ·Schedule messages for the recipient's working hours; never expect replies outside someone's hours.
Live: Google Meet
A meeting earns its place only when it produces a tangible outcome faster or better than async. Live time is scarce across time zones, guard it, and record it.
A meeting is worth it for
- ✓ 1:1s
- ✓ Critical or sensitive feedback
- ✓ Project kick-offs (after the prep doc)
- ✓ Customer-facing sessions
- ✓ Retros and demos
- ✓ Team face time and meeting new people
Skip it: do it async
- ✗ Brainstorms (canvas/doc + talk after)
- ✗ Status updates
- ✗ Repeating documented things
- ✗ Simple decisions
- ✗ Building reports
- Always have an agenda (a doc) and a clear desired outcome.
- Pre-read beats presenting, if you'd talk at people for the first 15 minutes, send a doc or Loom instead.
- End with owned actions (who, by when) and write the outcome into the wiki, linked in chat.
Broadcast
In this model: Live and recorded, with a written recap so nobody who was offline is left out.
Leadership comms cadence
A short, predictable written post from leadership each week does more for alignment than any meeting.
- · Headline: the one thing that matters most this week
- · Wins: progress and shout-outs
- · Priorities / focus: what we're pushing on and why
- · Metrics: a couple of numbers that show how we're doing
- · Asks / decisions needed: where leadership needs input or a call
- · Link to detail: back to the hub / roadmap, comments open
| Cadence | What | Channel |
|---|---|---|
| Weekly | Leadership update; events reminder | Written post in wiki + chat reminder |
| Weekly / bi-weekly | Project and team status | Written update, linked from hub |
| Monthly | Deep-dive; success stories | Loom or short doc, shared in chat |
| Bi-weekly / monthly | All-hands (updates, demos, Q&A) | Meet + recorded + written recap |
| Quarterly | OKR review; AMA | All-hands + wiki recap + AMA form |
Response-time expectations
| Channel | Reasonable expectation |
|---|---|
| Live Meet / Huddle | Real-time, during the call |
| Chat DM or @mention | Within the recipient's next working day |
| Chat channel (no mention) | When they get to it, no pressure |
| Doc comment / Loom | Within the author's stated window |
| Outside someone's working hours | No expectation until they're back online |
Rule of thumb: Urgency lives in sync tools; everything else is async and patient. If it's truly urgent, say so and use a sync channel during overlap hours.
The toolkit
Tool names change; the modes don't. Match the mode to the job, then use whichever tool you have for that mode.
| Mode | Typical tools | What it's for | Lifespan |
|---|---|---|---|
| Docs / Wiki | Slite, Notion, Confluence | Knowledge, decisions, processes, memos, anything that should outlive the conversation | Forever / for future hires |
| Chat | Slack | Coordination, quick questions, announcements, day-to-day chat | Days to a few weeks |
| Async video | Loom | Walkthroughs, demos, nuanced or personal messages where tone and visuals matter | As long as it's linked |
| Visual canvas | Miro, FigJam, Figma | Brainstorms, workshops, mapping, retros (Miro/FigJam); design and UI review (Figma) | Project to forever |
| Live | Google Meet, Huddles | High-bandwidth discussion that reaches an outcome faster than writing | The length of the call |
| Broadcast | Town hall / all-hands, AMA | Company-wide updates, vision, morale, sensitive news, open Q&A | Recorded + written recap |
Where should this go?
The decision flow: routing logic that works on every model.
- 1
Does this need an immediate answer? Yes → Chat (or a Huddle / Meet). No → keep going.
- 2
Can I explain it clearly in writing or a short recording? Chat for quick things; a doc for anything substantial; a Loom if tone or a screen-walkthrough helps.
- 3
Do people need time to reflect? Async gives everyone space to contribute thoughtfully.
- 4
Is this divergent / spatial thinking? (ideas, mapping, journeys) → a visual canvas.
- 5
Am I just sharing info or a status update? That's async. No meeting required.
- 6
Does the whole company need to hear it, with room for questions? → Broadcast (town hall / AMA), backed by a written recap.
- 7
Does it need to be found later? It lives in the wiki, wherever the conversation happened.
Scenario playbook
The toolkit tells you where; this tells you what good looks like in the moments people actually hesitate.
Written memo (wiki) + comment window
Propose a significant decision or change
A memo forces clear thinking and lets everyone engage on their own time. State the problem, options, your recommendation, and the decision needed. Share in chat, set a 48 to 72h comment window, then confirm the decision in the same doc.
Comments in the doc
Get structured feedback on a draft
Inline comments beat a meeting, quieter and offline voices weigh in equally. Be explicit: "Feedback by Thursday; I'll assimilate and share v2."
Loom (async video)
Explain something nuanced, visual, or where tone matters
A 3 to 5 min recording carries warmth and can walk through a screen in a way text can't. Pair it with a one-line TL;DR and the doc link.
Visual canvas (Miro / FigJam)
Brainstorm, workshop, map a journey or run a retro
Spatial, divergent thinking that a linear doc kills. Seed the board with structure first; use silent-write time so it's not just the loudest voices.
Figma
Review designs or give feedback on the actual UI
Comment directly on the frames so feedback is anchored to what it refers to. Keep decisions and rationale in the doc.
Town hall / all-hands
Share a company-wide update, vision, or sensitive news
High-trust moments deserve face time and live Q&A. Keep it tight, leave room for questions, record it, and post a written recap.
AMA
Open the floor to questions for leadership
Collect questions in writing beforehand, answer, and publish written answers so the whole team can refer back.
Written update
Give a routine status / progress update
Never a meeting. A short post every 1 to 2 weeks: what's done, blockers, next steps. Link it from the relevant hub.
Multi-channel sequence
Roll out a big change well
Town hall announcement → wiki doc + Loom walkthrough → Slack TL;DR + links → manager 1:1s → AMA. Repetition across mediums is what makes a message land.
Mode deep-dives
Shared guidance on each communication mode.
Docs / Wiki: the knowledge layer+Slite, Notion, Confluence…
- · Use for: decisions and reasoning, memos, processes and how-tos, project briefs, meeting notes and outcomes, team/role docs, anything a future hire would benefit from.
- · Write the decision, not just the discussion, what was decided, why, and who owns the next step.
- · One source of truth. If it's in the wiki, link to it rather than re-explaining. All comms link back to a central hub.
- · Make it findable with clear titles, structure, and tags. A doc nobody can find doesn't exist.
- · Keep it live. A stale doc is worse than no doc, update or archive.
- · Pre-read, then meet. Pre-reading plus shared questions can cut a 60-minute meeting to 20.
Chat: the coordination layer+Slack
- · Public by default. Channels over DMs, so knowledge stays shared and searchable. DMs hide information and create silos.
- · Right audience, right room. Before posting company-wide, ask: does everyone need this?
- · Reply in threads, always. Threads keep channels readable and let people catch up later.
- · Give context and state the ask: an answer by when, a decision, an FYI, or nothing. Say which, and link the doc.
- · Assume good intent, written text loses tone. Use reactions (✅ seen, 👀 on it) to close loops without noise.
- · Huddles are the lightweight sync option for quick "let's just talk for two minutes" moments.
Async video: Loom+Loom
- · Reach for it when: you're walking through a screen or demo, explaining the thinking behind a doc, delivering a message where warmth and tone matter, or onboarding someone to a process.
- · Keep it short (aim 2 to 5 min) and lead with the "so what" so people stay engaged.
- · Always pair with text: a one-line TL;DR plus the relevant doc link, so people can skim or skip.
- · Don't use it for simple things text handles, or anything needing live two-way discussion.
Visual collaboration: Miro, FigJam and Figma+Miro, FigJam, Figma
- · Use a canvas when thinking is spatial or divergent and a linear doc would flatten it.
- · Miro / FigJam: brainstorms, workshops, journey and system mapping, affinity clustering, retros, offsites.
- · Figma: product/UI design, design reviews, visual feedback on real screens.
- · Seed structure first. A blank canvas intimidates; pre-build frames, buckets, or a template.
- · Use silent-write time so it's not just the loudest voices.
- · Canvas is for thinking, the wiki is for deciding. Always capture the outcome and decision back in a doc.
- · Don't use a canvas for linear text, a simple decision, or a quick question.
Broadcast: town halls, all-hands and AMAs+Town hall / all-hands, AMA
- · The company-wide layer for alignment, trust, and morale. Structure beats sprawl.
- · Announcements: revenue/metrics and major news
- · People: hiring, new joiners, leavers, promotions, birthdays and anniversaries
- · Acknowledgements: kudos and shout-outs
- · Topic of the day: a short exec deep-dive on one theme
- · Q&A / AMA: ask leadership anything (collect questions in advance)
- · Demos: short, "so what"-first show-and-tell of recent work
Deltas matrix
Everything not listed here comes from the shared spine. This is the maintainer's map of what changes across editions.
| Dimension | Fully Async | Async-First | Hybrid | Sync-First |
|---|---|---|---|---|
| Default stance | Write / record everything | Async unless sync clearly wins | Sync in core hours, async otherwise | Real-time first; docs record it |
| Real-time ever mandatory? | No: always optional | Minimal (a few rituals) | Yes, in core hours | Yes: the primary mode |
| Meetings | Rare, optional, always recorded; never where decisions happen | Must pass "outcome faster than async"; recorded | Normal & expected, but need agenda + outcome; default-record | Frequent & expected; record only when someone's out |
| Response times | Working-hours / next-day; zero immediacy pressure | Next working day for DMs; patient otherwise | Same-day in core hours; async outside | Fast during work hours; chat near-real-time |
| Time zones | Built for zero overlap | Some overlap helpful; rotate meeting times | Assumes meaningful overlap / core hours | Single zone assumed |
| Decision-making | 100% async with comment windows | Async window before any live confirm | Can decide live, but document + short async window for absent voices | Decide live, then write up for the record |
| Broadcast cadence | Recorded + written; live attendance optional | Live + recorded + recap | Live (in-person + streamed) + recorded | In-person all-hands; recorded for the few who miss |
| Centre of gravity | The wiki | Wiki decides, chat coordinates | Split: meetings + chat for momentum, wiki for record | People + meetings; wiki is system of record |
| Visual collab | Async boards over a window | Async or live, both fine | Often live workshops + async bridges | Live whiteboarding (physical/digital) |
Cross-tool workflow
Anti-patterns to watch for
- Decisions that only exist in a chat thread or on a canvas, they vanish. Move them to the wiki.
- Meetings that could have been a doc or a Loom, especially status updates and one-way broadcasts.
- Important info buried in DMs, if others need it, it belongs in public or the wiki.
- A blank-canvas brainstorm with no structure, seed it first, or you get silence.
- Re-explaining documented things, link, don't retype.
- A town hall with no recap, someone always misses it.
- Decisions made live with no async window, they exclude everyone offline.
- Expecting instant chat replies, that's what sync channels are for.
Async-First
Quick reference
Forever? → Wiki · This week? → Chat · Show / explain? → Loom · Think it out together? → Canvas · Talk it out now? → Meet · Whole company? → Broadcast.
- · Before a meeting: could this be a doc, a Loom, or a canvas + comments?
- · Before posting company-wide: does everyone need this, or is it a thread / DM / link?
- · Before deciding live: has everyone offline had an async window to weigh in?
- · After every decision: is it written down somewhere findable?
More open resources
Other free templates and diagnostics from Open Org.
Culture Heatmap
Score 29 culture statements across nine areas to see where your organisation is thriving.
Transparency Charter Template
Document why transparency matters, what it means, and how and when you share openly.
Values Evolution Blueprint
Open Org's 7-step approach to values design, from survey to workshops and operationalisation.
Transformation Playbook
Eight-stage blueprint for delivering transformative change with alignment and engagement.
Compensation Philosophy Template
Design and document how your organisation pays people, with handbook examples and checklists.
Principles adapted from established distributed-team handbooks: Open Org, PostHog, GitLab, HelloBetter, Airalo, Mostly AI, Cal.com and Sourcegraph.
Want help applying this in your org?
Join Open Org Workspace