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: tap a step on the map to open its details, skill pills, and guidance in a side panel. 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.
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
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.
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.
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.
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.
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.
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.
