10 Jan 2026
I've been a junior BA. I've been a mid-level BA. I've been a senior BA. I've been a principal BA.
And here's what no one tells you about career progression:
The difference between junior, mid-level, and senior isn't years of experience.
It's the type of work you do.
I've met junior BAs with 5 years of experience. They're still junior because they're still doing junior-level work.
And I've met mid-level BAs who got promoted in 18 months — because they were already doing mid-level work.
Here's the real difference between each level.
Junior BA: Executes Tasks
What they do:
Document requirements as told
Attend meetings (mostly listening)
Create process maps from existing workflows
Follow established frameworks (SWOT, MoSCoW, use cases)
Mindset: "What am I supposed to do?"
Typical salary (UK): £25k - £35k
They're valuable when:
You need someone to document a well-understood process
You have clear requirements that just need writing up
You need support on a large project
They struggle when:
Requirements are ambiguous
Stakeholders disagree
No one knows what the solution should be
Mid-Level BA: Solves Problems
What they do:
Facilitate workshops (not just attend)
Challenge requirements (not just document)
Identify gaps and risks proactively
Propose solutions (not just capture problems)
Mentor junior BAs
Mindset: "What's the real problem here?"
Typical salary (UK): £40k - £55k
They're valuable when:
Requirements are unclear and need to be teased out
Stakeholders need help articulating what they want
There's a complex problem that needs breaking down
They struggle when:
Politics are involved and they need to influence senior leadership
The problem is strategic (not just tactical)
They need to define the problem (not just solve it)
Senior BA: Defines Problems
What they do:
Define BA strategy for programs/portfolios
Influence senior leadership decisions
Lead complex digital transformations
Solve ambiguous, strategic problems
Build BA capability in the organization
Mindset: "What should we be solving?"
Typical salary (UK): £60k - £80k+ (£90k+ in London/finance)
They're valuable when:
No one knows what the problem is yet
Senior leadership needs strategic advice
The organization needs to build BA maturity
There's a transformation with unclear scope
They struggle when:
They're asked to just "document requirements" (they'll be bored)
There's no ambiguity (they're over-qualified)
The Key Difference: Defined vs. Ambiguous Work
Junior: Work is defined. You execute.
Mid-Level: Work is partially defined. You solve.
Senior: Work is undefined. You define it.
Example: A CRM Project
Junior BA approach:
Attend workshops
Document what Sales says they want
Create requirements document
Hand off to IT
Mid-Level BA approach:
Facilitate workshops (not just attend)
Ask: "Why do you want this? What problem does it solve?"
Challenge requirements that don't make sense
Identify gaps (e.g., "You said you want better reporting, but you haven't defined what metrics matter")
Propose solution options
Senior BA approach:
Before the workshops: "Should we even build a CRM? What's the strategic goal?"
Map stakeholder landscape (who wins/loses from this project?)
Identify risks (e.g., "Sales has a history of not adopting new systems — how do we ensure this one succeeds?")
Influence the approach (e.g., "Let's run a pilot with 10 users before rolling out to 500")
Define success criteria that tie to business outcomes (not just 'system delivered')
How to Move from Junior → Mid-Level (2-3 years with intention)
1. Stop waiting to be told what to do
Junior BAs wait for tasks. Mid-level BAs proactively identify problems.
Example:
Junior: "I've documented the requirements. What should I do next?"
Mid-Level: "I've documented the requirements. I noticed 3 gaps. Here's what I think we should do about them."
2. Start facilitating (not just attending)
Mid-level BAs don't just show up to meetings. They run them.
How to practice:
Volunteer to lead the next workshop
Create the agenda (don't wait for someone else to)
Ask the questions (don't wait for the project manager to)
3. Challenge (diplomatically)
Mid-level BAs push back when requirements don't make sense.
Example phrases:
"Help me understand why we need this feature — what problem does it solve?"
"I want to play devil's advocate for a second..."
"What if we tried [alternative] instead?"
4. Build relationships with stakeholders
Junior BAs see stakeholders as "the people who give me requirements."
Mid-level BAs see them as partners. They:
Have coffee with stakeholders outside of formal meetings
Understand their goals and challenges
Position BA work as helping them succeed (not just gathering requirements)
5. Start mentoring others
You don't need to be senior to mentor. If you're 18 months into a BA role, you can mentor someone who's 6 months in.
Mentoring forces you to:
Articulate what you know
Identify what you don't know
Think strategically (not just tactically)
How to Move from Mid-Level → Senior (3-5 years with strategic positioning)
1. Influence strategy (not just execution)
Senior BAs are in the room when decisions are made — not just when they're implemented.
How to get there:
Volunteer for strategic initiatives (not just delivery projects)
Write position papers (e.g., "Here's why we should invest in BA capability")
Speak up in senior meetings (don't just take notes)
2. Get comfortable with ambiguity
Mid-level BAs want clear requirements. Senior BAs thrive when there are no requirements yet.
How to build this:
Volunteer for projects where no one knows what the solution is
Practice saying: "I don't know yet — let's figure it out together"
Use prototypes, scenarios, and hypotheses to explore the problem space
3. Advise senior leadership
Senior BAs don't just take direction from senior leaders. They advise them.
Example:
Mid-Level: "The CEO wants us to implement this system. Here's how we'll do it."
Senior: "The CEO wants this system, but I think we should explore [alternative] first. Here's why."
4. Lead transformations (not just projects)
Projects have clear scope and timelines. Transformations are messier.
Senior BAs lead transformations where:
Scope is unclear
Success criteria are ambiguous
Politics are high
The organization needs to change (not just the system)
5. Build a reputation beyond your team
Mid-level BAs are known in their team. Senior BAs are known across the organization.
How:
Present at internal conferences
Write articles or blog posts
Mentor BAs in other teams
Get involved in communities of practice
The Harsh Truth
You don't get promoted because you've "done your time."
You get promoted because you're already doing the next level's work.
If you want to move from junior to mid-level, start doing mid-level work now:
Facilitate (don't just attend)
Challenge (don't just document)
Propose solutions (don't just capture problems)
If you want to move from mid-level to senior, start doing senior work now:
Influence strategy (don't just execute)
Advise leadership (don't just follow)
Solve ambiguous problems (don't just solve defined ones)
Your title will catch up.