TL;DR
A portfolio review can have an accurate dashboard and still be unable to say why one project was funded ahead of another. The fix is funding discipline, not better reporting. Funding discipline is the authority, the evidence, and the willingness to start, continue, redirect, or stop a project.
What the paper develops
A portfolio review can have an accurate dashboard and still be unable to say why one project was funded ahead of another. Every project has a status color, a milestone date, and a budget line. The members leave informed, but no one can point to evidence that compared the projects. This paper argues that such a review needs funding discipline, not better reporting. Funding discipline is the authority, the evidence, and the willingness to start, continue, redirect, or stop a project. The claim follows from how the Project Management Institute defines portfolio governance: a group that makes decisions about investments and priorities. Reporting is the first half of that job. A review can finish it and never start the second.
A review needs three things in order to decide. Its members need the authority to move money and people, not only recommend. They need evidence that lets them compare projects, which is hard because projects sit at different stages and compete for the same resources. They also need the willingness to stop a project that is visible, sponsored, and already expensive. Authority and willingness belong to the executives on the review. Evidence is the one a portfolio management office (PMO) can mostly build. A question tests a review: could it have changed what a project received, and did it? If every project deserves what it asked for, a review will change little, so a no is a prompt to find which of the three was missing. The paper does not score a review by its number of stops.
The paper's remedy is one page that every project files each time it asks for money or people. It gives the outcome and the evidence that it is changing, the value expected and shown, the capacity the project holds, the criteria for stopping or redirecting it, and the owner. The PMO keeps that page comparable, keeps a ledger of the scarce people each approved project holds, and keeps a record of what each review decided. The paper also covers where the argument is weaker: a PMO without backing from the member who runs the review, a page that favors what can be measured, and sources that do not show what weak funding discipline costs.
What to do next
Before the next review, collect one page from each project that asks for money or people. Afterward, ask of each project: could this review have changed what it received, and did it?
Inside the white paper
- The three things a review needs in order to decide: authority, evidence, and willingness
- A question that tests a review without counting stops
- The page every project files, the capacity ledger, and the decision record the PMO keeps
Sources and notes
- Project Management Institute, The Standard for Portfolio Management, Third Edition, 2013 — PMI's standard defines portfolio governance as a governing body making investment and priority decisions, describes the review meeting as the place to decide, and lists the roles a PMO may take; it is a professional standard, not a study of outcomes.
- Stephen Hall, Dan Lovallo, and Reinier Musters, "How to Put Your Money Where Your Strategy Is," McKinsey & Company, March 1, 2012 — McKinsey's study of 1,616 US-listed companies found the capital each business unit received correlated 0.92, on average, from one year to the next; it measures business-unit capital, not projects. It also found higher shareholder returns for top-third reallocators over 15 years and lower returns for heavy reallocators over spans under three years.
- Robert G. Cooper and Scott J. Edgett, "Portfolio Management: Fundamental for New Product Success," Stage-Gate International — Cooper and Edgett define portfolio management as a dynamic decision process and note that projects at different stages must be compared on different amounts of information; it is a practitioner account, not a measured result.
- Dustin J. Sleesman, Donald E. Conlon, Gerry McNamara, and Jonathan E. Miles, "Cleaning Up the Big Muddy: A Meta-Analytic Review of the Determinants of Escalation of Commitment," Academy of Management Journal 55(3), 2012, 541–562 — A meta-analysis of 35 years of escalation-of-commitment research links personal responsibility for the original choice to more escalation; most of the studies cover individual decisions, not review groups.
- Bent Flyvbjerg, "Quality Control and Due Diligence in Project Management," 2013 — Flyvbjerg reports that front-end estimates of cost and benefit often differ significantly from actual results, drawing mostly on large transportation projects, and proposes checking a proposal against similar completed projects.
- Johannes-Tobias Lorenz, Joshan Cherian Abraham, Robert Levin, and Douglas Ziman, "From promise to impact: How companies can measure—and realize—the full value of AI," McKinsey & Company, April 24, 2026 — McKinsey's article describes recurring evidence packs and decision gates for AI use cases, with only those that prove value advancing to scale; it is a consulting argument, not a measured result.