When Growth Outruns the Organization

Growth is the outcome every leadership team works for. It is also the moment when the way the team works together is tested hardest. Orders become larger and more configured, customers expect more, and work that once moved on personal relationships now has to travel across more people, more systems and more handoffs.

This article looks at that moment from one seat at the leadership table—and follows one order as it travels through the business.

The view from the operations leader’s chair

Picture the vice president of operations at a growing manufacturer of engineered equipment. She sits on a capable leadership team. Sales is winning larger, more configured orders. Engineering is talented. Sourcing has strong supplier relationships. Manufacturing knows how to build. Installation and field service crews are respected by customers.

Yet from her chair, many weeks look the same. Orders reach the shop floor with open questions. Parts arrive late or at the wrong revision. Installation dates move. Field service finds issues that could have been caught months earlier. Each leader on the team can explain what happened in their own function. No one can fully explain what is happening to the order.

That is a common signal that growth has outrun the organization: not a failing function, but a flow of work that no single function owns.

One order, front to back

Follow one order—a configured system with installation and a service agreement—through six stages:

• Sales requirements — what the customer needs, the commercial terms and the promised dates.
• Engineering, configuration and bill of materials (BOM) — turning requirements into a buildable design and the list of parts it requires.
• Sourcing — securing the right materials and components, at the right revision, in time.
• Manufacturing — building, testing and preparing the system to ship.
• Installation — commissioning the system at the customer’s site.
• Field service — supporting the customer through the life of the equipment.

Each stage hands something to the next: information, decisions, materials and commitments. The customer experiences one order. Inside the business, that order passes between six functions, often through different systems, meetings and definitions of “done.”

As-Is: six functions, six versions of the order

In the As-Is state, each handoff is negotiated rather than designed. Common patterns include:

• Requirements are captured in a sales format that engineering must reinterpret, so questions surface after the order is booked.
• Configuration and BOM changes travel by email, so sourcing buys to a revision that is already out of date.
• Manufacturing schedules around missing parts and expedites, spending capacity on rework rather than flow.
• Installation learns the details of the site and the system late, and adjusts in front of the customer.
• Field service sees recurring issues, but the learning rarely returns to sales or engineering.

None of this requires anyone to perform poorly. Capable people are compensating for a flow that was designed for a smaller business. The cost can appear as expediting, waiting, rework, strained customer relationships and leadership meetings spent reconciling what each function believes is true.

To-Be: one order, one shared discipline

In a To-Be state, the leadership team treats the order as a shared value stream—work that crosses every function and belongs to all of them. That might look like:

• Agreed definitions of what each handoff must contain before work moves forward—for example, confirmed requirements before engineering begins configuration.
• One controlled source for the configuration and BOM, so sourcing, manufacturing and installation work from the same revision.
• Clear decision rights at each handoff: who decides, who must be consulted and who needs to be informed when something changes.
• A short, regular cross-functional review of orders in flow, focused on exceptions and decisions rather than status reports.
• A deliberate path for field-service learning to return to sales requirements and engineering standards.

The To-Be state is not a new organization chart or a software purchase. It is an operating discipline the leadership team designs and owns together. The specifics depend on the business, which is why discovery comes before any recommendation.

A practical path through the Compass Architecture

The Compass Architecture provides a connected sequence a leadership team can work through together, at the pace and depth the business requires:

• Strategic Intent — agree what the team is optimizing across the order: for example, reliable delivery commitments, margin on configured work and the customer’s experience after installation.
• FTB 80/20 — look front to back at customers, products and orders to see which few create most of the value, and which create most of the complexity.
• FOUNDATION — clarify roles and decision rights across the handoffs, so the order has owners beyond any one function.
• SIMPLIFY — map the value stream, distinguish value-added (VA), non-value-added (NVA) and necessary non-value-added (NVAR) work, and redesign the handoffs with intention.
• LEAD — establish the cross-functional cadence and accountability that keep commitments visible and decisions timely.
• GROW — identify the capabilities and capacity the next stage requires, such as configuration expertise, supplier development or installation coverage.
• ARC (Analyze, Refine, Commit) — review what the order flow is teaching the team, refine the design and commit to the next course of action.

Questions for your leadership team

• If we followed one recent order from the first customer conversation to field service, where would it have waited—and who would have known?
• Which handoff produces the most rework, and does any one of us own improving it?
• Do sales, engineering, sourcing, manufacturing, installation and service agree on what “complete” means at each step?
• When a change occurs mid-order, how quickly do the right people learn about it?
• What does field service know today that sales and engineering should hear?

Where to begin

Choose one recent order and walk it front to back as a leadership team—not to assign blame, but to see the flow everyone shares. The conversation itself often changes how a team talks about the work.

You and your team set the outcome. Compass partners with you and your team, using its Architecture to connect decisions to execution and to design the operating discipline that delivers it, beginning with a confidential conversation about what you want to achieve.