Escalation Done Right: When Leaders Should Solve the Problem - and When They Should Elevate It (Executive Coordination Series 4/4)

In many organizations, escalation carries an implicit stigma. If an issue reaches senior leadership, something has gone wrong — either the team below couldn't handle it, or someone is avoiding accountability. That framing misunderstands what escalation actually is.

Complex organizations encounter challenges that genuinely require broader authority, additional strategic context, or senior alignment. Escalation, used well, is not a failure of collaboration — it's a precision tool for moving forward when lateral resolution has reached its limits. The challenge is that most organizations have two opposing problems at once: some leaders escalate too quickly, routing issues upward the moment they feel uncertain; others avoid escalation entirely, letting problems persist rather than risk appearing unable to handle them. Strong leaders learn the difference

Four practices to help you escalate effectively:

1. Understand the System Before Proposing a Fix.  Leaders often notice problems outside their own function and jump quickly to solutions.  However, many organizational challenges are more complex than they first appear. What seems like a simple fix may be connected to upstream constraints, regulatory requirements, or technical limitations.  Quality pioneer W. Edwards Deming argued that the majority of organizational problems live in systems, not in individuals. Leaders who take the time to understand the broader system — asking questions, mapping dependencies, developing a fuller picture — are far more likely to identify the real problem rather than a visible symptom of it. This isn't a call for analysis paralysis; it's a call for disciplined inquiry before action.

2. Engage the Process Owner with Curiosity.  Once leaders understand the broader context, the next step is to engage the person responsible for the process.  Constructive conversations begin with observation and curiosity rather than criticism.  Organizational psychologist Chris Argyris described this approach as moving from advocacy to inquiry—a mindset that encourages learning and shared understanding.

3. Escalate When Collaboration Reaches an Impasse.  Even strong organizations occasionally reach moments where collaboration alone does not resolve an issue.  In these situations, escalation becomes a useful leadership tool.  Leadership scholar Roger Martin emphasizes that clear decision rights help organizations resolve disagreements and move forward effectively.  When escalation is framed as a mechanism for clarity rather than blame, it helps maintain trust between teams.

4. Choose Escalations Thoughtfully.  Not every issue requires escalation.  Effective leaders distinguish between problems that can be resolved locally and those requiring broader alignment or authority.  Escalating every issue creates unnecessary bureaucracy. Avoiding escalation entirely delays progress.  Strong leaders ask whether the issue requires senior alignment, additional authority, or strategic prioritization before elevating it.

When escalation is used thoughtfully, it keeps organizations moving. Leaders resolve issues at the appropriate level, avoid unnecessary bureaucracy, and ensure that important decisions receive the clarity and authority they require.

Throughout this series, we explored how leadership teams align around enterprise priorities, collaborate across functions, and engage in productive conflict. Escalation ensures that when alignment alone is not enough, organizations can still move forward decisively.

Quote of the Day. “The most important responsibility of an executive is to ensure that decisions are made.” — Peter Drucker

Reflection Question.  In your organization, do leaders escalate too quickly, avoid escalation entirely, or use escalation thoughtfully?  Comment and share below; we’d love to hear from you.

As an executive leadership coach, I work with executive leaders to strengthen their team effectiveness and help organizations navigate complex leadership challenges, contact me to learn more.

When do you know it’s time to escalate?

Horizontal Leadership: Why Great Executives Go Across, Not Up (Executive Coordination Series 2/4)

Most organizations are designed for vertical communication. Leaders manage up and down their chain of command. Accountability flows through hierarchy. But when a problem crosses departments — and most of the hard problems do — the vertical path creates friction by design.

An issue requiring input from marketing, product, and engineering can easily travel up through three layers of leadership before it reaches the people who can actually solve it. By then, the problem is older, the context is thinner, and the solution is further away. High-performing organizations learn to move differently. Before escalating upward, leaders move laterally — connecting directly with the people closest to the issue.

 Here's how the best leadership teams make it work in practice:

 1. Go Direct When a Problem Lives in Another Function.  Many organizations unintentionally create friction by requiring cross-functional issues to travel through layers of management before reaching the people who can solve them.  Strong teams adopt a simpler norm: go directly to the person who can help resolve the issue.

If marketing needs clarity from product, leaders connect directly with the product team. If operations requires financial insight, they reach out to finance rather than routing the issue through multiple layers.

 A well-known example comes from Intel. Former CEO Andy Grove encouraged leaders across functions to engage one another directly rather than relying solely on hierarchical channels. Grove believed fast decision-making required engineers, product leaders, and operations teams to communicate openly across boundaries.

Amazon reinforces a similar principle through its emphasis on ownership. Leaders are encouraged to solve problems wherever they arise rather than waiting for formal authority. Jeff Bezos often reminded teams that customers experience the company as a single system, not as separate departments.

 2. Replace Lane Protection with Shared Ownership.  Many organizations encourage leaders to stay in their lane. While clarity of responsibility is important, overly rigid lane management can create barriers when problems span multiple teams. Consider a customer issue involving product design, customer support, and logistics. If each department focuses only on its narrow responsibilities, the issue may move slowly from one group to the next. 

 Organizations that excel at collaboration adopt a different mindset. Leaders view outcomes such as customer satisfaction, product quality, and operational reliability as shared responsibilities rather than departmental handoffs.  Research published in Harvard Business Review consistently shows that cross-functional collaboration is one of the strongest drivers of innovation and effective problem-solving.

 3. Encourage Peers to Resolve Issues Before Escalating.  In weaker cultures, disagreements between departments are quickly escalated to senior leadership.  Strong leadership teams expect peers to address issues directly with one another first. Leaders clarify expectations, discuss tradeoffs, and work toward solutions before involving higher levels of authority.  This approach strengthens relationships across functions while improving decision speed.  Leadership consultant Patrick Lencioni emphasizes that high-performing leadership teams rely heavily on peer accountability rather than hierarchical enforcement.

 4. Model Collaboration Through Everyday Behaviors.  Horizontal collaboration is shaped not only by major strategic decisions but also by everyday behaviors.  Responding promptly when colleagues reach out, engaging with curiosity when another team seeks input, and making time for cross-functional discussions all strengthen trust across the organization.  When leaders delay responses or ignore requests, collaboration slows and issues begin escalating unnecessarily.  Organizational psychologist Amy Edmondson has shown that trust grows through repeated interactions that demonstrate reliability and mutual respect.

 Horizontal leadership is built through repetition, not declaration. Executives who want to shift their organization's default from vertical to lateral can start here:

  • Connect directly with peers before routing issues upward

  • Respond promptly when colleagues reach out across functions

  • Frame cross-functional challenges as shared problems, not territorial disputes

  • Model the lateral behaviors you want to see — your team is watching what you do, not just what you say

 Reducing friction between functions often unlocks speed, innovation, and stronger execution. When leaders move laterally rather than vertically, problems are solved closer to where they occur and decisions benefit from multiple perspectives. Over time, collaboration replaces unnecessary hierarchy and leaders begin to see themselves not only as stewards of their function, but as partners responsible for the success of the entire enterprise.

 Quote of the Day.  “The leaders who are most effective today are those who can work across boundaries.” — Ram Charan

 Reflection Question.  Where in your organization are issues moving vertically when they could be solved laterally?  Comment and share below; we’d love to hear from you.

 As an executive leadership coach, I work with executive leaders to strengthen their team effectiveness and help organizations improve cross-functional collaboration, contact me to explore this topic further.

The next blog in this series 3/4 will focus on how great executive teams handle conflict.

How do you work laterally?