Most organizational failures look like people problems. Dig deeper and you find missing information: expectations that were never written down, queues no one could see, decisions made without telling the people they affected.
Most daily disagreements aren't about who's right. They're about what wasn't communicated.
Research by Pondy (1967) and others describes conflict as a sequence: teams diverge in their goals, communication across boundaries gets worse, role ambiguity increases, stress compounds. By the time the conflict is visible, it's been building for months.
The triggers are mundane. A decision that affected a team's work without informing them. A handoff where "ready" was never defined. A priority dispute that had no forum.
As organizations grow, these patterns get worse. More handoffs mean more ambiguity. More teams mean more decisions made in one place that affect work happening elsewhere. What worked at 20 people creates cascading failures at 200.
Coordination works differently at different sizes:
0–15 people: Everyone talks. Decisions are made in rooms. Problems get solved in real time. This works until it doesn't.
15–100 people: The founder can't be in every room. Coordination starts passing through middle managers and leads. What everyone knew informally starts diverging from what the organization actually does.
100–500 people: Role boundaries blur. Teams develop different assumptions about how work should happen. Decisions sit waiting for the one person who knows the answer.
500+ people: Some organizations build formal coordination infrastructure: decision logs, response-time norms, documented handoff criteria. Others try adding people to the coordination problem, which usually multiplies it.
When a new leader arrives, the geometry of the system changes. Fault lines that were dormant become active. This isn't about the leader's capability. It's that the previous equilibrium was held in place by relationships and assumptions that a new person disrupts.
When you can see where work is piling up, try these in order. Apply each recursively. Stop when what remains is genuinely novel work that requires human judgment.
End-to-end delivery time for your most common work type: the elapsed wall-clock from "someone asked for this" to "they have it." Not velocity. Not story points. That number and its trend is the most direct signal of coordination health I know.
The coordination mode that works at one scale often fails at the next. At founding, conversation is fast and flexible. As you scale, conversation becomes a bottleneck. It creates dependency on specific people. It leaves no record.
The fix is written infrastructure: visible systems, documented criteria, decision logs. But building that infrastructure too early creates bureaucracy. Building it too late means you're already in crisis. The timing is the hard part, and there's no generic answer.
The organizations that navigate this are rarely the ones with better people. They're the ones that recognized the shift and rebuilt before the cost became unbearable.
More people adds coordination overhead without fixing the underlying ambiguity. More meetings substitutes cost for clarity. Before adding anything, ask what information is missing and what channel should carry it.
The Φ-Framework diagnoses where coordination breaks down in a specific organization. It maps how work moves through four channel types: visible systems, written agreements, habituated patterns, and real-time conversation. For each, it asks whether the channel is strong, weak, absent, or doing work it shouldn't.
The reports apply this lens to real companies. They're diagnostic, not advisory.
The framework draws on organizational information-processing theory (Galbraith, 1974), interdependence theory (Thompson, 1967), and the exploration/exploitation tradeoff (March, 1991). The operational version has four coordination channels and three diagnostic moves. The reports are how we practice — not a service we sell.