Executive summary

Leading a high-stakes project between conflicting senior sponsors is often framed as a personality clash, but the root cause is typically structural: fractured governance and misaligned accountability. When leaders attempt to bridge this gap through sheer diplomacy, they stop leading the work and start acting as a shock absorber for organisational failure.

This article outlines five strategic shifts to move from an exhausted mediator to a disciplined delivery lead:

  • Codify Authority: Move beyond “mixed messages” by clarifying formal decision rights.
  • Release Relational Ownership: Stop attempting to repair executive relationships you do not control.
  • Force Alignment: Replace fragile informal coordination with rigid governance mechanisms.
  • Escalate Consequence, Not Emotion: Reframe political friction as enterprise delivery risk.
  • Set Success Conditions: Define the explicit structural requirements for project viability.

Professionalism is not synonymous with indefinite endurance. The ultimate leadership challenge is recognising when healthy resilience has crossed the line into unhealthy accommodation.

Article

I was recently delivering a leadership programme when one participant raised a dilemma that immediately shifted the energy in the room. She described a situation that, while dramatic in its phrasing, was instantly recognisable to many experienced leaders. She was leading a strategically significant project with high organisational visibility, demanding stakeholders, and material commercial implications. The technical complexity of the work was substantial but manageable. The real challenge lay elsewhere. She reported into two regional CEOs who openly disliked one another. What should have functioned as executive sponsorship had instead become a source of instability.

Her question was direct: How do you lead when the people above you seem to be making success harder rather than easier?

It is a compelling question because it touches a leadership reality that is far more common than organisations care to admit. Modern organisations often celebrate matrix structures, dual reporting lines, and shared sponsorship models as evidence of maturity. In theory, these arrangements are intended to encourage collaboration across functions, geographies, and business units. They exist to reduce siloed decision-making and to create broader ownership of strategic work. At their best, they can do exactly that. Yet when accountability becomes blurred, authority remains undefined, or senior relationships deteriorate, the same structures that promise integration can become engines of confusion.

What was striking in that discussion was how quickly the instinctive explanation moved towards personality. Difficult bosses. Political executives. Fragile egos. While any of these may be true, they are often an incomplete diagnosis. Research into matrix organisations and role conflict has consistently shown that many leadership tensions emerge not because individuals are uniquely difficult, but because the surrounding system creates incompatible expectations, unclear decision rights, and competing demands that no one has properly resolved. What looks like interpersonal dysfunction is often structural ambiguity playing out through human relationships. That distinction matters because it changes the leadership response.

When situations like this are framed purely as personality problems, the implied solution is often endurance. Be more politically astute. Communicate more carefully. Manage upwards more skilfully. Adapt to the personalities involved. Many capable leaders do exactly this. They become translators between competing power centres, interpreting mixed messages, buffering their teams from executive inconsistency, and privately carrying the emotional strain of holding fragmented leadership together.

For a period, this can even be rewarded. The calm project leader who somehow keeps moving despite contradictory demands is often seen as resilient, mature, and highly capable. Yet there is a danger in admiring this adaptation too quickly. At some point, resilience becomes less about healthy leadership and more about absorbing dysfunction that should be addressed elsewhere. The individual in the middle stops leading the work and starts acting as a shock absorber for organisational failure.

The more useful question, then, is not simply how this leader can cope more effectively. It is whether coping is the right goal at all. Some leadership challenges call for patience, diplomacy, and emotional discipline. Others require clearer boundaries, more explicit governance, and a willingness to name structural problems that everyone else has learned to tolerate. The skill lies in knowing which situation you are in.

This article explores five practical responses for leaders caught between senior stakeholders whose conflict threatens execution. Not every divided leadership team can be repaired. Not every dysfunctional reporting structure can be redesigned by the person trapped within it. But leaders often have more options than they initially assume. The task is not merely to survive competing executive agendas. It is to understand the system clearly enough to decide how to lead within it with judgment, boundaries, and integrity.

1: Clarify decision rights before conflict becomes your full-time job

One of the most exhausting aspects of working between competing senior leaders is that the visible conflict is often not the true source of difficulty. The contradictory email, the changing priority, the quietly withdrawn resource, or the sponsor who appears supportive in one meeting and obstructive in the next are often symptoms rather than causes. Beneath these moments usually sits a more structural problem: uncertainty about who actually has the authority to decide.

