From Bottlenecks to Breakthroughs: How Resource Visibility Transformed a Pharma Services Portfolio

For this organisation, success depended on one thing: delivering innovation for Big Pharma on time. Working in the pharmaceutical services sector, they were paid to run complex development programmes for some of the world’s largest drug companies. Their business model was clear — they were paid to run development programmes, supplying high-value analytics and development services that pharmaceutical giants depended on.

Individually, their projects looked successful. Timelines were managed, milestones ticked off, deliverables achieved. But underneath the surface, the portfolio was in crisis. Resources clashed. Projects pulled people and critical equipment away from each other. Lead times stretched. Service levels dipped. And the business was haemorrhaging efficiency.

As one senior leader reflected: “It was the watermelon effect – outside every project looked green, but inside the overall portfolio was red.”

The challenge wasn’t incompetence — it was invisibility. Without oversight of resources across the suite of projects and activities, the organisation couldn’t balance competing priorities, invest wisely, or grow with confidence.

Oliver Wight was brought in to turn blindness into visibility. What followed was a transformation: from resource firefighting to portfolio foresight.

The brief: Delivering for Big Pharma under pressure

The organisation’s reputation rested on its ability to deliver reliably for some of the world’s largest pharmaceutical companies. If projects slipped, the clients didn’t just lose patience — their own solutions pipeline stalled.

The problems were acute:

• Resources were continually pulled from one project to another, delaying progress in innovative new solution offerings
• High-cost equipment was bottlenecked, with no process for prioritisation
• Uncertainty in incoming demand created instability, forcing constant reallocation
• Service levels dipped, lead times stretched and client confidence faltered
• Leadership struggled to decide where to invest — in people, analytics, or new equipment

One project manager admitted at the time: “We thought we were in control, but we were constantly distracted. Other priorities would pull our resources and delays crept in everywhere.”

The challenge: Resource chaos behind project success

At first glance, the company appeared effective. Customer projects hit milestones. Deliverables were completed. But behind the numbers, the story was different:

• No portfolio visibility – projects were tracked in silos, leaving leadership blind to the overall resource picture.
• Competing priorities – urgent projects cannibalised resources from others.
• Uncertainty of demand – new projects arrived without warning, stretching people and equipment.
• Delayed service – clients experienced longer lead times and reduced service levels.
• Investment blind spots – no clear framework for CapEx or analytics investment.

As the Oliver Wight Partner Birgit Breitschuh explains: “While individual projects were going fine, the challenge was how to use resources across the whole portfolio. Without oversight, they were always reacting — never in control.”

Our approach: From diagnostic to discipline

Step 1: Diagnostic — exposing the blind spots

The diagnostic was blunt. Resource shortages weren’t occasional — they were systemic. Every time a new project came in, people and equipment were pulled from elsewhere, creating delays across all projects.

Individual projects might still look “green” on paper, but this masked a deeper truth: the portfolio was stretched to breaking point. Delays were mounting, service levels were slipping and uncertainty in incoming demand meant future requirements were invisible.

As Oliver Wight Partner Les Brookes observes: “Individual projects that were going well then got delayed because resources were pulled somewhere else. Constant changes and uncertainty in demand led to longer lead times and lower service levels.”

Birgit sums it up: “The gaps were: lack of visibility of the resources required to deliver all programmes on time — and the impact of future requirements, albeit not yet defined.”

Step 2: First sprint — build control

Our first intervention was practical and urgent. The initial sprint established robust resource requirement visibility across all activities, giving leaders the ability to see, for the first time, where resources were tied up and where clashes were looming.

This wasn’t just about people. It was also about high-cost equipment — analytics and development machinery whose investment was significant, but which too often became bottlenecks. Without visibility, projects tripped over each other, wasting expensive assets and delaying client delivery.

Alongside visibility, the sprint introduced prioritisation criteria: clear decision rules to allocate resources fairly and consciously when demand spiked.

“We created visibility across all programmes — people and kit,” explains Birgit. “That allowed leaders to make decisions on when to add resource, how to balance priorities and how to stop projects from cannibalising each other.”

Step 3: Coaching and embedding (four months)

The team didn’t just design the new process — they stayed to embed it. Over four months of coaching, leaders learned how to apply the new discipline week by week, building confidence in portfolio-level decisions.

The effect was immediate. Delivery delays began to ease. Service levels rose. And for the first time, leaders could see not just where resources were stretched, but where capacity could be freed up. As Birgit notes: “The result was shorter lead times, more initiatives developed and freeing up resources for their own internal innovation.”

In other words, stability didn’t just improve client delivery — it created space for the organisation’s own R&D priorities, which had long been sacrificed to firefighting.

