Practical BA thinking.
Straight talking.

This is the most common question I get. "How do I become a business analyst when every junior business analyst job spec asks for two years of business analyst experience?" The honest answer is that the BA profession has a circular gatekeeping problem — and the way through it is to stop treating "experience" as something only employers can give you.

The BA role isn't really an entry-level role. Most people get there by lateral move: project coordinator, product owner, service delivery, ops manager, test analyst, change champion. If you're in one of those roles, you can probably reframe what you already do as business analyst work. Capture the requirements you've gathered. Describe the stakeholders you've managed. Show the process maps you've drawn. Most BA-adjacent roles already involve 60-70% of BA work — you just need to label it correctly on your CV.

Two routes that actually work

Route 1 — The Level 4 Business Analyst apprenticeship (ST0117). The UK government-funded apprenticeship route. 18-24 months, paid while you train, structured KSB evidence against 71 criteria, ends with End-Point Assessment. The advantage is the employer takes a punt on you with the apprenticeship levy paying for training. The disadvantage is you need an employer who'll sponsor you — most don't advertise these openly.

Route 1 — The portfolio-led applicant. Build a portfolio of BA artefacts before you apply: problem statements, stakeholder maps, BPMN process diagrams, requirements documents, options appraisals, recommendations. Use real or simulated projects. When you go to interview, walk the interviewer through your portfolio. This is what BA Hub's Project Maple and Project Bridgeway simulations are built for — both produce a portfolio you can actually show.

Route 2 — The internal promotion. If you already work in a company that has BAs, ask to shadow one. Volunteer for the next project that needs requirements work. Take the meeting notes. Map the as-is process. When the role opens, you'll be the obvious internal candidate. This is by far the fastest route but it requires you to already be in the right kind of company.

What employers actually look for in a junior BA

Hiring managers don't care that you've read a textbook. They care whether you can:

1. Sit in a room of people who don't agree and listen actively without taking sides.
2. Translate vague business language into something a developer can build.
3. Spot the difference between what someone says they want and what they actually need.
4. Write a requirement that doesn't get rewritten three times.
5. Pick the right diagram for the right audience — and explain it without jargon.

If you can demonstrate those five things — through your portfolio, through how you talk in the interview, through the questions you ask — you can get a BA job without ever having had a BA job. The certifications are useful (BCS Diploma especially), but they're not what gets you hired. Capability gets you hired, and capability has to be visible.

The CV mistake almost everyone makes

Most non-BAs applying for BA roles write a CV that reads like an org chart. "I was the project coordinator for X programme." That tells the hiring manager nothing about whether you can do the work. Rewrite every job line as what you did + what changed because of you. "I facilitated requirements workshops with eight stakeholders across three departments which surfaced a missing acceptance criterion that would have cost £40k in rework." That sentence does more for your application than any qualification on the back of the page.

The BA market is competitive but it's also one of the rare professional roles where capability shows quickly. If you can walk into an interview with a portfolio of artefacts and articulate your thinking clearly, you'll outperform graduates with three certifications and no real work to show for it.

• BA CV Builder — structured CV template designed specifically for business analyst roles
• BA Interview Prep — 150+ practice questions with model answers using the STAR framework
• Portfolio Generator — turn your simulation work into a downloadable PDF portfolio

Redundancy resets your perspective in a way that most career events don't. When the job you had disappears, you're forced to answer a question most employed people never ask: "What do I actually want to do next?" For a lot of people who find their way to BA — especially those who've been in project work, change delivery, operations, or service design — the answer turns out to be: something a lot like what I was already doing, but with a better job title and a clearer career path.

The business analyst role is, at its core, the person in the room who makes sense of things. They talk to the people who have a problem, talk to the people who'll build the solution, and bridge the gap between the two — in requirements documents, process maps, workshops, options papers, user stories, and recommendation reports. If any of that sounds like your last three jobs from different angles, that's not a coincidence.

What counts as transferable — more than you think

Most people undervalue their existing experience when they're transitioning into BA. They look at job specs that ask for "3 years business analysis experience" and assume they're starting from zero. They're not. Consider what typically counts:

• Project work — attending steering groups, tracking actions, chasing sign-off? That's stakeholder management and change control.
• Operations management — documenting processes, fixing bottlenecks, running daily standups? That's as-is analysis and improvement scoping.
• Customer-facing roles — complaints resolution, account management, client escalations? That's requirements elicitation from real users under pressure.
• Finance or data work — building reports, interrogating systems, producing MI for boards? That's data analysis and non-functional requirements territory.

