Prioritisation is a scaffolding problem

When a team tells you everything is a priority, the usual response is to fix the people. Run a values workshop. Coach assertiveness. Talk about courage, push-back, ownership. Send a memo.

It almost never works. And the reason it almost never works is the diagnosis is wrong.

“Everything is a priority” is not a character flaw. It is a structural condition. Teams produce that sentence when the system around them is missing specific scaffolding: the protocols, the rehearsal spaces, the shared structures that make good prioritisation behaviour possible rather than heroic.

Add the scaffolding, and the behaviour you were trying to coach into existence shows up on its own. Often within days.

The two wrong readings

When people don’t challenge a decision, upward, laterally, wherever the tension sits, leaders typically read it as cultural. “People here aren’t comfortable pushing back.” When teams don’t drop a priority, leaders read it as a discipline problem. “They can’t make hard calls.”

Both readings put the fault inside the people. Both lead to expensive, slow interventions that address the symptom rather than the cause.

Working recently with a cross-functional operations chapter, spanning brand strategy leads through to operational delivery teams, with the people who set priorities and the people who deliver them in the same room, two moments within the same engagement made the opposite point cleanly.

Moment one: a protocol unlocked a year of unsaid challenge

Early in the working day we introduced two small tools. SBI (situation, behaviour, impact) for framing a challenge. And a short active listening structure for receiving one. Neither is novel. Both have been around for decades. The deliberate design choice was placing them early, before the harder conversations of the day, so participants had language for challenge before the system asked them to use it.

What was striking was the speed. Within fifteen minutes of the protocol being introduced, people who had been described, by themselves and by others, as “not the type to push back” were surfacing challenges that had been quietly held for months. Some were lateral: peer-to-peer friction about how work entered the system mid-cycle, bypassing whatever planning rhythm was supposed to protect the team’s focus. Some were upward: naming the effect of a senior stakeholder’s request pattern on delivery commitments. All were specific, fair, and immediately actionable.

Nothing about the people changed in those fifteen minutes. What changed was that they now had a way to say a hard thing that did not require them to choose between saying it badly and not saying it at all. The protocol gave them a third option: say it well, in seconds, with a structure both sides recognised as legitimate.

The challenge had been there all along. The scaffolding hadn’t.

And here is the part that mattered more than the exercise itself: the protocol didn’t stay in the session. It threaded through every harder conversation that followed. Teams used it when surfacing conflict patterns, when debriefing trade-off decisions, when clarifying who actually owned what, and weeks later when navigating real intake disputes in follow-up check-ins. A fifteen-minute introduction became connective tissue across weeks of applied decision-making.

That is the difference between a technique and a piece of scaffolding. A technique gets taught and forgotten. Scaffolding gets introduced once and used everywhere, because it solves a problem the room is already carrying.

Moment two: a rehearsed trade-off became a real one within the week

The afternoon exercise was structurally simple. Each cross-functional team, the brand strategists and the operational people who deliver their work sitting at the same table, looked at their actual current initiatives and were asked to drop at least two. Not pretend initiatives. Real ones, from their own planning tools and backlogs. With one rule: it was a simulation.

The simulation framing did two things. It removed the social cost of the decision: nobody was committing to anything. And it forced the team to build the rationale for the drop. Not just “this one goes” but the reasoning behind it. What we’re stepping back from. Why. What we’d say to the person who asked for it. What we’d protect instead.

By the end of the exercise the rationale was on the wall.

This matters because deprioritisation, in most organisations, isn’t even a conversation. What usually happens is that one leader pulls rank on another and reprioritises work in their favour. The team whose work just got displaced absorbs the impact quietly. They don’t have shared criteria to appeal to. They don’t have a forum where both leaders and both teams see the trade-off at the same time. And they would seldom take a drop conversation upward, because the system gives them no mechanism for doing so. So the override happens invisibly, resentment builds, and the displaced work often continues anyway, unfunded and unprotected.

