HIGHLIGHTS:

Industry: Hardware, Software, and Services
Company Size: ~$5B annual revenue, global operations
Challenge: Growth slower than expected despite strong financial performance
Approach: Growth capability diagnosis, executive working sessions, targeted capability development
Results:

• Clear identification of systemic drag points across data, process, and decision-making
• Improved quote-to-cash visibility and predictability
• More focused investment decisions and fewer reactive initiatives
• Increased leadership alignment around where to intervene and where not to

SUMMARY: This case study describes how a $5B global hardware, software, and services company identified systemic organizational drag and improved business velocity without launching a large-scale transformation. Leaders examined how data, processes, and decisions interacted across divisions, including quote-to-cash flow, handoffs, approvals, and rework. Using structured diagnosis and executive working sessions, the leadership team gained clearer visibility into where friction accumulated, improved prioritization of interventions, and created headroom for more consistent execution and sustainable growth.

---

The Business Situation

This organization was not in crisis. It consistently met financial targets, managed margins, and operated at scale across hardware, software, and services. From the outside, performance looked solid. What made this case distinctive was the leadership team’s curiosity.

Senior executives believed the company should be growing faster and operating more smoothly than it was. They had recently completed work with a major consulting firm, yet there was a shared concern that many of the recommendations were difficult to implement in practice. Rather than defaulting to a large-scale transformation or restructuring, the Chief Operating Officer (COO) asked a different question: “what is keeping us from growing faster?”  

Early Signals: When “Making the Numbers” Masks Constraints

Despite solid results, execution felt harder than it should have been. Initiatives took longer to translate into impact. Operational issues consumed leadership attention. Decisions required repeated clarification and follow-up. None of this triggered alarms. The business was performing well enough.

That success made it easier to absorb inefficiencies and harder to see how much growth potential was being left on the table. As one executive put it later: “We weren’t failing. We just felt slower and more reactive than a company at our scale should be.”

What Was Actually Slowing the Organization Down

Initial conversations revealed a familiar pattern. Leaders pointed to data issues, process inefficiencies, and legacy systems. All were true. None fully explained the problem. The organization tracked extensive financial and operational metrics, including revenue, pricing, margins, cost structures, and EBITDA. Yet leadership discussions often stalled on interpretation rather than action.

Different divisions used different assumptions, definitions, and measures of success. Data explained results after the fact, but rarely illuminated tradeoffs before decisions were made. At the same time, business processes were complex and heavily interdependent. Years of acquisitions had left behind multiple systems and workflows that were poorly synchronized. Hand-offs between functions and divisions created delays that were rarely visible end to end.

Each issue made sense in isolation. Together, they created organizational drag: friction that slowed execution without ever causing outright failure. (We introduced the concept of organizational drag, drawing on principles of flight. The metaphor resonated immediately with the executive team.)

Shifting the Lens: From Symptoms to System Behavior

To move beyond surface explanations, we worked with the leadership team to view performance through a system lens. Rather than focusing on individual processes or metrics, discussions centered on business velocity, particularly the quote-to-cash flow. The question became:

“Are we satisfied with how quickly and predictably value moves through the business?”

This reframing changed the conversation. It revealed that:

• delays accumulated primarily at hand-offs
• approvals optimized for control reduced responsiveness
• rework and exceptions had become normalized
• variability increased as work crossed organizational boundaries

The company was profitable, but it was not operating as fast or as smoothly as it could.

Diagnosis Before Action

Rather than relying on anecdote or intuition, the leadership team agreed to establish a data-informed baseline of growth capability. Using the Growth Capability Assessment, leaders examined how well the organization was truly set up to grow. The assessment did not evaluate individual performance. It examined capability across the system. Leaders reflected on questions such as:

• how consistently strategic priorities were understood beyond the executive level
• how effectively data informed decisions rather than explained outcomes
• where processes enabled work and where they unintentionally created friction
• how well leaders recognized second-order impacts as decisions crossed functions

The results were clarifying. Leadership capability was strong, but unevenly distributed. Processes were documented  but not always understood in context. Data existed but was not consistently actionable at decision points. Most importantly, the assessment made visible which constraints were systemic rather than situational.

As one executive noted: “We stopped arguing about what to fix and started seeing where the system itself was slowing us down.”

What the Organization Did Differently

The leadership team resisted the temptation to launch a broad transformation. Instead, they focused on improving understanding before intervention. Executive working sessions were used to:

• align on where drag truly mattered
• distinguish necessary complexity from avoidable friction
• evaluate potential initiatives based on impact on flow and decision quality

Targeted capability development followed, focused on strengthening business acumen and strategic thinking where it would remove the most drag. Learning was tied directly to real decisions and operational challenges the organization was facing. The goal was not to add activity. It was to improve judgment.

What Changed in Practice

Changes were gradual but meaningful. Leadership conversations shifted from debating symptoms to examining system behavior. Decisions were framed more clearly. Tradeoffs were discussed more explicitly. Fewer initiatives were launched reactively.

Leaders became more deliberate about where to intervene and where to allow teams to operate. Attention moved away from fixing isolated problems and toward removing recurring sources of friction. As a result, execution felt less forced and more predictable.

Outcomes

The impact of this work was not best measured through short-term financial deltas, but through changes in how leaders understood the business, prioritized interventions, and made decisions under complexity. This work did not produce dramatic, overnight gains. That was not the goal.

What it produced was clarity. As a result, leaders gained:

• clearer visibility into where organizational drag accumulated
• greater confidence in prioritizing improvement efforts with real leverage
• reduced reliance on external “fixes” to address systemic issues
• more consistent decision-making across divisions and business lines

For a company already performing well, this clarity created meaningful headroom for growth and improved the organization’s ability to absorb complexity without slowing down.

What This Story Reveals

Growth is constrained less by ambition or investment than by an organization’s ability to understand how it really works. In this case, improving business acumen and strategic thinking did not eliminate complexity. It helped leaders see it more clearly, talk about it more productively, and intervene more selectively.

When leaders understand how data, process, and decisions interact across the system, they can reduce drag without disruption.

Better decisions, grounded in clearer system understanding, compound faster than programs.

Related Success Stories

• When leaders can’t agree on what’s constraining growth: How Leaders Identified Growth Constraints Before Choosing What to Fix describes how a $700M company used structured diagnosis to move past competing hypotheses and align on where to focus.
• When cross-functional decisions keep breaking down: How a Global Tech Company Improved Cross-Functional Decision Quality shows how strengthening shared business acumen reduced escalations by 40% and shortened decision cycles from weeks to days.