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

Strategy Fails Without Prioritization

Most organizations think the hardest part of strategy is deciding what to do.
It’s not. The hardest part is deciding what matters most—and what gets put aside to achieve it.
 

Prioritization Fails Without Governance

Prioritization is often seen as a meeting, a spreadsheet, or a wall of sticky notes.
But to maximize impact, it has to be more:
A systematic decision-making capability that connects data to power. Let’s explore how to solve these challenges.
 

Why Is This So Hard?

Because strategic delivery isn’t a task. It’s not even a process.
It’s an operating model—one that must connect multiple silos, each working independently but relying on each other for success. Here’s what that looks like in a typical organization:
  • Finance holds the budget and applies ROI measures that don’t fully reflect strategy.
  • Directors have objectives tied to strategy—but with a short-term, local focus.
  • Delivery teams try to support everyone while juggling unglamorous but critical enablers like tech debt and data governance. Louder voices often prevail.
  • New “must-have” work emerges from market trends and corridor conversations—often labeled “strategic” or “urgent” to bypass scrutiny.
  • PMOs try to manage capacity but lack authority to stagger, stop, or reject requests. Result? Too Many Projects.
  • Everyone prioritizes in isolation, using their own criteria, then gets frustrated when dependencies block progress.
  • Confusion breeds ambiguity, which becomes a shield for dodging accountability:
    “We missed targets because projects were late. Projects were late because resources were double-booked. Not my fault.”
Sound familiar? If this feels like your world, you’re not alone—and there’s a better way. These aren’t isolated issues. They’re systemic symptoms of three core problems:
  • Weak data
  • Weak collaboration
  • Weak governance

The Solution? Start with the Data

You don’t fix this with another layer of admin or a shiny new process everyone resents. You fix it by proving the value of better data, then iterating towards a governance model that scales and perpetuates that success.
 
So, we start with that foundation: Data.
 
Indeed, we have to start here because without it we're just building another subjective talking shop. But this is not just about building a database, we'll also explore how the process of quantifying peoples' insight can move the needle on another critical foundation: Collaboration.
 

Project Prioritization Starts with Better Data

Most portfolios are complex: multiple projects, multiple resource pools, benefits that don’t compare neatly.

Without data, selection becomes subjective—a “best guess” exercise. Think sticky notes, PowerPoint pitches, and painful workshops that produce brittle decisions. No wonder so many organizations cite project prioritization as a top challenge.
But it’s solvable—with some basic disciplines:
  • How much will it cost?
  • How much value will it deliver?
  • How many can we afford to do?
In other words: turn fragmented knowledge into a model that drives decisions.

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 destroy portfolios. If you know what kind of resource you’ll need, you can de-risk your planning process. De-prioritize projects that are greedy for your scarcest resource.
 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 this is an indicative view not (at this point) a hard and fast commitment.
  • Don’t accept “too early to say.” Without estimates, you can’t make data-driven decisions.
 
Without a good culture of estimation, you are working in the dark.

Modeling Project Value

Most approval processes lean on financial justification. Logical—Finance owns capital accountability.
But ROI alone rarely drives prioritization. If it did, we’d just rank by ROI and be done. The problem? ROI models often ignore what decision-makers truly care about:
  • Strategic alignment
  • Risk mitigation
  • Customer impact
  • Innovation potential
When these factors sit outside the model, ROI becomes a paper exercise, not a decision-making framework. The fix? Criteria-based models like AHP (Analytic Hierarchy Process):
  • Define what “value” means for your organization.
  • Weight those criteria based on importance. Get leadership to align on preferences.
  • Avoid vague terms like “aligns to strategy.” Add measurable sub-criteria that can’t be gamed.
  • Work in teams to score projects to reduce the “noise” of bias, blind spots, and errors of judgment.
The prize? A quantified, transparent scoring system that unites teams around a shared view of value.

Use Capacity Constraints to Force Trade-Offs

