19 Jan 2026
Let me tell you about the worst BA mistake I made in my first year.
I was working on a CRM project for a finance team. The Head of Sales wanted better reporting. The Head of IT kept pushing back on timelines. Every meeting felt like a standoff.
I did what every good junior BA does: I documented the conflict. I escalated it. I asked senior leadership to resolve it.
And the project stalled for 3 months.
Here's what I didn't understand then: The real problem wasn't technical. It was political.
IT didn't trust Sales to actually use the system. Sales had a history of requesting features and never adopting them. IT was tired of building things that sat unused.
Once I understood the politics, I could navigate them.
We ran a pilot. Sales proved they'd use the system. IT saw the adoption data. Trust was rebuilt. The project moved forward.
That's political navigation — and it's the BA skill no one talks about.
What Is Political Navigation?
Political navigation is understanding:
Who the real decision-makers are (it's not always the person with the fancy title)
Who the blockers are (and why they're blocking)
Which stakeholders have history (and what that history is)
Where the power actually sits in your organisation
Courses don't teach this. They teach you to "facilitate stakeholder workshops" and "manage conflicting requirements."
But they don't teach you what to do when:
The sponsor says "yes" in the meeting but kills the project behind closed doors
Two senior stakeholders hate each other and won't be in the same room
The person funding the project doesn't actually want it to succeed
That's politics. And ignoring it won't help you.
Why Political Navigation Matters
You can have perfect requirements. You can map every process. You can document every use case.
But if you don't understand the politics, your project will fail.
Example 1: The Silent Blocker
You're working on a workflow automation project. Everyone in the workshops says they want it. The business case is approved. Development starts.
Then nothing happens. Timelines slip. Resources get pulled. The project quietly dies.
Why? Because the Operations Manager — who wasn't in your workshops — sees this as a threat to their team's headcount. They're blocking it behind the scenes.
A junior BA wouldn't see this coming.
A senior BA would have mapped the stakeholders, identified the threat, and either:
Brought Operations into the conversation early
Adjusted the scope to protect their team
Built a coalition of support that Operations couldn't block
Example 2: The Proxy War
You're gathering requirements for a new reporting system. Finance wants one thing. Operations wants another. IT is stuck in the middle.
You treat it as a requirements conflict. You facilitate workshops. You try to find compromise.
But it's not a requirements conflict. It's a proxy war.
Finance and Operations have been fighting over budget allocation for 2 years. This project is just the latest battlefield.
Once you understand that, you stop trying to "resolve" the requirements. You escalate to someone who can resolve the budget fight. Or you split the project into two separate streams.
How to Build Political Navigation Skills
1. Map Stakeholder Relationships
Don't just map who your stakeholders are. Map:
Who reports to whom
Who has influence (formal and informal)
Who has worked together before (and what happened)
Who benefits from the project succeeding
Who loses if it succeeds
This is your political map. Update it as you learn more.
2. Ask: "What's Really Going On Here?"
When a stakeholder pushes back, don't just document the pushback. Ask why.
Is it:
A resourcing issue? (They don't have capacity)
A technical constraint? (It can't be done the way they want)
A trust issue? (They don't believe it will work)
A power issue? (They'll lose control/headcount/budget)
The reason matters. Because the solution is different in each case.
3. Watch How Decisions Are Actually Made
Attend as many senior meetings as you can (even if just observing).
Notice:
Who speaks first
Who defers to whom
Where the tension is
What doesn't get said out loud
Decisions are rarely made in the official meeting. They're made:
In the hallway after the meeting
In 1-on-1s before the meeting
In WhatsApp groups you're not in
Your job is to figure out where the real decisions happen — and position yourself accordingly.
4. Build Alliances Early
Don't wait until you need someone's support to build the relationship.
If you know the Head of Operations might block your project, talk to them early. Understand their concerns. Bring them into the conversation before they become a blocker.
If you know two stakeholders have history, don't put them in the same workshop. Talk to them separately. Find common ground. Build the alliance before you need it.
5. Learn to Read Between the Lines
When a stakeholder says: "I'm fine with that"
They might mean:
"I hate this but I don't want to argue"
"I'll say yes now and kill it later"
"I don't understand what you're asking"
Your job is to figure out which one it is.
Ask follow-up questions:
"What concerns do you have about this approach?"
"What would make you more comfortable?"
"Is there anything we're missing?"
If they still say "I'm fine," watch their body language. If they're avoiding eye contact, crossing their arms, or looking at their phone — they're not fine.
The Harsh Truth About Politics
Some BAs think politics are dirty. They think the work should speak for itself.
But here's the reality: Every organisation has politics. Pretending they don't exist won't help you.
The BAs who get promoted aren't the ones with the best technical skills.
They're the ones who:
Understand the power dynamics
Build the right relationships
Navigate conflict without creating enemies
Get things done in spite of the politics
This isn't cynical. It's survival.
The Bottom Line
Political navigation isn't about being manipulative. It's about understanding reality.
Every organisation has:
Stakeholders with hidden agendas
Decisions made behind closed doors
Blockers who won't say they're blocking
Your job as a BA is to navigate this reality — not pretend it doesn't exist.
If you're struggling to get your projects approved, or your requirements keep getting ignored, or your recommendations never get implemented — the problem might not be your BA skills.
It might be your political navigation.
Need help navigating complex stakeholder environments?
→ CV & Portfolio Audit (£75): We'll review how you're positioning your stakeholder management experience
→ BA Career Accelerator (£2,000+): 8-week 1-on-1 mentorship including advanced stakeholder and political navigation strategies
Book a free call to discuss your BA career.