Real BA work, inside simulated organisations running real programmes. You produce actual outputs, receive feedback built on practitioner rubrics, and build the kind of judgement that only comes from doing the work.
Each world is a fully realised fictional organisation running a technology-driven transformation programme. You join mid-programme as the BA. The work is already underway, and the stakeholders already have opinions. Your job is to make sense of it — and do something useful with what you find.
A private health network navigating the complex terrain of patient data interoperability across multiple clinical systems and care sites.
Connected Care — cross-site patient record access
A cross-government regulatory body working to modernise how agencies share information and verify identity across public services.
Identity Connect — unified digital verification
A regional energy network with a growing retail arm, implementing smart infrastructure to improve visibility and responsiveness across its customer base.
GridSmart — real-time network intelligence
You complete all eight modules within one world to earn your credential. Additional worlds give you the chance to apply the same skills in a different sector, with a different cast of stakeholders.
The modules follow the arc of a real BA engagement — from framing the problem through to embedding the change. Each one requires you to produce an actual BA output, assessed against a practitioner-built rubric.
Diagnose what's actually going on, separating symptoms from causes. Produce a structured problem statement your stakeholders will recognise as an accurate picture of the situation.
Output: Problem statementIdentify who matters, understand what they need, and build the relationships that make BA work possible. You'll have real conversations with the people inside your world — and not all of them will make it easy.
Output: Stakeholder mapPlan and run the activities that surface what you actually need to know — workshops, interviews, document analysis, observation. Then make sense of what you find and know what to do with it.
Output: Elicitation findingsFinalise your requirements so they are ready for development — well-structured, prioritised, and robust enough to hold up when the project gets complicated.
Output: Requirements registerEngage with solution design without overstepping your role. Review the outputs of technical specialists, ask the right questions, and contribute to how options are assessed and communicated to decision-makers.
Output: Solution options analysisWork alongside the delivery team to keep the backlog honest, the scope clear, and the team focused on what was actually asked for — not just what's easiest to build.
Output: Prioritised backlogSupport business users through user acceptance testing — helping them articulate what's working and what isn't, and whether the solution is what they asked for.
Output: UAT summary & sign-offDelivering a technical solution is not the same as delivering change. Plan for the human side of delivery, support the people most affected, and set the programme up for further improvement after go-live.
Output: Change & adoption planThe Apprentice BA credential is awarded on completion of all eight modules within a single simulation world. It's verifiable, shareable, and backed by a practitioner-built rubric.
It isn't a certificate of attendance, a review of literature, or a two-dimensional case study. It's evidence of work produced, feedback received, and self-reflection that is the beginning of your own practice.
Join the waitlist for early access and founding member pricing. We'll be in touch before anyone else.
Join the waitlistNo spam. Unsubscribe any time.