CASE STUDY: LEAN PORTFOLIO MANAGEMENT
Four Years of “Not Yet.”
Live in 45 Days.
How a global data center company finally got a clear view of an eight figure portfolio, after leadership had turned the idea down every year.
“During the LPM rollout, we took what could have been a dense, top-down framework and made it land with busy teams, turning complexity into steps people could act on, listening first, and building trust.”
PMO Portfolio Director, Global Data Center CompanyAT A GLANCE
A Fortune 500 portfolio, finally visible.
Client: Fortune 500 global data center company
Engagement: More than four years of enterprise agile coaching at the team, program, and portfolio levels, followed by an interim leadership role
Focus: Lean Portfolio Management for an eight figure portfolio
SIG team: Dr. Josh Stephens and Kari Kennedy
Time to a working portfolio: 30 to 45 days
BY THE NUMBERS
50+ work items
Pulled into one view in Jira within the first few days.
About 20% paused or cancelled
Triaged out within the first few weeks, before engineering hit the wall.
Months to days
Investment decisions that used to take months, or got forced, now take days.
1 portfolio, then 3
The client scaled it to three portfolios on their own, with more underway.
THE CHALLENGE
Everyone could feel the problem. Nobody could see the work.
For four years, we coached this organization’s teams, programs, and portfolios. Every year, Lean Portfolio Management came up at least once, and every year leadership decided it was not the right time.
That changed when Dr. Josh Stephens stepped into an interim leadership role inside the organization. From the inside, the cost of going without it was obvious. Work was assumed to happen. Nothing got stopped until engineering raised a red flag that they did not have the capacity. Mandatory regulatory work and nice to have requests were hard to tell apart, which created real regulatory risk. Peers, customers, and team members kept raising the same concerns.
No transparency
Leaders could not see what was being worked on, or why.
Invisible dependencies
Hard to see, and even harder to manage.
No single view of the work
Work lived in too many places to add up.
Capacity could not be allocated
New work, regulatory work, and existing commitments were all mixed together.
Decisions without data
Investment and roadmap calls were made without the information to back them up.
Unclear decision rights
Nobody could say for sure who should decide where money went, or what came next.
WHAT WE DID
Start small. Prove it fast. Then scale.
We started within three weeks. No waiting for the next annual planning cycle. We partnered with one of the organization’s portfolio managers, a strong communicator who picked up the concepts quickly, and got to work.
We built an incremental lean business case. Anyone with an idea could submit a short hypothesis: the work they thought was needed and the value they expected it to deliver. As an idea moved through the funnel into analysis, the business case grew with it, adding detail only as the work became more likely to happen. Good ideas got a fair hearing without a heavy process up front.
We put 100% of the portfolio’s work in one place. Within the first few days, more than 50 work items were in Jira. For the first time, leaders could see everything in flight and everything coming next in a single view.
We gave a small group the authority to decide. A small group of leaders took ownership of go and no go decisions, using a clear, documented process. Finance had a seat at the table, so upcoming projects and costs were visible before money was committed. Engineering leadership had a seat too, so new work and must do regulatory work could fit around the teams’ existing roadmaps and real capacity.
We proved it on one portfolio, then scaled. The organization had about 12 portfolios. We set the pattern in one, showed it worked, and then began rolling it out to the rest. Because Dr. Stephens is a certified SAFe Program Consultant (SPC), we delivered SAFe Lean Portfolio Management training to the portfolio managers, so every rollout followed proven practice while still fitting how this organization actually works.
THE RESULTS
Running in 30 to 45 days. Still growing without us.
Visibility leaders had never had. Portfolio leaders could see what was happening now and what was coming next, in one place.
About 20% of the work stopped early. Within the first few weeks, roughly one in five work items was moved to hold or cancelled outright. Those decisions were made on purpose, before the work collided with commitments that could not move.
Decisions in days, not months. Investment decisions that used to drag on for months, or got forced at the last minute, now take days.
Must do work protected. Regulatory and mandatory work was separated from nice to have requests, which lowered regulatory risk and gave engineering a realistic plan.
Practically zero added cost. The client already had Jira. This was a change in process and how people worked together, not new tools, new roles, or an expensive consulting program.
It lasted. The first portfolio leader has since scaled Lean Portfolio Management to three portfolios on their own, and the other portfolio managers were actively rolling it out when our engagement ended.
IN THEIR WORDS
From the leaders who did the work with us.
“During the LPM rollout, we took what could have been a dense, top-down framework and made it land with busy teams, turning complexity into steps people could act on, listening first, and building trust.”
PMO Portfolio Director
Global Data Center Company
“Rather than imposing a one-size-fits-all framework, he took the time to understand each team’s maturity level, culture, and pain points, then tailored his coaching accordingly. This made his guidance feel practical and achievable rather than theoretical, which is a big reason adoption stuck rather than fading after the initial push.”
Director, Technical Program Management
Global Data Center Company
The idea was never the problem. This organization had talked about Lean Portfolio Management for four years. What made the difference was starting small, partnering with a leader who believed in it, and proving value in weeks instead of waiting on a big approval for a full rollout.
Start the ConversationIs your portfolio stuck
at “not yet”?
Bring us the messy version. We will help you find the smallest place to start and prove value in weeks.