Every Business Unit Had Priorities. Nobody Owned the Order.

A global IT organization assumed its problem was too many priorities. Mapping its own structure showed something else: priorities were being set everywhere, by every business unit, and the one step that should have reconciled them had no owner at all.

03 RANK
The condition

An IT organization received clear, sincere priorities from every business unit it served, and no one owned the order in which they would be worked.

Clear Priorities, Very Little Focus

A global IT organization supported nearly every part of its company: sales, recruiting, payroll, customer platforms, and the internal services that kept everything running. From the outside it looked healthy. Inside, each group decided what came next on its own, and decisions were often reversed when someone escalated. More than eighty percent of available hours went to keeping the lights on and finishing existing projects, which left little room for improvement or new strategic work.

No one in the organization would have said it lacked priorities. Every business unit had them, clearly stated and sincerely held. The question was why so many clear priorities produced so little focus.

The answer began with a picture of the organization itself. A member of the internal change team had spent six weeks mapping its structure and which groups were involved in each part of how work moved. When she presented it to the team, the map explained more than any tool review had.

Divisional on Top, Matrixed Underneath

The business units were divisional. Each operated with its own leadership, its own portfolio, and its own priorities. The IT organization sat across all of them as a matrix, with dotted and solid reporting lines running in both directions and project teams forming and disbanding regularly. IT routinely received competing priorities from several business units at once. One leader on the team said it matched what he had been seeing for three years.

That combination is one of the harder shapes to work inside. Divisional separation works against enterprise-wide visibility. The matrix adds reporting relationships that have to be reconciled in real time, so accountability, governance, and decision-making become constant sources of friction. The friction the teams felt was what that structure produces when nothing has been designed to compensate for it.

Prioritization follows structure. A divisional organization develops divisional priorities, and a matrix produces competing priorities between functional leaders and project leaders. When an organization feels it is chasing too many goals, prioritization is rarely missing. It is happening everywhere, shaped by the organization's own architecture. And when nothing reconciles those priorities, the final decision lands on individuals. In our experience, someone holding competing asks from a manager, a project leader, and a business unit executive usually works on whatever came from the person who writes their performance review.

Figure 1
Many priority lists, one set of people
  • Sales priorities
  • Recruiting priorities
  • Payroll priorities
  • Customer platform priorities
  • Escalations
The same IT capacityNo shared criteria and no owner for the order
Each business unit's list made sense on its own. They all landed on the same IT capacity, and nothing in the system decided between them.

The Step With No Owner

The second map showed which groups ran each part of the work system. Work entered through multiple points across IT and the business units. Breaking work down lived inside the delivery teams. Some teams followed a delivery framework and others had none. Coordination across teams happened in ad hoc meetings whenever incidents and urgent requests forced it. Reporting came through monthly business reviews. Two steps had no defined process and no owner at all: understanding incoming work before committing to it, and deciding the order in which it would be done.

The PMO leader studied the diagram for a while. The two steps without owners, she said, were the two she had not been working on. For years the organization had been treating symptoms that traced back to steps nobody owned.

The answer was not to restructure. Most organizations do not need a reorganization to work well. They need a work system designed to offset the side effects their structure is known to create. Here that meant clear roles to settle boundaries, a common meeting cadence that gave every division a decision point it attended, and prioritization policies that removed the ambiguity about order, especially when a request arrived from more than one manager.

Figure 2
What the structure was costing
80%+of hours already committedKeeping the lights on and finishing existing projects
2steps with no ownerScoping incoming work and ranking it
Most of the organization's hours were already spoken for, and the two steps that should have governed new demand had no one responsible for them.
Two colleagues working out a structure together at a whiteboard.

What a Ranked Portfolio Would Look Like

When the change team designed the fix, we asked what they would see a year later if ranking worked. Their answers became the specification. One leader wanted a forum where trade-offs across the organization were made by people empowered to make them, against criteria everyone understood. Another wanted it to meet regularly: often enough for priorities to shift as new information arrived, and disciplined enough that decisions were not renegotiated every week. A third wanted agreed dimensions that would let a finance request be compared with a product request without a gut feeling or a fight. The PMO leader added the requirement the others depended on. The decisions that came out of the forum had to stick.

The outcome they wrote was a recurring prioritization forum that would evaluate all new work against defined value criteria and delivery capacity, act as the central body for sequencing incoming demand, and balance new opportunities against work already in flight. It would be running before annual planning, so prioritization became a standing capability rather than a once-a-year exercise. How the forum was set up, and the written policies that let teams defer work with a reason, are stories of their own.

Figure 3
Four requirements for ranking that holds
What it means
Empowered forumTrade-offs made by those who can
Steady cadenceAdapts, without weekly churn
Shared criteriaAny ask compared on one scale
Decisions stickNo quiet renegotiation after
The change team's own description of a working Rank component. Each requirement answered a failure they were already living with.

One Order, Written Down

In the pilot, the forum's first sessions produced criteria written with business partners for weighing requests on value, urgency, and capacity, and a running record of every item accepted, deferred, or cut. Teams commit to smaller amounts of work sized to their real capacity, which has cut disruption in the middle of a cycle.

The PMO leader describes the IT organization as beginning to operate as one portfolio, with consistent adoption still developing. By the close of the pilot, the forum was not yet the place where every priority call got made, and year-end pressure pushed it down the list. The structure that produced the competing lists had not changed. What changed was that the organization now had a place, a method, and an owner for turning them into one order.

An organization with a priority list in every business unit does not have too many priorities. It has no one ranking them.

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.