An org chart describes reporting lines. It does not describe how decisions actually get made, whose judgment people genuinely trust, or which relationships hold the organization together when something goes wrong. Every experienced leader has learned that the formal structure and the real structure are different documents.
Authority tells people what they must do. Influence determines what they will do when nobody is watching, when the guidance is ambiguous, and when doing the right thing is inconvenient. Only one of those scales.
The dependency trap
Capable leaders are often rewarded for exactly the behaviour that limits them. They step in, they resolve, they personally guarantee the outcome. It works — and the organization quietly learns that hard problems route to that person.
Over time this produces a team that performs well in the leader's presence and hesitates in their absence. That is not a strong team. It is a dependency, and it caps the size of what that leader can be responsible for.
Leadership is not measured by authority. It is measured by the strength of the organization that remains after the work is complete.
The discipline is uncomfortable: solving less, and building the conditions in which others can solve. In the short term it looks slower. It is the only thing that compounds.
What actually transfers capability
- Decision rights, stated explicitly. Most people are not avoiding decisions. They are unclear whether the decision is theirs. Name it.
- Context, not instructions. Instructions produce compliance in known situations. Context produces judgment in unfamiliar ones — and unfamiliar situations are where you are not present.
- Support after mistakes. The first time someone exercises new authority and gets it wrong, the organization is watching what happens. If the response is withdrawal of authority, nobody else steps forward.
- Visible consistency. Culture is built through repeated decisions. When leaders apply standards inconsistently, people learn that the real rule is discretion.
Influence across boundaries
Most consequential work in an enterprise happens across functions that do not report to each other. Transformation, customer experience, operational redesign — none of it fits inside a single box on the chart. Leaders who can only operate through their own reporting line are limited to problems small enough to fit within it.
Cross-boundary influence is not politics. It is built by being reliably useful to peers, by being straight about constraints, and by having a record of doing what you said. It accumulates slowly and it is the difference between a leader who can run a function and a leader who can move a company.
The question worth asking
A useful test, applied honestly: if you were unavailable for a month, what would degrade?
If the answer is "very little," some leaders hear that as a threat. I would hear it as the strongest possible evidence that the work was done properly — and as the reason that leader is ready for something considerably larger.
The strongest organizations do not rely on heroics. They create environments where capable people perform at a high level repeatedly, responsibly, and at scale.