The 3 Pillars of Project Prioritization

To optimize limited resources and aim them at the most meaningful work, you first need reliable visibility into demand and capacity. That was the subject of my last article.

The next thing you need is to understand which work is most important, since few organizations are blessed with the capacity to deliver everything they want right away.

That's the subject of this article: prioritization.

I've seen project prioritization fail in three predictable ways:

• Overly complex: months spent inventing fifteen scoring criteria.

• Overly burdensome: trying to rank 3,282 projects sequentially.

• Overly simplistic: reducing everything to a 1, 2, or 3.

If you’ve ever sat through a prioritization exercise, you’ve probably seen at least one of these patterns.

The truth is, prioritization isn't easy, but it can be made practical. As Albert Einstein said, "Everything should be made as simple as possible, but not simpler."

In my Capacity Quadrant™ model, Visibility tells you what’s on the table and how much capacity you truly have. Prioritization tells you what deserves that capacity first. Without both, you either optimize the wrong work or make capacity decisions in the dark.

A practical framework is to use three primary lenses of information as input—not as a magic calculator that spits out “the answer.” Together, they give you a three‑lens, one‑priority view of the work, as shown in the diagram above.

• Strategic Alignment – Start with where the organization is trying to go.

  • Which objectives and strategies does the program or project support?

  • Does it advance critical outcomes or nice‑to‑have improvements?

  • How clearly can you trace the line from this initiative to your stated goals?
    

• Project Scoring – Then look at how the project performs against agreed‑upon comparison metrics. Typical criteria include:

  • Benefit scores (strategic fit, financial return, competitive advantage, operational efficiency, quality, probability of commercial success).

  • Risk scores (technical complexity, program complexity, skill gaps, resource scarcity).

  • Financial metrics (IRR, ROI, NPV).

  • Urgency and regulatory or customer commitments.
    

• Project Categorization – Finally, make sure you’re comparing apples to apples—and deciding explicitly when oranges matter more.

  • Which categorizations (business unit, project type, impact type, region, risk level, sponsor, etc.) help you group similar work?

  • Are you reviewing growth initiatives against other growth initiatives, regulatory must‑dos against other compliance work, and maintenance against maintenance—and consciously deciding when a “regulatory orange” should outrank a “growth apple” based on your current goals? In some seasons, a particular business unit, a strategic program, or even a fast‑moving competitive response deserves to sit higher in the bowl.

What do we do with all this?

The idea is to use this holistic input to assign a priority band to each project (for example 1000, 2000, 3000, 4000), with the 1000 band containing the most important work. Within a band, you only rank projects when they are competing for the same scarce resources or deadlines.

Priority becomes the tie-breaker when you’re allocating scarce capacity. Higher-priority projects get first claim on coveted skills and funding, and many resource management tools can automatically favor higher bands when scheduling.

Who actually owns project prioritization in the organization?

In most organizations, prioritization is a governance responsibility, not an individual project manager’s job. A portfolio review board (or equivalent steering committee) is usually best positioned to weigh trade‑offs across business units and initiatives.

Sponsors advocate for their projects—exactly as they should—but if each sponsor is allowed to set priorities in isolation, everything becomes "highest priority," and the system breaks. The board’s role is to apply the three lenses consistently, make explicit trade‑offs, and protect capacity from being overcommitted by local decisions.

At the same time, good scoring depends on good inputs. Financial metrics like IRR or NPV typically come from the business case and the sponsoring team. Likewise, the people closest to the work are usually best placed to articulate benefits and risks. The trick is to use smart scores—clear scoring rules and ranges—so a “1, 3, or 5” reflects defined thresholds (for example, specific IRR bands or qualitative descriptions of risk) rather than whoever argues loudest in the meeting.

One of the best risk/benefit models I’ve seen took this approach:

• Start with a handful of critical dimensions (for example scope stability, clarity of business benefits, delivery timeliness, budget health, stakeholder engagement, and unresolved risks).
  

• For each dimension, define what high risk, medium risk, and low risk look like using specific thresholds (e.g., “delays >15% of key milestone lead time” vs. “on‑time or <10% delay,” or “costs >15% over budget” vs. “within 5% of budget”).
  

• Score each dimension using a simple scale (1–5 or red/yellow/green), based on those thresholds—not on gut feel.
  

• Combine the dimension scores using straightforward rules (for instance, “if any dimension is high risk, treat the overall risk profile as high”) so you can quickly spot projects that need attention.

This kind of structure is what I mean by smart scores. Instead of arguing whether a project “feels like” a 1, 3, or 5, you define the bands in advance—quantitative ranges for metrics like IRR, and qualitative descriptions for risk factors—so sponsors and reviewers know exactly what each score represents.

Using priority bands in portfolio review

In a well‑run portfolio review meeting, the three lenses become the backbone of the conversation, rather than a slide you gloss over:

• Start with strategic alignment: which objectives are under‑served, and which proposed initiatives actually move those needles?
  

• Look at the scoring next: which projects consistently land in the top bands when you balance benefit, risk, and financial return?
  

• Use categorization to make fair comparisons—review growth initiatives with other growth initiatives, regulatory work with other regulatory work, and so on.

Once the board agrees which projects belong in the 1000 band, discussions about “which projects sit above the line” (that is, approved and funded) shift from politics to solid principles. You only drill into sequential ranking by exception when two projects in the same band are directly competing for the same scarce skills, funding, or time window.

Creating Better Capacity Conversations

When you combine Visibility with Prioritization, capacity conversations change. Instead of asking, “who shouts the loudest?” you ask, “which work advances our strategy, clears risk, and delivers value sooner?” The remaining elements of the Capacity Quadrant build on that foundation—how you schedule, staff, and adapt in the face of change—but none of that works if you don’t know what matters most.