Prioritization, Governance, and Collaboration: How to Deliver Strategy That Sticks

Strategy Requires Choices, Not Just Priorities

Strategy sets direction. The harder test comes when several worthwhile commitments compete for the same funding and capacity.

Leadership then has to decide what matters most, what gets supported and what has to give way.

Prioritization is often treated as a meeting, a spreadsheet, or a wall of sticky notes. But the real test comes when the result has consequences: which commitments receive resources, which wait, which change and which continue despite competing claims.

That requires more than a ranked list. It requires a repeatable decision-making capability that connects leadership priorities, credible evidence and real constraints to the choices the organization makes.

Why Is This So Hard?

Because strategy delivery crosses the boundaries where decisions about value, money, capacity and execution are made. That makes it an operating model problem, not simply a prioritization problem.

Different parts of the organization see different parts of the same decision:

• Finance sees affordability, investment discipline and financial returns.
• Strategy sees enterprise priorities and the outcomes leadership wants to achieve.
• Business leaders see commitments, opportunities and objectives within their own areas.
• Delivery teams see dependencies, bottlenecks, technical constraints and the operational work that competes for the same people.
• PMO and portfolio teams may coordinate the process and make trade-offs visible, without controlling all of the funding, capacity or strategic choices involved.

None of those perspectives is wrong. The problem starts when they are reconciled too late, or not at all.

• Funding is allocated one way while capacity is committed another.
• New priorities arrive without reopening existing commitments.
• Different functions assess value using different assumptions and criteria.
• Dependencies and scarce specialist capacity surface only after work has been approved.
• “Strategic” or “urgent” work enters through exceptions rather than competing through the same decision process.
• Accountability becomes blurred when objectives stay fixed even though the resources available to deliver them have changed.

The result is not simply “too many projects.” It is a decision system in which worthwhile commitments can compete for the same resources without a shared way to decide what should give way.

That creates three practical problems:

• Incomplete or inconsistent decision inputs
• Fragmented collaboration across functions
• Governance that cannot reliably turn priorities into resource commitments

Project Prioritization Starts with Better Inputs

You don’t fix this with another layer of admin or a shiny new process everyone resents. A more useful starting point is to improve the information people use to make prioritization decisions, then build the governance around it as the approach proves its value.

So yes, data matters. But this is not about building the perfect database. Much of the information that matters lives in different places: financial forecasts, delivery estimates, strategic priorities and the judgement of people who understand the work.

Bringing those inputs together does two things. It makes decisions easier to challenge and explain, and it gives different functions something concrete to collaborate around.

Portfolio decisions can involve multiple projects, multiple resource pools, uncertain estimates and benefits that don’t compare neatly.

The goal is not perfect information. It is enough structure to move beyond competing presentations, spreadsheets and opinions towards a decision people can examine and revisit.

Three basic questions get you a long way:

• What will it cost?
• What value could it deliver?
• What funding and capacity will it require?

In other words: turn fragmented knowledge into decision-ready information.

Estimating Project Cost

Cost isn’t just financial: it’s operational. Budgeting discipline matters, but so does understanding effort: the resource a project will consume, and the opportunity cost of what won’t get done if this project is selected.

Why estimating matters:

• Internal resource is not free. The benefits of a project must justify the cost of the time that will be spent on it. Use this perspective to challenge pet projects and poorly thought-through proposals.
• Bottlenecks can make an apparently affordable portfolio undeliverable. If you know which kinds of resource the work will need, you can test the plan against the constraints most likely to bind. Look beyond headline capacity to understand the hidden constraints on delivery, then compare whether resource-intensive projects justify what other work must give way.

To estimate effort we recommend the following:

• You don’t need a detailed bottom-up plan at the start. This is usually overkill if there is a possibility the project isn't going to happen right away.
• Use templates, T-shirt sizing, or triage models if they help.
• Engage the experts early, but be clear that this is an indicative view, not a hard and fast commitment at this point.
• Don’t let “too early to say” end the conversation. Use an indicative range or assumption, make the uncertainty visible and improve the estimate as you learn more.

Without a good culture of estimation, you are working in the dark.

Modeling Project Value

Financial justification matters. Finance needs to understand affordability, expected returns and the assumptions behind an investment.

But portfolio choices usually involve other forms of value too. Leadership may also care about:

• Strategic alignment
• Risk mitigation
• Customer impact
• Innovation potential

The problem? Those other forms of value are often harder to compare. “Strategic,” “important” and “customer-focused” can quickly become claims that every project makes. The fix is to give them structure. Criteria-based approaches like AHP (Analytic Hierarchy Process) can help:

• Define what “value” means for your organization.
• Weight the criteria to make leadership’s relative priorities explicit.
• Avoid vague terms like “aligns to strategy.” Add clearer sub-criteria so assessments can be explained and challenged.
• Bring different perspectives into the scoring process so disagreements, assumptions and inconsistencies become visible.

The result is a structured, transparent view of value that gives different functions a common basis for comparing projects.

Use Capacity Constraints to Force Trade-Offs

Michael Porter put it plainly: “The essence of strategy is choosing what not to do.”

