Status meetings multiply
People need synchronous updates because current state cannot be reconstructed reliably from the systems, artifacts, or interfaces around the work.
Why are we in so many meetings?
Meetings may be doing coordination work the system itself is not doing: reconstructing state, locating authority, resolving dependencies, surfacing constraints, or establishing ownership.
A signal is evidence to investigate, not a diagnosis by itself.
Short Answer
Meetings may be doing coordination work the system itself is not doing: reconstructing state, locating authority, resolving dependencies, surfacing constraints, or establishing ownership.
Meetings may be doing coordination work the system itself is not doing: reconstructing state, locating authority, resolving dependencies, surfacing constraints, or establishing ownership.
What You're Seeing
The pattern is visible in the work.
The same people attend everything
A small group becomes necessary because they carry context, authority, or dependency knowledge that the broader system does not make available.
Decisions wait for the meeting
Work pauses until the right authority is present, even when the decision itself is routine or local to the work.
Meetings create more meetings
A conversation exposes another dependency, missing owner, unresolved constraint, or stakeholder who now needs to be brought into the loop.
Attendance feels defensive
People join because being absent means losing state, influence, context, or awareness of decisions that may affect their work.
Nothing feels safe to decide asynchronously
Unclear authority, incomplete state, or hidden dependencies make synchronous consensus feel safer than independent action.
Why It Matters to the Business
Meetings are expensive. Coordination latency is more expensive.
When meetings compensate for missing state, unclear authority, or hidden dependencies, the cost is larger than calendar time. Decisions wait for synchronous coordination, expensive people become routing infrastructure, and work slows while the organization reconstructs what it needs to proceed.
Slower decisions
Work waits for the right people to assemble before routine decisions can move.
Lost capacity
High-value people spend time reconstructing context instead of producing outcomes.
Execution latency
Dependencies and constraints are discovered in meetings rather than early enough to plan around them.
Common Interpretation
“We have a meeting problem.”
The usual remedies target the visible behavior: reduce meetings, require agendas, shorten default durations, declare no-meeting days, train managers, or move updates into Slack. Those practices can improve bad meeting hygiene. But if meetings are performing missing coordination functions, removing them can remove the compensation without fixing the condition that made the compensation necessary.
Structural Interpretation
Follow the symptom into the coordination system.
State
People cannot reconstruct what is happening. Meetings become the place where current state, prior decisions, changing conditions, and context are assembled into a shared picture.
Authority
People do not know who can decide. The meeting assembles enough authority to make a decision legitimate—or creates consensus because legitimate authority is unclear.
Constraints
Dependencies become visible too late. Meetings are where teams discover that another actor, resource, approval, system, or condition is preventing progress.
Participation
The real system crosses formal boundaries. Recurring cross-functional meetings may be reconstructing a coordination system that the formal organization does not represent.
Failure
Problems need broad human containment. Issues routinely pull additional actors into synchronous coordination because failure does not remain bounded where it originates.
Adaptation
The meeting identifies problems but the system does not change. The same discussion recurs because observation is not producing durable structural change.
Evidence to Look For
What would support—or weaken—the structural interpretation?
The signal alone is not enough. Look for evidence that distinguishes a structural mechanism from other plausible explanations.
- SupportsMeeting time is repeatedly spent establishing what happened, what changed, who knows what, or which version is current.
- SupportsDecisions routinely wait for particular leaders or require broad consensus because decision rights are unclear.
- SupportsTeams repeatedly discover blockers, approvals, or downstream effects only when everyone is together.
- SupportsSimilar status, escalation, dependency, or ownership conversations recur without changing the underlying operating conditions.
- WeakensThe work requires genuine collaborative synthesis, negotiation, creative exploration, or high-bandwidth judgment that is difficult to reproduce asynchronously.
- WeakensParticipants arrive informed, decision rights are explicit, dependencies are known, and the meeting is primarily used to make progress rather than reconstruct context.
Relevant Structural Characteristics
Where to look structurally.
State TraceabilityDecision AuthorityConstraint VisibilityFailure ContainmentAdaptation Capacity
The Question Underneath the Question
Move from symptom to mechanism.
Ask insteadWhat state, authority, dependency, or coordination are people reconstructing through meetings because the system does not provide it?
Related Signals
The same structural conditions can surface elsewhere.
What is this signal costing the outcome?
2ndSys helps make the coordination system producing the signal visible so you can see what is consuming capability and where attention belongs.