There is a particular kind of meeting that expands to fill whatever time you give it. Development prioritisation is one of them. Offer an hour and it will take ninety minutes, plus a follow-up. Offer two hours and it will produce a spreadsheet, three caveats, and a lingering sense that nothing has really been decided.
The mildly counterintuitive truth is that prioritisation works best when it is treated as a scarce resource. Fifteen minutes, properly structured, tends to produce clearer decisions than an afternoon spent admiring the complexity of the problem.
This is because time pressure forces honesty.
What follows is a way to run a development prioritisation meeting in fifteen minutes that results in actual priorities, not an annotated list of aspirations.
Start by Acknowledging the Fiction
The first minute matters more than it should.
Open the meeting by stating, plainly, that this is not about finding the “right” answer. It is about agreeing what to do next, given what is known today, and accepting that this decision will look slightly wrong in three months.
This framing disarms two common failure modes immediately.
First, the instinct to perfect the ranking before committing.
Second, the belief that prioritisation is a one-time act of truth rather than a rolling judgement call.
When everyone understands that this is a provisional decision made in good faith, the temperature drops. People stop arguing for theoretical supremacy and start thinking about consequences.
You have now earned the right to move quickly.
Limit the Agenda Before You Enter the Room
The most important work happens before the meeting starts, which is convenient because it does not require a meeting.
There must be a hard cap on the number of items under consideration. Five is ideal. Seven is survivable. Anything above that is a sign the conversation has already failed.
If someone asks why their item is not on the list, the answer is not defensive. It is factual. “We are choosing between these five this week. Others will come back.”
This constraint does something subtle but powerful. It converts the conversation from what matters to what matters more. The latter is uncomfortable, but it is the entire point.
Bring the list into the room already written down. Not projected. Written. It signals that the scope is fixed.
Establish One Decision Lens, Not Five
Prioritisation meetings often collapse under the weight of their own frameworks. Value versus effort. Risk versus reward. Strategic alignment. Customer delight. Technical hygiene. Career advancement, occasionally disguised as architecture.
In fifteen minutes, you get one lens. Choose it deliberately.
The lens should answer a single question, such as:
What most reduces business risk this quarter or What most improves customer outcomes we can measure?
Do not debate the lens in the meeting. That is a different meeting, with a different clock. The purpose here is to decide, not to philosophise.
Once the lens is stated, enforce it gently but firmly. When someone argues from a different angle, acknowledge the point, then translate it back through the chosen lens.
This is about coherence.
Force Relative Judgement, Not Absolute Scoring
Scoring systems feel objective and waste astonishing amounts of time.
Instead, force relative judgement. Ask one simple question:, “If we could only do one of these in the next cycle, which would it be?”
Get an answer. Then ask the same question again for the remaining items.
This approach surfaces priorities faster because it mirrors reality. Development teams do not build scores, but build one thing before another.
Relative judgement also exposes hidden assumptions. When someone hesitates between two items, that hesitation is usually where the real information lives.
Let it surface briefly. Then move on.
Treat Disagreement as Signal, Not Obstacle
In a short meeting, disagreement is not a problem to be resolved. It is data to be sampled.
If two senior people disagree strongly about an item’s importance, note it explicitly. Often the disagreement is not about the item at all, but about an unstated risk, dependency, or expectation.
Ask one clarifying question. Not three.
If clarity emerges, adjust the order. If it does not, park the item lower by default. Unresolved disagreement is itself a risk, and lower priority is a reasonable temporary home for risk.
This approach reassures participants that dissent is heard without allowing it to consume the meeting.
Make the Trade-Off Explicit
Before the ten-minute mark, state the provisional order out loud.
Then do something that feels uncomfortable but saves weeks of confusion later. Name what will not be done as a result.
“By doing these two first, we are explicitly not doing the others this cycle.”
Silence often follows. Let it.
This moment is where prioritisation becomes real. It converts a ranking into a commitment and exposes any last-minute objections that actually matter.
If nothing explodes, you are done.
Assign Ownership, Not Consensus
The final minutes are not about agreement. They are about accountability.
Confirm who owns communicating this decision to the wider organisation and who will revisit it if circumstances change.
Avoid the phrase “we all agreed”. It creates a fragile consensus that dissolves under pressure. Prefer “this is the decision, and this is who will revisit it”.
Paradoxically, this increases trust. People relax when they know how decisions will be revisited, not when they are told the decision is perfect.
End Slightly Early
If you finish in twelve minutes, stop.
Ending early reinforces the discipline and signals confidence. It also creates a useful association: this meeting respects time, so it earns attention.
Over time, participants arrive more prepared, arguments sharpen, and the fifteen minutes become increasingly effective.
The Quiet Payoff
The real benefit of a short prioritisation meeting is not speed. It is focus.
By compressing the conversation, you remove the space where politics, over-analysis, and speculative anxiety tend to breed. What remains is judgement, trade-offs, and responsibility.
Fifteen minutes does not trivialise prioritisation. It reveals it.
And once a team experiences that clarity, it becomes strangely difficult to justify anything longer.
Discover more from Diary Of A CTO
Subscribe to get the latest posts sent to your email.