Organisational researchers have been studying this problem for decades. Rizzo, House, and Lirtzman (1970), in one of the foundational studies on role conflict and role ambiguity, found that employees experience significant stress and reduced effectiveness when faced with incompatible expectations from different authority figures, particularly when responsibilities and decision boundaries are unclear. While their research predates today’s complex matrix organisations, the underlying dynamic remains remarkably familiar.

The lived experience is straightforward enough. One executive communicates that delivery speed is critical because of a commercial commitment. Another emphasises risk mitigation, wider consultation, or tighter cost control. Each request may appear entirely reasonable when viewed in isolation. The difficulty emerges when these demands are operationally incompatible and nobody with formal authority resolves the contradiction.

This is often where highly capable leaders make a subtle but costly mistake. Rather than challenging the structural ambiguity, they respond by becoming more adaptive. They work harder to interpret shifting expectations, translate conflicting signals for their teams, and privately reconcile tensions that should have been resolved at a governance level. Adaptability becomes the coping mechanism.

Yet adaptability is not the same as clarity. Bartlett and Ghoshal (1990), writing on matrix management, argued that matrix structures are not inherently dysfunctional, but they require unusually high levels of clarity, coordination, and mature leadership behaviour to function effectively. Without those conditions, complexity quickly becomes confusion. The problem is not the existence of multiple reporting lines. The problem is the absence of explicit agreements about how authority will actually operate when priorities collide.

This distinction matters because many leaders unintentionally become informal governance mechanisms. They absorb contradictions, make judgment calls on behalf of absent sponsors, and quietly protect the wider system from the consequences of poor executive alignment. For a time, this can even look like strong leadership. The calm project lead who somehow keeps things moving despite ambiguity is often praised for resilience and maturity. But over time, this creates a dangerous pattern in which personal effort compensates for structural weakness.

Peterson et al. (1995), in a large cross-national study of workplace role stress, reinforced the link between role ambiguity, role conflict, and employee strain. Their findings suggested that uncertainty about expectations is not merely frustrating; it has measurable effects on well-being and effectiveness. In practical terms, leaders trapped between competing executives are not simply facing a political inconvenience. They are operating in conditions known to increase cognitive overload and reduce performance.

The practical response, therefore, is not to become indefinitely better at absorbing contradiction. In a high-stakes initiative, that path usually ends with exhaustion, delivery failure, or the project leader becoming the convenient explanation when things go wrong. The more constructive move is to make ambiguity visible, not as a personal frustration, but as an operational risk to the organisation.

This distinction matters. A project leader caught between competing executives does not strengthen their position by appearing overwhelmed by politics. They strengthen it by demonstrating disciplined concern for execution.

That means shifting the conversation away from personalities and towards governance.

Questions such as these become critical:

  • When strategic priorities conflict, who has final decision authority?
  • Who owns commercial, budgetary, and resource commitments?
  • What happens when sponsors provide contradictory direction?
  • What escalation mechanism exists when executive alignment breaks down?
  • Which decisions sit with the project lead, and which require sponsor agreement?

On paper, these look like straightforward governance questions. In practice, they can be politically charged, particularly where senior relationships are already strained and unresolved tensions sit beneath the surface.

That is precisely why the framing matters. The issue is rarely best raised as “I am receiving mixed messages.” A stronger framing is: “To protect delivery on a strategically significant initiative, we need greater clarity on decision ownership and escalation, as current ambiguity creates execution risk.”

The difference is subtle but important. One approach sounds personal. The other sounds like leadership. Where the stakes are high, relatively simple governance mechanisms can dramatically improve execution. A clearly defined sponsorship model, an agreed decision framework, explicit escalation routes, or a disciplined steering structure can move conflict out of private interpretation and into visible organisational process.

If clarity improves, the issue may have been one of poor governance rather than active dysfunction. If clarity is resisted, the signal is more concerning. In some organisations, ambiguity persists not because nobody has noticed the problem, but because unresolved ambiguity preserves political flexibility for those with power. That may protect executives in the short term, but it leaves the person leading delivery exposed.

And on a project where failure carries significant organisational consequences, that is not a risk any serious leader should ignore. That is a different problem entirely.

2: Stop trying to fix the relationship and start managing the reality

A common trap for capable leaders in difficult stakeholder environments is the belief that sufficient diplomacy, emotional intelligence, or relationship skills can eventually bring alignment where conflict exists. This instinct is understandable, particularly for leaders who pride themselves on their ability to build trust, navigate complexity, and find common ground between competing perspectives. Yet there are situations where this assumption becomes less a strength and more a source of distraction.

