Project portfolio management: 13 best practices for 2027

Dr. Tassilo HenikeBy Dr. Tassilo Henike
13-Best-Practices-for-Effective-Project-Portfolio-Management-in-2025

Project portfolio management best practices come down to one discipline: decide on evidence, at a fixed rhythm, and move money fast. The 13 practices below cover four stages: select, fund, review, and stop. Teams that review priorities often cancel more projects and report higher returns. Stopping is the skill most portfolios lack.

Most project portfolio managers measure success by delivery. Projects ship on time, on budget, and the dashboard turns green. That view misses the bigger cost. The money sits in projects that should have ended two quarters ago.

The 2026 data points the same way. PMI's Pulse of the Profession 2026 reports that 31% of complex projects fail to achieve their full intended benefits. That rate is more than twice the rate for projects overall. Tempo's 2026 State of Strategic Portfolio Management surveyed 667 planning and PMO leaders. Respondents report that nearly one in three projects was cancelled or stopped early for misalignment or weak ROI.

Stage Best practice The test question
Select 1. Run one intake for every source Does every request enter through the same door?
Select 2. Score against strategy with fixed weights Would two reviewers rank the same project the same way?
Select 3. Balance horizons on purpose Does the mix match the target split?
Fund 4. Fund in tranches tied to gates Does each gate release only the next tranche?
Fund 5. Plan capacity before you approve scope Do the named people have the hours?
Fund 6. Map skills to the projects that need them Can you find the expert in one search?
Review 7. Review priorities monthly, budgets quarterly When did the portfolio last change?
Review 8. Replace status decks with a live dashboard How many hours go into the next steering deck?
Review 9. Report decisions over activity Which decisions did the last review produce?
Stop 10. Write kill criteria at approval Is the stop condition on record?
Stop 11. Give the gate board explicit decision rights Who can stop a project, in writing?
Stop 12. Reallocate freed budget within 30 days Where did the last stopped budget go?
Stop 13. Run a review on every stopped project What did the last stop teach the team?

Exhibit 1: 13 project portfolio management best practices at a glance

Here is the twist. Teams that review priorities frequently cancel 8 percentage points more projects. They also report about 8 points higher ROI. Effective project portfolio management treats stopping as a feature of the system. Every stop frees money for the right projects.

This guide is written for portfolio managers in R&D, product, and innovation, and for the project management office (PMO) that supports them. It builds on our guides to strategic portfolio management and R&D portfolio management.

The project portfolio management process in five steps

Every project portfolio management process runs the same loop. The project management office often runs the loop, close to program management. The portfolio management team owns the decisions. Teams track progress against business goals at every review. The 13 best practices sharpen each step.

  1. Clarify business objectives. Translate the organization's strategic objectives into three to five investment themes with target budgets.
  2. Capture project ideas and requests. Collect new projects through one intake process with the same minimum data.
  3. Evaluate and prioritize projects. Evaluate projects on financial and scoring criteria tied to strategic alignment. Then prioritize projects based on score and capacity.
  4. Validate portfolio feasibility. Check the tentative portfolio against resource capacity and budget before you commit. A tentative portfolio above capacity delays every project in it.
  5. Monitor and rebalance. Track portfolio performance with key performance indicators, so the portfolio remains aligned as markets shift.

Many organizations treat step five as a reporting exercise. Effective portfolio management turns it into a decision step. That shift explains most of the practices below. The loop exists to achieve strategic objectives with a limited budget.

Why effective project portfolio management starts with stopping

A project portfolio improves when weak projects leave it early. Every approval creates a claim on people and budget. Without regular stops, those claims pile up until strong new projects wait in line.

Project portfolio management (PPM) is the centralized management of all the projects a company funds against its strategic objectives. Project management delivers individual projects through project management processes such as planning and scheduling. Program management coordinates related projects toward one outcome. Portfolio management decides which projects deserve the people and the budget. Successful project portfolio management needs all three, with clear handoffs.

The data says stopping is the skill

Tempo's survey separates high performers from traditional planners. High performers report ROI or strategic value on 81% of projects. Traditional planning organizations report 45%. The gap tracks review frequency, integrated processes, and scenario planning.

Scenario planning users report ROI or strategic value on 17 percentage points more projects. PMI finds the same lever underused. About one in five practitioners use scenario planning today.

Both studies rely on self-reported data. The direction is consistent, though. Portfolios that look often and decide often keep fewer zombies.

Chart showing that teams reviewing priorities frequently cancel 8 points more projects and report 8 points higher ROI, and that high performers report ROI on 81% of projects versus 45%

Exhibit 2: Frequent reviewers stop more projects and earn more

Three symptoms of an overloaded project portfolio

Run three checks before changing any process.

First, count active projects per full-time equivalent in R&D. A ratio above one signals that people are managing multiple projects at once, and each one slows down.

Second, list projects older than their planned end date. Each one holds people a new project needs.

Third, ask finance how much budget moved between projects in the last twelve months. A number close to zero means the annual plan runs the portfolio, and strategy follows it.

