HIGHLIGHTS:

Industry: B2B Technology (Global) 

Challenge: Cross-functional decisions stalling, excessive escalations 

Approach: Capability diagnosis, business acumen and strategic thinking development 

Results: 40% reduction in escalations, decision cycles shortened from weeks to days

SUMMARY: This case study describes how a global B2B technology company improved cross-functional decision quality by diagnosing capability constraints and strengthening business acumen and strategic thinking. The work reduced executive escalations by 40% and shortened decision cycles from weeks to days.

---

The Business Situation

A global B2B technology organization had experienced leaders, strong functional teams, and a clearly articulated growth strategy. From the outside, the company appeared well run. Internally, however, results were falling short of expectations.

Product launches were delayed. Priorities shifted frequently. Senior leaders were increasingly pulled into decisions that should have been resolved much lower in the organization. Cross-functional initiatives stalled, restarted, or escalated repeatedly. When asked what was wrong, leaders used familiar terms: poor execution, lack of alignment, accountability issues.

Those descriptions were not inaccurate. They were also proxy language. They described what leaders were experiencing, but not why capable teams were struggling to make decisions that held together across functions.

What Was Actually Breaking Down

As discussions deepened, a pattern became clear. Functional leaders were making reasonable decisions within their own domains, but those decisions were not aligning at the enterprise level. Meetings were spent defending priorities rather than clarifying enterprise tradeoffs. Data was presented to justify positions, not to inform decisions.

As one executive later reflected: “Everyone was doing their job. We just weren’t making decisions that worked across the business.” Issues were routinely escalated not because teams lacked authority, but because they lacked a shared way to frame problems, evaluate tradeoffs, and understand downstream impacts.

Introducing Capability as a Lens

Rather than debating execution quality, we reframed the conversation around organizational capability.  We asked the leadership team a simple question: “How do you define capability?”

There were eight leaders in the room and eight different answers. That moment mattered. Leaders intuitively understood the concept, but they lacked a shared definition or language for how capability influenced decision quality.

As we used the term, capability did not refer to individual competence. It referred to the organization’s collective ability to operate as a system. Specifically, how well it could frame problems at an enterprise level, evaluate tradeoffs consistently, use data to inform judgment, and communicate decisions across functions.

This reframing resonated, but it immediately raised a practical question: “If capability is the issue, how do we know where we’re constrained?”

Diagnosis Before Action: Making Capability Constraints Visible

Before introducing training or new initiatives, the leadership team agreed to establish a capability baseline, much like the beginning of a strategic planning process.

Using the Business Acumen Growth Capability Assessment, leaders examined how decisions were being made across functions. The diagnostic focused on patterns, not performance reviews. It looked at how the organization:

• framed and prioritized problems
• translated strategy into cross-functional decisions
• used data to inform judgment rather than justify outcomes
• managed handoffs and dependencies
• recognized second-order impacts

The results were clarifying. Two constraints stood out:

1. Data existed, but was not integrated into enterprise decision-making. Different functions used different metrics and assumptions, making tradeoffs difficult to evaluate consistently.
2. Leaders lacked a clear line of sight between their work and enterprise goals. Decisions optimized locally often conflicted globally.

As one senior leader put it: “We had plenty of information. What we didn’t have was a shared way to use it.”

What the Organization Did Differently

Rather than restructuring or adding governance, the leadership team focused on strengthening business acumen and strategic thinking where it mattered most.

Cross-functional cohorts participated in a series of Business Acumen Essentials and Strategic Thinking Workshops combined with applied work projects. The goal was not functional skill-building. It was to improve how leaders framed decisions and evaluated tradeoffs together.

The work focused on:

• clarifying the decision before debating solutions
• applying shared business and financial criteria
• understanding downstream impacts across functions
• connecting daily decisions to enterprise priorities

Importantly, the learning was anchored in real decisions the organization was actively facing, not hypothetical cases.

What Changed in Practice

Changes became visible within months. Meetings became more focused and productive. Leaders began explicitly stating the decision to be made, the criteria being applied, and the tradeoffs involved. Discussions shifted from defending positions to evaluating options.

Data was used differently. Instead of competing metrics, leaders worked toward shared assumptions. This reduced circular debates and re-litigation.

Escalations declined. Teams resolved more cross-functional issues without involving senior executives. As one executive described it: “We didn’t suddenly agree on everything. But decisions stopped bouncing back up to us, and when teams committed, they followed through.”

Outcomes

Within six months, the organization observed several measurable shifts:

• Cross-functional decisions that previously took weeks were often resolved in days
• Executive escalations on operational decisions declined by roughly 40 percent
• Fewer initiatives were paused or restarted due to misalignment
• Senior leaders reported spending less time resolving downstream conflicts

While these changes did not instantly transform financial results, they created capacity. Leaders were able to focus attention on fewer, more strategic priorities, and execution became more predictable.

What This Story Reveals

This organization did not lack talent, effort, or strategy. What it lacked was a shared way to make decisions that held together across functions.

By strengthening business acumen and strategic thinking, leaders improved how problems were framed, how tradeoffs were evaluated, and how decisions were communicated. Execution improved not because people worked harder, but because decisions became clearer and more durable.

The most important outcome was not faster meetings or fewer escalations, although those mattered. It was the organization’s growing ability to make aligned decisions without relying on constant executive intervention. We see this pattern regularly. 

When performance problems are described as execution failures, the underlying constraint is often capability. When leaders develop a shared understanding of how the business works as a system, decision quality scales and execution follows.  For this organization, capability development was not an HR initiative. It was a lever for improving how the business made decisions under complexity.

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

Related Success Stories:

• When growth feels stuck despite strong performance: How a $5B Technology Company Reduced Organizational Drag explores how leaders diagnosed systemic friction that was slowing execution.
• When product decisions don’t connect to strategy: How a Product-Led Organization Rebuilt Investment Discipline shows how business acumen development helped teams avoid misdirected investments.