What goes wrong when you ignore that shared mental models enable coordination?

The most common reason fails: Assuming that shared mental models form automatically from working together. They do not. Proximity creates familiarity, not alignment. Two engineers who have worked side by side for three years may have fundamentally different models of how the deployment pipeline works, what 'ready for review' means, or who has authority to approve an architecture change. The models diverge silently because the team never makes them explicit. The divergence only becomes visible during a crisis, a disagreement, or a handoff failure — exactly when the cost of discovering the misalignment is highest. Shared mental models must be built deliberately, through externalization, discussion, and periodic re-alignment.

The fix: Select a recurring team process — a deployment, a sprint planning, a design review, or an incident response. Interview or survey three team members independently, asking each to describe: (1) the steps in the process, in order; (2) who is responsible for each step; (3) what triggers the process to begin; and (4) what criteria determine that the process is complete. Compare the three descriptions. Where they align, you have a shared mental model. Where they diverge, you have a coordination cost that the team is paying every time the process runs — through negotiation, confusion, rework, or conflict. Document the merged model and share it with the team. Ask: 'Is this how we actually work? Is this how we should work?'

The underlying principle is straightforward: When team members share the same understanding of the situation they coordinate naturally — without constant explicit communication.