A complete, honest roadmap for the skills business analysts actually use, from domain understanding and requirements gathering through documentation, process modelling, data analysis, reporting, stakeholder communication, agile ways of working, and AI. It runs top to bottom, foundational to advanced, so you always know what comes next. Free to read, no signup required.
How to use this: each step below is collapsed. Tap one to expand its details, skill pills, and guidance (only one opens at a time). Work down the spine in order; each stage assumes the ones above it. Business analysis is learned by doing, so practise these on real or realistic problems, because judgement develops through actual work.
01
A business analyst sits between the people with a problem and the people who build a solution. Start by understanding that bridge, because the role varies a lot by company.
The core of the role: Understanding a business need, defining what a solution must do, and making sure what gets built actually solves the problem.
What a BA is not: Not a note-taker or a ticket-writer. The value is in asking the right questions and turning fuzzy asks into clear, agreed requirements.
Where BAs work: IT and software, but also operations, finance, and strategy. The tools shift, the analytical thinking stays the same.
BA, product, and project roles: How the BA role overlaps with and differs from product managers and project managers, which matters when you apply.
The BA role is defined more by a way of thinking than by a fixed toolset. People who can understand a problem deeply and communicate it clearly stay valuable across every industry.
The BA roleProblem framingBridge roleIndustry variations
02
You can’t analyse a business you don’t understand. Domain knowledge is what turns a generic analyst into a trusted one.
How businesses operate: Core functions, how they make money, and how a change in one area ripples into others.
Business processes: Seeing work as processes with inputs, steps, and outputs, which is the lens most BA work runs through.
Metrics & KPIs: The measures a business actually cares about, so your analysis connects to outcomes leaders track.
Domain depth: Learning the specific field you work in (finance, healthcare, retail) so your recommendations reflect how it really works.
Business operationsProcessesMetrics & KPIsDomain knowledge
03
The most important BA skill is drawing out what people actually need, which is often different from what they first ask for.
Elicitation techniques: Interviews, workshops, surveys, and observation, and knowing which fits a given situation.
Asking good questions: Open questions, probing for the why behind a request, and surfacing the assumptions nobody stated.
Functional vs non-functional: What a system must do versus how well it must do it (speed, security, reliability), because both matter.
Managing scope: Separating the essential from the nice-to-have early, before scope quietly balloons.
People rarely hand you the real requirement. They describe a solution they imagined. The BA’s job is to get back to the underlying problem before anything gets built.
ElicitationInterviews & workshopsFunctional vs non-functionalScope management
04
A requirement that lives only in your head helps no one. Writing clearly and unambiguously is a defining BA skill.
Requirements documents: Business and functional requirements written so that a stakeholder, a developer, and a tester all read them the same way.
User stories & acceptance criteria: Breaking needs into clear, testable increments with explicit conditions for done, the common format on agile teams.
Use cases: Describing how a user and a system interact step by step to reach a goal, including the paths that go wrong.
Traceability: Linking each requirement back to a business need and forward to what was built, so nothing is lost or gold-plated.
Modern business analysts are expected to work with data, not only words. The ability to pull and interpret numbers makes your recommendations credible.
Spreadsheets: Formulas, pivot tables, and lookups to summarise and slice data, still the most-used analysis tool in business.
SQL basics: Querying a database directly with SELECT, joins, and aggregation, so you’re not dependent on someone else for every number.
Interpreting data: Reading trends and comparisons with a skeptical eye, and telling correlation apart from causation.
From data to insight: Turning a table of numbers into a clear finding a decision-maker can act on.
Most BAs now work on agile teams. Understanding how modern delivery works lets you fit in and add value from day one.
Agile basics: How iterative delivery works (backlogs, sprints, and continuous refinement) and where a BA fits in it.
Backlog & refinement: Keeping requirements prioritised, refined, and ready so a team always has clear next work.
Working with product & dev: Collaborating with product managers, designers, and engineers rather than handing over a document and leaving.
User acceptance testing: Helping validate that what was built meets the requirements before it reaches real users.
Agile & scrumBacklogRefinementUATCollaboration
11
AI is changing analyst work and creating new projects to analyse. Understanding it is quickly becoming part of the job.
AI in your workflow: Using AI to draft documentation, summarise research, and speed up data work, while you verify and own the result.
Analysing AI projects: Gathering requirements for AI features, which behave differently from deterministic software and need different expectations.
Data literacy: Enough understanding of data and models to ask sharp questions and spot where an AI initiative is over-promising.
AI raises the value of the core BA skills, not lowers them. Framing the right problem and communicating it clearly is exactly what AI can’t do for you.
AI in the workflowRequirements for AIData literacyResponsible use
Build a requirements and analysis pack
You can’t show business-analysis skill with a certificate alone. A worked example, a real or realistic problem taken from need to specification, is the most convincing thing you can bring to an interview.
Pick a business problem, interview a few people about it, and write up the real requirements you uncover.
Map the current process as-is, then design an improved to-be version with the changes marked.
Pull real or sample data on the problem and build a short dashboard that supports your recommendation.
Write a one-page business case: the problem, your proposed solution, and the cost, benefit, and risk.
Write it up clearly and keep it. Being able to walk an interviewer through how you got from a vague ask to a clear specification is exactly what the role is about.
Frequently asked questions
Do I need to know how to code to be a business analyst?
No. You need enough technical literacy to work with developers and increasingly to query data with SQL, but you don’t write production code. The core skills are understanding problems, defining requirements, and communicating clearly.
What’s the difference between a business analyst and a product manager?
They overlap and the line varies by company. Broadly, product managers own what to build and why against a business strategy and are accountable for the outcome; business analysts focus on understanding needs and specifying requirements in detail, often within IT projects. The analytical and communication skills transfer between the two.
How long does it take to become a business analyst?
It depends far more on building real skills and some domain knowledge than any fixed timeline. Many people move into BA roles from adjacent jobs (operations, support, QA, domain expertise) by taking on analysis work where they are, then moving over.
Do I need a specific degree or certification?
No specific degree is required. Certifications exist and can help pass some hiring filters, but demonstrated ability, a strong understanding of a domain, and clear communication carry more weight in interviews.
How much data analysis do I really need?
More than in the past. You don’t need to be a data scientist, but comfort with spreadsheets and basic SQL, plus the judgement to interpret numbers honestly, is now expected in most BA roles and makes your recommendations far more credible.
Do I need to master every topic on this roadmap?
No. Requirements gathering, documentation, process analysis, and stakeholder communication are the core. Data modelling, deeper data analysis, and specific tools you deepen as your role demands, and the mix varies a lot by industry.
Ready to prepare for real interviews with a personalized plan?
This roadmap is the map. When you’re ready to actually get hired, Interview Ready turns it into a personalized 30-day plan built around your resume and a specific target role: real practice in the right order (requirements, case studies, behavioural), a guided project track alongside it, and progress tracking the whole way. Start free.
