Between Personal Closeness and Formal Authority

Leadership relationships do not always fit neatly within an organizational chart.

A senior leader was responsible for a strategically important program that had begun to lose momentum. Progress increasingly depended on renewed attention from an executive sponsor whose focus had shifted elsewhere.

On paper, the route forward appeared straightforward: raise the issue through the reporting line and ask the direct manager to re-engage the sponsor.

In practice, it was far more complicated.

The relationship with the manager extended beyond their formal roles. It was longstanding, personal, and built on considerable mutual loyalty. This closeness had many advantages, but it also made some conversations more difficult. Challenging the situation could be interpreted not only as a professional concern, but also as a personal criticism or a sign of disloyalty.

The leader therefore felt caught between two risks. Remaining silent could allow the program to drift further. Speaking directly could affect both the professional relationship and the friendship behind it.

When the obvious route feels closed

Initially, the dilemma was framed as a choice between confronting the manager and accepting the delay.

But this assumed that influence could only travel upward through the formal hierarchy.

A different question opened a different possibility:

Where does room for responsible action remain when the obvious route feels closed?

Rather than treating the issue as something he had to solve alone, the leader shared more of the underlying dilemma with his team. He did not transfer responsibility or ask them to challenge the hierarchy on his behalf. Instead, he invited them to think about the wider system around the program.

Together, they examined where attention, interest, and influence still existed. Which relationships could be activated? What information might make the program relevant again? Who understood the sponsor’s current priorities? And how could the importance of the work become visible without forcing a direct confrontation?

The team identified several legitimate routes through which interest in the program could be renewed. Their approach did not depend on the manager intervening personally. Gradually, the program regained the sponsor’s attention and began moving forward again.

What happened next was equally significant. The manager did not experience the solution as an act of disloyalty or an attempt to bypass authority. Instead, he complimented the leader on the way the situation had been handled.

Authority is not the same as influence

The turning point was not a new technique for stakeholder management. It was a shift in how the leader understood his own position.

He had initially seen the formal hierarchy as both the source of the problem and the only possible route toward a solution. Once that assumption was questioned, other sources of influence became visible.

The experience also changed his relationship with the team. He became more willing to share dilemmas before he had already determined the answer. In doing so, he created more room for team members to contribute their own perspectives, relationships, and judgment.

That did not diminish his authority. It made the collective intelligence around the program more available.

Personal closeness and formal authority can coexist, but their combination can make candor more difficult. Loyalty may become confused with silence. Respect for hierarchy may narrow the field of action. A leader can begin to assume that protecting a relationship requires avoiding the very conversation—or question—that the situation demands.

Sometimes the way forward is not to push harder against the formal structure. It is to look more carefully at the wider context in which influence is already moving.

When the formal route feels closed, where else might responsible influence be possible?

This vignette has been adapted and generalized to protect confidentiality and should not be read as an account of an identifiable individual or organization.