A leadership team holds a complete, accurate list of its problems and has no way to act on it.
Six categories of evidence on one screen
The diagnosis had produced a great deal of material: survey results, interview transcripts, workshop outputs, raw observations, impact statements. We had organized it into six categories, strategy, visualization, portfolio prioritization, tools, customer, and reporting, and walked the internal change team through each one in turn. We wanted them, not us, to name the themes their plan would be built on.
The material was sobering in its consistency. In a self-assessment, half of the participants from the project management office scored the alignment of their work to strategic intent at five or below on a ten-point scale. Not one scored it a ten. Visibility clustered in the same middle range. People felt spread too thin across competing projects. Reports were compiled by hand from several sources and stayed subjective. Early in the review, one of the team's leaders said they had been seeing these as delivery problems, and that they were clearly problems with the connection between strategy and execution. It was the team's first glimpse that symptoms often show up far from their causes.
Eighty-three, and a sponsor who said it was too many
When the last category closed, one of the team let out a heavy sigh and asked how many findings they were looking at across all six. We had counted. Eighty-three discrete findings.
The executive sponsor's face soured. Her reaction was immediate and reasonable: that was far too many to absorb at one time. She was right. No leadership team can responsibly build an eighty-three-item plan. Each finding was accurate, and each one could justify its own project, its own owner, and its own status report. Taken one at a time, they would have consumed the organization's attention for years and left the conditions that produced them untouched.
We told the team they were not going to design a plan that addressed eighty-three findings. They were going to identify the underlying conditions that produced them, and design the strategy to change those conditions. One of the leaders leaned forward and asked us to show them how that worked.

One question asked five times
We had already grouped the eighty-three observations into clusters. For each cluster, the team would answer one question: what is the root cause that produces it?
The first cluster held fragmented priorities, visibility gaps, rapidly changing direction, and inconsistent executive sponsorship. Four problems that looked unrelated on a slide. One team member answered first. Work was entering the organization through too many doors: business councils, strategic plans, annual planning, partner requests, leader asks, face-to-face conversations. With no single front door, there was no single place to set priorities or check alignment. Four symptoms collapsed into one condition: fragmented intake.
The team worked through the rest the same way. Uneven prioritization and localized decisions became the absence of a shared method for deciding what matters, where the loudest voice won. Tool confusion and constant context switching became inconsistent delivery practices that made it impossible to predict how long anything would take. Informal, team-bound lessons became unstructured release practices that limited learning. And the reporting findings became the plainest statement of all: leadership was making decisions on whatever someone had pulled together by hand the day before the meeting.
- Fragmented priorities
- Visibility gaps
- Rapidly changing direction
- Uneven executive sponsorship
- Fragmented intakeWork enters through too many doors
- No shared way to prioritizeEach unit ranks inside its own walls
- Inconsistent deliveryNo way to predict how long work takes
- Unstructured releasesLessons stay inside the team that learned them
- Decisions without dataReports assembled by hand before each meeting
From themes to things to build
When the fifth theme went up, one of the leaders studied the screen for a long moment. They said it was the first time they had seen the organization's problems arranged in a way they could build a plan of attack against.
The team and Agileon spent the rest of that day and most of the next turning each theme into a desired outcome with concrete activities across people, process, and product. Fragmented intake became an outcome built around a single, visible way for work to enter, a baseline of the current state, and a method for turning requests into resource-aligned work. The prioritization theme became a standing forum with defined participants, structure, tooling, and measures of success. Delivery, release, and reporting each became an outcome of their own. As each theme was written, we noted which part of the work system it touched, so the plan would address the system rather than five unrelated projects.
Then we revealed a one-page synthesis. The eighty-three findings were all still there. They had become the evidence base for a strategy rather than a backlog of complaints, each one traceable to the theme designed to resolve it.
| Condition | Where it sits |
|---|---|
| Fragmented intake | Surface, Scope |
| No shared way to prioritize | Rank |
| Inconsistent delivery | Cascade, Flow |
| Unstructured releases | Flow, Bridge |
| Decisions without data | Signal |
Start where the work enters
The next question was whether to roll all five themes out at once. The answer was one pilot first, and choosing it is a story of its own. The sponsor asked where to begin. Where the work enters, we said.
The method outlasted the plan. After the pilot closed, when the team running the system found new signals of drift, one of its members proposed handling each new finding the way they had handled the original eighty-three: not closing gaps one at a time, but looking for the underlying condition. The number had stopped being a burden. It had become the way the organization thought about its own problems.
A list of findings is evidence. It becomes a plan only when someone asks what keeps producing it.
Share With Your Team
Choose who it is for. You send it yourself from your own email; Agileon never writes to your colleagues.