Any of the three justifies changes to the project portfolio management process. All three call for a reset.

Project portfolio management best practices for selection and intake

Selection locks in most of the project portfolio's future cost. A project that enters on a weak case consumes reviews, people, and patience before anyone stops it. Tight project selection protects every later stage.

1. Run one intake for every source

Ideas, customer requests, technology scouting finds, and executive asks all compete for the same budget. Give them one intake form with the same minimum fields. Require a problem statement, an owner, a first cost estimate, and the business objectives it serves. Project managers and portfolio managers then work from the same project data.

One intake also exposes duplicates. Goldbeck saw this firsthand. Many departments scouted startups and ran pilots through parallel channels. People spent significant time working out who had talked to whom. A single view of all initiatives ended the duplicate work.

2. Score against strategy with fixed weights

Weighted scoring turns debate into comparison. It is the fastest way to prioritize projects on strategic alignment over sponsor seniority. Pick five to seven criteria, such as strategic fit, business value, urgency, risk, feasibility, and time to impact. Fix the weights for the year and publish them.

Fixed weights keep reviewers honest. A project sponsor can argue a score. Changing the weights for one project requires the whole board. Fixed weights also align projects with business goals across business units. For a deeper criteria set, use our guide to project prioritization.

3. Balance horizons on purpose

Scoring alone favors safe, near-term projects. They score high on feasibility and low on risk. Left alone, the portfolio drifts toward incremental work and low value projects.

Set a target split across horizons before scoring starts. The 70-20-10 model is a common starting point: core, adjacent, and transformational. Score projects within each horizon, then fill each bucket from the top.

Review the split once a year against business strategy and organizational goals. A company entering a new market may shift budget toward adjacent bets for two cycles. Document the change so the board scores against the new target.

ITONICS board showing initiatives by phase in columns and strategic objective in swimlanes, colored by health status

Exhibit 3: Initiatives by phase and strategic objective on an ITONICS board

Resource allocation practices that fund the right projects

Funding in one annual block locks money into last year's assumptions. Tempo's respondents name capacity as the top barrier to executing strategy, cited by 30%. Funding and capacity planning belong in the same decision.

Resource allocation decides which strategic priorities get done. Allocate resources to the highest value projects first. Fund the rest only when resource capacity remains. Optimizing resource allocation starts with an honest count of ongoing projects.

4. Fund in tranches tied to gates

Release budget per stage, sized to the next learning milestone. A concept phase gets enough to test the core assumption. A pilot phase gets enough to prove the business case.

Tranche funding caps the cost of a wrong bet. It also respects resource constraints, because each tranche names the people it needs. It also gives every gate a real decision, because money moves only when the evidence does. The stage-gate process supplies the structure.

ITONICS Workflow builder with project phases, gates, and an open gate configuration with reviewers

Exhibit 4: Phases and gates with gate configuration in the ITONICS Workflow builder

5. Plan capacity before you approve scope

A project approved without people becomes a project delayed by people. Capacity is a resource management question first. Before approval, name the critical roles and check their load for the next two quarters.

Use scenario planning here. Model the portfolio with and without the new project. Compare which existing projects slip. Leadership then decides with the trade-off in view. Resource managers and portfolio managers share one view of resource utilization, so resource constraints surface before project execution starts. Good resource management treats expert hours as the scarcest input in project work.

6. Map skills to the projects that need them

R&D portfolios depend on scarce experts. A battery chemist or a regulatory specialist often limits multiple projects at once, sometimes ten. Keep a skills map linked to project records.

When a new project arrives, search the map first. Assign the expert to the highest-scoring project and log the conflict for the rest.

The conflict log is portfolio data in its own right. Here the portfolio manager works closely with resource managers to balance workloads across multiple projects. A skill that blocks five projects every quarter points to a hiring or partnering decision. Bring that pattern to the annual planning round with numbers attached. Our article on R&D resource management covers allocation methods in detail.

Project portfolio review practices that produce decisions

A portfolio review earns its slot when it changes something. Track the share of reviews that end with a stop, a scale, or a reallocation. Reviews that only confirm status belong in a dashboard.

Regular portfolio reviews keep the portfolio aligned with business strategy as strategic goals shift. They are also where portfolio managers see the entire portfolio at once.

7. Review priorities monthly, budgets quarterly

Priorities shift faster than budgets. A monthly priority review catches projects whose context changed. A competitor launched first, a regulation moved, or a technology matured early. Each review checks every project against current strategic goals.

Budget changes follow at the quarterly review. This cadence lets the portfolio react within weeks. Portfolio management turns dynamic, while governance stays stable. It also keeps finance on a predictable rhythm. Quarterly reviews allocate resources between portfolio projects.

8. Replace status decks with a live dashboard

Project status decks cost hours and age by the meeting date. Most project portfolio management tools ship a dashboard for this. Build one portfolio dashboard in your project portfolio management software. Show phase, health, budget burn, and the next gate date. Project status and project performance come from records that project teams already update.

