Project Portfolio Management (PPM)

Select and prioritize projects for the most value: the PPM process, scoring criteria, portfolio balance, and when to stop a failing project.

11 min read 7 sections Guide 12 of 13, Project Management Updated

New to this topic?

Read these first to get the most out of this guide:

Select
Do the Right Projects
Prioritize
Sequence by Value
Balance
Risk, Timeline, Type
Kill
Stop Low-Value Work

What Is Project Portfolio Management?

Project Portfolio Management (PPM) is the centralized management of an organization's collection of projects to achieve strategic objectives. While project management asks "Are we doing this project right?", portfolio management asks "Are we doing the right projects?"

VISIBLEHIDDEN
Cost of qualityThe cost of quality is an iceberg: scrap and rework above, the larger hidden part belowThe Cost of quality guide

In manufacturing, the portfolio typically includes capital projects (new lines, equipment), improvement projects (lean, quality, cost reduction), compliance projects (regulatory, safety), and IT/systems projects (ERP, MES, automation). The total demand for these projects almost always exceeds the organization's capacity to execute them, making selection and prioritization essential.

The Hidden Cost of Too Many Projects

Most manufacturing organizations have 2-3x more active projects than their resources can support. The result: every project takes longer because resources are split, context-switching destroys productivity, and nothing finishes on time. Critical Chain research shows that cutting the number of active projects in half can reduce average project lead time by 30-50%. Doing fewer projects faster creates more total value than doing many projects slowly.

The PPM Process

CAPACITY
Capacity planWeekly load bars rise against the capacity line; the overloaded week shows in tapeThe Capacity plan guide
Inventory All Projects & RequestsGather every active project, proposed project, and backlogged request. Include resource consumption (people, budget, equipment time). Most organizations are shocked by the total list when they see it for the first time.
Align to StrategyMap each project to one or more strategic objectives (from Hoshin Kanri or the annual operating plan). Projects that do not support a strategic objective should be questioned: why are we doing this?
Score & PrioritizeRate each project on consistent criteria: strategic alignment, financial return, risk, resource requirements, urgency. Use a weighted scoring model. Stack-rank the portfolio from highest to lowest value.
Assess CapacityCalculate total resource capacity (engineering hours, maintenance hours, capital budget, contractor capacity). Compare to total portfolio demand. Identify the constraint: the resource type that limits portfolio throughput.
Draw the LineWorking down the priority list, load projects until capacity is consumed. Everything below the line is deferred, not killed. It enters the backlog for future consideration. This is the hardest but most valuable step.
Balance the PortfolioCheck the selected portfolio for balance: short-term vs. long-term, high-risk vs. low-risk, growth vs. maintenance, across business units. Adjust the selection to ensure the portfolio is not over-concentrated in one area.
Execute, Monitor, & ReprioritizeTrack active projects monthly. Use EVM and buffer management for performance. Kill or defer projects that are no longer viable. As projects complete, pull the next-highest-priority project from the backlog.

Scoring Criteria

SafetyHazard tape lays across the aisle and the walkway lines mark the safe pathThe Safety guide
CriterionWeight (example)Scale
Strategic Alignment30%1-5: How directly does this support a strategic objective?
Financial Return (ROI / Payback)25%1-5: Expected return on investment relative to cost
Risk (inverse)15%1-5: Lower score = higher risk (technical, execution, market)
Urgency / Compliance15%1-5: Regulatory deadline, customer commitment, safety criticality
Resource Efficiency15%1-5: Value per resource-hour consumed

Portfolio Balance

A healthy portfolio is balanced across multiple dimensions:

The constraintOutput is set by the constraint; an hour lost there is lost for the systemThe constraint guide
DimensionBalance CheckRisk of Imbalance
TimelineMix of quick wins (<3 months) and strategic investments (6-18 months)All long-term = no visible progress. All short-term = no transformation.
RiskMix of safe, proven projects and innovative, higher-risk onesAll safe = stagnation. All risky = high portfolio failure rate.
TypeGrowth + maintenance + compliance + improvementAll growth = infrastructure decay. All compliance = no competitive advantage.
Business UnitProportional investment across divisions/plantsOne plant gets everything, others stagnate.
Resource TypeNo single resource type is overloaded beyond capacityEngineering bottleneck delays everything.

The Kill Decision

PROB.IMPACT
Project riskA risk sits high on the probability and impact grid; the response moves it downThe Project risk guide

Sunk Cost Discipline

The hardest portfolio management decision is stopping a project that has already consumed significant resources but is no longer viable. The sunk cost fallacy ("we've already spent $200K, we can't stop now") is the enemy of good portfolio management. The only relevant question is: "Given what we know now, is the remaining investment worth the remaining value?" If not, stop. Redirect those resources to higher-value work.

Kill or defer a project when:

TriggerAction
Strategic objective it supports has changed or been removedDefer or kill
Business case no longer viable (costs up, benefits down)Re-evaluate, likely kill
Critical technical risk has materialized with no viable solutionKill
Resource needs have grown beyond what the organization can supportDefer to a future period
A higher-priority project needs the same resourcesDefer the lower-priority project

