
6 Feb 2022
"I can't get a BA job without a portfolio. But I can't build a portfolio without a BA job."
I hear this every week.
And I get it. It feels like a catch-22.
But here's the truth: You don't need a BA job to build a BA portfolio.
You just need to reframe what you're already doing.
Let me show you how.
The Problem with "I Don't Have Experience"
Most aspiring BAs think they have zero BA experience.
But when I audit their CVs, I find:
They've mapped processes (they just called it "documenting workflows")
They've gathered requirements (they just called it "talking to stakeholders")
They've identified problems and proposed solutions (they just called it "fixing inefficiencies")
You've probably done BA work. You just didn't know it was BA work.
Your first job is to reframe your existing experience.
Step 1: Audit Your Current Work
Ask yourself these questions:
Have you ever:
Mapped out how a process works?
Identified a bottleneck or inefficiency?
Proposed a better way of doing something?
Gathered input from multiple people to make a decision?
Documented how a system or tool works?
Created a checklist, template, or framework?
Analysed data to inform a decision?
If you answered "yes" to any of these, you've done BA work.
You just need to document it properly.
Example: Sarah (Admin Assistant → Junior BA)
Sarah worked in admin for 3 years. She thought she had no BA experience.
But when we audited her work, we found:
She'd mapped the invoice approval process (15 steps, 4 stakeholders)
She'd identified a bottleneck (invoices waiting 2 weeks for Finance Director approval)
She'd proposed a solution (delegate approval for invoices under £500 to Finance Manager)
She'd presented a business case (save 40 hours/month of waiting time)
That's BA work.
We turned it into a portfolio piece:
Process map (As-Is → To-Be)
Stakeholder matrix
Business case (£X saved, Y hours saved)
Three weeks later, she had a £42k Junior BA offer.
Step 2: Create 3 Strong Portfolio Pieces
You don't need 20 projects. You need 3 strong ones.
Here's what hiring managers want to see:
Portfolio Piece #1: Process Map (As-Is → To-Be)
Shows you can understand a current process
Identify problems
Propose improvements
Portfolio Piece #2: Requirements Document
Shows you can gather requirements
Structure them logically
Write clearly
Portfolio Piece #3: Business Case
Shows you can quantify impact
Justify investment
Think commercially
Project Idea #1: Analyse Your Current Workplace
Pick one inefficient process at your current job.
Step 1: Map it out (As-Is)
What are the steps?
Who's involved?
Where are the bottlenecks?
Step 2: Identify the problem
What's inefficient?
What's the cost? (time, money, frustration)
Step 3: Propose improvements (To-Be)
What should change?
What's the impact? (hours saved, cost saved)
Step 4: Document it professionally
Process map (Visio, Lucidchart, or even PowerPoint)
Business case (1-2 pages)
Add it to your portfolio.
Example: The Invoice Approval Process
As-Is:
15 steps, 4 stakeholders, 2-week average approval time
Bottleneck: Finance Director has to approve everything (even £50 invoices)
To-Be:
Delegate approval for invoices under £500 to Finance Manager
Director only approves invoices over £500
Reduces approval time from 2 weeks to 2 days
Impact:
Saves 40 hours/month of waiting time
Improves supplier relationships (faster payment)
Frees up Director for strategic work
Portfolio piece:
1-page process map (before/after)
1-page business case
Project Idea #2: Volunteer for a Nonprofit
Nonprofits always need process improvements. And they're free to work with.
What to offer:
"I'll document your current processes"
"I'll identify inefficiencies and propose improvements"
"I'll create templates or frameworks you can use"
In exchange, you get:
Real-world BA experience
A reference/testimonial
A portfolio piece
Where to find nonprofits:
Local charities
Community groups
LinkedIn (search "nonprofit volunteer opportunities")
Example: Nonprofit Volunteer Management
I worked with a charity that managed 50+ volunteers using spreadsheets.
Problem: No one knew who was available, who had which skills, or who hadn't volunteered in 6 months.
Solution:
Mapped the current volunteer management process
Identified gaps (no skills database, no communication system)
Proposed improvements (simple CRM, monthly check-ins)
Portfolio piece:
Process map
Requirements document for the CRM
Implementation roadmap
Project Idea #3: Create a Hypothetical Case Study
If you don't have access to real projects, create a hypothetical one.
Pick a real business problem you've observed, then treat it like a BA project.
Example: "How could Uber improve driver retention?"
Step 1: Define the problem
Research: Why do Uber drivers leave? (search online, read forums, ask drivers)
Problem statement: "Uber loses 30% of drivers within 6 months due to low earnings and lack of support"
Step 2: Gather requirements
What would improve retention?
Interview drivers (or research driver feedback online)
Identify themes: better earnings, flexible hours, driver support
Step 3: Propose solutions
Feature 1: Driver earnings transparency (show expected earnings before accepting trips)
Feature 2: Driver support chatbot (24/7 help for common issues)
Feature 3: Driver rewards programme (bonuses for high ratings, long tenure)
Step 4: Build a business case
Current cost of driver churn: £X/driver to recruit and train
Projected improvement: Reduce churn by 10% = £Y saved annually
Portfolio piece:
Problem statement (1 page)
Requirements document (2-3 pages)
Business case (1 page)
How to Present Your Portfolio
Don't just attach Word docs to your CV.
Create a simple portfolio website or PDF that shows:
For each project:
Problem statement (1 paragraph)
"The invoice approval process took 2 weeks on average, causing supplier payment delays."
Your approach (1 paragraph)
"I mapped the As-Is process, identified the bottleneck (Finance Director approval), and proposed a To-Be process with delegated approval."
Deliverables (visuals)
Process map (As-Is → To-Be)
Business case
Requirements doc (if relevant)
Impact (metrics)
"Reduced approval time from 2 weeks to 2 days"
"Saved 40 hours/month"
Make it visual. Make it clear.
Common Mistakes to Avoid
Mistake #1: Waiting until you have "real" projects
You don't need a BA job to build a portfolio. Start with what you have access to now.
Mistake #2: Building a portfolio but not talking about it
Your portfolio is useless if you don't mention it in interviews.
Practice explaining each project:
"I mapped the invoice approval process at my previous company and identified a bottleneck that was costing 40 hours/month..."
Mistake #3: Making it too complicated
You don't need 20 projects. You need 3 strong ones.
Mistake #4: Not quantifying impact
"I improved the process" = weak
"I reduced approval time from 2 weeks to 2 days, saving 40 hours/month" = strong
The Timeline
Week 1-2: Audit your current work. Identify 3 potential portfolio pieces.
Week 3-4: Create Portfolio Piece #1 (Process Map)
Week 5-6: Create Portfolio Piece #2 (Requirements Doc or Business Case)
Week 7-8: Create Portfolio Piece #3
Week 9: Build simple portfolio site or PDF
Week 10: Start applying with portfolio
Total: 10 weeks from zero to portfolio-ready.
The Bottom Line
You don't need a BA job to build a BA portfolio.
You need:
To reframe the BA work you're already doing
To create 3 strong portfolio pieces (process map, requirements doc, business case)
To present it professionally
The catch-22 is a myth.
You can build a portfolio today. You just need to start.