Why are we in so many meetings?
More communication may be compensating for missing state, unclear authority, invisible dependencies, or uncertainty about ownership.
Follow this signalRecurring meetings, escalating decisions, cross-functional heroics, rework, stalled change, and overloaded leaders are often treated as people problems. They may be signals of the coordination system underneath the work.
Start with what you can see. Follow the signal to the system producing it.
These are ordinary-language symptoms leaders and teams already recognize. Each can be followed toward a more precise structural question.
More communication may be compensating for missing state, unclear authority, invisible dependencies, or uncertainty about ownership.
Follow this signalEscalation may indicate that decision authority is absent, ambiguous, too constrained, or separated from the actors closest to the work.
Follow this signalExceptional effort may be compensating for boundaries, dependencies, or participation that do not coordinate cleanly.
Follow this signalThe handoff may not be the problem. The relevant coordination system may cross the formal teams and expose constraints the org chart hides.
Follow this signalThe organization may possess the information without producing traceable state where the actors who need it can reconstruct what is happening.
Follow this signalResponsibility can be assigned to actors who do not control the decisions, dependencies, resources, or constraints required to produce the outcome.
Follow this signalFailure may be escaping the part of the system where it originates and propagating across dependencies, teams, leaders, or customers.
Follow this signalThe organization may observe failure repeatedly without changing the structural conditions that reproduce it.
Follow this signalGrowth can increase load on coordination structures that previously survived through slack, proximity, executive attention, or informal workarounds.
Follow this signalAdding machine capability does not automatically resolve unclear authority, weak state, hidden constraints, or poorly coordinated participation.
Follow this signalCombining structures, systems, and reporting lines does not itself create the coordination required for a shared outcome.
Follow this signalWhen leaders continually reconstruct state, resolve dependencies, authorize exceptions, and contain failures, the system may be outsourcing coordination to executive attention.
Follow this signal2ndSys examines five structural characteristics of a coordination system. They are not symptom categories and they are not a scorecard. They provide a governed way to investigate what may be producing the signal.
Who can legitimately make the decisions required by the work?
Can actors reconstruct what is happening, what happened, and why?
Can the conditions preventing realization be seen?
Can failure remain bounded rather than propagating through the system?
Can observation produce meaningful change?
The structural question becomes useful inside the boundary of the actors and dependencies responsible for the outcome.
Once we know which system is producing the work, 2ndSys can show what is happening inside it and compare that with what you need the system to do.
Start with one system that matters. If the evidence points beyond it, follow the work into the related systems around it.
Start with the system producing the symptom—not another attempt to make people compensate for it.