Lead the work, not just the plan
You already get things delivered. What you are missing is the half of the job that decides what should be delivered at all: the business case, the benefits, the trade-offs and the judgement to run AI work where 'done' is a quality threshold rather than a checklist.
- → Project and programme managers
- → Delivery leads, scrum masters and PMOs
- → Consultants running client delivery
- + A business case and benefits model for a real initiative
- + An AI delivery playbook: risks, evaluation and governance
- + A portfolio piece that shows leadership, not just coordination
From outputs to outcomes: value, users and the problem behind the plan
Business cases, benefits, cost and risk in plain numbers
Running AI delivery: data, evaluation, governance and safety
Stakeholders, operating model and a delivered initiative you can show
One skill stack. Read it through your own job.
Twelve pillars, the same for everyone — because the product system is the same. What changes is what each pillar asks of you and what you produce.
See where delivery ends and product judgement begins in your organisation.
- Product Management
- Product vs Project vs Programme
- PM/PO responsibilities
- Product operating models
- Product lifecycle
An operating-model map of your own team
Use AI to map an operating model and spot where decisions actually get made.
Find the problem behind the plan before you commit a team to it.
- Voice of the customer
- Customer research
- Jobs to be Done
- Personas
- Journey mapping
- Problem discovery
- Problem validation
A problem statement your sponsor signs off on
Synthesise interview transcripts into themes and quote evidence in minutes.
Know the external pressure your programme is really responding to.
- Market research
- TAM/SAM/SOM
- PESTLE
- Porter's Five Forces
- Competitive strategy
- AI-powered research
A market and competitor brief for your initiative
Run market and competitor research in hours instead of weeks.
Trace every workstream back to a strategic choice, or cut it.
- Vision
- Mission
- Strategy
- Strategic choices
- Positioning
- OKRs
- Strategic alignment
A strategy-to-delivery alignment map
Pressure-test strategic choices against competitor moves and scenarios.
Cut scope on evidence instead of on the loudest voice.
- Opportunity discovery
- Prioritisation
- MVP
- Hypotheses
- PRDs
- User stories
- Acceptance criteria
A prioritised delivery scope with a written rationale
Draft PRDs, acceptance criteria and edge cases from a problem statement.
Build design and testing into a plan instead of bolting it on.
- Design thinking
- UX
- User journeys
- Information architecture
- Prototyping
- Usability testing
A journey map with delivery risks marked
Generate and iterate on prototypes fast enough to test the same week.
Run AI work where 'done' is a quality threshold, not a checklist.
- AI/ML fundamentals
- LLMs
- RAG
- Agents
- Prompt engineering
- AI UX
- Evaluation
- Guardrails
- Responsible AI
An evaluation, guardrail and governance plan
This pillar is the AI accelerator — how AI products are specified and judged.
Read the architecture well enough to see where the risk sits.
- APIs
- Data
- Cloud concepts
- AI architecture
- Integrations
- Security
- Privacy
- Scalability
A technical risk and dependency map
Use AI to explain, diagram and interrogate an architecture you didn't write.
Turn a plan into cost, benefit and ROI a sponsor will sign.
- Business models
- SaaS
- Platform models
- Pricing
- Unit economics
- Business cases
- ROI
- Financial modelling
A business case and benefits model
Go from assumptions to financial projections without building a spreadsheet first.
Prove benefits landed after go-live, not just that you delivered.
- Product analytics
- North Star metrics
- Funnels
- Retention
- Experiments
- A/B testing
- Growth loops
- Network effects
A benefits realisation and tracking plan
Interrogate product data in plain language and surface what moved.
Plan rollout and adoption as part of delivery, not after it.
- Positioning
- Messaging
- Go-to-market
- Launch strategy
- Beta
- Rollout
- Adoption
A rollout, comms and adoption plan
Draft, test and sharpen positioning and messaging against real objections.
Say no to a sponsor and keep the relationship.
- Stakeholder management
- Negotiation
- Executive communication
- Decision-making
- Influence
- Product leadership
An escalation and governance approach
Rehearse the hard conversation and stress-test your argument before the room.
Shown through the Project & Delivery track. The pillars are the same on every track — the work you produce is not.
18 modules. One complete
product, built to launch.
Same eighteen modules for everyone. What changes is how deep each one runs for you and why it matters to the job you are doing.
See exactly where your remit stops being a plan and starts being a bet.
Find the problem behind the plan before a team is committed to it.
Understand the external pressure your programme is answering.
Trace every workstream to a strategic choice, or cut it.
Rank scope on value rather than on who asked loudest.
Turn a delivery plan into cost, benefit and ROI a sponsor signs.
Cut scope on evidence and keep the sponsor with you.
Plan design and testing in, instead of bolting them on.
Run work where done is a quality threshold, not a checklist.
Read the architecture well enough to see where the risk sits.
Understand what a build week really costs and contains.
Prove benefits landed after go-live, not just that you delivered.
Put credible cost and benefit numbers in the business case.
Plan adoption as part of delivery rather than after it.
Run cutover, comms and adoption as one plan.
Say no to a sponsor and keep the relationship.
Design the governance that keeps decisions moving.
Show leadership and judgement, not just coordination.
The same situation. A different call, depending on your job.
Short decision exercises used through the curriculum. Read one and you can feel where the tracks separate.
A clinical documentation tool has strong sign-ups and almost no second week. Clinicians say they like it.
Do you improve what exists, or accept the tool solves the wrong moment in the day?
You pause the next release and take the evidence to the sponsor with two options.
Every order loses eighty pence. Growth is up thirty percent and the board is delighted.
Do you keep growing, raise prices, or cut the segment that loses the most?
You rebuild the business case with real margin data and reset the plan.
An internal AI assistant answers confidently and is wrong roughly one time in eight.
Do you ship with a confidence warning, restrict scope, or hold until accuracy improves?
You put a human-in-the-loop control and an escalation path into the rollout plan.
A new onboarding flow lifts completion by twelve percent and drops ninety-day retention.
Do you keep the flow, roll it back, or split the difference?
You show the sponsor that the delivered benefit did not land, and why.
A sponsor demands a fixed date for an AI feature whose accuracy is still unproven.
Do you commit, refuse, or offer something else?
You reframe the commitment around a quality gate rather than a calendar date.
A well-built product launches to silence. The team blames marketing; marketing blames positioning.
Do you relaunch, reposition, or change who you sell to?
You plan adoption into the next release rather than treating it as a comms task.
Illustrative teaching examples built from the capstone worlds, not accounts of named clients.
Learn through real product challenges.
Build an AI product for clinicians and patients.
Turn behaviour into measurable outcomes.
Search, RAG and enterprise workflow.
A full zero-to-one product journey.
Build an AI-native career platform.
Improve financial health and retention.
Build a collaboration and productivity product.
Personalised learning with an AI tutor.
Retention, unit economics and growth.
Design a safe, engaging consumer product.
Or bring your own problem — most people do, and the programme is built for it.