How a Global Bank Reduced Reactive Work by Strengthening Strategic Thinking and Decision-Making Capability

HIGHLIGHTS:

Industry: Financial Services – Banking
Organization: U.S.-based bank with global operations
Challenge: Constant reactivity, shifting priorities, and late-stage surprises despite strong financial performance
Approach: Strategic thinking and business acumen development grounded in real work and leadership interviews
Results:

• Fewer late-stage disruptions and reactive priority shifts
• Earlier recognition of downstream impacts across IT, operations, product, and compliance
• Improved cross-functional communication and role clarity
• Reduced rework and more predictable execution in a regulated environment

SUMMARY: This case study describes how a U.S.-based global bank reduced reactive work and late-stage “surprises” by strengthening strategic thinking, cross-functional communication, and decision-making under complexity. Based on leadership interviews and real-work analysis in a highly regulated environment, the organization improved how teams surfaced implications earlier, clarified cross-functional dependencies, and communicated risks and tradeoffs before work was already underway. The result was reduced rework, fewer disruptive priority shifts, and more predictable execution across IT, operations, product, and compliance.

The Business Situation

This global bank was not struggling financially. It operated at scale, managed risk effectively, and met regulatory expectations across multiple regions. From the outside, performance appeared strong. Internally, however, two consecutive employee satisfaction surveys revealed a different picture. Across multiple groups, employees reported feeling unproductive, working on tasks that did not seem important, and increasingly frustrated by how work unfolded day to day.

Employees cited slow-moving critical IT and operations initiatives that were repeatedly re-scoped. Cross-functional teams described being asked to add steps late in the process, further slowing progress. Senior leaders spent significant time resolving conflicts between IT, operations, product, and compliance.

Despite strong functional talent and clear intent to execute well, reactivity had become the norm and inefficiency was increasingly tolerated.

As one senior leader put it:

“When things seem to be moving forward, people are constantly surprised by urgent interruptions and shifting priorities.”

For a successful financial services organization operating at global scale, this level of reactivity was more than inefficient. It increased operational risk, diluted leadership attention, and made outcomes harder to predict.

What Leaders Initially Thought Was the Problem

In early discussions, leaders pointed to familiar explanations:

• unclear ownership
• alignment challenges across functions
• regulatory complexity
• resource constraints

Each explanation was reasonable. None fully explained why similar issues kept recurring across initiatives, even when plans were sound and teams were experienced.

Leaders were describing symptoms. What they lacked was a shared way to explain why risks surfaced late, why tradeoffs were discovered under pressure, and why decisions often had to be revisited after work was already underway.

What Was Really Happening

As conversations with leaders deepened, a clearer pattern emerged. Teams were working hard and trying to move quickly. What they lacked was a shared way to understand how decisions and tradeoffs would ripple across the organization over time.

Work crossed functional boundaries with limited shared context. Outputs from one group became inputs for another, often without clarity about downstream implications. In interviews, some teams described work being “thrown over the wall” without explanation. As a result, unexpected problems surfaced late, triggering rework, escalation, or last-minute compromises that displaced other work considered urgent and important. People were not ignoring consequences. They were discovering them too late.

As one leader reflected: “We weren’t short on data or effort. We were short on foresight.”

Communication was frequent, but largely tactical. Information moved, but implications did not. Raising concerns about what might happen often felt speculative, while reacting to what had already happened felt legitimate. Over time, the organization normalized reactivity.

Strategic Thinking as a Core Capability

We brought these observations back to the leadership team and suggested that many of the issues they were experiencing were not execution failures, but gaps in strategic thinking capability. Leaders initially believed they understood what strategic thinking meant. As the conversation connected the concept to their lived experience, interest deepened. The focus shifted away from execution discipline and governance toward strengthening the organization’s ability to think and act more strategically under complexity.Strategic thinking, as used here, did not mean long-range planning or abstract strategy work.

Drawing on the ideas in Strategic Thinking in Action, it referred to a practical organizational capability: the ability to recognize patterns, probe more deeply, understand system-wide impacts, and make better decisions under uncertainty.

Specifically, it meant strengthening the organization’s ability to:

• frame problems before reacting
• recognize interdependencies across functions and time horizons
• surface risks and tradeoffs early, while options still existed
• communicate implications, not just status
• translate insight into decisions that could hold across the enterprise

In short, strategic thinking was the capability that allowed leaders and teams to pause without losing momentum. This reframing resonated, but it raised a practical question:

“If foresight is the issue, how do we strengthen it without slowing the organization down?”

Diagnosis Before Development