Careers & Certification
How to build a business analyst portfolio without experience
Part of our guide to how to become a business analyst.
Why a portfolio helps when you have no experience
Hiring managers reading an application for a first analyst role face a problem: they cannot tell from a list of skills whether you can actually do the work. A portfolio answers that question. It shows how you approach a problem, how you write and how you reason, which is exactly what an experienced CV would otherwise prove.
A good portfolio is small. Three well-explained pieces beat fifteen thin ones. The reader is usually busy, so each piece should be understood in a couple of minutes. Think of it as a short conversation on paper: here is a problem, here is what I found, here is what I proposed, and here is what I learned.
It also helps you. Writing a case study forces you to organise your thinking, and in an interview you can walk through something concrete rather than speaking in generalities. If you are still deciding on a route into the role, read how to become a business analyst with no experience.
Honesty rules: what makes a portfolio trustworthy
This is the most important section. A portfolio full of invented experience is worse than none, because interviewers ask follow-up questions and the story collapses. Follow these rules.
- Label every piece. Mark it clearly: "Practice project", "Workplace improvement (anonymised)", "Volunteer project for a local club" or "Fictional case study".
- Never imply a client or employer you did not have. Do not write "Delivered for a major bank" for a fictional bank exercise.
- Do not invent numbers. If your fictional data says returns fell by a certain percentage, say it is illustrative. For real work, give figures only if you can source them, and describe results qualitatively if you cannot.
- Protect confidentiality. Remove names, customer data, internal figures and anything covered by an employer's policy. If in doubt, ask permission or use a fictional version.
- State your role. If you worked in a team, say what you did and what others did.
- Do not copy. Using someone else's template is fine; presenting someone else's finished case study as yours is not.
- Do not claim certifications you do not hold, and never describe practice as accredited training. See the certification guide.
Honest labelling is not a weakness. Interviewers respect a candidate who says, "This was a practice project, here is what I learned and here is what I would do differently with a real stakeholder."
Write
- “Practice project” or “Fictional case study”
- “Workplace improvement (anonymised)”
- “Figures are illustrative”
- What you did, and what others in the team did
Never write
- “Delivered for a major bank” for a fictional exercise
- Invented results presented as real
- A company logo on fictional work
- A certification you do not hold
What to include: the artefacts that show your thinking
You do not need every document. Choose pieces that show the skills employers care about, and make sure the set tells a coherent story. These are the most useful.
| Artefact | What it shows | Guide |
|---|---|---|
| Problem statement and scope | You can frame a problem and set boundaries | Problem statement |
| Stakeholder map and RACI | You think about people and ownership | Stakeholder analysis and RACI |
| Interview plan and notes | You gather information well | Elicitation techniques |
| AS-IS and TO-BE process model | You can model and improve a process | AS-IS vs TO-BE |
| User stories with acceptance criteria | You write testable requirements | User stories |
| A SQL query with explanation | You can check data | SQL for business analysts |
| KPI definition and dashboard sketch | You can specify measures | KPI vs metric |
| Test scenarios or a traceability table | You connect needs to tests | Traceability matrix |
| Reflection | You learn and are honest | A short paragraph |
For a first portfolio, aim for two or three case studies that each include four or five of these artefacts, rather than one artefact per case. The strongest portfolios show the thread from problem to evidence to requirement to test.
- ProblemFramed, with scope.
- EvidenceInterviews, observation, a query.
- RequirementStories with acceptance criteria.
- TestScenarios that prove it works.
Three project ideas you can start this week
1. Improve a process at your current workplace
Choose something small and annoying, such as how leave requests or expense claims are processed. With your manager's agreement, observe it, interview two colleagues, map the current steps, list pain points and propose one change with a user story and acceptance criteria. Anonymise before sharing outside work.
2. Analyse a public or fictional dataset
Take a small dataset, such as the fictional tables in our SQL practice guide. Define a business question, write the query, check the result and explain its limits. Then define the KPI and sketch the dashboard that would show it.
3. Run a fictional end-to-end project
Work through a full simulated project, from business case to go-live. Our free worked project guide and BRD example show the shape, and the BA Lab offers a longer simulated company project with tasks and feedback at each stage. If you use any guided practice, remember to label the output as practice.
Bonus: volunteer
A local charity or club often needs help describing a process or choosing a tool. Agree the scope in writing and keep it small. Real stakeholders produce real feedback, which is gold in an interview.
A case study template you can reuse
Keep each case study to one or two pages. Use these headings in this order.
- Title and label (for example, "Reducing missed appointments: practice project").
- Context in two or three sentences: the fictional or anonymised organisation and the situation.
- Problem statement with the evidence you had.
- What I did as a short list of steps: interviews, observation, data checks.
- What I found with one diagram or table.
- What I proposed, including the user stories and acceptance criteria.
- How I would test it with two or three scenarios.
- What I would do differently or what remains uncertain.
Write in plain language and show your reasoning. Avoid jargon for its own sake, and avoid claims you cannot support. A reader should finish with the impression: this person thinks clearly, writes clearly and is honest.
Diagram in words
- Title and label: “Reducing missed appointments: practice project”
- Context: Two or three sentences about the organisation.
- Problem: Statement and evidence
- What I did: Interviews, observation, data
- What I found: One diagram or table.
- What I proposed: Stories and criteria
- How I would test it: Two or three scenarios
- What I would do differently: What remains uncertain.
A worked example: one short case study
Below is a compact example, using a fictional company, to show the shape. It is not a template to copy word for word; use your own subject and your own reasoning.
Reducing missed appointments (practice project, fictional company)
Context
Orchard Health Clinics is a fictional group of clinics. Reception staff report that patients often miss appointments without notice, leaving gaps that could have been used.
Problem statement
Patients miss appointments without cancelling, which leaves clinic slots unused. In the practice dataset of 400 invented appointments, 52 were missed, which is 13 percent; the figure is illustrative and does not describe any real clinic.
What I did
- Wrote five interview questions and role-played a receptionist interview, recording the answers as notes.
- Mapped the AS-IS booking process and found that reminders depend on one receptionist remembering to phone.
- Wrote a SQL query to count missed appointments by weekday:
SELECT weekday, COUNT(*) FROM appointments WHERE status = 'missed' GROUP BY weekday. The practice data showed more misses on Mondays.
What I proposed
Story: "As a patient, I want a text reminder the day before my appointment, so that I do not forget it." Acceptance criteria: the reminder is sent only to patients who consented; it includes the date, time and clinic; it is not sent for cancelled appointments; and a failed send is logged.
How I would test it
Three scenarios: a consenting patient receives a reminder; a patient who withdrew consent does not; and an appointment cancelled after scheduling does not trigger a reminder.
What I would do differently
I used invented data, so the cause is not proven. With real stakeholders I would check whether Monday misses relate to weekend bookings and whether text reminders are acceptable to patients.
Notice what makes this credible: it is labelled as practice, the number is flagged as illustrative, the reasoning is visible and the last section admits what is unknown. That honesty is a feature.
Where to put it and how to talk about it
- Format: a single PDF, a simple web page or a shared folder with a short index. Make sure it opens on a phone and carries no confidential information.
- Link it: from your CV and your professional profile. Keep a one-line description of each case study.
- Tailor it: lead with the case study closest to the job. A banking role should see the transfer rules; a logistics role should see the process model.
- Prepare to talk: for each piece, be ready to explain the decision you are proudest of, the mistake you made and the question you would still ask. The interview questions guide shows how to turn these into answers.
- Keep improving: add a short note when you update a piece, and remove anything you no longer stand behind.
Mistakes to avoid
- Submitting a long document nobody will read.
- Including only templates with no reasoning.
- Putting a company logo on fictional work.
- Showing diagrams with no explanation of what they mean.
- Claiming outcomes you cannot show.
A portfolio is not a credential, and it does not guarantee interviews. It is evidence of how you think, which you build with each practice cycle. The BA Lab is one way to produce practice artefacts across a whole project, and the glossary helps you use the vocabulary correctly. For a broader skills checklist, see business analyst skills.
Frequently asked questions
What should a business analyst portfolio contain?
Two or three short case studies showing the thread from problem statement to evidence, process model, requirements, acceptance criteria and a reflection. Each should be clearly labelled as real, anonymised or practice work.
Can I use fictional projects in my portfolio?
Yes, if you label them clearly as practice or fictional. Employers care about your reasoning, and honest labelling builds trust.
How many projects do I need?
Two or three good ones are enough. Quality and clear reasoning matter more than quantity.
Should I include screenshots of Jira or Confluence?
Only if they contain no confidential information. A cleaned-up example or a mock-up created for the portfolio is safer.
Where should I host my portfolio?
Anywhere you can control access and that opens easily: a PDF, a simple web page or a shared document. Make sure the link works on a phone and that nothing confidential is included.
This article is educational. All companies, people and numbers in the examples are fictional. BA Mentorship does not issue professional certifications and cannot guarantee any job or interview outcome.