A leader could list twenty-three things wrong with her organization and could not say which one was the actual problem.
Two pages of symptoms and no cause
The leader who called us had run out of levers. For two years she had worked the most obvious problems in her organization and watched each fix produce the same lackluster result. When she finally sat down to write out what was actually wrong, she filled two pages of a notebook and still could not get to a cause.
She had the notebook on the conference table when we met the following week, and she turned it around so we could read it. Twenty-three bullet points in her handwriting. Delivery slipping. Capacity invisible. Three frameworks in five years. A sprawling tech stack. Her best people leaving. Decisions made on stale data. Cross-team handoffs dropped. The list went on. Every item was real, she told us. She could spend a year on any one of them, and on some she already had. What she could not tell us was which one was the actual problem.
Why every fix got absorbed
Her list was familiar because it is what an under-designed work system feels like from the inside. Leaders in her position usually go after the pain one symptom at a time: outsourcing, another tool, new hires, headcount cuts, the next framework, a new department. Each can produce real gains on its own. How much depends on the system it lands in.
A great solution inside a broken system yields a great solution that the system neutralizes. The investments do not disappear. They become overhead, in the form of more burden on the people inside, more red tape, and more frustration. Three frameworks in five years sat on her list as a symptom, not as a record of fixes.
None of her twenty-three items felt like the core problem because the architecture of the work system itself was not on the list. She had been describing what the system produced, not the system.
Not what it was, but where it happened
So we asked her to read the list again with a different question. Instead of treating each item as its own problem, where in the flow of work did it happen? As work came into the organization? While the organization decided what to do? While teams tried to deliver? While teams tried to coordinate with each other? When the organization tried to see what it had done?
She went quiet and read down the list. After a minute she picked up her pen and started marking items. Some were about work coming in. A few were about deciding what mattered. A group was about teams getting in each other's way. Another was about what she could and could not see. She set the pen down. The symptoms were not random. They clustered by where in the flow they happened.
She had made the first move of the diagnostic without knowing it. Every work management system we have walked into follows the same basic flow, and that flow breaks into steps that should be happening for every piece of work. When all of them happen well, work flows. When any one of them breaks, the effects ripple through the rest.
- SurfaceWhen work comes in
- ScopeWhen work gets understood
- RankWhen deciding what matters
- CascadeWhen work gets broken down
- FlowWhen work moves to delivery
- BridgeWhen work crosses teams
- SignalWhen the system reports back

Seven names on a fresh page
We walked her through those steps in plain language. Work comes in. It gets understood well enough that the organization knows what it is actually being asked to do. The organization decides whether it matters enough to do, and in what order relative to everything else. It gets broken into pieces small enough for teams to carry. It moves through the processes that carry it toward delivery. It crosses whatever teams and groups it needs when no single team can deliver it alone. And it produces information about itself, in time for the organization to act on what that information says.
We had named each step as a component of the work system so it could be examined, diagnosed, and redesigned by name. We wrote the seven names on a fresh page of her notebook. Surface is how work enters the organization. Scope is how work gets understood before commitments are made. Rank is how the organization decides what matters most. Cascade is how large work gets broken down into pieces a team can carry. Flow is how work moves through the delivery process. Bridge is how work crosses team boundaries when no single team can deliver it alone. Signal is how the organization sees itself, the reporting that supports decisions at every level. Each one has a healthy state and characteristic ways of failing.
We went through all seven with her, with examples of good and broken from other organizations, until she could describe missing structure instead of symptoms. Then she annotated her own list. Items about work coming in became Surface. Items about competing priorities became Rank. Items about teams stepping on each other became Bridge. Several things she had struggled to put into words landed in Cascade and Signal. A few items moved as she talked, because the new language drew distinctions her original bullets had not.
Weakest component first
Naming the parts also exposed how they fail together. When one component breaks, the effect transfers to the next. Intake that floods in through invisible channels makes prioritization impossible. Priorities that are not really priorities make focus impossible. Without focus, coordination across teams fails. Failed coordination makes reporting unreliable. And unreliable reporting hides the system from the people who would otherwise be able to correct it.
That is why any system is only as strong as its weakest component, and why the whole system has to be examined before anything is fixed, with the weakest components addressed first. Working the twenty-three items one at a time was the approach that had already failed.
She sat back and looked at the annotated page. Symptoms she had been managing in isolation were now distributed across seven named components, with patterns visible that had not been there an hour earlier. The next step was the diagnostic that would show which of her components were weakest and in what order to address them. We have watched leaders reach the same recognition across industries and at every scale.
-
Where it broke Intake floods in unseen Surface
-
Where it broke Prioritization fails Rank
-
Where it broke Focus disappears Across every team
-
Where it broke Coordination breaks Bridge
-
Where it broke Reporting goes unreliable Signal
-
Where it broke The system stays hidden The whole system
A list of problems cannot be redesigned. A system with named parts can.
Share With Your Team
Choose who it is for. You send it yourself from your own email; Agileon never writes to your colleagues.


