1 · Learn
Concept cards
Each idea is explained as What it is, Why it matters and an Example, in plain English.
THE BA LAB
Join a fictional company, take briefs from your manager and do the work stage by stage: business case, requirements, SQL, APIs, tickets, documentation and dashboards. Each task gets checks that explain what to fix.
7-day free trial, Google sign-in, no card. Opening the Lab asks you to sign in.
1 · Learn
Each idea is explained as What it is, Why it matters and an Example, in plain English.
2 · Brief
“Ana from Ops needs…” Simple words, a realistic problem and the data to solve it.
3 · Do
Write the requirement, run the query, send the API call or file the ticket.
4 · Check
Good, warning or problem, with why it matters and how to fix it.
What a BA does in a company, your team, your first week
Problem statement, objectives, scope, success measures
Stakeholder map, power/interest, RACI, communication plan
Interviews, workshops, good questions, meeting notes
BRD, functional/non-functional, user stories, acceptance criteria
AS-IS / TO-BE flows, BPMN basics, pain points
Tables, joins, aggregates, data validation with SQL
REST, endpoints, JSON, status codes, API requirements
Epics, stories, bugs, backlog, sprint planning
Requirement pages, meeting notes, decision log
KPIs, data model, measures, visuals, storytelling
Test cases, RTM, defect triage, sign-off
Release readiness, change management, benefits, portfolio
STAGE 4 · REQUIREMENTS
A requirement about how well the system works, such as speed, security or availability, rather than what it does.
Vague quality words cannot be tested, so the team disagrees about whether the work is finished.
“Search results appear within 2 seconds for 95% of requests.”
A sample written for this page. Browse the glossary.
Checks are deterministic: the same draft gets the same answer. Each one says why it matters and how to fix it.
Why it matters: testers cannot pass or fail “fast”, so the team argues about it after launch.
How to fix: replace the vague word with a number, a condition and a percentage.
Why it matters: a developer cannot fix what they cannot see happen.
How to fix: add the steps, the expected result and the actual result.
Why it matters: callers cannot tell success from failure by the status code alone.
How to fix: use 201 for a created record and a 4xx code with a clear error message when the request is invalid.
Why it matters: two people will calculate it two different ways.
How to fix: state the numerator, denominator, time period and data source.
Why it matters: a query can run without error and still answer the wrong question.
Next step: write one sentence on what the number means for the business.
Illustrative examples. Optional AI review is only available when the owner enables it, and is not required for the checks above.
Query the fictional company’s tables and compare your result with what the business asked.
Send GET and POST requests to a simulated service, read status codes and write the API requirement.
Create epics, stories and bugs, set priority and plan a sprint. A simulation, not Jira.
Draft requirement pages, meeting notes and decision logs from templates. A simulation, not Confluence.
Define KPIs, pick measures and visuals and explain them. Power BI concepts in the browser: a concept simulation, not Microsoft Power BI.
Trace each requirement to a test case and decide what is ready for sign-off.
The free trial includes one domain of your choice. Starter and Experience include one. Core includes four and Advanced includes all seven. Compare packages from $19.
It is simulated, self-guided practice. It does not grant a certification, guarantee a job or replace working with real stakeholders. Practice work is learner-authored and unverified. Jira-style and Confluence-style tools are simulations, and browser dashboards are a concept simulation rather than Microsoft Power BI.
Join the project, write a business case, map stakeholders and run your first interview.