Michael Porter said it best: “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.
That’s weak governance. It avoids tough choices and breeds bloated roadmaps nobody trusts. Instead, use data-led planning:
  • Set resource and budget constraints.
  • Rank projects by value.
  • Select the best mix within those limits.
Three big behavioral shifts are needed:
  • Honest estimates—no padding, no gaming.
  • Model capacity—be clear about teams’ ability to support projects, then hold them to their commitment to avoid “day job creep.”
  • Learn to say “No” (or “Not Yet”)—and if something truly is a priority, agree what stops to make room.

How Do You Get Better Data?

The Technical Answer

In purely functional terms, the process of getting this data is relatively simple:
  • Collate projects, defining the minimum standard for justification, sponsorship, and scope.
  • Define a template and timetable for submitting project estimates.
  • Run workshops to weight criteria and score projects.
  • Build scenarios, applying modeled constraints to fix spending and capacity limits.
  • Hold governance sessions where trade-offs can be made and iterations reviewed.
We have a deployment process if you want to go deeper.

The Political Answer

Prioritization is more than data—it’s about engaging people to participate. It’s critical to show the benefits, the “What’s in It for Me” (WIIFM) for different participants. For Delivery Teams:
  • Smoother pipeline → more scope to focus
  • Scoring surveys → decision-making values their expertise
For Leadership:
  • Better prioritization → better ROI
  • Control of weights → ability to focus on their top goals
Sponsorship is also critical, especially if you’re running this from a support function like the PMO. Get these commitments:
  • Leadership fully engaged with criteria definition and weighting.
  • Make prioritization the only route to funding and resources. No shadow portfolios allowed.
  • Get support on comms to amplify the WIIFM and support compliance.
  • Show that collaboration is better for career advancement than playing the system.
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.

The Pragmatic Answer

If you are looking for a place to start, we see the best results when people keep it simple, fast, and practical:
  • Document a simple Case for Change to show the benefits of prioritization.
  • Find a self-contained opportunity to implement a pilot.
  • Package it as a 90-day initiative.
And yes, the right tooling helps— TransparentChoice is a collaboration platforms with built-in AHP scoring and AI-powered selection, and it beats a spreadsheet every time.
 

Follow this approach and you will see benefits. But you will also probably realize there is a lot more still to be done, because turning a one-off review into an ongoing capability is not a trivial task, and is likely to be the point at which the PMO needs to extend their influence to a far broader audience.

Turning Prioritization into a Capability

Fixing prioritization once is good. Embedding it as a capability is better. But it is at this point that it will become apparent that there is a need for a mechanism to help the organization work, and for this we recommend Business Integrated Governance (BIG), a free collection of best-practice frameworks designed to help scale quality decision-making.

Common Data Model

Forecasts, criteria, scores, constraints—this isn’t just “PMO data.” It’s enterprise data.
A common standard for these metrics enables decision-making to cascade and escalate smoothly across the organization.

Why a Common Model Matters

A shared model does more than standardize data—it defines “value.”
Done properly, it acts as a Golden Thread that aligns teams across all levels of the business.
  • It doesn’t have to be one-size-fits-all.
  • It can adapt to different contexts.
  • But it must provide a consistent framework for decision-making.

The Flow of Prioritization

For prioritization to succeed at an enterprise level, it must flow up and down:
  • A pure top-down mandate fails because it ignores operational realities.
  • A wholly decentralized process fails because it disenfranchises leadership from driving change.
The solution is nested criteria modelling:
  • Leadership defines value and cost parameters, enabling governance to make high-level trade-offs and put funding where it adds the most value. 
  • Teams plan independently, but within guiderails set by leadership.
  • Value can be consolidated into an Enterprise plan, thereby enabling smart high level trade-offs that move constraints between portfolios to follow the opportunity

Why Tooling Is Critical

This scaled approach to prioritization cannot run on spreadsheets.
If every team has its own version, the truth rapidly dissipates—along with the integrity and velocity that are core to success.
 
Rock-solid tooling ensures:
  • A single source of truth
  • Real-time scenario modeling
  • Governance decisions based on accurate, shared data