The board then spends meeting time on exceptions and makes data driven decisions. Every attendee sees the same numbers before the meeting starts.

Start with four widgets and resist adding more. Portfolio value by horizon, projects by phase, projects past their gate date, and budget burn against plan. Each widget should answer a question the board asks every month.

ITONICS portfolio dashboard with value forecast, pipeline by horizon, budget left, and costs per priority

Exhibit 5: Portfolio dashboard with pipeline by horizon and forecast value inside ITONICS

9. Report decisions over activity

End every review with a decision log. Record each stop, scale, start, and reallocation with its reason. Share the log with project teams and stakeholders within a day.

The log becomes the project portfolio's memory. New board members read it to learn how the board thinks. Project management teams read it to learn what evidence moves a decision.

Project portfolio governance practices for stopping projects

Governance decides whether stops happen. Most portfolios have the data to stop projects. They lack a rule that forces the decision and a person who owns it.

Portfolio governance also covers portfolio risk. Assess risk for individual projects and for the entire portfolio. Identify potential threats early, such as a single key supplier, a single expert, or a pending regulation. Ten projects that depend on one technology or one customer form a single bet.

10. Write kill criteria at approval

Set the stop conditions when the project starts, while the team is still neutral. Examples include a cost ceiling, a target customer test result, or a technology readiness level by a date.

At each gate, the board checks the criteria first. A project that misses them carries the burden of proof. Kill criteria protect strategic alignment long after approval. McKinsey goes one step further in its bias busters series. It recommends a dedicated reviewer who makes the case to stop each active project.

11. Give the gate board explicit decision rights

Write down who can stop a project, scale it, or move its budget. Name the board members and the quorum. Clear rights create accountability among stakeholders. PMI lists unclear governance as an organizational source of project complexity.

Explicit rights also protect project managers. A project manager who flags a weak result early faces the board, and the board owns the call. Our guide to innovation governance shows how to assign roles with RACI.

12. Reallocate freed budget within 30 days

A stop only creates value when the money moves. Freed budget that waits for the next annual cycle disappears into general spend. Tempo uses the term strategic drift for funding that stays locked while priorities move on. Fast reallocation restores strategic alignment.

Keep a ranked waiting list of approved but unfunded projects. When a project stops, the next one on the list starts within 30 days. Rank the list against strategic goals to align projects with the current strategy.

Project list with owners, costs, and status inside ITONICS

Exhibit 6: Project list with owners, costs, and status inside ITONICS

13. Run a review on every stopped project

Stopped projects carry the cheapest lessons in the company. Run a 45-minute review within two weeks of each stop. Capture what the team learned, which assumption failed, and what the next team should reuse.

Store the findings with the project record, so teams managing projects in the same field reuse them. Link them to the trends and technologies involved. The next project in the same field starts from evidence.

Celebrate good stops in public. A team that ends a project early on clear evidence saved the company money. Name that outcome in the portfolio review and in the decision log. People repeat what leadership rewards.

How to measure effective project portfolio management

Measure project portfolio management by decisions and business value, alongside delivery. The five key performance indicators below show whether the practices work. Track portfolio performance quarterly and show the trend on the dashboard.

Metric What it shows Starting target
Share of projects stopped per year Whether gates make real decisions 20% to 30% of active projects
Days from stop to budget reallocation Whether freed money moves 30 days or fewer
Share of portfolio by horizon Whether the mix matches strategy Within five points of target split
Active projects per R&D FTE Whether capacity matches approvals Below one
Hours spent on steering material Whether reporting is automated Down 50% in year one

Exhibit 7: Five KPIs for effective project portfolio management

The targets are starting points from practice. Adjust them to your industry cycle. A pharma discovery portfolio stops more projects than a consumer goods portfolio, by design. For more metric ideas, see our R&D KPI guide.

How ITONICS supports project portfolio management

ITONICS is strategic portfolio intelligence for enterprise R&D and innovation. It keeps projects, ideas, trends, and technologies as linked elements in one system. Portfolio decisions happen where the evidence sits.

ITONICS Prism portfolio review recommending which initiatives to stop, scale, or start

Exhibit 8: Prism portfolio review with stop, scale, and start recommendations

Project portfolio managers use it as project portfolio management software that connects strategic alignment with project execution.

  • Select. Every request enters as an element with the same configurable properties. Rating criteria and the Matrix compare projects on fixed weights. Excel import maps existing project lists into the system.
  • Fund and review. The Workflow builder defines phases and gates with criteria, assignees, and notifications. Capacity planning runs in Excel templates synced through the Smart Excel property. Kanban boards and dashboards show health and phase across the portfolio. Dashboards embed Power BI or Tableau, and PowerPoint export uses configurable templates.
  • Stop and reallocate. Prism, the ITONICS AI, reviews the portfolio and answers what to stop, scale, or start. Relations link each project to the trends and technologies behind it, so a changed signal flags the affected projects.

More insights on Strategy