Step 06

Prioritize

In Brief — Resources are finite and priorities are not equal, regardless of what anyone says in a planning meeting. This step builds a scoring model that reflects actual strategic priorities, applies it consistently across all portfolio candidates, and makes the tradeoffs visible — so the organization can make deliberate decisions about what to do now, what to defer, and what to say no to. Prioritization shapes the input to the tollgate. The tollgate owns the output.

What’s Actually Happening

Everything is high priority.

Ask any leader to rank the active initiatives in their portfolio and they will tell you that all of them are important, most of them are urgent, and few of them can be deferred without consequences. The organization is running sixty projects and treating all sixty of them as if they are in the top five.

This is not a failure of individual judgment. It is what happens when there is no structure for making tradeoffs explicit. When saying yes to everything is easier than saying no to anything, the portfolio fills up with commitments that individually seemed reasonable and collectively are not executable. Everyone is overcommitted. Nothing gets the attention it needs. The organization produces the experience of always being busy and the result of consistently underdelivering.

Why This Step Exists

Because resources are finite and commitments are not.

Every organization has more worthy work than it can fund, staff, and absorb simultaneously. Prioritization is not about finding the perfect work to approve. It is about making a defensible, consistent decision about what to do now, what to defer, and what to stop — given what the organization actually has available to deploy.

Without prioritization, the portfolio reflects informal authority. Work that powerful people want advances. Work without a powerful champion waits. Prioritization also creates accountability: when the criteria that determine priority are explicit and visible, leadership cannot shift priorities informally without the shift being visible.

What Good Looks Like

The organization has a scoring model that reflects what it is actually trying to accomplish this year — not a generic framework or a balanced scorecard that weights everything equally. The criteria map to the two or three things leadership has genuinely committed to prioritizing.

The model is applied consistently to all work of the same type. The same criteria apply to the CFO’s initiative and the operations manager’s proposal. Executive preference is visible when it overrides the model, not hidden inside it.

The governance forum uses the model as a starting point for a conversation, not as a calculator that produces a final answer. The model surfaces the tradeoffs. The leaders in the room make the call. Both of those things need to happen.

How to Do It

Start by naming what matters. Sit down with the leadership team and ask: if we are still in business and healthy a year from now, what will have been true about how we spent our time and money? The answer defines the criteria.

Typical criteria include: strategic alignment, financial value, risk reduction, mandatory requirements, customer or operational impact, delivery readiness, and adoption readiness. Not all deserve equal weight — set weights to reflect actual priorities and review them at each planning cycle.

Score the work. Apply the model to every proposal in the active and proposed portfolio. Do not adjust scores in response to political pressure during scoring — if adjustments are needed, they happen as deliberate overrides with documented rationale, not as quiet score revisions.

Then look at the ranked output alongside three additional views the model does not show: capacity, dependencies, and timing. The highest-scoring work is not always the right work to approve next if the resources it needs are already committed. Bring the full picture to the governance forum. That is where the decision happens.

What Breaks When You Skip It

The portfolio is managed by whoever asks loudest, and the people who ask loudest are not always working on the most important things.

New work gets approved on its own merits without being evaluated against existing commitments. The portfolio grows continuously. Resources get spread across an increasing number of initiatives. Nothing gets the sustained attention it needs to succeed.

There is also a slower failure: the organization loses its ability to make deliberate choices. When everything is always a priority, the word loses its meaning. Leaders stop trusting governance to help them make tradeoffs.

The Gotchas

Scoring is manipulated after the answer is known. The defense is process integrity: scores are set before the ranked output is visible, criteria definitions are written precisely enough to limit subjective interpretation, and overrides are documented separately rather than embedded in scores.

The model gets overengineered. More criteria, finer-grained scales, weighted sub-criteria. A model that people understand and use consistently beats a model that is technically superior and operationally ignored. If someone cannot explain how it works in three sentences, it is too complicated.

Mandatory work crowds out everything else. When this happens, the conversation needs to shift: not “what do we do?” but “given that we must do these things, what can we also do, and in what order?”

The model stops getting updated. The criteria are set once and never revisited. Prioritization should be a living practice. Review the model at each planning cycle and adjust weights when priorities shift.

Where the Disciplines Show Up

→ Decision Discipline: Prioritization is a decision, not a calculation. The model informs the decision; it does not make it. Who has the authority to approve, defer, and stop work must be defined before the scoring session begins. When human judgment overrides the model’s output, that override is documented with the rationale written down.

→ Change & Absorption: Adoption readiness belongs in the prioritization model as a criterion, not as an afterthought. An organization can be technically capable of executing ten initiatives and organizationally capable of absorbing four simultaneously. Prioritization without a change absorption view consistently overcommits.

→ Enterprise Fit: At this step, the question is not just “does this project fit our architecture?” — it is “what does the combination of approved and proposed work look like from an architecture standpoint?” Two projects that each pass individual review may reveal a coordination problem when seen together.

→ Evidence: Scoring based on evidence produces different results than scoring based on perception. “Strategic alignment” scored against the actual language of the strategic plan produces different scores than the same criterion scored against how strategically important a sponsor believes their project is. Anchor scores to something verifiable.

→ Political: Prioritization is the most overtly political step in the sequence. It produces winners and losers. Political discipline means the coalition-building happens before the prioritization session, not during it. A result that stakeholders understood was coming — because the criteria were published and the key conversations happened before scoring — has political durability that a surprise result does not.

The Key
The scoring model should expose tradeoffs, not disguise them. It should be possible to look at the output and say: “If we approve items one through seven, we are choosing not to do items eight through fifteen this cycle. Here is what we lose by deferring eight and nine specifically.” That conversation is governance working.

You know this step is working when a sponsor whose project ranked lower than expected can explain why — not because you told them, but because the model’s logic is transparent enough that they worked it out themselves. And when work that ranked low actually gets deferred, rather than proceeding informally through a sponsor’s relationship with the CEO.

The Artifacts

T6 — Prioritization Scoring Model

A weighted scoring framework with defined criteria, explicit scales, and written definitions for each score on each criterion. The definitions determine whether the model produces consistent scores across different reviewers.

T21 — Weighting Guidance

Explains why the current weights are set the way they are, which criteria reflect the current planning period’s priorities, and when the weights were last reviewed.

T22 — Prioritization Tradeoff Summary

Produced after each prioritization cycle: what was approved, deferred, stopped, and the explicit reasoning. This is the record the organization can look back on to understand why the portfolio looks the way it looks.