The simulation broke that pattern. It put the leaders who set priorities and the teams who deliver them at the same table, working from the same criteria, building the rationale for a drop together. There was no room for a quiet override because the trade-off was visible to everyone it affected. By the following week, several of those simulated drops had become real drops. Not because anyone made a brave decision after the session. 

The decision had already been made. In the simulation. When the team returned to their operating rhythm, they weren’t deciding any more; they were executing a decision that had been built collectively, with reasoning that had been articulated in front of the colleagues who would be affected.

The transfer from simulation to reality was easy precisely because the hard part, building a defensible, shared rationale while the right people were in the room, had already happened. And the follow-up cadence gave the decision structural support: when we reconvened the following week, those drops were among the first things surfaced. The decisions held because the scaffolding around them held.

The unifying principle

Both moments are the same lesson wearing different clothes.

Behaviour that gets read as cultural (silent rooms, undropped priorities, shifting commitments) is usually scaffolding-shaped. The team is being asked to perform at speed a behaviour that the system around them gives them no structure to perform well.

Add a protocol for purposeful communication, and the challenge happens.

Add a rehearsal space with the right people in the room, and the trade-offs happen.

Neither requires anyone to become braver, more disciplined, or more committed than they were last Tuesday.

And critically, neither works as a standalone intervention. The protocol introduced in the morning earned its value across weeks. The rehearsed trade-offs held because a follow-up cadence, a mix of coaching, mentoring, and live decision support, kept the reasoning visible when real urgency reappeared.

I want to linger on that third ingredient because it is the one most frequently missing. The coaching cadence is not a check-in. It is not a retrospective. It is a structured container where the decisions made in the room meet real operating conditions for the first time: where a team that agreed to drop two priorities discovers that a senior stakeholder has just asked for one of them back, and has to decide in the moment whether the rationale still holds. Without that container, the decisions erode quietly. With it, they get pressure-tested and reinforced. The scaffolding doesn’t just create the behaviour; it holds the behaviour in place while it becomes the new normal.

Three pieces of scaffolding

Scaffolding is not a single prop. It is a connected system, and it has specific, buildable components.

A protocol for purposeful challenge. Something concrete enough that any two people in the room could use it in thirty seconds, regardless of seniority. Not a principle. Not a value. A named, practised structure for saying a hard thing well. If your team doesn’t have one, that is where the silence is coming from.

A rehearsal space for consequential trade-offs. A place where the rationale for dropping, deferring, or re-sequencing work gets built before the moment of decision, with the people who set the priorities and the people who deliver them in the same room. If the only time your team reasons about what to drop is at the point they’re being asked to drop something, you are asking them to make hard calls without preparation and without the right audience.

A follow-up rhythm that holds decisions in place. A small, regular container where the new decision language gets pressure-tested against real conditions before it has time to erode. The urgency that created the original problem will reassert itself within a planning cycle. If there is no cadence holding the new behaviour, the room will quietly return to “everything is a priority” because there is nothing stopping it.

Remove any one piece and the behaviour you were hoping for becomes heroic again: dependent on individual courage rather than structural support.

What to do if your team is currently saying “everything is a priority”

Don’t reach for the culture programme. Run three diagnostics first.

Ask whether there is a shared, named protocol for purposeful challenge. If not, that is where the silence lives. Build it.

Ask whether there is a place where the rationale for trade-offs gets built before the moment of decision. Ask whether the people who set the priorities and the people who deliver them are in that room together. If not, build the rehearsal space.

And then ask the harder question: what happens after the room disperses? If there is no follow-up rhythm, the scaffolding is temporary. Build the cadence.

Prioritisation is not a people problem. It never was. It is a design problem. And design problems have design solutions. Scaffolding is not an event. It is a system. And the system is where the fix lives.

This is the first in a series on the structures underneath good prioritisation. Next: what your team already knows but hasn’t seen together, and the case for making the invisible visible before you fix anything.