How to Become a Business Analyst (And Where It Leads)

A business analyst works out what a business actually needs before anyone builds it. It's one of the most accessible ways into product and project work — the entry certification requires no experience at all, while the senior one demands roughly 3.6 years of full-time BA hours.

We've written repeatedly on this site that Product Owners often arrive from business analysis — and then moved on without explaining what that means. This is that article. Business analysis is one of the most accessible routes into product and project work, and it's also one of the most misunderstood roles in the field.

What a business analyst actually does

The caricature is "the person who writes requirements." The reality is closer to investigation. A stakeholder arrives asking for a specific feature; the analyst's job is to find out what problem sits behind the request, whether that problem is real, whether the feature would solve it, and what it would cost elsewhere in the business.

That work looks like this in a typical week:

• Interviewing stakeholders and, crucially, the people who do the work day to day
• Mapping how a process currently runs — which is almost never how anyone thinks it runs
• Identifying where the real cost or delay sits, rather than where it's assumed to sit
• Writing requirements a team can act on without three follow-up questions
• Modelling data and process flows so a decision can be argued about visually
• Validating afterwards that what was built actually solved the problem

BA, Product Owner, or project manager?

These three roles overlap enough to confuse everyone, including employers who advertise one and describe another. The clean way to separate them is by the question each is accountable for answering.

In small organizations one person often does all three, which is where the confusion starts. In larger ones they're distinct jobs with distinct authority. For the roles alongside this one, see what a Product Owner actually does and Scrum Master vs project manager.

The realistic route in

Business analysis is unusually open to career-changers, because the core skills — asking good questions, listening properly, structuring messy information, writing clearly — are built in almost any job that involves understanding how an organization works.

That's why analysts so often come from adjacent roles rather than from a BA degree:

• Operations or customer support — you already know where the process breaks
• Finance or accounting — you're used to interrogating numbers and reconciling them
• Domain specialists in healthcare, insurance, logistics — the industry knowledge is often the harder half
• Testers and QA — you already read requirements critically for a living
• Project coordinators — you've watched requirements go wrong from close range

The certification ladder, and what it really costs

The main certifying body is IIBA, and its credentials are tiered by experience rather than by subject. This matters more than it sounds, because two of the three tiers are closed to you until you've done years of the work.

Two details are worth pulling out of that table, because they change how you should plan.

The ECBA is the opposite, and it's the useful one for a career-changer. It requires no experience at all — just 21 hours of professional development and knowledge of IIBA's BABOK Guide, which is the body of knowledge the exam draws from. From 2026 the first year of IIBA membership is included in the exam cost, so the quoted $300 to $395 covers both.

Is the certification worth it?

Honestly: it helps most when you have nothing else to show. If you're changing careers and can't point to analysis work you've done, the ECBA signals that you've learned the vocabulary and the framework, and it gets you past filters. If you've already been doing analysis under another title, your examples matter far more than the certificate — the same conclusion we reach about project management in do you need a certification to be a project manager.

One genuine caution: unlike project management, business analysis has no single dominant credential that employers routinely name in postings. The PMP is asked for by name; the ECBA rarely is. That doesn't make it worthless — it makes it a learning investment and a signal, rather than a key that unlocks a specific door.

Where the career leads

Business analysis is a genuine destination for people who like the investigative work — senior and lead analyst roles exist, and domain expertise compounds over years. But it's also one of the best-positioned launchpads in this field, because the skills transfer directly.

The move to Product Owner is the most common of these, and it's a real step up in authority rather than a sideways retitle — the analyst recommends, the Product Owner decides. If that appeals, the route is in how to become a Product Owner. If delivery attracts you more than product, see how to become a project manager, and the entry rung below it in how to become a project coordinator.