Documentation First vs Tacit Coordination
Usually a scale-and-memory decision.
- Really about
- How much of the system of work should survive beyond people's heads and meetings.
- Not actually about
- Whether documentation is virtuous in itself.
- Why it feels hard
- Tacit coordination is fast; documentation is slower but scales and survives.
The decision
Should teams rely primarily on written artifacts or on synchronous or tacit coordination?
Usually a scale-and-memory decision.
Default stance
Where to start before any evidence arrives.
Document enduring decisions and critical operations; keep ephemeral coordination lightweight.
Options on the table
Two poles of the trade-off
Neither is the right answer by default. Each option's conditions, strengths, costs, hidden costs, and failure modes when misused are laid out in parallel so you can read across facets.
Option A
Documentation First
Best when
Conditions where this option is a natural fit.
- team count is high
- turnover or onboarding matters
- decisions have lasting impact
Real-world fits
Concrete environments where this option has worked.
- architecture decisions
- runbooks and critical operational procedures
- cross-team product or platform contracts
Strengths
What this option does well on its own terms.
- durability
- better onboarding
- reduced memory dependence
Costs
What you accept up front to get those strengths.
- slower upfront effort
- risk of stale docs
Hidden costs
Costs that surface later than expected — the main thing novices miss.
- documentation can become ritual rather than useful memory
Failure modes when misused
How this option breaks when applied to the wrong context.
- Creates artifact theater with weak real alignment.
Option B
Tacit Coordination
Best when
Conditions where this option is a natural fit.
- team is small
- work is fast-moving and local
- high-bandwidth communication is easy
Real-world fits
Concrete environments where this option has worked.
- small colocated teams
- short-lived decisions
- rapid problem-solving loops where durability is not yet needed
Strengths
What this option does well on its own terms.
- speed
- lower artifact overhead
- high-bandwidth nuance
Costs
What you accept up front to get those strengths.
- fragility under scale or absence
- memory dependence
Hidden costs
Costs that surface later than expected — the main thing novices miss.
- knowledge lives in people until the cost becomes visible
Failure modes when misused
How this option breaks when applied to the wrong context.
- Leads to hero trap and ownership drift.
Cost, time, and reversibility
Who pays, how it ages, and what undoing it costs
Trade-offs are rarely zero-sum and rarely static. Someone pays, the payoff curve shifts with the horizon, and the decision has an undo cost.
Option A · Documentation First
Who absorbs the cost
- Authors and maintainers
Option B · Tacit Coordination
Who absorbs the cost
- Future joiners
- On-call responders
- Teams depending on missing memory
Option A · Documentation First
Wins as team scale and memory needs increase.
Option B · Tacit Coordination
Wins only while coordination remains local and short-lived.
What undoing costs
Easy-moderate
What should force a re-look
Trigger conditions that mean the answer may have changed.
- Team scales
- Onboarding pain grows
- Critical knowledge concentrates
How to decide
The work you still have to do
The reference can frame the trade-off; only you can weight the factors against your context.
Questions to ask
Open these in the room. Answering them is most of the decision.
- Will someone need this decision or process later?
- What happens if the people currently coordinating disappear for two weeks?
- Is this worth writing down, or only worth resolving quickly?
- Do we trust our docs enough to act on them?
Key factors
The variables that actually move the answer.
- Team size
- Decision longevity
- Turnover risk
- Coordination speed
Evidence needed
What to gather before committing. Not after.
- Onboarding pain signals
- Decision retrieval pain
- Runbook/document trust assessment
Signals from the ground
What's usually pushing the call, and what should
On the left, pressures to recognize and discount. On the right, signals that genuinely point toward one option or the other.
What's usually pushing the call
Pressures to recognize and discount.
Common bad reasons
Reasoning that feels convincing in the moment but doesn't hold up.
- Docs slow us down
- Everything should be written down
Anti-patterns
Shapes of reasoning to recognize and set aside.
- Writing documents nobody uses
- Keeping critical operational knowledge only in chats and memory
What should push the call
Concrete signals that genuinely point to one pole.
For · Documentation First
Observations that genuinely point to Option A.
- Cross-team work
- Lasting decision impact
For · Tacit Coordination
Observations that genuinely point to Option B.
- Small tight-loop teams
- Low-longevity decisions
AI impact
How AI bends this decision
Where AI accelerates the call, where it introduces new distortions, and anything else worth knowing.
AI can help with
Where AI genuinely reduces the cost of making the call.
- AI can summarize decisions and improve findability of useful docs.
AI can make worse
Distortions AI introduces that didn't exist before.
- AI can generate lots of documentation quickly, increasing the risk of stale but polished memory.
Relationships
Connected decisions
Nearby decisions this is sometimes confused with, adjacent decisions that are often entangled with this one, related failure modes, red flags, and playbooks to reach for.
Easy to confuse with
Nearby decisions and how this one differs.
-
That decision is about real-time vs async collaboration. This one is about whether written artifacts or tacit context is the durable carrier of org memory.
-
That decision is about who carries accountability. This one is about which artifact carries organizational memory.
- Adjacent concept A wiki-tooling choice
Tooling is the substrate. This decision is whether writing-down-first is the coordination mode, regardless of tool.