How Do I Get Things Done in a Hierarchical Organization
Every organization has formal structure of some kind, reporting lines, decision authorities, or approval processes.
And then there's how things actually work.
Projects will stall for reasons that don't make sense on paper. Perfectly reasonable initiatives will die quietly without explanation.
The org chart shows you who has authority. It doesn't show you who has influence.
Learn to read informal power
Formal power is easy to identify. It's the VP whose approval you need. The department head who controls the budget. The executive sponsor who signs off on initiatives.
Informal power is harder to see but often more important. It's the senior individual contributor who's been there fifteen years and who everyone trusts. The operations manager who can make your initiative easy or impossible to implement. The team lead whose opinion shapes how their peers interpret new directives.
These people don't have decision authority. But they have credibility, relationships, and the ability to accelerate or quietly undermine your work.
If you ignore informal power, you'll get formal approval and implementation failure. If you engage it, you'll get both adoption and sustainability.
Identify who influences who
Most decisions are shaped in conversations that happen before the meeting.
Pay attention to who talks to who before decisions get made. Who do executives check with informally? Whose concerns get addressed before announcements go out? Who gets consulted even when they're not formally required to be involved?
Those are your influence nodes. They're the people shaping outcomes even when they're not in the approval chain.
When you're trying to move something forward, engaging those people early, before you need their support, changes outcomes.
Understand currency beyond title and authority
Some people think navigating hierarchical organizations means playing power games. Building alliances. Trading favors.
That works for some people. But there are other currencies that matter more in most organizations.
Competence is currency. If you consistently deliver good work, people want to work with you. Your judgment gets trusted. Your initiatives get supported because people believe you'll execute well.
Reliability is currency. If you do what you say you'll do, when you say you'll do it, people depend on you. That dependency creates influence without requiring maneuvering.
Clarification is currency. If you're the person who makes complex things understandable, you become essential. People need you to translate, explain, simplify. That creates access and influence.
You just have to be valuable in ways the organization needs.
Map the real decision process
For any initiative you're trying to move forward, map the actual decision process. Not the formal one. The real one.
Who needs to be convinced? Who has veto power even if it's not official? Who will be asked for their opinion even if they're not on the approval list? Whose resistance will kill the initiative even if leadership approves it?
Once you know the real map, you can engage the right people at the right time. You can address concerns before they become blockers. You can build support before you need it.
This isn't manipulation. It's realistic planning. You're accounting for how decisions actually get made instead of pretending process charts reflect reality.
Build relationships before you need them
The time to build relationships with key stakeholders is not when you need their approval. It's before you have anything to ask for.
Offer help. Share information that's useful to them. Ask good questions that show you understand their constraints. Acknowledge their work publicly when it's relevant.
When you eventually need their support, you're not a stranger asking for a favor. You're someone who's already demonstrated you understand their world and care about organizational success.
Navigate conflict without escalation
Hierarchical organizations often have tension between departments, competing priorities, or historical friction between leaders.
You don't have to solve those conflicts. But you do have to navigate around them without making them worse.
Acknowledge constraints without taking sides. Frame proposals in terms of shared goals rather than departmental wins. Give people ways to say yes that don't require them to lose face or concede ground on other issues.
Most organizational tension is about dignity and autonomy, not actual resources. If you can give people those things while still moving your work forward, you can navigate complexity without escalation.
The goal isn't to win. It's to execute.
Navigating hierarchy effectively isn't about accumulating power. It's about getting important work done in environments where formal authority doesn't tell the whole story.
You learn to read the room. You engage the right people early. You build credibility through delivery. You navigate complexity without creating unnecessary conflict.
You operate effectively in the organization you actually have, not the one they tried for on paper.
References & Related Reading:
1) Krackhardt and Hanson, "Informal Networks: The Company Behind the Chart" (Harvard Business Review, 1993): https://hbr.org/1993/07/informal-networks-the-company-behind-the-chart
2) Cohen and Bradford, "The influence model" (Journal of Organizational Excellence, 2005): https://onlinelibrary.wiley.com/doi/abs/10.1002/joe.20080
Related Blog Posts:
How do I get three teams to cooperate when none report to me?
How to build influence without a title?