Jehn (1995), in her influential work on intragroup conflict, distinguished between task conflict, which centres on disagreement about the work itself, and relationship conflict, which arises from interpersonal tension, mutual frustration, and emotional friction. Her findings suggested that while disagreement about ideas can, under the right conditions, sharpen thinking and improve outcomes, relationship conflict is far more corrosive because it distorts communication, reduces trust, and makes objective judgment progressively harder. Once conflict becomes relational rather than merely task-based, people stop responding only to the issue at hand and begin reacting to one another.

That distinction matters here. If the tension between senior sponsors is genuinely interpersonal rather than simply structural, the leadership response needs to change accordingly. The task is no longer to assume that a better meeting, clearer communication, or more thoughtful facilitation will naturally restore alignment. In some executive relationships, historical grievances, personality clashes, or mutual distrust become embedded features of the operating environment rather than temporary obstacles waiting to be resolved.

The practical risk for the project leader is becoming an unofficial mediator in a conflict they neither own nor control.

This often begins innocently enough. One sponsor asks for a message to be softened before it reaches the other. A decision is privately reframed to reduce tension. A conversation is carefully managed to avoid triggering a predictable reaction. Over time, the project leader can find themselves spending increasing emotional and political energy interpreting personalities, managing reactions, and attempting to preserve fragile working relationships, all while believing this is part of effective leadership.

On a strategically critical initiative, that is a dangerous drift. The leader responsible for delivery is not there to repair broken executive relationships. Attempting to do so can consume attention, create false optimism, and quietly shift accountability away from the people who actually own the sponsorship challenge. More importantly, it encourages decisions to be made based on hoped-for alignment rather than operating reality.

Bolman and Deal (2017), in their work on organisational politics, argue that organisations are not purely rational systems, but environments shaped by competing interests, power dynamics, and human behaviour. This is not a cynical observation so much as a realistic one. In politically charged environments, particularly where senior leaders carry significant authority and history, interpersonal dynamics often shape decisions as much as formal structures do.

Seen through that lens, certain patterns become easier to interpret with greater clarity. One executive may routinely challenge ideas associated with the other, not because the substance is flawed, but because support itself carries symbolic meaning. Decision-making may slow because visible agreement feels politically costly. Resource allocation may fluctuate according to shifting alliances or emotional reactions rather than operational need. What initially feels erratic may, in fact, be disturbingly consistent once the relational dynamic is acknowledged.

The leadership task is therefore not to become emotionally entangled in every interaction, nor to personalise every contradiction, but to recognise the environment for what it is and lead with disciplined realism.

That means asking different questions. Rather than: How do I help these two work better together? The more useful question may be: Given the relationship as it currently exists, what leadership choices best protect delivery, the team, and my own effectiveness?

That shift creates distance, not detachment in the cold sense, but the kind of professional clarity that allows leaders to stop reacting to each incident as an isolated frustration and instead recognise the broader operating pattern.

On high-visibility initiatives, where execution failure carries commercial, strategic, or reputational consequences, this clarity becomes essential. Leaders who continue investing disproportionate energy in repairing relationships they do not control may lose focus on the work they are actually accountable for delivering. Leaders who see the reality clearly are far better positioned to make sound choices about governance, escalation, communication, and boundaries.

Not every leadership challenge can be solved through relationship repair. Some require the harder discipline of accepting imperfect human behaviour and leading intelligently in its presence.

3: Create forced alignment mechanisms rather than relying on informal coordination

One of the most dangerous assumptions in high-stakes projects is that senior alignment will emerge organically if people simply communicate often enough.

In healthy leadership environments, informal coordination can work remarkably well. Senior leaders speak regularly, clarify misunderstandings quickly, and resolve tensions through direct conversation. Decisions may not always be elegant, but ambiguity is contained because relationships have enough trust and maturity to absorb disagreement without paralysing execution. That assumption becomes unsafe when the sponsorship environment is fractured.

Galbraith (2009), whose work on matrix organisations remains influential, argued that complexity increases the need for deliberate coordination mechanisms rather than informal dependence on goodwill or personal relationships. As organisational interdependence rises, informal alignment becomes less reliable, particularly where competing power centres exist.

