Lean Portfolio Management

Traditional portfolio management was designed for a world of annual budgets, predictable requirements, and stable technology. It works like this:

1. Business submits project proposals annually
2. A governance board evaluates proposals and funds winners
3. Projects get fixed budgets, timelines, and scope
4. Progress is measured against the original plan
5. Projects are declared "done" when the budget runs out

This model has deep problems in a world of rapid change:

Project funding creates perverse incentives: Teams inflate estimates to get bigger budgets. Money is spent to "use it or lose it." Starting many projects simultaneously (to justify headcount) creates massive WIP that slows everything down.

Fixed scope prevents learning: If you fund a project for 12 months with fixed requirements, you can't adapt when you learn that the market has shifted. You deliver what was planned, not what's needed.

Cost accounting distorts decisions: When each project carries its own costs, teams hoard resources. Sharing a developer between projects requires complex cross-charging. The overhead of tracking costs exceeds the value of the information.

Project completion is a fiction: Software products are never "done." They need ongoing development, maintenance, and evolution. The project model pretends otherwise.

Lean Portfolio Management replaces this model with one designed for continuous flow: fund value streams (not projects), use guardrails (not gates), and measure outcomes (not output).

Lean Portfolio Management operates across three dimensions:

1. Strategy and Investment Funding

This is about connecting business strategy to execution through investment allocation:

• Strategic themes define the business direction (e.g., "Expand to European markets," "Reduce operational cost by 30%")
• Portfolio budget is allocated to value streams, not projects
• Guardrails define spending boundaries (e.g., "70% on existing products, 20% on new capabilities, 10% on exploration")
• Lean budgets give value streams funding for a period (typically PI or quarterly), not for specific deliverables

2. Agile Portfolio Operations

This is the day-to-day management of epic flow:

• Portfolio Kanban visualizes and manages the flow of epics
• Epic Owners shepherd epics through analysis, implementation, and measurement
• WSJF prioritization sequences epics by economic value
• Lean Business Cases replace heavyweight business cases with lightweight, hypothesis-driven proposals

3. Lean Governance

This replaces traditional phase-gate governance with continuous, lightweight oversight:

• Spending guardrails instead of project-level budget approvals
• Dynamic budgeting adjusts funding based on results, not annual cycles
• Objective milestones based on working software, not document reviews
• Continuous compliance built into the development process, not bolted on at the end

These three dimensions work together. Strategy defines direction, operations executes it, and governance ensures alignment and compliance.

Starting with Lean Portfolio Management requires significant organizational change. Here's a practical approach:

Start with visibility: Before changing anything, make current investment allocation visible. Where is the money going? How much is going to new development vs. maintenance? How many initiatives are in flight? Most organizations are shocked by the answers.

Identify value streams: Map out how value flows from idea to customer. Value streams are the organizational unit for funding—not departments, not projects, not teams. This is often the hardest step because it challenges existing organizational boundaries.

Pilot with one portfolio: Don't try to transform the entire organization at once. Pick one portfolio (a group of related value streams) and pilot LPM practices. Learn, adapt, then expand.

Shift to Lean budgets gradually: You don't have to eliminate project funding overnight. Start by allocating a portion of the budget to value streams while keeping some project funding. Shift the ratio over time as the organization builds confidence.

Measure outcomes, not output: Define business outcomes for each value stream and measure them. Revenue growth, customer satisfaction, operational efficiency—whatever matters. Stop measuring lines of code, story points, or number of features delivered.

The biggest obstacle to LPM isn't process—it's politics. People who control project budgets have power. Shifting to value stream funding redistributes that power. Expect resistance and plan for change management.