Careers › Product & Program Management › Business Analyst
For students and early-career professionals
Maps processes and requirements to help teams improve systems and decisions.
11 chapters · About 4–5 months · 15–30 min a day
Start this plan free → Chapter 1 is free.
What's in the plan
Practice 9 practice tasks Tasks from the real work of the job, 10 to 30 minutes each
Projects 2 projects you keep Funnel analysis of a public dataset with three product recommendations User research to clickable prototype with five usability tests
Interview 19 interview questions Practise your answers, with feedback
People 3 people to reach Who they are, with 4 messages ready to send
Also: choose your route in (3 credentials compared, none required) and 3 life skills courses.
Skills
8 skills, and what you'll learn in each
Each skill is a few short lessons, then practice. You rate yourself at the start and again at the end.
Core to the job
Chapter 2
Communication Rewrite an update for two different readers, cutting extra lines
What you'll learn
Lead with the point Match detail to the reader Said versus heard Specific feedback Chapter 2
Stakeholder alignment Map key people's goals and hear their concerns before decisions
What you'll learn
Stakeholder map Decision roles Pre-meeting alignment Hidden disagreement Chapter 6
Process mapping Map a real process, then check it with the team
What you'll learn
Steps, decisions, owners Real process path Process bottleneck Practice
Document a workflow with swim lanes30 min Map a Familiar Process and Find the Bottleneck15 min Chapter 6
Writing specs Write a one-page spec with problem, user and success measure
What you'll learn
Problem statement User story Acceptance criteria Open question Practice
Turn a vague request into a real spec15 min Write a 1-page PRD for a small feature30 min Slice a feature into 5 user stories20 min Chapter 7
Metrics and measurement Pick a success measure and define exactly how it's calculated
What you'll learn
Success metric Guardrail metric Vanity metric Practice
Read a product chart and ask 3 sharp questions20 min Read a Product Dashboard and Write a Memo15 min
3 more in the plan
Working with others Contribute to group work, ask for help and credit teammates Ch 2 What you'll learn
Early team friction Clear ownership Challenge ideas, not people Lead or follow Problem solving Test each possible cause of a problem instead of guessing Ch 4 What you'll learn
Problem vs symptom Clean problem splits Root cause Deciding under uncertainty Practice
Separate the Problem from the Symptom10 min Critical thinking Spot a weak assumption and ask where numbers come from Ch 4 What you'll learn
The hidden assumption Argue the other side The base rate Fact vs inference Wanting it to be true Practice
Spot the Weak Link in an Argument10 min
Your plan
Chapter by chapter. 11 chapters, in this order. Chapter 1 is free.
1 ~2 wks See the work of a Business Analyst Start Free
2 ~2 wks Get stakeholders to agree on one plan Skills
3 ~2 wks Build a funnel analysis with three recommendations Project
4 ~2 wks Find the cause before you fix it Skills
5 1–2 wks Talk to two working business analysts People
6 ~2 wks Map the work and write buildable specs Skills
7 ~2 wks Measure what users actually do Skills
8 ~2 wks Take user research to a tested prototype Project
9 1–2 wks Answer the questions interviewers ask Interview
10 1–2 wks Decide how you will get in Decide
11 on your timeline Send your first applications Apply
The job
What a Business Analyst does Analyzes business needs and processes, turns them into clear requirements, and helps teams deliver better systems and decisions.
The work Analyze current processes to find gaps, risks, and improvement opportunities Gather requirements from stakeholders and turn them into clear user needs Document workflows, rules, and data definitions in simple, shared formats Coordinate with product, design, and engineering to clarify scope and tradeoffs Validate solutions with users through demos, testing, and feedback sessions Track issues and changes, and keep requirements aligned as priorities shift Measure outcomes using basic metrics to confirm the change worked as intended A typical day Join a standup, then follow up with stakeholders on open questions Run a requirements workshop and capture decisions and action items Write user stories and acceptance criteria, then review them with the team Check test results, log gaps, and confirm fixes meet the agreed needs Tools Spreadsheets: Excel, Google Sheets Documentation: Confluence, Google Docs Diagrams: Lucidchart, Microsoft Visio Backlog tools: Jira, Azure DevOps Databases: SQL Prototyping: Figma
Ways in
There is more than one route. Ways to study Bachelors degree in business, information systems, economics, or a related field Diploma or certificate in business analysis, project management, or IT Bootcamp or short course in analytics, SQL, and requirements writing How people get their first job Apply for business analyst internships or product operations internships Start in support, operations, or QA and move into requirements and process work Build a small portfolio with process maps, user stories, and a simple dashboard Earn an entry certificate in business analysis or agile fundamentals Volunteer to document and improve a process for a club or local nonprofit Life skills in this plan: Networking · Job interviews · Job search
How the work is changing
What AI is doing to this role How AI is changing this role · one of 6 tasks we track
Create specs and low-fidelity wireframes Sped up a lot
What AI does Miro AI and Figma AI generate wireframe drafts from a description.
Still yours You decide what level of detail the team actually needs.
Reviewed September 2026
In the app · Premium
The rest is in the app
How AI affects the other 5 tasks Whether this job is growing or shrinking How hard the first job is to get Similar roles that are easier to get into Updated every month, with sources
See it in the app →
How we rate a job →
Already working
Already a Business Analyst? Plan your move to Senior Business Analyst: 10 chapters that end with a strong case for your next review.
Grow in the role →
Other roles in Product & Program Management
Questions
Questions about this plan How long does it take to become a business analyst with Welica? The plan is 11 chapters, 4–5 months at 15 to 30 minutes a day. You can go faster or slower; the plan moves with you.
Do I need a degree? Not always. Common routes are bachelors degree in business, information systems, economics, or a related field, diploma or certificate in business analysis, project management, or IT, or bootcamp or short course in analytics, SQL, and requirements writing.
What is free? Chapter 1, See the work of a Business Analyst, is free for good. Premium unlocks the rest of the plan.
Start the Business Analyst plan. Chapter 1 free. About 15 to 30 minutes a day.
Already have an account? Sign in