Together BIG and TransparentChoice can help you generate, structure and perpetuate the common data model you need to support the value-led decision making your strategy neeeds to succeed.

Decision-Making at Scale

Once you have data, 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?

These questions are easy to model—but divisive politically unless you connect them to objectives:

  • Move resources? Then adjust goals.
  • Starve Division A? Lower their targets.
  • Feed Division B? Demand results.

If managers in an organization are forced to choose between doing the right thing for the organization and doing the right thing for themselves, the system will fail—because self-interest usually wins. This is where governance and performance management converge, and again BIG provides complementary frameworks to make this connection achievable.

Collaboration Through Shared Processes

Integrated planning also requires collaboration at a process level, through recognising that it is decisions that matter, and not the team who "owns" them. There are many ways this alignment can happen - here are some examples:
  • Finance and PMO align on one gating process for project approvals.
  • Strategy includes capacity planning from the start.
  • Delivery teams contribute to scoring and estimates early, and monitor their accuracy.
  • Demand Management becomes more than PMO triage—it’s a decision-making funnel for all project funding and resource management.
  • Central planning and local planning co-exist in one process with iterative scenarios to build complementary outcomes
Rigid adherence to siloed “best practices” kills this if every function insists on their own way of doing things, because the route to a decision becomes convoluted, and compliance starts to feel like too much work. But having one team “own” the process, the model, the governance introduces a new level of bias, with a suspicion that participation will somehow lead to the other teams “losing out.”
 
This is where a neutral framework like BIG is invaluable. It’s not just a Finance Model, a PMO Tool, or a Leadership Framework. It’s all those things, held together with a shared commitment to data-led decision-making.

Build Towards Dynamic Decision-Making

Prioritization usually starts as a project in itself, but long-term success lies in adoption—the progression from new initiative to “how we do things round here.” This is how we make prioritization systematic—and agile. There are practical skills people need to develop, hone, and embed:
  • Faster collaborative scoring to review projects.
  • Better estimates, with a learning loop for next time.
  • Clear selection capability, including tolerance for hearing “No” and “Not yet.”
With a solid data model, governance framework, and leadership commitment, it can become second nature, such that prioritization becomes a competitive advantage, offering greater productivity and agility to those organizations with the commitment to make it happen.
 
But not right away—making patience the critical fourth ingredient to success. Implementing this kind of re-wiring of your organisational brain is a Change Management challenge, so don't expect to succeed without bringing others on the journey.
 

Find the Metrics That Matter

Great organizations measure what matters, using KPIs as a drumbeat to focus decision-making and hold people to account for outcomes. For measuring Strategic Delivery, try these:
  • Decision Velocity – How fast can you make quality decisions?
  • Project Flow – How quickly do projects complete?
  • Benefits Realization – Are you delivering promised value?
  • Strategic Fit – Are all the goals of the strategy being effectively supported?
  • Forecast Accuracy – How close are estimates to reality?
Again, this is where tooling beats Excel-based improvisation every time. Structured data means teams can be held to account, performance managed upwards over time, and gains made from the process clearly measured and loudly celebrated.

Four Steps to Brilliant Prioritization

Are you ready to start this journey?
  1. Fix your data, find quick wins
    Build a prioritization model. Get a roadmap. Then keep going—this is the start, not the finish. A 90-day TransparentChoice pilot will help you achieve this.
  2. Think BIG
    Use frameworks from Business Integrated Governance to align processes across Finance, Strategy, and Delivery, to find ways to scale prioritization.
  3. Start small
    Build alliances that address one dimension at a time, one relationship elevated to a data-led process, one portfolio aligned, one planning cycle transformed.
  4. Get help
    Whether it’s facilitation, process design, or coaching, leverage experts who’ve done this before and will support your journey. We have a community of partners who can help.

Ready to Turn Noise into Outcomes?

Book a call with TransparentChoice to learn more about how to start your prioritization journey.
 
Quote BIG on the Form for a Deep Dive into the challenges of prioritization governance.