5 BA Skills No Course Teaches (But Every Employer Wants)

You've got the BCS certification. You've studied SWOT analysis, MoSCoW prioritisation, and use case diagrams. You can map a process in your sleep.

So why aren't you getting hired?

Here's the uncomfortable truth: courses teach you frameworks. Experience teaches you people.

And the skills that separate junior BAs from senior BAs aren't in any textbook.

Here are 5 BA skills every employer wants — but no course teaches.

Skill #1: Reading the Room

You can have perfect requirements documentation. But if you can't sense when a stakeholder disagrees (but won't say it out loud), you're missing half the conversation.

This is the skill of noticing:

• Body language shifting when you mention a specific requirement

• The senior stakeholder who went quiet after the project manager spoke

• The "I'm fine with that" that really means "I hate this but I don't want to argue"

How to build it:

• Attend as many stakeholder meetings as you can (even if just observing)

• After each meeting, write down: Who dominated the conversation? Who stayed silent? Where was the tension?

• Ask yourself: What was said vs. what was meant?

This isn't taught in courses. It's learned by screwing up — by pushing a requirement through that "everyone agreed to" only to find out later that half the team hated it.

Skill #2: Political Navigation

Every organisation has politics. Pretending they don't exist won't help you.

Great BAs know:

• Who the real decision-makers are (it's not always the person with the fancy title)

• Who the blockers are (and how to work around them)

• Which stakeholders have history (and why they don't trust each other)

Example: You're working on a CRM project. The Head of Sales says they want better reporting. But the Head of IT keeps pushing back on timelines.

A junior BA documents the conflict and escalates it.

A senior BA asks: Why is IT pushing back? Is it a resourcing issue? A technical constraint? Or do they not trust Sales to use the system properly?

Once you understand the politics, you can navigate them.

How to build it:

• Map stakeholder relationships (who reports to whom, who has influence, who has history)

• Ask: Who benefits from this project succeeding? Who might lose out?

• Watch how decisions are actually made in your organisation (spoiler: it's rarely in the official meeting)

Skill #3: Dealing with Ambiguity

Stakeholders will tell you: "I want a better system."

Your job is to translate that into something a developer can build.

That's not a science. It's an art.

Courses teach you to ask: "What are your requirements?"

But stakeholders don't know their requirements. They know their problems.

How to build it:

• Get comfortable saying: "I don't know — let's figure it out together"

• Use prototypes, mockups, and scenarios to help stakeholders see what they actually want

• Ask: "What would success look like? What would failure look like?"

You won't learn this from a textbook. You'll learn it by asking the wrong questions, building the wrong solution, and iterating until you get it right.

Skill #4: Saying "No" Diplomatically

Sometimes the stakeholder's request doesn't make sense.

Maybe it's technically impossible. Maybe it's out of scope. Maybe it directly contradicts what they asked for last week.

Junior BAs document the request and move on.

Senior BAs push back — without making an enemy.

Example phrases:

• "I understand why you want that. Here's the challenge we'll face..."

• "Let me play devil's advocate for a second..."

• "What if we tried [alternative approach] instead?"

How to build it:

• Practice framing pushback as helping them succeed (not telling them they're wrong)

• Use data: "If we add this feature, the timeline shifts by 6 weeks. Is that trade-off worth it?"

• Offer alternatives: Don't just say no — propose a better solution

Skill #5: Managing Expectations

You'll face:

• Unrealistic deadlines

• Impossible budgets

• Conflicting priorities

Great BAs set boundaries early and often.

Example: Stakeholder: "Can we have this in 2 weeks?"

Junior BA: "I'll try."

Senior BA: "To deliver in 2 weeks, we'll need to cut these 3 features and increase the budget by £10k. Or we can keep the original scope and deliver in 6 weeks. Which do you prefer?"

How to build it:

• Document everything (scope, timelines, dependencies)

• Communicate early when things change (don't wait until the deadline to say you're behind)

• Give options, not excuses: "We can't do A and B. Which matters more?"

The Bottom Line

Courses teach you to be a competent BA.

Experience teaches you to be a great one.

These 5 skills — reading the room, political navigation, dealing with ambiguity, saying no diplomatically, and managing expectations — separate the BAs who get hired from the ones who stay stuck.

And you don't learn them from a textbook.

You learn them by:

• Volunteering for real projects (even internal ones)

• Shadowing experienced BAs

• Making mistakes and adjusting

• Getting mentorship from practitioners (not just trainers)

If you're trying to break into BA work or level up from junior to mid-level, focus on building these skills.

Your portfolio can prove you know the frameworks.

These skills prove you can do the job.