How to Build a Business Analyst Portfolio Without BA Experience
A business analyst portfolio can help you explain how you approach a problem, even when you have not held a business analyst job title. The strongest starting point is one clear case study that connects a business need to evidence, requirements and a way to check the proposed improvement.
For UK career changers, this is a practical learning exercise and a useful interview aid. A portfolio does not replace an employer’s entry requirements or guarantee an interview. Label training projects, fictional scenarios and unpaid work accurately.
What should a business analyst portfolio demonstrate?
The National Careers Service business analyst profile describes a role centred on understanding business problems and considering improvements. Your portfolio should therefore show your reasoning, rather than simply displaying attractive documents. The exercises below are our suggested approach to practising those skills.
A reviewer should be able to see what you investigated, what you assumed, who would be affected and why you recommended a particular change. A short explanation of an imperfect decision is more useful than a polished template you cannot discuss.
1. Choose a small, realistic problem
Start with a process you understand: booking appointments, handling customer returns or organising volunteer shifts. Keep the scope narrow enough to investigate. For a fictional appointment-booking project, the problem might be incomplete booking information causing extra follow-up calls. State that this is a simulated problem and that the data is invented for practice.
Write a one-paragraph brief with the current problem, who experiences it, the desired outcome and the boundaries. Avoid starting with “we need an app”. A better starting question is “what prevents the team from confirming appointments with the information already available?”
2. Separate evidence from assumptions
Create a simple evidence log. Record the source, what it tells you and what remains uncertain. In a real volunteer project, obtain permission before collecting or sharing information. In a simulation, explain which interviews or observations you would conduct instead of inventing stakeholder quotations.
List the people affected: customers, the booking administrator, service staff and a manager. For each, write what they need and what questions you would ask. For example, the administrator may need complete contact details while customers may need a straightforward way to correct a booking.
3. Map the current process and propose a change
Draw the main steps from the initial request to confirmation. Show who performs each step, where information passes between people and what happens when details are missing. A readable diagram in a familiar tool is enough; explain your notation if it is not obvious.
Compare at least two options, such as improving the existing form or introducing a different booking tool. Consider effort, accessibility, privacy, ongoing support and the effect on staff. Record why you favour one option and what evidence could change your recommendation.
4. Write requirements you can check
Replace “make booking better” with a specific need: “The administrator needs a reliable way to contact the customer before confirming a booking.” Then describe observable acceptance criteria. For example: a request cannot be submitted without one supported contact method, and the customer receives a clear explanation when information is missing.
Show how each requirement connects to the problem. Prioritise the essentials and explain the trade-offs. Do not make every feature mandatory. Include questions that still need stakeholder agreement, such as which contact methods the organisation can support.
5. Explain how success would be evaluated
Suggest a baseline and a measurement plan, such as tracking how many requests require clarification before and after a pilot. Consider an unintended effect too: a longer form might reduce incomplete submissions but discourage some customers. If you have not run the pilot, describe expected benefits as hypotheses, not achieved results.
Package your case study for a reviewer
Lead with a brief summary, then show selected evidence: your problem statement, process map, options comparison, a few requirements and an evaluation plan. Add a reflection on what you would improve. Use readable headings, descriptive links and diagrams that remain legible on a laptop. Test access permissions before including a portfolio link in an application.
Keep personal details, client information and employer documents out of public examples. Redrawing a confidential process does not automatically make it safe to publish. When permission is unclear, create an original fictional case instead.
Frequently asked questions
Do I need specialist software? Start with tools you can use confidently. Clear analysis matters more than a long list of applications.
Can I include coursework? Yes, where sharing is permitted. Identify it as coursework, credit collaborators and explain your personal contribution.
How many projects should I include? Begin with one complete case you can defend. Add another when it demonstrates a different skill rather than repeating the same templates.
Explore our business analysis training and career support to discuss your learning goals. When comparing programmes, our business analyst course guide can help you frame questions about practical work, feedback and interview preparation.