PPM in Manufacturing

POWERINTEREST
StakeholdersA power and interest grid; stakeholders drift into their quadrantsThe Stakeholders guide
ApplicationPPM Value
Annual capital planningPrioritize capital requests across all plants using consistent criteria instead of "loudest voice wins"
Lean/CI program managementSequence improvement projects to maximize total savings and avoid overloading CI resources
Multi-plant operationsAllocate shared engineering and maintenance resources across facilities by portfolio priority
New product pipelineBalance NPI resources between products at different lifecycle stages

Good Portfolio Management

  • Review the full portfolio monthly, not just individual project status
  • Use consistent scoring criteria across all project types
  • Limit active projects to match resource capacity
  • Kill or defer projects that no longer deliver value: sunk costs are irrelevant
  • Connect portfolio priorities to strategic objectives

Common Mistakes

  • Approving every project that sounds good: no prioritization, just addition
  • Running 3x more projects than resources can support (everything is slow)
  • Using "first in, first out" instead of value-based prioritization
  • Never killing a project once started (sunk cost fallacy)
  • Managing projects individually without seeing the portfolio-level picture

Key Takeaway

The biggest leverage in project management is not running individual projects better. It is choosing the right projects to run. PPM forces the discipline of prioritizing, limiting work-in-progress, and killing projects that no longer make sense. In most manufacturing organizations, cutting the active project count in half and focusing resources will deliver more total value, faster, with less chaos. The portfolio management discipline of "do fewer things better" mirrors the TOC principle of focusing on the constraint, and it works for exactly the same reason.

Interactive Demo

Prioritize project proposals with weighted scoring. Find the best value projects for your budget.

Portfolio Prioritization Matrix

Weight the criteria to rank projects. Select which projects to fund within your budget. The scatter plot shows benefit vs cost — projects toward the upper left are the best value.

Criteria Weights
35%
0%100%
25%
0%100%
20%
0%100%
20%
0%100%
$1000K
2002000
Benefit vs Cost
Cost ($K)BenefitAutomation LineQuality SystemNew ProductEnergy EfficiencyWarehouse Expansion
Project Rankings
RankProjectScoreBenefitCostRiskFund?
1Quality System Upgrade77.87/10$120K3/10
2Automation Line 366.49/10$450K6/10
3Energy Efficiency64.35/10$200K2/10
4New Product Launch5310/10$800K8/10
5Warehouse Expansion50.86/10$550K4/10
Budget Utilization$0K / $1000K
0 / 5
Projects Funded
$0K
Total Investment
0
Total Benefit
WITHIN
Budget Status

Ready for the full knowledge check? Guided scenarios and data export. Included with every plan.

PlanTake the advanced knowledge check
Share this guide: LinkedIn X Follow SymplProcess on LinkedIn

Take this to a room

The running order

For leadership deciding what to fund. They should leave willing to draw a line and defer everything below it.

7 beats · 11 min
  1. 1

    List everything first

    Every active project, every proposal, every backlogged request, with its resource consumption.

    • Most organisations are shocked by the total when they see it in one place.
    • Include the informal projects that never went through approval.
    • You cannot prioritise a list you have not written down.

    Ask the room How many projects are actually running here right now?

  2. 2

    Ask what each one is for

    Map every project to a strategic objective. The ones that map to nothing are the finding.

    • If it supports no objective, ask why we are doing it.
    • That question is uncomfortable and it is the point of the exercise.
    • Some good answers exist. Most of the time there is no answer at all.
  3. 3

    Score consistently

    The same criteria for every project type, or the comparison is not a comparison.

    • Strategic alignment, financial return, risk, resources, urgency.
    • Weighted scoring, then stack-rank the whole portfolio.
    • Consistency matters more than sophistication in the model.
  4. 4

    Compare demand to capacity

    Total portfolio demand against total resource capacity. Identify what actually limits throughput.

    • Engineering hours, maintenance hours, capital budget, contractor capacity.
    • One of them is the constraint. That resource sets the portfolio's throughput.
    • Everything else is not the limit, however busy it looks.

    Ask the room What is our portfolio constraint?

  5. 5

    Draw the line

    Load projects down the priority list until capacity is consumed. Then stop.

    • Everything below the line is deferred, not killed: it goes to the backlog.
    • This is the hardest step and the one with all the value.
    • Running three times more projects than capacity means everything is slow and nothing finishes.
  6. 6

    Kill decisions

    Sunk cost is irrelevant. The only question is whether the remaining spend is the best use of the remaining capacity.

    • A project no longer delivering value should stop, whatever has been spent.
    • Never killing anything is how the active list grows to three times capacity.
    • Make killing normal and unembarrassing, or it will not happen.

    Ask the room Which of our active projects would we not start today?

  7. 7

    It is TOC for projects

    The connection is exact, and it explains why doing fewer things works.

    • Limit work in process, focus on the constraint, and throughput goes up.
    • Cutting the active project count in half usually delivers more total value, faster.
    • Review the portfolio monthly, not just individual project status.

    Ask the room Can we agree to defer everything below the line this quarter?