For a project leader caught between two senior sponsors in conflict, this has practical implications. If the project depends on private conversations, individual interpretations, or informal relationship management to maintain momentum, then execution is sitting on unstable foundations. What feels like flexibility can quickly become fragility.

This is where many capable leaders drift into what might be called invisible heroics. They privately reconcile competing instructions, adapt messaging depending on audience, interpret executive intent, and work hard to keep the initiative moving without forcing difficult conversations into the open. Often this is done with good intentions. The desire is to reduce friction, protect the team, and avoid escalating political tension.

Yet invisible heroics rarely scale on strategically significant programmes. What begins as pragmatic adaptation often evolves into systemic dependency. The project becomes reliant on one individual’s political navigation skills rather than stable governance. If that leader becomes overwhelmed, makes an incorrect judgement call, or eventually exits, the underlying dysfunction is suddenly exposed.

This is not a robust delivery model. The more sustainable alternative is to create structures that require alignment rather than quietly compensating for its absence. That may involve practical mechanisms such as:

  • Formal steering meetings with both sponsors present
  • Written decision logs documenting commitments and ownership
  • Explicit priority reviews where trade-offs are surfaced transparently
  • Shared milestone governance rather than fragmented approval conversations
  • Escalation routes that are defined in advance rather than improvised under pressure

These mechanisms are not about adding bureaucracy for its own sake. Their purpose is to reduce private interpretation and force ambiguity into visible organisational processes.

This matters because political conflict often survives precisely where ambiguity remains hidden. A contradictory instruction delivered privately can be rationalised, softened, or reinterpreted. A conflicting position voiced openly in a structured governance forum becomes harder to ignore.

That does not mean formal alignment mechanisms will magically resolve executive friction. In some cases, the tension will remain entirely intact. The value lies elsewhere. Formal structures reduce the extent to which interpersonal conflict can quietly distort operational decisions without scrutiny.

Edmondson (2012), writing on teaming in dynamic environments, emphasised the importance of explicit coordination practices where complexity, uncertainty, and interdependence are high. While her work focuses more broadly on organisational collaboration, the principle applies strongly here: when stakes are high, coordination cannot be left to assumption.

The political challenge, of course, is implementation. A project leader cannot realistically march into a room of senior executives and announce a new governance regime as though authority naturally sits with them. The framing must be thoughtful.

The conversation is rarely: “You two need to align better.” It is more likely: “Given the strategic importance of this initiative, stronger shared governance may help reduce delivery risk and improve execution speed.” The difference is significant. One frames the issue as executive failure. The other frames it as responsible programme leadership.

Where these mechanisms succeed, the initiative becomes less dependent on personality management and more grounded in organisational discipline. Where they are resisted, the leader gains useful information. Resistance to visible alignment often reveals that ambiguity is not merely accidental. It may be politically useful. And that is a risk signal in its own right.

4) Escalate risk, not emotion

One of the more difficult disciplines in politically charged environments is resisting the temptation to escalate a problem exactly as it feels.

When leaders find themselves repeatedly caught between contradictory instructions, delayed decisions, or behaviours that quietly undermine delivery, the natural instinct is to describe the experience in human terms. The sponsors are impossible. The politics are exhausting. Nothing gets resolved. The whole situation feels dysfunctional.

While these reactions may be entirely justified, they are rarely the most effective way to influence upwards. Dutton and Ashford (1993), in their research on issue selling, found that managers are significantly more effective when framing concerns in terms of strategic importance, organisational consequence, or enterprise relevance rather than personal frustration. How an issue is presented materially affects whether it is interpreted as a legitimate leadership concern or dismissed as emotional complaint.

That distinction is particularly important in senior organisational environments, where political sensitivity is high and executive relationships are often more complex than they appear from the outside.

A project leader who escalates frustration may be heard as reactive, personally overwhelmed, or lacking political judgement. A leader who escalates operational risk is far more likely to be seen as acting responsibly in the interests of delivery. This requires a subtle but important reframing.

  • Instead of: The sponsors keep giving mixed messages. The more useful formulation may be: Conflicting executive direction is creating execution ambiguity and increasing delivery risk.
  • Instead of: The politics are making this impossible. A stronger articulation might be: Current governance conditions are slowing decision-making and affecting programme momentum.
  • Instead of: I am stuck in the middle. A more effective framing becomes: The absence of clear sponsorship alignment is creating operational uncertainty that requires resolution.

