Definition of lean portfolio management
The SAFe framework website (framework.scaledagile.com) defines lean portfolio management, abbreviated to LPM, as what “aligns strategy and execution by applying Lean and systems thinking approaches to strategy and investment funding, Agile portfolio operations, and governance”. The French equivalent is gestion lean de portefeuille. Our entry on SAFe presents the framework.
The status of the notion has changed on the site. The “Lean Portfolio Management” page makes it one of the seven core competencies of business agility. A notice at the top now points to the article “Lean Portfolio Management Discipline”, and the glossary places LPM among the five disciplines of the framework. This article, updated on 31 March 2025, is public and breaks the discipline down into nine competencies. The original page is only partly public: the rest requires an account and is not described here. Reading of 12 November 2026; the site’s home page refers to the SAFe 6.0 configurations.
A discipline geared towards strategy agility
According to the article, traditional portfolio management approaches were not designed for today’s uncertainty and pace of delivery. LPM aims there for “strategy agility”: sensing a market change, quickly applying a new strategy, and persevering with what works.
The elements of LPM, according to the site
| Element (original term) | What the site says about it |
|---|---|
| SAFe Portfolio | A set of value streams, under a single funding and governance model |
| Lean Budgets | The budget goes to value streams and not to projects; guardrails frame spending |
| Epics | Strategic initiatives; a minimum viable product (MVP) is tested before any full commitment |
| Portfolio Kanban | Makes the flow of epics visible, from idea to implementation |
| Portfolio Leadership | The team that holds the highest level of decision-making and financial accountability |
| Value Management Office (VMO) | The function that facilitates the LPM process and its governance |
Two events set the rhythm: the strategic portfolio review, generally quarterly and held at least a month before the next PI planning, then the portfolio sync, generally monthly. Performance is measured through OKRs and key indicators, reviewed at least every quarter.
Lean portfolio management and project portfolio management: not to be confused
Project portfolio management, or PPM, is a general discipline: it selects, sequences and re-examines projects, which have a start and an end. LPM is one framework’s answer to the same question, with different objects.
The article itself contrasts the two approaches: instead of project funding, value stream budgets adjusted along the way; instead of centralised intake of requests, a portfolio kanban; instead of phase gates, measures based on working solutions. This comparison is drawn up by the publisher, in terms unfavourable to the approach it calls traditional.
Example: a breakdown alert put to the test
Suppose a lift manufacturer whose digital portfolio brings together three value streams: the technicians’ application, the connected services of the equipment, spare parts. Each receives an annual budget, framed by guardrails.
An initiative is proposed: a breakdown alert sold to building managers. It enters the portfolio kanban as an epic, with its hypothesis. A minimum viable product, limited to one range of equipment, tests it. At the next strategic review, portfolio leadership reads the result, then reallocates part of the budget or removes the epic from the kanban.
Prioritisation criteria, reading of capacity, arbitration body: these mechanisms apply with or without a framework, and our page on project portfolio management describes how they are implemented. The choice of a framework is covered by our page on agile at scale.