Case Study: Authority, Conflict, and Trust Inside a Leadership Team
The meeting began as many leadership meetings do. Executives arrived gradually, exchanged brief informal remarks, and settled into their seats. The atmosphere was neutral, functional, unremarkable.
Then the chairman entered.
The shift was immediate. Conversations stopped, posture changed, and the room reorganised itself without a word being spoken. Authority had arrived – not through title, but through presence.
Formally, the CEO led the organisation. In practice, it became clear within minutes that leadership operated elsewhere. The chairman, who was also the CEO’s father, assumed control of the discussion, questioning numbers, directing attention, and shaping the flow of the meeting.
The CEO remained present, yet peripheral.
This was not a single moment. It was a pattern.
Psychological Safety — The Absence of Voice
At first glance, the meeting was active. Executives spoke, presented data, and engaged in discussion. Yet the direction of communication revealed something more important than the volume of speech. Almost all contributions were oriented toward the chairman.
“This is how we see the numbers… does that align with your view?” one executive said, turning slightly toward him before finishing the sentence. Another paused mid-explanation, glanced across the table, and added, “Of course, we can adjust this if needed.”
The implicit question in the room was not “What is the right decision?” but “How will this be received?”
This distinction is subtle but critical. It signals a lack of psychological safety. When leaders calibrate their input based on authority rather than judgement, the system begins to filter reality.
The CEO’s behaviour made this even more visible. During a moment of tension with the chairman, his posture shifted inward. “But we agreed last quarter that this direction—” the CEO began, his voice steady at first. The chairman interrupted. “No, that’s not how I see it. The numbers don’t support that.”
There was a brief silence.
The CEO’s shoulders dropped slightly. He looked down at the table, nodded once, and said more quietly, “Alright… we can revisit the assumptions.”
It was not disagreement that defined the moment. It was withdrawal. In that instant, psychological safety did not fail loudly. It disappeared quietly.
Trust — Built on Position, Not Relationship
Trust within the team appeared functional on the surface. There was no open hostility, no visible breakdown in communication. Yet the quality of interaction suggested something else. Executives competed for space. They interrupted each other, raised their voices, and asserted positions with intensity.
“No, that’s not the issue — the real problem is execution,” one said, leaning forward. “That’s not accurate,” another cut in. “We’ve been waiting on your team for weeks.” “That’s simply not true.”
The dynamic resembled rivalry more than collaboration. What was missing was not communication. It was relational trust.
Trust is not measured by whether people speak. It is measured by how they speak, and what becomes possible because of it. Here, communication did not create alignment. It created noise.
At one point, two executives spoke over each other for several seconds before stopping abruptly. Both turned toward the chairman, almost instinctively, waiting for him to intervene. He did. “Alright, enough. Let’s move on.”
The CEO remained silent. Formally, he held authority. Informally, he did not exercise it. This created a vacuum in which trust could not stabilise. When authority is unclear, trust has no anchor.
Conflict — Present but Unused
Conflict was not absent in this leadership team. It surfaced repeatedly. Discussions escalated quickly, voices overlapped, and disagreements became visible. Yet nothing moved forward.
“We cannot continue like this,” one executive said sharply. “This is affecting delivery.”
“So what are you proposing?” another responded.
“I’m saying we need to change the approach.”
“To what exactly?”
The exchange intensified, voices rising slightly, the pace accelerating. For a moment, it seemed as though the discussion might reach a point of clarity.
Instead, it dissolved.
“Alright,” someone said after a pause, “we’ll need more analysis on this.”
“Yes,” another added quickly, “let’s take this offline.”
“Agreed. We’ll revisit.”
The tension dropped, but nothing had been resolved.
Conflict was expressed, but not resolved.
This is one of the most costly patterns in leadership teams. Conflict that is not processed becomes recurring friction. It consumes time, diffuses accountability, and gradually erodes trust. Constructive conflict requires containment. It requires clarity about ownership, decisions, and next steps. Without that structure, conflict becomes performative rather than productive. In this team, conflict existed — but it was not doing any work.
Sustaining Trust — The System Under Pressure
Trust is not tested when conditions are stable. It is tested under pressure.
In this system, pressure revealed the underlying structure. Authority moved upward, conflict dissipated without resolution, and the CEO retreated from his role.
Over time, these patterns create predictability — but not the kind that sustains trust. Executives learn what is safe and what is not. They learn when to speak and when to hold back. They learn which conflicts will be addressed and which will be deferred. This is how trust erodes gradually, without a single defining moment. It is not broken. It is weakened.
A System, Not an Individual
It would be easy to interpret this case through the lens of individual behaviour. A passive CEO, a dominant chairman, competitive executives. Yet the pattern is systemic.
The organisation operates within overlapping roles: father and chairman, son and CEO, peers and competitors. These roles are not clearly separated, and as a result, authority becomes ambiguous.
In such systems, behaviour follows structure.
The CEO’s withdrawal is not only personal. It is relational. The chairman’s dominance is not only individual. It is reinforced by the system. The executives’ rivalry is not accidental. It is adaptive.
Without structural clarity, even capable leaders become constrained by the system they operate in.
Coaching Perspective — Where Change Begins
From a coaching perspective, the intervention point is not the surface behaviour. It is the underlying structure of authority, role, and expectation.
Several questions become central:
- Where does authority actually sit in this system?
- What is the CEO authorised — and expected — to do?
- What behaviours are implicitly rewarded or discouraged in this team?
- What conversations are systematically avoided?
Equally important is restoring the link between conflict and decision-making. Conflict must lead somewhere. Without resolution, it becomes noise.
Psychological safety must also be addressed directly. Not as a value, but as a behaviour. Leaders need to experience that speaking openly changes outcomes, not just dynamics. Trust, in turn, follows from this. Not as an intention, but as a consequence of consistent interaction.
Making It Work — What This System Requires
For this leadership team to function effectively, several shifts are required:
- Reclaiming role clarity — separating formal authority from informal dynamics
- Re-establishing decision ownership — ensuring conflict leads to clear outcomes
- Creating psychological safety in practice — enabling direct, consequence-free challenge
- Stabilising leadership behaviour — making responses predictable under pressure
None of these changes are cosmetic. They require sustained attention and deliberate intervention.
Final Thoughts
Leadership teams do not fail because of lack of intelligence or capability. They fail because the system they operate in does not support effective behaviour.
In this case, authority was present but not enacted, conflict was visible but not resolved, and trust was assumed but not sustained. For CEOs, owners, and shareholders, the implication is clear. The quality of leadership is not only defined by who sits at the table. It is defined by what becomes possible once they are there. And that is always a function of the system.