This is not linguistic polishing for its own sake. It reflects a fundamentally different leadership posture. One framing centres the emotional experience of the individual. The other centres the organisational consequences of the situation.

That matters because senior stakeholders may tolerate interpersonal friction for surprisingly long periods, particularly when the conflict sits between powerful individuals. What becomes harder to ignore is measurable enterprise risk.

For a strategically significant initiative, those risks may be substantial:

  • Delayed milestone delivery due to unresolved decisions
  • Inconsistent stakeholder messaging weakening implementation confidence
  • Fluctuating resource commitments increasing operational exposure
  • Customer-facing commitments becoming vulnerable
  • Commercial opportunities being missed through decision latency
  • Reputational consequences if a visible initiative begins to drift

The leadership discipline is to convert emotional experience into observable operational consequence.

Gross (1998), in his work on emotional regulation, highlighted the importance of cognitive reframing in shaping effective responses under pressure. In organisational settings, that same discipline becomes politically valuable. Leaders who can regulate frustration sufficiently to translate emotional tension into strategic language are often significantly more influential than those who simply communicate the immediacy of their experience.

That does not mean sanitising reality or avoiding difficult truths. The goal is not to produce sterile programme language while privately absorbing dysfunction. It is to make the problem discussable in terms that invite action rather than defensiveness.

A useful escalation might sound like: “Given the strategic importance of this initiative, the current ambiguity in sponsorship and decision ownership presents a growing delivery risk that would benefit from clearer executive alignment.”

The issue has not been softened. It has been elevated. That is the distinction. On lower-stakes work, poor sponsorship can be frustrating but survivable. On business-critical initiatives, unresolved sponsorship conflict becomes a governance risk. And governance risks deserve escalation.

5: Build an explicit “conditions for success” agreement

The final move is to stop treating delivery as a matter of personal commitment and make the conditions for success explicit. On a business-critical project, it is not enough for the project leader to be capable, resilient, and politically skilled. Capability matters, but it cannot compensate indefinitely for missing resources, unresolved sponsorship conflict, unclear decision rights, or contradictory executive expectations. At some point, the leader needs to define what successful delivery requires and place those conditions in front of the people who own the authority to provide them.

This is different from asking for support in a general way. Many leaders ask for support and receive encouragement, sympathy, or vague reassurance. What they need instead is a specific agreement about the practical conditions under which the work can succeed. That means naming the resources, decisions, sponsorship behaviours, escalation routes, and trade-offs required to deliver the project responsibly.

A useful framing might be: “Given the strategic importance of this initiative, I want to be explicit about the conditions needed for successful delivery. These include clear decision ownership, confirmed resource commitments, a single escalation route when sponsor views conflict, and timely resolution of priority trade-offs. Without these, the project remains deliverable in intention but exposed in practice.”

This changes the conversation. The project leader is no longer asking the executives to like each other, resolve their history, or become different people. She is asking them to make an adult choice about the work. If the project matters, then the conditions for success must be created. If those conditions are not created, then the risk should be acknowledged rather than quietly transferred to the person leading delivery.

This is where personal accountability and organisational accountability need to be separated. The project leader can own the quality of planning, communication, stakeholder engagement, team leadership, risk management, and execution discipline. She cannot own contradictory sponsorship, disappearing resources, or unresolved executive conflict. To pretend otherwise is to accept accountability without authority, which is one of the most dangerous positions a leader can occupy.

The practical output should be a short written “conditions for success” document. It does not need to be long or dramatic. In fact, it is more powerful if it is clear, concise, and operational. It might include:

  • The decisions required in the next 30, 60, and 90 days
  • Named owners for budget, resources, scope, and escalation
  • The trade-offs that must be resolved
  • The risks created by current ambiguity
  • The support needed from each sponsor
  • The consequences if those conditions are not met

The aim is not self-protection alone, although that matters. The aim is responsible leadership. A leader on a high-visibility project should not allow the organisation to maintain the illusion that success is simply a matter of individual effort when the system around the work is failing to provide the conditions required for delivery.

If the executives respond constructively, the project gains a stronger foundation. If they avoid, deflect, or resist, the project leader has learned something essential: the organisation wants the outcome, but may not be willing to create the conditions that make the outcome possible.

That is the moment when leadership becomes a choice. Not a choice between caring and not caring, but between continuing to absorb impossible expectations or making the real delivery equation visible.

Final reflections

One of the quieter dangers in high-pressure leadership environments is that capable people often adapt long before they consciously realise they are adapting.

