The Practical Path In

There is a catch-22 that traps almost everyone trying to break into this field: you need experience to get the job, and the job to get the experience. I stood in the middle of that loop once, qualified on paper and stuck in practice, wondering how anyone ever gets through the door. Here is what I learned climbing out of it, and what I now tell everyone I mentor. You do not break the loop by waiting for someone to grant you a first chance. You break it by building evidence that you can already do the work, before anyone has paid you to. Everything below is a way of doing exactly that.

Learn the craft properly

Do not wait to absorb business analysis on a job you cannot get yet. Learn it deliberately, the way I did, through a proper course, a school, or structured self-study. Get the real fundamentals: how to elicit and write requirements, how to map a process, the basics of working with stakeholders, and the common vocabulary and frameworks the profession uses. You are aiming for enough to speak the language and do the work, not an endless wall of certificates. The goal here is competence you can demonstrate, not badges you can list.

Do the work before you have the title

This is the move that actually breaks the catch-22, and most people skip it. You can practise the work without holding the job. Volunteer to analyse and improve a process at whatever job you are in now, whatever it is. Offer to help a small business or a charity map and fix something that frustrates them. Take a real problem and produce the artefacts an analyst would: a clear problem statement, a process map, a set of requirements. Do that once or twice, and you no longer have aspiration; you have evidence. You have done the job. The title is just the part that has not caught up yet.

A concrete version: pick something broken in your current workplace, however humble, the messy onboarding process, the report everyone complains about, the approval that takes too long. Interview the people involved, map how it works today, find where it breaks, and write up how it could work better. Produce it the way an analyst would, cleanly and clearly. You have now done real analysis on a real problem, and you hold an artefact you can actually show. That single piece of work is worth more in an interview than a shelf of certificates.

But what if you don't have a real problem sitting in front of you?

Here's the part people don't say out loud: not everyone has a workplace generous enough to hand them a process to fix, or a charity willing to let a stranger poke around their operations. That gap is where most people actually get stuck, not because they lack drive, but because they lack a live problem to point their drive at. This is exactly the gap I built the mentorship program to close. I don't hand mentees a generic textbook exercise and call it practice. I take them through real case studies built around the actual business context or BA niche they're trying to break into, whether that's fintech, healthcare, retail ops, or something else entirely, so the artefact they walk away with isn't theoretical. It's the same standard of work a hiring manager expects from someone already doing the job, because it was built to answer the exact question that manager will ask in the interview: show me you can already do this.

That's the difference between "I understand process mapping" and handing someone a process map you built on a case modelled on the world they operate in. One is a claim. The other is proof they can hold in their hands.

Move sideways if you can

The most underused path in is the internal move. If you already work somewhere that has a technology, product, or project function, get close to it. Volunteer for the analysis-shaped work nobody else wants. A great many analysts, myself included in spirit, got in by quietly doing the job unofficially until it became official. It is far easier to become an analyst at a company that already trusts you than to be hired cold as an unknown from outside. The door from inside is almost always more open than the one from the street.

Find a mentor

I would not have moved half as fast without someone a step ahead of me who was willing to help. A mentor shortens your mistakes and tells you the things nobody writes down. You do not need a formal programme or a famous name. You need one person a little further along who will answer your questions and tell you the truth. So ask. Most people are far more generous with their time than the fear in your head predicts, and the worst answer you will get is a polite no, which costs you nothing. And if you want that first conversation to be with someone who does this for a living, that's exactly what a Flotog BA Insights session is. Book one and bring whatever you're stuck on.

Turn it all into a story

When you finally apply, you are not selling a blank slate. You are selling the transferable experience you learned to name yesterday, plus the craft you deliberately studied, plus the real work you did before anyone gave you the title. Package that into a simple, honest story: here is a real problem I analysed, here is what I produced, here is what changed because of it. That is a portfolio, and a portfolio of actual work beats a stack of certificates every time, because it answers the only question a hiring manager truly cares about: can this person already do the job?

Where to actually look for the first role

When you start applying, aim wider than the exact title business analyst. Many first roles hide under other names: junior analyst, product analyst, project support, operations analyst, or business-analyst-adjacent work inside teams that will let you grow into it. Smaller companies and internal moves are often kinder doors than large firms hiring cold, because they care more about whether you can think than whether your CV ticks every box. And do not underestimate being visible and specific. People who share what they are learning, and who can point to real work they have done, get found and referred far more often than people who apply silently into the void.

The honest part

None of this is quick, and none of it is a straight line. You will be told no more than once, and the first role is the hardest thing to get in the entire career. After it, the path opens quickly. Two traps snare people at this stage, and both are worth naming.

• The first is hiding inside endless certifications as a substitute for doing the work, because collecting courses feels safer than producing something and risking a no.
• The second is waiting until you feel ready, which never arrives. The people who get in are rarely the most qualified on paper. They are the ones who started behaving like an analyst before anyone gave them permission to.

So pick one thing this month: analyse one real process, or ask one person to mentor you. The path in is not a single leap. It is a series of small, deliberate moves that quietly add up to proof.

Go out and be successful.

Oluwatosin Ogunkoya | Flotog BA Insights  |  www.flotogbainsights.com

Tomorrow: The Honest Truths and the Roadmap - The whole way in on one page, and the things nobody tells you about breaking in.