A company-wide planning session produced seventy-three shared goals for one quarter, and nobody could say whether that was too many.
None of the Ideas on the Wall Matched the Plan
The leadership team of a healthcare technology company set aside a full day before its annual all-company goal-setting event. The agenda looked simple: confirm the year's goals and break them into quarterly goals the teams could plan against the next morning. Before the session, two of the most senior leaders had each told us, separately, that the organization already had three annual goals in mind. Neither shared the details. We expected to spend half an hour confirming them.
Instead of asking for an alignment vote, we asked the room a different question: what are the most important things this company needs to accomplish over the next year? Within five minutes the whiteboard held more than twenty ideas, in different handwriting and from different vantage points. We compared them with the three annual goals the two leaders had described. None matched.
The people responsible for the company's direction were not working from a shared picture of it, and nothing in the planning process had ever forced the difference into the open.
An Hour of Debate Produced One Quarterly Goal
The two leaders wrote their three annual goals on a clean section of the board, and we asked the team to decompose them into quarterly outcomes the company could realistically pursue. Those outcomes were meant to go into the all-company session the next morning.
The discussion lost momentum almost immediately. Leaders reopened the annual goals, debated wording, and questioned scope. An hour later the room had produced one quarterly goal, possibly two, and the event was less than a day away.
We made the call to stop decomposing from the top. If the leadership team could not break the goals down in time, the organization would build the quarter from the bottom up. The next morning a senior leader introduced the three annual goals to the whole company, and we asked one question: to achieve these three, what does the company need to accomplish this quarter?
Ideas poured in from every function and level. Once the notes were clustered, a pattern appeared. The same commitment often showed up in four or five functions under different wording, because it was the same underlying work seen from different seats. We synthesized the clusters into shared goals: pieces of quarterly work that crossed functions and needed coordination to deliver. There were seventy-three of them.
-
Day before, first minutes
The reveal 20+ ideas, none matched Not one matched the three annual goals two leaders had described.
-
Day before, next hour
Where it broke One goal, possibly two Top-down decomposition stalled in debate over wording and scope.
-
Next morning
What changed The company is asked What must we accomplish this quarter to reach the three goals?
-
Same session
73 shared goals Clustered from every function and level of the organization.
Nobody Knew What Too Many Looked Like
When we brought the number back to the leadership team, no one said seventy-three was too many. No one could. The company had never tracked how much work it completed in a quarter. There was no throughput history and no prior count. Seventy-three might be reasonable. It might be three times what the organization could absorb.
That made the order of the work decisive, so we asked the obvious question: if you cannot finish all seventy-three, and you probably cannot, how will you decide what comes first? The answer was mostly murmuring. Each of these leaders had set priorities for years. As a group, they had never built a way to do it. Work had been managed through discussion and consensus, with each function's authority tending to override any central view. That had been enough while the company was smaller. It no longer scaled, and without a common method, priorities shifted depending on who happened to be in the room.

Every Ranking Factor Came From an Objection
We started with the simplest exercise available: place each goal on a value and effort grid and calculate a return score. The list sorted cleanly. Then the objections began, and each one made the method better.
One leader pointed out that several lower-ranked goals had hard deadlines, and two were commitments the company had already made. They were not the highest return, but missing them would cost revenue. The room defined urgency together, scored it, and the ranking changed.
Another noticed that some goals could not start until others finished. One goal on the list was blocked until a different goal was finished. Dependencies, we agreed, set sequence regardless of score, because work that unlocks other work has to go first. The list shifted again.
A third leader observed that some goals were nearly finished. Completing something eighty or ninety percent done could be worth more than starting something new, given how little effort remained. We added a weighting for completion, and the list moved a final time.
It took four hours. At the end the leadership team had something it had never had: a single prioritized list of shared work, and a framework of six factors (value, effort, urgency, dependencies, percent complete, and pre-existing commitments) built by the people accountable for following it. Every factor came from someone in the room.
-
Value against effort A return score from a simple grid.
-
What changed Add urgency Hard deadlines and commitments already made.
-
What changed Add dependencies Work that unlocks other work goes first.
-
What changed Add percent complete Nearly finished work is weighted up.
-
One ranked list Value, effort, urgency, dependencies, percent complete, prior commitments.
The List Became a Way to Learn
Ranking was only half of what the seventy-three needed. When we asked who would review a new goal entering the shared backlog and confirm it was complete enough to act on, the leadership team had no answer. Intake had been treated as everyone's responsibility, which in practice made it no one's. Leaders volunteered as named reviewers for each category of work, one or two per category, and agreed that a request should be reviewed within two to four business days or be escalated. As the goals moved through review, some advanced, some went back for clarification, and some were consolidated where reviewers found overlap.
At the end of the quarter, the leadership team reviewed what had been delivered against what the framework predicted. A single chart compared, for each completed goal, the value delivered with the effort invested. Several of the highest-ranked goals showed exactly the shape the method was designed to reward: moderate effort, high value. Others had taken far more effort than expected, and a few had delivered less value than anticipated.
That was the real change. The framework was no longer only a way to sort a list. It had become a way to learn whether the sorting was right. For the first time, the leadership team knew what a quarter of its work was worth, and the next quarter's list could start from a baseline instead of opinion.
A priority list is only as strong as the method behind it, and the method holds when the people who must follow it are the ones who built it.
Share With Your Team
Choose who it is for. You send it yourself from your own email; Agileon never writes to your colleagues.


