Competing Priorities Resolve at the Contention Point

Most advice about priorities is advice about length. Count the list, cut it, protect the number. The counting is honest work and it has its own arithmetic. It also stops being useful at the exact point where most leadership teams are stuck, which is after the cut has been made.

A team that has reduced to three priorities often finds the pressure unchanged. The three are each correct. Each has a sponsor, a budget line, and a case that survives scrutiny. And each of them obstructs the other two, because they draw on the same engineers, the same hours of senior attention, and in some cases the same unmade decision. Nothing on that list is clutter. Subtracting further would remove something the business needs.

Where subtraction stops helping

Competition of that kind is a different problem with a different remedy. Clutter is solved by deciding what not to do. Competition is solved by deciding, in advance, how the conflict resolves when it surfaces, and it surfaces in the ninth week, in a room where the two sponsors are peers and neither of them is wrong. A leadership team that has cut its list well has not finished the work; it has earned the right to start on the conflicts that remain.

Two priorities in a plan look independent. They are written as outcomes, in separate boxes, with separate owners and separate measures. What makes them compete never appears in either box. It is the shared thing both of them consume, and the plan has no field for it.

Most contention traces back to a short list of scarce inputs, and they are not interchangeable.

• People. Rarely headcount in aggregate, almost always a specific team or a specific person whose judgment both initiatives need in the same weeks.
• Senior attention. The scarcest of the three and the only one with a hard weekly ceiling, since a leadership team cannot buy more Thursdays.
• A decision. Two priorities that imply opposite answers to one question, such as how much friction the checkout carries or how much risk the underwriting tolerates, are contending for a ruling rather than for resources.

Naming the contention point

The work is to write the shared thing down beside the pair. Not "A and B are both important," which every plan already says, but "A and B both need the platform team in the third quarter, and the platform team has eleven weeks." The sentence is unglamorous and it converts an argument about importance into an arithmetic problem, which is a far better argument to be having. A conflict named as a specific scarcity can be resolved; a conflict described as two important things cannot be.

When two named priorities collide and no rule exists, the collision resolves anyway. It resolves in favour of whoever is more senior, more persistent, closer to the chief executive, or simply in the room on the day. Every organisation has watched this happen, and most describe it afterwards as a judgment call rather than as the absence of one.

A conflict with no rule still resolves. It resolves in favour of whoever is in the room.

A rule set while nobody is losing

The alternative is not a scoring matrix. It is one sentence, agreed at a moment when nobody is losing anything by it, naming which consideration outranks which when both cannot be served. A payments business might declare that authorisation rate outranks checkout conversion for two quarters. A platform business might declare that commitments to existing customers outrank new-segment work. The declaration is arbitrary in the sense that the opposite reading is also defensible, and that is not an objection to it. Its value is that it exists before anyone needs it.

Why the rule has to cost something

A tiebreaker that costs nothing has not chosen. If it can be read out without anyone wincing, it is a statement of values rather than a rule. The test is whether the person whose work it deprioritises can repeat it back accurately, which is a harder thing than nodding at it in a planning session. A rule is only doing work if someone in the room can name what they gave up to it.

Once the contention is named and a rule exists, the team still has to choose a shape. There are two of them, and they are routinely run together as though they were one.

Splitting runs both priorities at reduced rate. It preserves visible movement on each, and it is politically cheap, because nobody is told to wait. The cost does not appear in the plan: two half-resourced initiatives land later than two sequenced ones, and each carries the overhead of a team dividing its attention between them every week.

Sequencing runs one to completion, then the other. The first finishes sooner, which means it starts returning something while the second is still waiting. It is politically expensive, because a sponsor is told that this quarter is not theirs, in a meeting, with their peers present.

The case each shape is actually for

Splitting is right when two priorities have genuinely different scarce inputs and only appear to compete because they share a calendar. Sequencing is right when they contend for the same people or the same ruling, which is the more common case. Teams split by default because splitting requires nobody to be told no, and then read the resulting slippage as an execution problem rather than as the shape they chose.

Which one is actually running is legible in the weekly rhythm rather than in the plan. A team that says it has sequenced, and whose Thursday hour still goes half to the deferred item, has split without admitting it.

The pattern in the businesses we are asked into is consistent enough to describe in advance. The priority list is short, which is presented as evidence that prioritisation has been done. Underneath it, three initiatives contend for one team and one decision nobody has made, with no rule about which yields. The quarter closes with all three partially delivered, and the response is another planning cycle, which produces another short list with the same structure underneath it.

What replaces the reset

What changes the outcome is smaller than a planning cycle and lasts considerably longer than one.

• Name the shared scarcity beside every pair of priorities that touches it, written into the plan rather than left in conversation.
• Write one tiebreaker sentence for each contested pair, agreed before the contention surfaces and specific enough that someone can name what it costs them.
• Choose splitting or sequencing on purpose, then check the choice against where the weekly meeting actually spends its hour.

Run this way, competing priorities stop being a recurring argument and become a small set of decisions with dates attached, most of which are made once. Where that thinking becomes work is consulting, and the neighbouring notes in growth discipline cover the counting that comes before this and the cost of a list allowed to grow past it.