The task is to translate that experience into BA language — not pretend it's something it isn't, but accurately describe what you were actually doing. Most BA-adjacent roles already include 60–70% of the work. The gap is usually vocabulary, framing, and the artefacts that make the work visible.

The fastest way to close the remaining gap

The thing that gets career changers and redundant professionals stuck isn't the knowledge gap — it's the evidence gap. Hiring managers want to see BA artefacts: a problem statement, a stakeholder map, a requirements document, an options appraisal. They don't care whether those artefacts were produced on a live project or a simulated one. They care whether they demonstrate clear thinking.

This is exactly why BA Hub's project simulations — Project Maple, Project Aurora, Project Bridgeway — are built around realistic scenarios with real stakeholders, real tensions, and real decisions. You're not filling in a template; you're practising the thinking. And the outputs you produce are portfolio-ready.

How to explain the gap in your CV

If you've been out of work while you've been retraining or job-searching, don't hide it. Explain it cleanly. "Following a period of redundancy, I used the time to formalise the BA skills I'd been using throughout my career — building a portfolio and studying the BCS Business Analysis Practice framework." That sentence does three things: it explains the gap, it reframes your existing experience, and it signals initiative. Hiring managers have heard worse reasons for gaps. They've rarely heard this one, and it's honest.

The BA market is one of the more resilient professional segments in a downturn — every business going through change, difficulty, or digital transformation needs someone who can make sense of requirements and translate between business and technology. If you made it this far reading about what BAs do, there's a reasonable chance you're already one. You may just need to say so clearly.

• Transferable Skills Mapper — translates your existing role into BA language with evidence prompts
• BA CV Builder — structured template designed for career changers moving into BA
• Project Maple — your first full BA simulation, portfolio-ready output included

Every BA learns BPMN, then promptly draws process maps in PowerPoint with rectangles and arrows because the audience doesn't speak BPMN. That's not a failure — it's a sensible adaptation. The question isn't "is this BPMN?" The question is "does my reader understand this and will they make the right decision because of it?"

When to use full BPMN 2.0

Full BPMN with pools, lanes, gateway types, intermediate events, data objects and message flows is the right call when:

• The process crosses multiple actors and you need precision about handoffs (use swimlanes)
• You're modelling for automation — a BPM engine will execute the diagram (use service tasks, script tasks, business rule tasks precisely)
• The audience includes other BAs, architects, or consultants who read BPMN fluently
• You need to express different gateway types: exclusive (XOR), parallel (AND), inclusive (OR), event-based
• The process has exception flows that need different end events — error, terminate, signal, message

When to use UML activity notation instead

UML activity diagrams (start node, end node, action, decision, fork/join) are the standard for the BCS Diploma syllabus. They're cleaner for:

• Single-actor processes (no swimlanes needed)
• Educational material — they're easier to teach because there are fewer shapes
• Software workflow internals — where the actor is the system, not a human

When to just draw a box with an arrow

For executive stakeholders, customer-facing collateral, or one-page summaries: plain boxes and arrows. No notation overhead. The reader gets the gist in three seconds. Label the boxes with verbs (what happens) and the arrows with conditions (when this branch). That's it.

I've seen BAs spend half a day perfecting a BPMN diagram that the CEO won't read past the first lane. Notation is for the reader, not the modeller. If a Visio rectangle does the job, use the Visio rectangle.

A practical rule of thumb

1. Audience is technical / will use it for automation → full BPMN 2.0
2. Audience is BAs being trained → UML activity (cleaner notation)
3. Audience is mixed business stakeholders → BPMN with swimlanes but minimal gateway markers (most people read XOR diamonds intuitively; few read inclusive vs exclusive)
4. Audience is the C-suite or external → box-and-arrow on one page

You can build all three from the same source if you use a tool that supports multiple notations. BA Hub HubFlow lets you switch between Process Flow (UML activity), BPMN 2.0, Use Case, Rich Picture and Data Flow Diagram on the same canvas — and Billie helps you pick which is right for your audience.

• HubFlow — diagramming tool with BPMN, UML, Use Case, Rich Picture and DFD support
• BA Templates — free templates for process mapping, requirements and more