The same applies to portfolios. Drawing the cut-off line is hard. It’s tempting to approve everything and hope delivery teams “find a way” through hidden buffers and heroics.

Approving everything simply pushes the trade-off into delivery, where scarce people and resources make the choice for you. That’s weak governance. Better governance brings the choice forward:

• Set resource and budget constraints.
• Compare projects using the agreed view of value.
• Compare feasible combinations against those limits, including dependencies and mandatory work, then decide what stays, changes or waits.

Three big behavioral shifts are needed:

• Honest estimates: no padding, no gaming.
• Model capacity: be clear about teams’ ability to support projects alongside their operational responsibilities, then revisit commitments when that balance changes.
• Learn to say “No” (or “Not Yet”): if something truly is a priority, agree what stops to make room.

How Do You Build Better Decision Inputs?

The Technical Answer

In purely functional terms, the process is relatively simple:

• Collate the work being considered, with a minimum standard for justification, sponsorship and scope.
• Define a practical approach and timetable for estimating cost, effort and other decision inputs.
• Run workshops to define and weight criteria, then assess projects against them.
• Build scenarios using the relevant funding, capacity and other constraints.
• Bring those scenarios into governance sessions where trade-offs can be discussed and assumptions revisited.

For the practical inputs behind these steps, see 10 portfolio data sources every effective PMO needs to know, including the information and commitments to obtain from Finance, resource owners and the business.

For a more detailed approach to introducing prioritization, see our eight-week prioritization roadmap.

The Political Answer

Prioritization is more than data: it’s about engaging people to participate. It’s critical to show different participants the “What’s in It for Me” (WIIFM). For Delivery Teams:

• Smoother pipeline → more scope to focus
• Scoring surveys → decision-making values their expertise

For Leadership:

• Better prioritization → a stronger basis for allocating scarce funding and capacity
• Influence over criteria and weights → a clearer link between strategic priorities and the choices that follow

Sponsorship is also critical, especially if you’re running this from a support function like the PMO. Get these commitments:

• Get leadership fully engaged with criteria definition and weighting.
• Agree that material funding and resource commitments go through the same decision process rather than being added through informal exceptions.
• Get support on comms to amplify the WIIFM and support compliance.
• Align incentives so people are not penalized for supporting the wider portfolio at the expense of a local target.

The point is that prioritization cannot be seen as a PMO process to reluctantly follow. It has to be something people agree is simply a better way to run an organization.

For a practical example, see how APA used board-defined criteria and executive scoring to build a clearer backlog.

The Pragmatic Answer

If you are looking for a place to start, keep it simple, fast and practical:

• Document a simple Case for Change that explains why the current way of prioritizing needs to improve.
• Find a self-contained opportunity to test the approach.
• Time-box the pilot, for example as a 90-day initiative.

And yes, the right tooling helps. TransparentChoice structures leadership judgements with AHP and compares feasible portfolios against funding, capacity and other constraints, so leaders can test the trade-offs and decide what to commit to.

A pilot can show how the approach works in practice. But turning a successful one-off exercise into an ongoing capability is a different challenge, because Finance, Strategy, Delivery and governance all need to keep using the model as decisions recur.

Turning Prioritization into a Capability

A prioritization exercise can improve one decision. A capability makes the same discipline reusable across planning cycles, governance forums and different parts of the organization.

That requires more than a scoring model. The decision inputs, governance and accountability all need to work together. One framework for thinking about that wider operating model is Business Integrated Governance (BIG), which connects strategy, delivery and accountability around shared decision-making.

Common Data Model

Forecasts, criteria, scores, constraints: this isn’t just “PMO data.” It’s enterprise data.

A common model gives Finance, Strategy, Delivery and governance a shared language for comparing work, challenging assumptions and passing decisions between different levels of the organization.

Why a Common Model Matters

A shared model does more than standardize fields. It creates a consistent way to describe value, cost, capacity and other factors that influence a decision.

That consistency matters when decisions move between teams, portfolios and governance levels. People can still disagree, but they are disagreeing within a structure they can understand and challenge.

Done well, that common model can act as a Golden Thread between priorities, local decisions and enterprise governance.

• It doesn’t have to be one-size-fits-all.

• It can adapt to different contexts.

• But the underlying decision logic should remain understandable as work moves across the organization.

The Flow of Prioritization

At enterprise level, prioritization has to work in both directions:

• A strongly top-down model can miss operational realities, dependencies and local knowledge.

• A highly decentralized model can make it difficult for leadership to turn enterprise priorities into coherent resource choices.

Nested criteria modelling is one way to connect the two:

• Leadership defines and weights what matters, giving governance a common basis for higher-level trade-offs.
• Teams can plan within that framework while adapting criteria, assumptions and detail to their own context.
• Results can then be brought back together so leadership can compare portfolios, see where priorities conflict and reconsider how transferable funding and capacity are allocated.

For a practitioner discussion of how prioritization changes as you move from individual and team choices to organization-scale decisions, watch Prioritizing Prioritization. Harry Max, Wes Bright and Stuart Easton explore how priorities connect across organizational levels, why different decisions call for different methods, and why a ranked result still requires leadership judgement.

