Learning path
Become a technical product or project manager
Learn to frame problems, understand users and work with designers and engineers to deliver the right thing.
You will be able toYou'll finish able to turn a vague request into a researched, prioritised plan a team can deliver.
Stage 01
Foundations
Assumes: Nothing. A computer with a web browser.
Frame problems clearly and learn to read and comment on design files.
Turn a feature request into a user-centred design brief
You will turn a one-line request into a one-page brief that names the people affected, what they are trying to get done, what is known and what is guessed, ready to hand to a team.
Beginner · 12 min
Plan a project with the double diamond
You will have a two-week project plan drawn as a double diamond, with dated phases, the activities and outputs for each, two decision gates and a note of what each shortcut would cost.
Beginner · 14 min
Write a problem statement before you design
You will have one problem statement your team agrees on, naming a person, a situation and a consequence, plus a log of rejected drafts with the reason each one failed.
Beginner · 11 min
Turn a problem statement into how-might-we questions
You will have a sorted set of how-might-we questions drawn from one problem statement, with three workable questions chosen to explore and a note on why the rest were set aside.
Beginner · 12 min
Find your way around the Figma canvas
You will have a Figma file with one phone-sized frame holding a heading, a card and an avatar, and you will know which part of the screen controls each of them.
Beginner · 14 min
Share a Figma file and collect comments
You will run one complete feedback round on a single Figma screen, from writing the question you need answered to sharing a link to that frame, sorting the comments and resolving every one.
Beginner · 11 min
Stage 02
Core skills
Assumes: You can write a problem statement and a brief.
Understand users and stakeholders, and map how a service works today.
Map your assumptions and choose which to test first
You will turn your team's guesses about a product into a ranked map and leave with the two or three riskiest assumptions, each written up as a test you can run.
Intermediate · 12 min
Interview stakeholders at the start of a project
You will have run short interviews with the people who own, fund and operate a product, and written a one-page summary of where they agree, where they conflict and what success means to each.
Beginner · 14 min
Write a one-page research plan
You will have a research plan that fits on one page, with every question tied to a decision, and a stakeholder sign-off you got in a five-minute read.
Beginner · 12 min
Run your first user interview
You will run a 45-minute one-to-one interview with a note-taker beside you and finish with a recording, a page of structured notes and a five-line debrief written within the hour.
Beginner · 16 min
Write job stories with jobs to be done
You will have a checked set of job stories for booking a clinic appointment, written from interview notes, set side by side with the user stories they replace, and a note on where they agree and clash with your personas.
Beginner · 14 min
Map a current-state customer journey
You will have a journey map of how patients book, attend and follow up on a clinic appointment today, with every pain point tied to the research that shows it and every guess marked as a guess.
Beginner · 14 min
Prioritise opportunities from a journey map
You will turn the pain points on a journey map into opportunity statements, score each one for frequency, severity and effort, and end with a ranked list of three opportunities to design for and a written reason for each.
Intermediate · 14 min
Draw a user flow for one task
You will have a user flow for booking a first appointment that shows every screen, decision and error path, and a screen list taken from it that tells you exactly what to wireframe.
Beginner · 13 min
Draw a service blueprint for an appointment service
You will have a service blueprint of one appointment booking that lines up what patients do with what staff and systems do behind them, with each behind-the-scenes failure marked and backed by evidence.
Intermediate · 16 min
Stage 03
Build projects
Assumes: You have run interviews and mapped a journey.
Decide what to build and how to measure it.
Run a jobs-to-be-done switch interview
You will have a dated timeline of one person's switch to a new way of booking appointments, from first thought to first use, and a forces diagram that sets out the pushes, pulls, anxieties and habits behind it.
Advanced · 17 min
Use analytics to decide what to research next
You will turn a booking flow's funnel and event data into two or three research questions, each tied to a specific number, a specific group of people and a method that can answer it.
Intermediate · 14 min
Choose UX metrics for a feature with the HEART framework
You will have a short metrics table for one feature, with a goal, signal, metric, baseline and owner for each HEART category you kept, and a written reason for each one you dropped.
Advanced · 17 min
Stage 04
Job-ready
Assumes: You have taken a feature from problem to plan.
Run the reviews and reports that keep a team aligned.
Report research findings so the team acts on them
You will have a short findings report that opens with the decisions it supports and backs each finding with evidence, plus a 15-minute playback plan that ends with a named owner for each recommendation.
Beginner · 13 min
Run a design critique in FigJam
You will set up a FigJam board for one critique, run it in 30 minutes with a silent review before any discussion, and leave with a sorted list of agreed changes, each tied to the goal it serves.
Beginner · 12 min