Step 4: Second engagement — building foresight

With the basics under control, the second engagement looked forward. Now that the organisation had visibility across current programmes, the question became: where should we invest next?

Oliver Wight helped leadership build foresight into upcoming portfolio requirements, aligning resource planning with strategic investment choices. Should they invest in analytics? Development resources? High-cost equipment? With clarity on demand and capacity, these choices could finally be made proactively, not reactively.

“It was also about choices of where to invest — analytics or development resources or assets — and aligning CapEx and workforce management,” says Birgit.

This phase gave the business something it had never had before: the confidence to grow strategically, with the right people and equipment in place ahead of demand.

Key findings: From Method to Meaning™

The data wasn’t the real issue. Behaviours were. Managers optimised for their own projects, not the portfolio. Success was measured locally, not systemically. The result was predictable: projects appeared green, but the overall portfolio was delayed, inefficient and unstable.

The new process changed that. By creating visibility across programmes, people were forced to confront the truth — and make conscious trade-offs. As one executive reflected: “We realised our problem wasn’t doing projects badly. It was doing too many well — at the cost of everything else.”

This was the shift from Method to Meaning™. Resource management became more than scheduling. It became a shared discipline that linked operational success to business growth.

The journey: From firefighting to foresight

The transformation didn’t happen overnight. It unfolded in a series of deliberate steps, each building on the last to shift the organisation from reactive chaos to confident foresight.

Short-term sprint – creating stability

The first sprint gave leaders what they had never had before: true visibility of resources across the entire portfolio. Suddenly, they could see which projects were competing for the same people and equipment, where bottlenecks would occur and what the knock-on effects would be. For high-cost assets — advanced analytics machines and development kit — this visibility was critical. Instead of projects tripping over each other and wasting capacity, they could be planned and prioritised consciously. Portfolio visibility stabilised the eco-system almost immediately.

Coaching and embedding – building confidence

The next step was to make the new discipline stick. Over four months of coaching, we worked with managers to embed weekly and monthly cycles of review and adjustment. These forums created rhythm and structure: instead of firefighting daily crises, leaders came together regularly to make portfolio-level decisions. This not only built confidence but also changed behaviours. Decisions were no longer about protecting individual projects, but about balancing the needs of the whole portfolio. Leaders began to act with foresight, not fear.

Longer-term growth – planning for the future

With stability in place, the organisation could finally look ahead. The second engagement focused on foresight: visibility of future portfolio requirements and alignment of investments in people and capabilities, analytics and equipment. Leadership could now make proactive decisions about CapEx and workforce strategy, ensuring resources were in place before demand hit. This gave the business the ability to scale sustainably, to take on more projects without breaking the system and to grow profitably with confidence.

Birgit notes: “It was about creating prioritisation criteria, resource visibility and managing uncertainty. Once leaders could see the whole picture, they stopped firefighting and started planning.

Results and benefits: Early wins, lasting impact

The outcomes were tangible and significant:

• Efficiency gains – resources were optimised across projects.
• On-time delivery improved – service levels rose, client satisfaction increased.
• 20% more projects delivered – with the same resources, capacity expanded dramatically.
• Profitability up 2–2.5% – efficiency flowed directly to the bottom line.
• Lead times reduced – development times cut by months, reducing time to market.
• CapEx alignment – better decisions on analytics and development equipment.
• Planning stability – resource allocation became predictable, not reactive.

One senior leader described the cultural shift: “Before, we were blind. Now we can see across everything. We can grow without breaking.”

Beyond process: Why it mattered

For the organisation, the real breakthrough wasn’t just fixing today’s delays. It was creating a capability for tomorrow.

By embedding visibility of future service portfolio offering and resource discipline, leaders gained the confidence to look ahead — not just to the next project, but to the future shape of the business. With clear sight of upcoming demand, they could align CapEx and workforce strategy, investing in the right analytics, development equipment and people at the right time. Decisions that were once reactive became deliberate, strategic and growth-oriented.

The impact was profound. With the same resources, the business could deliver up to 20% more projects, raising efficiency, reducing lead times and improving service levels across the board. Profitability rose by an estimated 2–2.5%, creating both financial headroom and client confidence. They also progressed their own innovation pipeline successfully.

“Once leaders could see the whole picture, they stopped firefighting and started planning,” says Les.

This wasn’t just operational improvement. It was strategic capability — the ability to take on more work, serve more clients and grow profitably without breaking the system.

From firefighting to foresight.

From short-term fixes to long-term growth.

From resource bottlenecks to portfolio control.

In short: a platform for profitable, sustainable expansion in one of the most demanding industries in the world.