Where Tooling Helps

This scaled approach to prioritization is difficult to sustain in disconnected spreadsheets.

When different teams maintain separate models, assumptions, criteria and scenarios can drift apart. That makes it harder to understand why decisions differ and harder to revisit them when circumstances change.

Good tooling can support:

• A shared record of criteria, assumptions and assessments

• Scenario modelling when priorities or constraints change

• Governance decisions based on information whose sources and assumptions can be examined

Together BIG and TransparentChoice can support that wider decision capability: BIG connects strategy, delivery and accountability through governance, while TransparentChoice structures leadership judgement and compares feasible portfolio choices against agreed priorities and constraints.

Decision-Making at Scale

Once the model is in place, you can ask bigger questions:

• Are our resource limits right?
• Should we shift funding between divisions?
• What happens if we double down on growth areas?

Those questions can become politically difficult when objectives and resources move independently:

• Move resources? Revisit the goals attached to them.
• Reduce funding or capacity in one area? Reconsider what that area is expected to deliver.
• Invest more in another? Make the expected outcomes and accountability explicit.

This is also a question of organizational accountability: objectives, decision authority and expectations should reflect the resources leadership has actually allocated.

If people are measured against local objectives that conflict with the wider portfolio decision, local optimization is a predictable result. This is where governance, resource allocation and performance management need to reinforce the same priorities.

Collaboration Through Shared Processes

Integrated planning also requires collaboration at a process level. Decision ownership should be clear, but the inputs and consequences usually cut across functions. Finance, Strategy, Delivery and portfolio governance all contribute to the same set of choices.

There are many ways to make that work in practice:

• Finance and PMO or portfolio teams align on one shared stage-gate process for project approvals and subsequent funding reviews.
• Strategy includes capacity considerations from the start.
• Delivery teams contribute to scoring and estimates early, and monitor their accuracy.
• Demand Management becomes more than PMO triage: it becomes a decision-making funnel for funding and resource commitments.
• Central and local planning coexist, with scenarios used to understand where their choices reinforce or conflict with each other.

Problems emerge when every function optimizes its own process and the route to a decision becomes a chain of hand-offs. But putting all the criteria, data and governance in the hands of one function can create a different problem: other participants may distrust a process they feel they do not help shape.

A cross-functional framework such as BIG can help connect these pieces. The aim is not to turn prioritization into a Finance process, PMO process or leadership exercise, but to create a shared route from strategy through decisions to delivery and accountability.

Build Towards Dynamic Decision-Making

Prioritization often starts as an initiative in its own right, but long-term success lies in adoption: the progression from a new process to “how we do things round here.” That requires practical skills people can develop and improve over time:

• Faster collaborative scoring and review.
• Better estimates, with a learning loop for next time.
• Clear decision rights and the ability to say “No” or “Not yet.”

With a shared decision model, workable governance and leadership involvement, prioritization can become repeatable rather than something rebuilt for every planning cycle. The value is not one perfect answer. It is the ability to make choices consistently, learn from them and revisit them when circumstances change.

That takes time. Embedding this kind of change in how people plan, decide and work together is a Change Management challenge, so adoption matters as much as process design.

Find the Metrics That Matter

If prioritization is becoming an organizational capability, measure both the quality of the decision process and what happens after those decisions are made. Useful measures might include:

• Decision Velocity: How long does it take to reach a decision once the necessary inputs are available?
• Project Flow: How quickly do projects complete?
• Benefits Realization: Are the expected benefits actually being realized?
• Strategic Fit: Does funded work reflect the priorities leadership says matter?
• Forecast Accuracy: How closely do estimates of cost, effort and outcomes match what actually happens?

At scale, tooling can make these measures easier to sustain by keeping assessments, assumptions, scenarios and decision history connected over time. That creates a feedback loop: better information improves decisions, and what happens afterwards improves the information used next time.

Four Steps to Better Prioritization

You do not need to redesign the whole operating model at once.

1. Improve the inputs and find a quick win
   Build a practical prioritization model around a real portfolio or decision. Learn what information is genuinely useful before adding more complexity.
2. Think BIG
   Use frameworks from Business Integrated Governance to explore how Finance, Strategy and Delivery can connect their processes as prioritization scales.
3. Start small
   Build alliances one relationship at a time: one decision process improved, one portfolio aligned, one planning cycle transformed.
4. Get help where you need it
   Facilitation, process design and coaching can help when the challenge crosses functional boundaries. We have a community of partners with experience in these areas.

Where Does the Next Trade-Off Need to Happen?

A shared decision model proves its value when Finance, Strategy and Delivery can use it to answer a real question: with the funding and capacity available, what stays, what changes and what gives way?

Bring a current or emerging allocation decision to a Decision Review. We’ll work through the choice you are facing, what is constraining it and what would have to change for the answer to be different.

30 minutes. No fee. Confidential. No preparation needed.

Start with a Decision Review →

💚 If you enjoyed this article, please consider following us. It’s a small gesture that means a lot to us and encourages us to keep sharing what we learn. See the ways to follow us below ↓