Interview Insights · Business Analyst
Why Every Business Analyst Should Practice Explaining Their Portfolio Aloud
Quick summary — BA portfolio
Interviewers do not grade your portfolio documents; they grade how you explain the thinking behind them. Most BA portfolios I see contain the right artefacts: a business requirements document, a process map, a few user stories, maybe a dashboard. The difference between candidates appears when I say 'take me through this'. Some open files one by one. Others tell me a short story: a business problem, how they analysed it, which artefact captured which decision, and what they would change now. That second skill is learnable, but only by saying it out loud several times.
In this guide you will learn:
- Which three pieces to put at the front of your BA portfolio
- A problem-to-decision story that ties the pieces together
- How to present each artefact in one or two sentences
- The questions interviewers ask about portfolio work and how to answer
- A rehearsal plan for a five-minute portfolio walkthrough
SECTION 01Choose three pieces and give each one a job
A long portfolio is not a strong portfolio. In a typical interview you will get a few minutes to present, so you need a small set of pieces that together show the full BA cycle. I suggest three, each with a clear job: one that shows you can understand a problem, one that shows you can document a solution, and one that shows you can work with data.
When you rehearse aloud, you will quickly notice which pieces you can talk about for two minutes and which you can only describe in a sentence. Keep the first kind at the front. Move the second kind to an appendix you open only if asked.
| Portfolio piece | Its job in the story | What to point at | Common mistake |
|---|---|---|---|
| As-is and to-be process map | Shows you understood the real problem | The step you removed or changed | Showing only the to-be map with no before |
| Short BRD or user story set | Shows you can document a solution | One rule you clarified with stakeholders | Twenty pages nobody can scan |
| Dashboard or data analysis | Shows you can support a decision | The one number that drove a choice | Many charts with no question answered |
| One-page case summary | Holds the three together | Problem, method, outcome in five lines | Missing entirely, so the pieces feel random |
CASE: Missed appointments at a small dental clinic
PROBLEM
Patients booked by phone. No reminders. Front desk said
many slots went empty each week.
WHAT I DID
- Interviewed 2 front-desk staff and the clinic owner
- Mapped the as-is booking process (BPMN)
- Analysed 3 months of appointment records in Excel
- Wrote 8 user stories for SMS reminders and online booking
KEY FINDING
Most no-shows were first-time patients booked more than
a week ahead.
RECOMMENDATION
Reminder 24 hours before, confirm-or-cancel reply, and a
short waitlist to refill cancelled slots."This is a practice case I did on a dental clinic that
was losing appointments.
I started by talking to the front desk, because they
handle bookings. Then I mapped how booking works today -
you can see there is no reminder step anywhere here.
The appointment data showed that no-shows were mostly
first-time patients booked far in advance.
So my user stories focus on a reminder with a
confirm-or-cancel option, plus a waitlist. If I did this
again, I would also interview a few patients, not just
staff."The spoken version is short and uses the artefacts as evidence, not as the topic. That is the shift you are rehearsing: you are telling a case, and the documents are the exhibits.
SECTION 02Explaining each artefact in two sentences
Once the story is in place, each artefact needs a two-sentence explanation: what it is, and what decision or insight it shows. This is harder than it sounds. Candidates often describe the format ('this is a swimlane diagram with four lanes') instead of the meaning ('this shows the front desk handles three hand-offs that the owner did not know about').
Practise these lines aloud until you can say them without looking at the screen. If you cannot explain an artefact in two sentences, it probably does not belong at the front of your portfolio.
| Artefact | Format sentence (weak) | Meaning sentence (strong) | Likely follow-up |
|---|---|---|---|
| BPMN process map | It has swimlanes and gateways | It shows bookings depend on one person answering the phone | Where is the bottleneck? |
| User story | As a patient, I want a reminder | It solves the forgot-the-date problem, and the criteria cover the cancel reply | How would you test it? |
| Excel pivot analysis | I made a pivot table by month | It showed first-time patients cause most no-shows | How did you clean the data? |
| Low-fidelity wireframe | I made it in Balsamiq | It tests whether patients can rebook in two taps | Did anyone try it? |
STORY BK-03
As a patient with an upcoming appointment,
I want an SMS reminder the day before,
so that I do not miss my slot.
Acceptance criteria
- Given an appointment tomorrow, when it is 10 AM today,
then the patient receives an SMS with date, time and
clinic name.
- Given the patient replies C, then the slot is released
and the first waitlisted patient is notified.
- Given the patient replies Y, then the booking is marked
confirmed in the front-desk view.
- Given no reply by 6 PM, then the front desk sees the
booking flagged for a call.Excel steps I can describe aloud:
1. Removed test rows and duplicate bookings
(same patient, same slot, entered twice).
2. Added a column: IsFirstVisit = TRUE/FALSE.
3. Added a column: LeadDays = AppointmentDate - BookedDate.
4. Inserted PivotTable:
Rows -> IsFirstVisit, LeadDays (grouped by 0-7, 8+)
Values -> Count of Booking ID
Filter -> Status = No-show
5. Compared with the same pivot for Status = Attended.
The point: the first-visit, 8+ day group stood out.If an interviewer asks you to open the pivot, be ready to explain the cleaning steps. Data cleaning questions are common, and they reveal quickly whether the analysis was really yours.
SECTION 03Handling the questions that come after the walkthrough
A portfolio walkthrough is an invitation for questions, and the questions are where interviewers actually decide. They will test whether you understood the stakeholders, whether you can defend your recommendation, and whether you know the limits of your own work. Candidates who rehearse only the presentation and not the questions often do well for four minutes and then stumble.
The good news is that portfolio questions are predictable. Write them down, answer them aloud, and keep each answer under a minute.
| Question | What it tests | Strong answer starts with | Avoid |
|---|---|---|---|
| Who disagreed with you? | Stakeholder handling | The owner wanted online booking first, staff wanted reminders... | Everyone agreed |
| What would you measure after launch? | Outcome thinking | No-show rate for first-time patients, compared with before | We would see if it works |
| What did you leave out? | Scope judgement | Payments, because it needed a gateway decision first | Nothing, it was complete |
| What would you do differently? | Self-awareness | Talk to patients earlier, not just staff | I would use a better tool |
Q: Did any stakeholder disagree with your recommendation?
A: Yes. The owner wanted a full online booking system
first. The front desk wanted reminders, because that was
the pain they saw daily.
I showed both of them the no-show analysis. Reminders
attacked the biggest cause with much less effort, so we
agreed to do reminders and the waitlist first, and keep
online booking as phase two.
I wrote that decision and the reason into the BRD so it
would not be reopened every meeting.Q: How would you know your solution worked?
A: I would track three things, each against the months
before launch:
1. No-show rate, split by first visit vs repeat visit.
2. Share of cancelled slots refilled from the waitlist.
3. Front-desk time spent on reminder calls.
I would not judge it after one week. I would agree a
review point with the owner, because seasonal patterns
can hide or exaggerate the change.SECTION 04A five-minute portfolio walkthrough you can rehearse
Use these three tabs to build and rehearse your walkthrough. The outline sets the timing, the recording routine helps you hear what the interviewer hears, and the checklist keeps your portfolio itself clean.
0:00 - 0:30 Who I am and what this case is
(practice / college / volunteer - be clear)
0:30 - 1:15 The business problem in plain words
Who was affected, and what it cost them
1:15 - 2:30 How I analysed it
Stakeholders spoken to, process map, data used
2:30 - 3:45 What I produced and why
Stories or BRD, one rule I clarified
3:45 - 4:30 Recommendation and how to measure it
4:30 - 5:00 What I would do differently next time
Then stop, and invite questionsDAY 1 Record the full walkthrough on your phone.
Do not stop if you stumble.
DAY 2 Listen. Note every place you said 'basically',
'so yeah' or read a slide word for word.
DAY 3 Re-record with the screen hidden from yourself.
Can you still explain each artefact?
DAY 4 Present live to a friend. Ask them for three
questions you did not expect.
DAY 5 Answer those three questions aloud, then
record the full walkthrough one last time.[ ] One-page case summary at the very front
[ ] As-is AND to-be process maps, clearly labelled
[ ] BRD or story set short enough to scan in a minute
[ ] At least one analysis with the key number visible
[ ] Clear label: practice case / college / real project
[ ] No client names or data you are not allowed to share
[ ] Files open fast, no broken links in the PDF
[ ] A backup copy offline in case screen sharing fails
[ ] A 'what I would change' line for every caseSECTION 05Small habits that make a portfolio presentation land
The content matters most, but these habits decide whether the interviewer can follow it.
- Share one window, not your desktop — Keep the case summary open in a single PDF or slide window so the interviewer never watches you hunt through folders.
- Point before you explain — Say 'look at the third lane here' before you describe it, so the interviewer's eyes are where your words are.
- Pause after the problem — Stopping for a breath after the problem statement gives the interviewer time to care about it before you show the solution.
- Use the business's words — Say 'empty slots' and 'reminder calls' rather than 'resource utilisation', because the stakeholder in your story would talk that way.
- End with a question — Closing with 'which part would you like me to go deeper into?' hands the interviewer control and usually leads to your strongest material.
SECTION 06Interview Q&A — BA portfolio
Q1What should a fresher business analyst include in a portfolio?
One or two complete cases are better than many fragments. Each case should have a short summary, an as-is and to-be process map, a small set of user stories or a short BRD, and one piece of data analysis. Label clearly whether it is a practice case, college project or real work.
Q2How do you present a portfolio in a BA interview?
I start with the business problem in plain words, then explain how I analysed it, which artefacts I produced and what each one showed, and finally my recommendation and how I would measure it. I keep it to about five minutes and then invite questions.
Q3What if my portfolio is based on a practice case, not a real client?
That is fine as long as you say so. Interviewers mainly want to see your method: how you framed the problem, which questions you asked and how you documented decisions. A clearly labelled practice case explained well is stronger than a vague claim about real work.
Q4How do you show stakeholder management in a portfolio?
I include a short stakeholder list with each person's interest and influence, and I explain one disagreement and how it was settled. In a practice case I may have role-played stakeholders with classmates, and I say that honestly.
Q5Which tools should appear in a BA portfolio?
Tools matter less than the thinking, but common ones help: Excel or Power BI for analysis, a BPMN tool or Visio-style diagrams for process maps, Jira-style story formats, and a simple wireframing tool. Show the tool output only where it supports the story.
SECTION 07Test yourself — BA portfolio quiz
Five questions. No sign-up.
0 / 5Pick an answer to see why it is right or wrong.
SECTION 08Frequently asked questions
Do business analysts need a portfolio?
It is not always required, but it helps a lot, especially for freshers without work experience. A small portfolio with one or two well-explained cases gives the interviewer concrete material to discuss instead of only theory questions.
How do I make a business analyst portfolio with no experience?
Pick a realistic problem, such as a small shop, clinic or college process, and run a full BA cycle on it: interview people, map the current process, analyse some data, write user stories and propose a solution. Label it as a practice case.
What format should a BA portfolio be in?
A single PDF or slide deck with a one-page summary per case works well because it opens quickly and is easy to share on a call. Keep source files such as spreadsheets ready in case the interviewer asks to see detail.
How many projects should be in a business analyst portfolio?
Two or three is usually enough. It is better to have a few cases you can explain deeply than many that you can only describe in a line. Interviewers rarely look at more than one or two in detail.
Can I include a Power BI dashboard in my BA portfolio?
Yes, if it supports a business question in your case. Explain which decision the dashboard helps with and which number matters most. A dashboard without a clear question looks like tool practice rather than analysis.
How can I prepare for Business Analyst interview answers with a trainer?
Yes. Uncodemy's Business Analyst Training Course in Noida (classroom and online) includes live projects, one-to-one mock interviews and resume reviews, so you practise Business Analyst interview answers with trainer feedback before the real interview. You can book a free demo class from this page to see how the sessions work.
SECTION 09Related reads
Classroom & online · Noida
Build a BA portfolio you can talk about
Our Business Analyst Training Course takes you through real-style case studies, process mapping, user stories and analysis, so you finish with portfolio pieces and practice presenting them.
Talk to a counsellor for current fees- Case study based learning
- Process maps & BRD practice
- Portfolio review sessions
- Mock interviews