A mid-market pharmaceutical operator had reached the point where growth was beginning to expose the limits of the organization beneath it. Revenue had increased, the product portfolio had expanded, customer relationships had multiplied and the company was managing significantly more operational complexity than it had only a few years earlier.

But internally, much of the organization was still operating through structures designed for a smaller business.

Responsibilities overlapped. Senior leaders remained involved in decisions that should increasingly have sat elsewhere. Information moved unevenly across functions, while commercial, supply-chain and operational priorities were not always synchronized.

The business was growing.

The operating model was struggling to grow with it.

The challenge

Initial work with the leadership team focused on understanding where growth was creating organizational strain.

The company did not have a performance problem in the conventional sense. It had capable people, valuable products, established customers and a viable commercial platform.

The issue was structural.

Growth had gradually introduced more customers, more products, more dependencies and more decisions without a corresponding redesign of how the business worked.

Senior management had become an escalation point for too many routine issues. Functional responsibilities frequently crossed over. Teams were highly active, but activity did not always translate into coordinated execution.

Commercial decisions could be made without sufficient visibility into supply-chain implications. Operations frequently responded to immediate requirements rather than a shared forward plan. Leadership meetings moved between strategic questions and operational troubleshooting.

The organization was carrying more complexity than its operating architecture could efficiently absorb.

Diagnosing the real constraint

Sabah approached the engagement by looking at the organization as an operating system rather than simply an organizational chart.

The question was not:

Who should report to whom?

It was:

What does this business need to be able to do reliably at its next level of scale?

That distinction was important.

A conventional restructuring could have changed reporting lines without materially changing how decisions, information and work moved through the organization.

Instead, I examined four areas:

• where decisions were being made;
• where accountability was becoming diluted;
• where information or work repeatedly stalled between functions; and
• which activities were absorbing disproportionate leadership attention.

The analysis revealed a recurring pattern.

The company had scaled commercial activity faster than management infrastructure.

Redesigning the operating model

The transformation began by clarifying what different parts of the business needed to own.

Responsibilities were reorganized around outcomes rather than historical task ownership.

Commercial teams were given clearer accountability for customer development, revenue generation and pipeline quality.

Operations became more explicitly responsible for execution capacity, workflow discipline and service reliability.

Supply-chain responsibilities were connected more closely to demand planning and commercial forecasting rather than remaining primarily reactive.

Leadership responsibilities were also tightened.

Instead of allowing senior executives to remain involved in every material operating issue, clearer decision thresholds were introduced so that routine decisions could sit closer to the people responsible for delivering the outcome.

This began moving the company from a person-dependent model toward a system-dependent one.

Simplifying how the business worked

Organizational transformation is often associated with adding more process.

In this engagement, much of the work involved removing it.

We identified duplicated approvals, unclear handoffs and recurring meetings that existed largely because information did not move reliably through the organization.

Management discussions were redesigned around decisions, priorities and performance outcomes rather than broad status updates.

Functions were given clearer operating measures.

Cross-functional dependencies were made more explicit so that commercial growth, inventory planning, customer commitments and operating capacity could be considered as part of the same business system.

The objective was not bureaucracy.

It was organizational clarity.

Building management capacity

One of the most important requirements for scale was reducing the company’s dependence on a small number of senior people.

The business had developed around experienced leaders who knew the organization intimately and could resolve problems quickly.

That had been a strength at an earlier stage of growth.

At greater scale, however, the same dependency had begun to constrain the organization.

Knowledge, relationships and decision authority were too concentrated.

I worked with leadership to identify where stronger management ownership was required, where roles needed clearer authority and where senior executives needed to stop functioning as permanent problem-solvers.

The shift was subtle but significant.

Connecting transformation to growth

The restructuring was not treated as an internal efficiency exercise.

Every structural change had to support the company’s future growth.

We considered the operating model against expected commercial expansion, product growth, customer concentration, supply requirements and increasing organizational complexity.

This allowed leadership to distinguish between structures required for today’s organization and capabilities required for the company it was becoming.

A critical test became whether the business could absorb additional revenue without creating a proportionate increase in management friction.

Because a company is not truly scaling if every incremental layer of growth requires more intervention from senior leadership.

The outcome

The transformation produced a more disciplined and scalable operating model.

Accountability became clearer across commercial and operational functions.

Decision-making moved closer to the people responsible for outcomes, reducing unnecessary escalation to senior leadership.

Cross-functional planning improved as customer commitments, supply requirements and operating capacity became more closely connected.

Leadership discussions became more focused on performance, priorities and strategic decisions rather than recurring operational troubleshooting.

Most importantly, the organization became better positioned to absorb future growth without recreating the same complexity at a larger scale.

The company had not simply been reorganized.

It had developed a stronger organizational platform for growth.

The broader lesson

Many mid-market companies reach a stage where the structures that helped them grow begin to become the structures that slow them down.

Informal communication, flexible roles, centralized judgment and senior-level intervention can all work extraordinarily well when a business is smaller.

At scale, however, those same characteristics can produce bottlenecks, ambiguity and organizational dependency.

The answer is not complexity for complexity’s sake.

It is to redesign the business around the capabilities required for its next stage.