The most expensive decision in a delivery program is often the one that never gets made. Not the wrong call, the absent one. The priority conversation that ends with "let's keep momentum on all fronts" and a room full of people who know exactly what that means for the next six weeks. This essay is about making that non-decision untenable.
"The problem isn't that leadership won't decide. It's that the decision hasn't been presented in a way that makes non-decision more expensive than committing."
The Avoidance Pattern
Here is the scenario in its most recognizable form. A program is running three parallel workstreams with shared resources: the same architects, the same integration team, the same QA capacity. Each workstream has a sponsor. Each sponsor believes their initiative is the priority. The delivery team is caught in the middle, context-switching, and making invisible trade-offs every sprint. You've been asked, informally, to figure it out.
You bring the question to the leadership layer. You frame it clearly: the team cannot do all three at full capacity simultaneously. Something has to sequence. The response is encouragement rather than direction. "Let's keep momentum on all fronts." "We don't want to lose ground on any of these." "Can we revisit this next quarter?"
This is not obstruction. It is avoidance, and it has a structure. When leadership deflects a prioritization question, it is almost never because they don't understand what's being asked. It is because the question, as presented, has not made the cost of avoidance clear. Saying "all three" feels like retaining optionality. What it actually does is transfer the decision, and the accountability for the consequences, back to the delivery team.
The way to break this pattern is not to ask harder or escalate louder. It is to turn an ambiguous prioritization conversation into a visible governance choice with named consequences.
Why Leaders Don't Decide
Before reaching for a technique, it is worth understanding what's actually happening when leadership avoids a prioritization call. There are three distinct dynamics, and they require different responses.
Choosing one initiative over another has visible losers. The sponsor who doesn't get the resource commitment will feel it. The political cost of choosing is immediate and personal. The cost of not choosing: delivery delays, team burnout, downstream rework; is diffuse, delayed, and easier to attribute elsewhere. Until you change that calculus, the rational move is to defer.
Leaders sometimes avoid committing because they genuinely don't have the picture they need. They don't know what the sequencing actually costs, what slips if capacity shifts, or what the downstream dependencies look like. The absence of that information doesn't stop the meeting, it just produces vague answers where specific ones are needed.
Organizations that have historically rewarded ambition over discipline will often default to "we find a way to do both" as a cultural norm. Leaders who rose through environments where heroic delivery was the standard may genuinely believe the answer is effort, not trade-offs. In these environments, refusing the trade-off is often misread as leadership ambition, when it is really a decision to hide the cost inside the system.
The technique in the next section addresses all three. It doesn't ask leadership to be less political, or to know more than they do, or to abandon their instincts. It just makes the structure of the choice impossible to misread.
Making Trade-offs Visible
The core move is to stop presenting the prioritization problem as an abstract resource question and start presenting it as a set of concrete, named scenarios with documented consequences. When you ask "which workstream should we prioritize," you are asking leadership to reason abstractly. When you show them three scenarios with specific delivery outcomes attached to each, you are asking them to choose a future, not adjudicate a process debate.
This is the shift that changes the dynamic. Abstract choices invite deference. Concrete scenarios demand a position.
A well-constructed trade-off brief has four components for each scenario:
Name the initiative or workstream that receives full resource commitment under this option. Be specific. Not "focus on the platform" but "Platform migration gets 70% of integration capacity through Q3."
Name exactly what moves, pauses, or descopes. "Customer portal launch shifts from July to October. Regulatory reporting module remains on current timeline." Not "other things slow down."
Translate the trade-off into a business outcome. "This delays the portal launch by 14 weeks, which pushes the revenue recognition event from Q3 into Q4 and affects the board forecast." This is the line that makes non-decision expensive.
State the conditions under which this scenario holds. "This assumes the platform migration vendor SLA doesn't slip past mid-August." Assumptions make the choice real and reviewable, not theoretical.
The scenarios below are illustrative, but the structure is the point: each option makes the organization choose a concrete future rather than debate priorities in the abstract.
| Scenario | Prioritizes | Defers | Delivery consequence |
|---|---|---|---|
| A: Platform first | Platform migration at full capacity | Customer portal; regulatory module phase 2 | Portal shifts ~14 weeks; Q3 revenue event moves to Q4 |
| B: Portal first | Customer portal July launch | Platform migration to phased delivery; integration team split | Migration extends 6 months; platform tech debt accumulates through H2 |
| C: Split capacity | Both at reduced pace | Nothing formally; informal absorption by team | Both initiatives miss original targets; team utilization at 115%; quality risk across both |
Scenario C is the current state, written down. Most leadership teams, when they see it named and costed, do not choose it. The "split capacity" option stops feeling like pragmatism and starts looking like what it is: a decision to absorb risk invisibly. That visibility is the mechanism.
The Forcing Frame
The brief alone is not sufficient if it's presented without a clear ask and a deadline. The forcing frame is the wrapper that turns the document into a decision event rather than an update.
Three elements make it work:
A named default
Tell them what happens if no decision is made by the deadline. "If we don't have a direction by Friday, the team will proceed under Scenario C: split capacity. I want to flag that this is the highest-risk option and will result in both timelines slipping." This is not a threat. It is a fact about how delivery systems work. It also means that silence is no longer neutral — it becomes an active choice with a documented outcome.
A recommendation
Don't present the scenarios as equally valid without guidance. Offer a view. "Based on the downstream dependencies and the Q3 revenue commitment, I recommend Scenario A. I've flagged the portal sponsor separately and they're aware this is the trade-off under discussion." Leaders are more likely to act on a framed recommendation than an open question. Your job is to make the decision easy to take, not to remain impartial.
A single, specific ask
Close with one question that requires a yes or a no, not a discussion. "Can you confirm which scenario to proceed with by end of day Thursday?" Not: "I'd love your thoughts on the approach." The specificity of the ask signals that you are managing a decision, not soliciting feedback. It also gives leadership a clear, low-friction action to take.
Together, the brief and the frame shift the conversation from "we need you to prioritize"; which is a request; to "here are the consequences of each option and the cost of waiting", which is a governance document. One invites deflection. The other requires a position.
Delivering It Right
The technique is effective. Used without care, it can also land as coercive, presumptuous, or politically clumsy. A few things determine which way it goes.
- Presenting it cold without a pre-meeting conversation with sponsors
- Making the "default" scenario sound like a warning rather than a fact
- Naming losers without acknowledging their perspective
- Sending the brief without a recommendation, forces leaders to do the work you should have done
- Framing it as "the team can't continue without a decision"
- Pre-briefing the key sponsors before the document circulates
- Framing the default as a planning assumption, not a threat
- Acknowledging trade-offs explicitly: "I know this is a difficult ask for the portal team"
- Including a clear recommendation that takes the analytical burden off the decision-maker
- Framing it as "here's what the data shows so you can decide with full information"
The goal is not to corner leadership. It is to make the shape of the choice clear enough that the decision can actually be made. Most senior leaders, given a complete picture, a recommendation, and a low-friction path to yes, will take it. The failure mode isn't usually unwillingness. It's ambiguity: the picture was incomplete, the ask was unclear, or the cost of inaction wasn't visible.
When you remove all three of those obstacles at once, the dynamic shifts. Staying silent is no longer the easier path. Choosing is.
Make the trade-off concrete. Name the default. Ask clearly and on a deadline. Once inaction has a visible cost, the decision usually stops hiding.
The PM Reality Check
Weekly strategies for the human side of delivery. Plus the free Stakeholder Field Guide on signup.