Map a real process
Map how a familiar service works today, such as opening a bank account, and mark three pain points.
Understand how a business works, find what needs to change and turn it into clear requirements teams can build.
You have reached the end of the beginner stages. Prove what you learned with a project.
You have reached the end of the intermediate stages. Prove what you learned with a project.
You have reached the end of the advanced stages. Prove what you learned with a project.
Map how a familiar service works today, such as opening a bank account, and mark three pain points.
Interview three people about a shared problem and summarise their needs in one page.
Write user stories with acceptance criteria for a small app, prioritised with MoSCoW.
Use SQL or a spreadsheet to test one assumption a stakeholder made, and report what you found.
Write a business case for a process change with costs, benefits, risks and a recommendation.
Plan training, communication and success measures for introducing a new system.
The same roadmap as a reading list: every stage, what each topic covers, and which ones are optional.
Bridge the people who have a problem and the people who will solve it, with evidence and clear documents.
Departments, processes, goals and how money flows through a business.
Open questions, follow-ups and checking you understood correctly.
Organise lists, compare options and summarise data quickly.
Find out what people need, not just what they ask for.
Map who is affected, who decides and how to involve each group.
Look past symptoms with techniques such as the 5 whys and fishbone diagrams.
Compare where the business is with where it wants to be.
Clear, testable statements of what a solution must do.
Describe needs from the user's point of view, with conditions for done.
Step-by-step descriptions of how a user and a system interact.
Decide what matters most with methods such as MoSCoW.
Draw how work flows today and how it should flow tomorrow.
Make clean flowcharts and diagrams others can edit.
Entities, attributes and relationships behind the system.
Check facts in the data yourself instead of relying on opinions.
Refine the backlog, answer questions quickly and accept finished work.
Check with real users that the solution meets the requirements.
Help people adopt the new way of working with training and support.
Compare costs, benefits and risks so leaders can decide.
Track whether the change delivered the promised results.
Lead with the decision you need and keep the detail in the appendix.
Learn your industry deeply, whether banking, health, telecoms or retail.
IIBA certificates such as ECBA and CBAP are widely recognised.
They study how an organisation works, find problems and opportunities, and describe the changes needed in requirements that teams can build and test.
Usually not. SQL, spreadsheets and diagramming help a lot. Some technical BA roles expect more understanding of systems and APIs.
Often by moving from support, operations, finance, testing or sales inside a company, where they already know the business.
© 2026 KamerLink. All rights reserved.