At first, the extra emotional labour feels temporary. The contradictory instructions are rationalised as normal complexity. A lack of clarity is compensated for by additional effort. Meetings are carefully managed, tensions privately translated, and risks quietly buffered away from the team. Because the leader remains competent, composed, and outwardly effective, the wider system continues functioning just well enough to avoid confronting the underlying problem.

Over time, adaptation can become normalisation. Kahn et al. (1964), in their work on organisational role conflict, observed that individuals facing prolonged incompatible demands often compensate through increasing psychological accommodation, even where the structural conditions remain unchanged. Maslach and Leiter (2016), in their research on burnout, similarly argue that chronic overload rarely arrives as a dramatic collapse. More often, it accumulates gradually through sustained tension, emotional strain, and unresolved misalignment.

This is where an important leadership question emerges. At what point does professionalism become unhealthy accommodation?

Strong leaders are often praised for their resilience, adaptability, and ability to remain calm under pressure. Those are valuable qualities. But there is a meaningful difference between leading through difficulty and becoming structurally responsible for containing dysfunction that belongs elsewhere. The difficult discipline is knowing the difference.

Three reflection questions may help:

What am I currently absorbing that should properly be visible to the wider system?

Have I accepted accountability for outcomes without the authority needed to shape the conditions for success?

If nothing materially changes in the next three months, is this still a leadership challenge I can responsibly own?

The strongest leaders do not simply ask, How do I get this done? They also ask, What must be true for this work to succeed, and who has the authority to make those conditions real?

Do you have any tips or advice for managing complex / matrix conflict upwards?

What has worked for you?

Do you have any recommended resources to explore?

Further reading:

Frequently asked questions

How do you manage two bosses who disagree?

Managing two senior leaders who disagree requires shifting attention away from personalities and towards governance. The instinct is often to become a translator, mediator, or diplomatic buffer between competing viewpoints. While this may help temporarily, it rarely creates sustainable clarity. The more effective move is to establish explicit decision rights, escalation routes, and agreed trade-off authority. Who decides when priorities conflict? Who owns resources? What happens when contradictory instructions are given? Without this clarity, the project leader becomes the informal mechanism through which executive dysfunction is absorbed. In matrix organisations, professionalism is not endlessly adapting to conflicting demands. It is helping create the conditions under which clear execution becomes possible.

What should I do if senior leaders give contradictory instructions?

Contradictory instructions should not be quietly absorbed indefinitely, particularly on strategically important work. While capable leaders often compensate through additional effort, interpretation, or informal diplomacy, this approach increases personal strain while leaving the underlying problem unresolved. A more effective response is to document the contradiction, clarify the operational implications, and frame the issue as delivery risk rather than personal frustration. For example, conflicting sponsor direction may create execution ambiguity, delayed decisions, resource uncertainty, or reputational exposure. Escalating the issue in this way shifts the conversation from interpersonal tension to organisational consequence, which is far more likely to prompt constructive action.

How do you lead in a toxic matrix organisation?

Matrix structures are not inherently dysfunctional, but they become difficult when accountability is blurred, authority is unclear, and stakeholders pull in competing directions. Leading effectively in this environment requires discipline rather than heroics. Strong leaders create clarity wherever possible through governance, decision documentation, formal alignment forums, and explicit escalation routes. They also set boundaries around what they will and will not absorb. A common trap is becoming indispensable precisely because you privately compensate for organisational dysfunction. That may preserve short-term momentum, but it increases long-term risk. Effective matrix leadership is not about surviving confusion indefinitely. It is about creating enough clarity for responsible execution while recognising when the system itself requires intervention.

What is role conflict in leadership?

Role conflict occurs when a leader receives incompatible expectations from multiple stakeholders, authority figures, or organisational demands. A project leader may be told to move quickly by one sponsor while another insists on additional consultation, tighter controls, or reduced cost. Both demands may appear reasonable individually, yet become impossible when combined. Research has consistently linked role conflict with increased stress, ambiguity, reduced effectiveness, and eventual burnout risk. In leadership settings, role conflict often hides beneath political frustration, because the problem appears interpersonal when it is actually structural. Recognising role conflict helps leaders shift from self-blame or endless adaptation towards clearer governance conversations about authority, priorities, and decision ownership.

What if executive conflict threatens project delivery?

