Portfolio Operations Kaizen
Aligning Four Teams Through Problem Solving & Leadership Development
International Biopharma Company
The Problem We Had to Solve
This international biopharma company was operating in a highly complex portfolio environment, supported by four cross-functional teams—nearly 40 people working together during the Kaizen week.
The teams were smart, capable, and deeply invested in the work. But the system around them wasn’t helping.
Leaders were feeling the strain:
Accountability expectations weren’t clear or consistent
Communication across teams created friction and rework
Too much energy was spent reacting instead of improving
Governance conversations often surfaced issues late
Underneath it all was a leadership challenge:
Team leads were expected to act as strong delivery owners and challengers—but without a shared playbook, clear expectations, or consistent routines.
This wasn’t a “skills gap.” It was a clarity and alignment problem across a complex system.
How We Approached the Work
This Kaizen was designed to do two things at once:
Help teams solve real portfolio challenges
Strengthen how leaders showed up inside that work
Our Belief
Kaizen isn’t just about fixing problems—it’s about building capability
Leadership behaviors directly shape how work gets done
Complex systems require shared language, shared ownership, and shared expectations
What We Did
Before the Kaizen: Creating Focus
Before bringing 40 people into a room together, we slowed down to get clear. We:
Surveyed participants to understand their real, day-to-day experience
Identified common pain points around accountability, communication, and governance
Turned those insights into a small set of focused problem statements
Formed four clear teams with defined charters
This ensured the Kaizen week was focused, relevant, and grounded in reality.
During the Kaizen: Solving Problems Together
During the in-person Kaizen, the 40 participants worked in four teams, tackling real portfolio challenges in real time. The work blended:
Leadership development — trust, accountability, communication, and influence
Practical problem solving — applied directly to current work
Team-based Kaizen — designing better ways of working across teams
Daily coaching and reflection — reinforcing ownership and confidence
Rather than separating leadership from execution, leadership behaviors were practiced inside the work itself.
After the Kaizen: Sustaining the Shift
To make sure the work didn’t stop when the week ended, we supported the teams with:
30 / 60 / 90-day follow-ups
Clear roadmaps and ownership
Simple measures to track progress
This helped teams keep moving forward without slipping back into old habits.
The Results
What Changed in the Work
Clearer, more focused problem statements
Stronger ownership across teams
Earlier identification and escalation of risks
Less time reacting, more time improving
What Changed for Leaders
Leaders gained practical tools they could use immediately
Communication across teams became clearer and more consistent
Teams developed a shared language for problem solving
Confidence increased in navigating complex, cross-functional work
Participants shared:
“We explored new approaches to tackling tough topics and turned them into actionable solutions we can use in our daily work.”
“I really appreciated the practical tools. It wasn’t overly theoretical—it was immediately useful.”
“Your leadership during the workshop was tremendous and inspirational.”
Why This Worked
This Kaizen worked because it respected the complexity of the system.
Four teams, not silos
Real work, not case studies
Leadership expectations tied directly to daily execution
By blending Kaizen with leadership development, the organization didn’t just improve how work flowed—it strengthened how leaders showed up inside that work.
What This Means for Other Organizations
In complex environments, challenges rarely come from one broken process. They come from:
Unclear roles and expectations
Gaps in accountability
Leadership behaviors that aren’t fully supported
This case shows what’s possible when teams are given the structure, space, and coaching to solve problems together—at scale.
This work reflects how we approach improvement at The KPI Lab:
solve real problems, develop leaders, and build systems that can handle complexity.
Closing
What teams experience when people and process come together
If you’re facing a problem that feels:
Technically complex
Culturally hard to move
Politically sensitive
Bigger than any one team
That’s often a signal that process alone—or leadership alone—won’t be enough. We’d love to explore it with you.
No sales pitch. Just a thoughtful conversation about what’s possible when people and process move together.
