Concept
Coherence Maintenance
The ongoing work required to keep a system governable: enough agreement about who decides, what happened, and what must change next for learning to remain possible.
The ongoing work required to keep a system governable: enough agreement about who decides, what happened, and what must change next for learning to remain possible. Coherence maintenance becomes expensive as independently evolving boundaries multiply. Systems sometimes pay for it through clear ownership and timely feedback; they sometimes pay through coordination substitutes that preserve throughput while thinning corrective capacity.
Recognition signals
- disagreement persists about who decides and what happened
- independently evolving boundaries multiply governance cost
- coordination substitutes preserve throughput while thinning correction
- hallway conversations carry risk signals formal structures never capture in time
- governance meetings multiply while no redesign-capable owner holds the full picture
Questions to ask
- Is the system paying for coherence through ownership or through substitutes?
- Which substitute coordination costs are growing faster than clear ownership?
- Can anyone here redesign the structure, not only synchronize around it?
Counterbalances
- invest in timely feedback paths before adding approval layers
- name ownership at redesign-capable boundaries explicitly
- treat coordination machinery as debt when it replaces consequence return
Trajectory
Early signals
- small disagreements about facts and next actions appear across teams
- independently owned services begin drifting on different release calendars
Intensification
- approvals and reporting layers multiply to preserve a shared picture
- throughput stays visible while corrective capacity thins
Failure modes
- organizations synchronize activity without returning consequence to redesign
- coherence maintenance cost dominates engineering or operational capacity
Restoration paths
- pay for coherence through ownership and feedback rather than substitutes alone
- shrink the number of boundaries that must agree before local correction
Manifestations
software
- architecture board meetings replace absent team-level ownership of integration risk
organizations
- hospitals run daily huddles while committees debate last quarter's staffing metrics
leadership
- executives require weekly cross-functional syncs because no single owner holds end-to-end outcome
politics
- interagency task forces form after failures because statutory authority remains fragmented