Once executive conflict begins affecting milestones, resources, decision speed, stakeholder messaging, or customer commitments, it is no longer merely an interpersonal issue. It becomes an organisational risk. The leadership task is to make that risk visible in concrete operational terms. Rather than saying “the sponsors are impossible,” stronger language would describe delayed decisions, execution ambiguity, unstable resource commitments, or increased delivery exposure. This changes how the issue is heard. Senior organisations may tolerate difficult personalities for longer than expected, but they are generally less comfortable ignoring visible delivery risk. Effective leaders do not escalate emotion. They escalate consequences.

How do I stop becoming the shock absorber between senior leaders?

This is one of the most common traps for capable leaders. Because they are politically aware, emotionally intelligent, and committed to delivery, they begin privately compensating for dysfunction above them. They soften messages, reinterpret contradictions, buffer teams from volatility, and quietly absorb the emotional strain of fragmented sponsorship. Over time, this can become normalised. The key question is not whether you can keep doing it, but whether you should. Leadership does involve resilience, but resilience becomes unhealthy when it masks structural failure. Practical boundaries may include refusing to act on contradictory direction without clarification, documenting decisions more explicitly, escalating risks earlier, and making trade-offs visible rather than privately compensating through overwork.

When should I escalate executive conflict?

Escalation becomes appropriate when executive disagreement materially affects delivery, decision quality, team stability, or strategic outcomes. The trigger is not irritation. It is a consequence. If priorities repeatedly conflict, decisions are delayed, resources are withdrawn unpredictably, or the project is exposed to commercial or reputational risk, escalation is a leadership responsibility. The most effective escalation focuses on business impact rather than emotional frustration. Senior stakeholders are more likely to respond to clearly articulated risks than to complaints about difficult behaviour. The goal is not to criticise personalities. It is to ensure that organisational risk becomes visible early enough for corrective action.

What are the warning signs that a project leader is carrying too much organisational dysfunction?

Several warning signs suggest that adaptation has become unhealthy accommodation. These include constantly translating contradictory instructions, making private trade-off decisions without authority, repeatedly buffering the team from executive volatility, working excessive hours to compensate for missing clarity, and feeling personally responsible for resolving tensions that sit above your role. Another sign is emotional exhaustion combined with the belief that “if I stop holding this together, everything will fall apart.” That may reflect commitment, but it can also indicate structural dependency. Effective leadership includes resilience, but not silent ownership of problems the wider system refuses to address.

References:

Bartlett, C.A. and Ghoshal, S. (1990) ‘Matrix management: not a structure, a frame of mind’, Harvard Business Review, 68(4), pp. 138–145.

Bolman, L.G. and Deal, T.E. (2017) Reframing organizations: artistry, choice, and leadership. 6th edn. Hoboken, NJ: Jossey-Bass.

Dutton, J.E. and Ashford, S.J. (1993) ‘Selling issues to top management’, Academy of Management Review, 18(3), pp. 397–428. doi: 10.2307/258903.

Edmondson, A.C. (2012) Teaming: how organizations learn, innovate, and compete in the knowledge economy. San Francisco, CA: Jossey-Bass.

Galbraith, J.R. (2009) Designing matrix organizations that actually work: how IBM, Procter & Gamble and others design for success. San Francisco, CA: Jossey-Bass.

Gross, J.J. (1998) ‘The emerging field of emotion regulation: an integrative review’, Review of General Psychology, 2(3), pp. 271–299. doi: 10.1037/1089-2680.2.3.271.

Jehn, K.A. (1995) ‘A multimethod examination of the benefits and detriments of intragroup conflict’, Administrative Science Quarterly, 40(2), pp. 256–282. doi: 10.2307/2393638.

Kahn, R.L., Wolfe, D.M., Quinn, R.P., Snoek, J.D. and Rosenthal, R.A. (1964) Organizational stress: studies in role conflict and ambiguity. New York: Wiley.

Maslach, C. and Leiter, M.P. (2022) The burnout challenge: managing people’s relationships with their jobs. Cambridge, MA: Harvard University Press.

Peterson, M.F. et al. (1995) ‘Role conflict, ambiguity, and overload: a 21-nation study’, Academy of Management Journal, 38(2), pp. 429–452. doi: 10.2307/256687.

Rizzo, J.R., House, R.J. and Lirtzman, S.I. (1970) ‘Role conflict and ambiguity in complex organizations’, Administrative Science Quarterly, 15(2), pp. 150–163. doi: 10.2307/2391486.