Prioritization Is a System, Not a Meeting

In a healthcare technology company, every function ranked its own shared goals while almost every goal depended on the same few functions. A standing cross-functional council turned hallway surprises into explicit trade-offs.

03 RANK
The condition

One leader's top-priority goal was not even in the top twenty of the team it could not be delivered without.

The Backlog Kept Growing From Every Direction

After a company-wide goal-setting event, a healthcare technology company had something it had never had before: one shared backlog of goals that crossed functions. Then the backlog kept growing. Product and engineering added a goal whenever they wanted to enhance an existing product. Customer-facing teams added goals whenever clients gave them feedback. Each new goal recorded the function that owned it and the other functions that would need to support it.

What no one weighed when adding a goal was that they could not do the work alone. When we built a dashboard showing the owners and supporters of every shared goal, the pattern was hard to miss. Four functions were involved in almost every one. They depended on each other constantly, and they had no consistent meeting or method for putting the work in an agreed order.

Not Even in Her Top Twenty

The cost surfaced in a hallway. A senior executive stopped a functional leader who had just added a data restructuring goal and moved it into his group's highest-priority slot. He confirmed it without hesitation: from where he sat, it was the most important thing the company needed to be doing.

The leader of the client team happened to be passing, and the executive asked whether the new goal was on her radar. She opened her backlog on her phone and scrolled. It was not in her top ten. She kept scrolling. It was not in her top twenty. Could his group deliver it without her? No. They would need two of her people for at least a month. He agreed. He could not finish the work without her team's product knowledge.

Nothing about that exchange was unusual, which was the point. Each function ranked its own work independently, while most goals could only be achieved across functions. When one group pulled in work to fill its own capacity, it created context switching for every group it depended on, and the surprise request for support pulled people away from commitments they had already made.

A Council With a Purpose and Boundaries

The decision was to bring the leaders of the dependent functions together on a regular cadence to agree one priority order, with policies to control the flow of new work into it. Six leaders became members of a new cross-functional prioritization council.

Before ranking anything, the council settled two questions. The first was roles: a facilitator to keep the council running well, voting members to represent value, business outcomes, and delivery realities, and a tie-breaker to resolve conflicts the votes could not. One senior executive volunteered to facilitate and another to break ties. The second was purpose. The council decides the order of shared goals and makes the trade-offs explicit, weighing value, effort, urgency, dependencies, and prior commitments. It produces a prioritized shared backlog, the reasoning behind each trade-off, and clear direction to teams on what to do in what order. It does not define the goals, and it does not run delivery.

Any request to move a goal up had to arrive with a five-point narrative: what it was, why it mattered, how success would be measured, the expected return, and when it needed to be done.

Two colleagues reviewing a list together on a laptop by an office window.

What Gets Bumped?

The first real test was the data restructuring goal. Its sponsor read through the narrative and asked for it to move into the top ten. The tie-breaker pointed out that, halfway through the year, a place in the top ten meant something else had to move down. The facilitator asked which functions the work would need. The sponsor's best estimate was a month or two of dedicated time from the client team, plus analytics support for the back-end work.

Then the facilitator asked the question the council existed to ask. If this goes into the top ten, what has to be deprioritized to free up the client team? The client team's leader was already scrolling the backlog. Client renewal work would be bumped, she said. The same people supported both.

Put that way, the trade-off was no longer abstract. The sponsor said, slowly, that he was not sure his goal was more important than client renewals, given the company's annual retention goal. The client team's leader added that it might well be more important next month, once renewals were finished and her people could refocus. Neither leader lost an argument. They made a decision with its cost in plain view.

Figure 1
The trade-off the council made visible
Data restructuringClient renewals
The askMove into the top tenAlready under way
People it needsClient team for 1 to 2 monthsThe same client team
Tied toOne function's top slotAnnual retention goal
OutcomeWaits; may rise next monthKeeps its place
Both pieces of work drew on the same people. Once the cost of moving one up was named, the sponsor concluded his goal could wait.

Second Nature Within Two Months

Within a couple of months the meeting ran the same way every week. It opened with the facilitator restating the council's purpose and boundaries. It moved to a review of prior decisions and open actions, each one closed or updated by its owner. It then took up the decisions raised by a weekly health check on the top-ranked shared goals: was the organization actually working on the agreed priorities, and which groups were overloaded? The rest of the time went to negotiating where incoming work would land and adjusting the overall order. It closed with the decisions posted in a company-wide channel.

What changed was not the quality of the conversation. These leaders had always been able to argue well. What changed was the structure around the conversation: a standing place where competing work met, criteria the leaders themselves had named, a cadence that held, and decisions the whole company could see. Separate functional priority lists became one shared, ordered backlog, revisited every week. The trade-off that used to surface by accident in a hallway now surfaced on purpose in the room, before anyone's capacity had been spent.

Figure 2
The weekly council, in order
  1. Restate purpose What the council decides, and what it does not.
  2. Review open actions Prior decisions confirmed or updated by owners.
  3. Weekly health check Are we on the agreed priorities? Who is overloaded?
  4. Place incoming work Negotiate where new goals land in the order.
  5. Publish decisions Posted in a company-wide channel.
The same five moves every week. The structure, not the debate, is what kept decisions from being relitigated elsewhere.

A prioritization forum proves its worth the first time it asks what gets bumped and someone gives an honest answer.

Share With Your Team

Choose who it is for. You send it yourself from your own email; Agileon never writes to your colleagues.

Not sure where to start?

Answer five questions about where work stalls. We send back a starting plan: where to begin and what to look at first.