Lean Portfolio Management

Lean Portfolio Management: a portfolio that makes real trade-offs

Lean Portfolio Management is the mechanism that connects strategy to execution: what gets funded, in what order, and on what grounds work stops. Most set-ups fail for a simple reason: they are described in a framework and kept up to date by hand in spreadsheets. We design them with the people who make the trade-offs, then make them run in Clarity, Jira and Confluence.

The problem we deal with

In many organisations, teams have moved to agile ways of working while the portfolio has stayed in project mode. The symptoms are familiar.

Everything is declared a priority, and the portfolio takes on more initiatives than capacity can absorb.
Budget is allocated once a year to projects, while teams deliver continuously.
Portfolio forums spend their time rebuilding information instead of deciding.
Tracking relies on a spreadsheet kept by hand, wrong as soon as the person who maintains it is away.

The fourth symptom is not a detail. A Lean Portfolio Management system whose data is re-keyed does not survive its third quarter.

From strategy to portfolio

Lean Portfolio Management only makes sense if it applies a strategy. So we start with what is most often missing: strategic themes precise enough to make trade-offs, an investment split across those themes, and guardrails that say what each value stream can commit to without going back to committee. Without this step, the Portfolio Kanban sorts requests. With it, the Portfolio Kanban applies choices. These are the first links of the Strategy-to-Execution chain.

What we put in place

The decision framework. Value-based steering, strategic themes, the Epic lifecycle, a Portfolio Kanban with its entry and exit criteria, Lean Business Cases. WSJF prioritisation where it helps, run in workshops with the people who actually make the trade-offs.

Funding. Funding rules by value stream, capacity funding, participatory budgeting. Investment guardrails and stop criteria. This is the part finance looks at most closely, and we build it with them.

Governance forums and decision rights. Portfolio Sync, Strategic Portfolio Review, quarterly review. For each one: an agenda, the decisions expected, the participants and their mandate, aligned through a RACI for portfolio governance. A forum with no decision expected is an information meeting, and people stop attending.

Roles and the VMO. Epic Owner, Business Owner, Lean Portfolio Manager, and the VMO (Value Management Office) that keeps the system running between forums. We structure the roles and decision processes, support the people who hold them, and set up a community of practice so the system outlasts our involvement.

The connection to execution. A portfolio decision only counts if it changes what teams work on. Epics are broken down and linked to the backlogs of trains or teams, and execution results come back to the portfolio as facts. The operating model is what carries that connection from leadership to teams.

The tools. The system is represented in the tools already in place, object by object. Epic lifecycle and funding in the portfolio tool, Clarity, Planisware or another. The link to execution in Jira, Jira Align, Azure DevOps or Rally. The governance reference in Confluence. Portfolio views are built on source data.

What it has made possible

Large services group: a portfolio that can stop. Lean Portfolio Management was deployed across several portfolios, with Portfolio Sync, the Portfolio Kanban, governance, funding and tools. What changed was the decisions: initiatives above €1M can be stopped when they no longer support priorities, and initiatives with no strategic link are identified and dealt with. Read the case study

Financial institution: a model that lives in the tools. Lean Portfolio Management was designed in workshops, then built into Clarity and Jira: Epic lifecycle, WSJF, Portfolio Kanban, PI Planning, capacity funding and strategic steering. The model did not stay a document. It is represented in the tools the portfolio and the teams use every day. Read the case study

Our working rule

No steering view that needs continuous manual entry. Everything is fed automatically from source. If a data item cannot come from Jira or Clarity, we change the source or drop the view. See Tools & Data.

FAQ

Frequently asked questions

Do we need SAFe in place before introducing Lean Portfolio Management?

No. Lean Portfolio Management applies to any portfolio that has to choose between competing initiatives with limited capacity. It gives its full value when execution is organised in value streams, but value-based prioritisation and capacity funding can be introduced straight away.

What does capacity funding change in practice?

You no longer fund projects one at a time, with a budget and a team to assemble for each. You fund value streams with stable capacity, and decide what that capacity works on first. Investment decisions become more frequent and lighter.

We already use Clarity. Can it carry Lean Portfolio Management?

Yes, in most cases. Clarity handles financial and capacity governance with a depth few tools have. The work is to represent the Epic lifecycle, prioritisation and funding in it, and to connect it to Jira for execution.

How long does it take to put in place?

Three to six months for Lean Portfolio Management that runs: portfolio governance, capacity funding, governance forums, and the tools that serve them.

We have not staffed a VMO. Is that a blocker?

No. We have built a Lean Portfolio Management system in that situation, then supported the VMO team that took it over.

Related expertise

Go further

A portfolio that will not make trade-offs

Describe your current governance in a few lines. We will tell you what can run in your tools, and what will not.

Describe your governance