Skip to main content

Learning path

Become a product designer

Learn to research what people need, design screens in Figma, prototype them and test them with users, the way product and UI/UX designers work.

You will be able toYou'll finish able to take a product idea from research to a tested, high-fidelity prototype and hand it to developers.

Stage 01

Foundations

Assumes: Nothing. A computer with a web browser and a free Figma account is enough.

Frame a design problem before drawing anything, and learn your way around Figma.

  1. 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

  2. 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

  3. 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

  4. 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

  5. Add accessibility requirements to a design brief

    You will add an accessibility section to a design brief that names who could be shut out, sets a WCAG 2.2 target and lists testable requirements with how and when each one is checked.

    Beginner · 14 min

  6. Choose between Figma, Sketch, Adobe XD, Penpot, Framer and Canva

    You will have a one-page decision sheet that picks a design tool for three real jobs, with the reasons written down so you can defend each choice to a client or a team.

    Beginner · 15 min

  7. Build your first screen in Penpot

    You will have a finished Pick a time screen for the Larkfield Clinic booking app in Penpot, built from a board, a flex layout and a reusable time slot component, and you will have read its CSS in the Inspect tab.

    Beginner · 14 min

  8. 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

  9. Organise a Figma file with pages, frames and layers

    You will have a Figma file for the Larkfield Clinic booking app with a cover, a page for each stage of work, named mobile and desktop frames for all six screens, and sections that group them.

    Beginner · 12 min

  10. Name and group layers so others can work in your file

    You will turn a messy Figma screen into one whose Layers panel another designer or developer can read at a glance, with clear names, frames where they belong and no hidden leftovers.

    Beginner · 13 min

  11. Draw icons with vectors and boolean operations in Figma

    You will have drawn a calendar icon and a clinic icon on a 24 px grid in Figma with the pen tool, shape tools and boolean operations, and turned them into flattened, outlined SVGs ready for a developer.

    Beginner · 16 min

  12. Place, crop and mask images in Figma

    You will have a doctor's profile card in Figma with a cover photo, a circular portrait, a tiled pattern strip and a masked status band, and you will know when to use an image fill and when to use a mask.

    Beginner · 13 min

  13. Keep layers in place with constraints when a frame resizes

    You will have a phone screen in Figma whose header and bottom bar hold together when you resize it from 320 pixels wide to tablet width, and you will know when constraints apply and when auto layout takes over.

    Beginner · 13 min

  14. 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 frame a problem and find your way around a Figma file.

Run the research methods designers use most, make sense of what you find, and build screens from auto layout, components and variables.

  1. 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

  2. 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

  3. 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

  4. Recruit participants for user research

    You will have a one-page recruitment plan, a private scheduling sheet and a first round of research sessions booked with the right people, including a spare for the person who does not turn up.

    Beginner · 15 min

  5. Write a screener survey to find the right participants

    You will have a screener of eight questions that finds people who booked a clinic visit in the last six months without hinting at the answer you want, plus written rules for who qualifies, who is turned away and who fills a quota.

    Beginner · 13 min

  6. Get informed consent and store research data safely

    You will have a plain-language consent form for one study and a data-handling checklist that says what you record, where it lives, who can see it and when it is deleted.

    Beginner · 14 min

  7. Write an interview guide without leading questions

    You will have a 45-minute interview guide built from your research questions, with a warm-up, story-based questions, follow-up prompts and a close, plus a list of leading questions you caught and rewrote.

    Beginner · 14 min

  8. 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

  9. Design a short survey people will finish

    You will have a survey that takes under five minutes, built from a short list of questions that each feed a decision, piloted with three people, sent, and reported with an honest completion rate.

    Beginner · 13 min

  10. Write unbiased survey questions and answer scales

    You will have a corrected set of survey questions, each with an answer scale that fits what it measures and a one-line reason for every change you made.

    Beginner · 14 min

  11. Build an affinity map from interview notes

    You will turn the notes from five or six interviews into an affinity map of five to eight groups, each named as a finding and backed by notes from more than one participant.

    Beginner · 14 min

  12. Turn research themes into insight statements

    You will have five insight statements, each saying what people do, why they do it and what it means for the design, with quotes from several participants and a confidence level beside it.

    Intermediate · 14 min

  13. Build a persona from research data

    You will have two personas for Larkfield Clinic patients, each built from a group of interview participants who behave alike, with a source note against every line and no invented detail.

    Beginner · 14 min

  14. 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

  15. 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

  16. 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

  17. 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

  18. Run an open card sort

    You will have a deck of 30 to 40 neutral content cards, sorts from around 15 participants, and every group and group name they made recorded in one sheet, ready to analyse.

    Beginner · 16 min

  19. Analyse card sort results with a similarity matrix

    You will turn raw open card sort data into a similarity matrix in a plain spreadsheet, read which cards belong together, and finish with a draft site map that has the evidence for every section written beside it.

    Intermediate · 18 min

  20. Run a tree test on your navigation

    You will have a proposed navigation tested with real people as a text-only tree, scored for success, directness and first click on every task, and a list of the labels to change before anyone designs a screen.

    Intermediate · 17 min

  21. Run a heuristic evaluation of an existing app

    You will have one merged list of usability problems in an existing booking flow, found by two evaluators working apart, with each problem tied to a heuristic, a screen and a severity rating.

    Intermediate · 16 min

  22. Review a booking flow for cognitive load

    You will have an annotated booking flow that marks every point where someone has to remember, calculate, decide under time pressure or decode jargon, and a ranked list of fixes for each one.

    Intermediate · 15 min

  23. Include disabled people in your user research

    You will have a research plan and a per-participant session setup that let disabled people take part on their own terms, from recruitment and consent to session length, assistive technology and payment.

    Intermediate · 16 min

  24. Plan a usability test with tasks and success criteria

    You will have a written usability test plan for a booking flow, with scenario tasks that do not give away the answer, a success rule for each task and a session script another person could run without you.

    Beginner · 14 min

  25. Run a five-person usability test

    You will run five in-person think-aloud sessions on a live product in one day, hold back from helping when people struggle, and finish with a list of observed problems showing how many of the five hit each one.

    Beginner · 15 min

  26. Rate and prioritise usability problems by severity

    You will have a severity table for the problems from a usability test, rated on a three-factor scale that two people apply the same way, and a ranked fix list the team can plan a release from.

    Beginner · 13 min

  27. Build a button with auto layout

    You will have a Figma button whose padding, gap and alignment come from auto layout, so it resizes by itself for "Book" and "Book an appointment" and can show an icon on either side.

    Beginner · 12 min

  28. Build a responsive card with auto layout

    You will have an appointment card in Figma, with a photo, a stack of text and a button, that keeps its layout at any width from 280 to 600 pixels because every layer has the right hug, fill or fixed setting.

    Beginner · 14 min

  29. Build a list screen with nested auto layout

    You will have a full Upcoming appointments phone screen built from nested auto layout frames, where duplicating a card moves everything below it and a floating button stays pinned to the corner.

    Intermediate · 16 min

  30. Make layouts wrap and stretch with auto layout min and max sizes

    You will have one Figma frame for a time-slot picker that reflows from a 360 wide phone layout to a desktop layout by itself, using wrap, minimum and maximum widths and the grid flow, with no separate frame for each size.

    Intermediate · 14 min

  31. Make your first component and use its instances

    You will have one appointment card component in the Larkfield Clinic file, with instances on three screens that all change when you edit the main component.

    Beginner · 12 min

  32. Turn a button into a component with variants

    You will have a Figma button component set with Type, Size and State properties, so a teammate can place one button and switch it between primary, secondary, large, small and disabled from the right sidebar.

    Beginner · 14 min

  33. Add text, boolean and instance-swap properties to a component

    You will have a button component set whose label, icon visibility and icon choice are component properties rather than variants, so the eight variants from the previous tutorial cover what would otherwise take thirty-two.

    Intermediate · 14 min

  34. Override instances without breaking the main component

    You will have Larkfield Clinic screens whose appointment cards carry their own text, colour and nested-instance overrides yet still pick up every other change from the main component, and you will know when to reset and why not to detach.

    Beginner · 13 min

  35. Create colour variables with light and dark modes

    You will have a Figma screen whose every colour comes from variables, so switching one setting on the frame turns it from light to dark and back.

    Intermediate · 16 min

  36. Use number variables for spacing and corner radius

    You will have a card and a list screen in Figma whose gaps, padding and corner radius all come from number variables, so changing one value in the variables table restyles every card at once.

    Intermediate · 15 min

Stage 03

Build projects

Assumes: You can run an interview or usability test and build screens with auto layout and components.

Take one product, a booking app for a fictional clinic, from paper sketches to a tested prototype, then stretch into harder research and prototyping.

  1. Pick the right fidelity for what you need to learn

    You will have a one-page fidelity plan for one of your projects that pairs each open design question with the cheapest artefact that can answer it and says when to move up.

    Beginner · 13 min

  2. Build a small wireframe kit you can reuse

    You will have a Wireframe kit page in Figma with thirteen plain greyscale components built on auto layout, and a test screen that proves you can assemble a new wireframe from them in minutes.

    Beginner · 18 min

  3. Wireframe with real content instead of placeholder text

    You will have Larkfield Clinic booking wireframes filled with real names, service descriptions, error messages and translated labels, with every layout that broke under that content fixed and a short list of content rules for developers.

    Beginner · 14 min

  4. Series: Design a product end to end

    1. Sketch wireframes on paper before opening Figma

      You will have a photographed set of paper sketches for every screen and state in the Larkfield Clinic booking flow, each one chosen from several rough layouts drawn against the clock.

      Beginner · 14 min

    2. Build a low-fidelity wireframe in Figma

      You will have five grey-box wireframes in Figma for the Larkfield Clinic booking flow, drawn from your paper sketches with rectangles, lines and plain text only, and a written list of what you chose to leave out.

      Beginner · 16 min

    3. Take a wireframe from low to mid fidelity

      You will have the six Larkfield Clinic booking screens and four state frames at mid fidelity in Figma, still greyscale but with real copy, four text styles, one spacing scale and a small kit of reusable wireframe components, ready to test for content and flow.

      Beginner · 19 min

    4. Turn a mid-fidelity layout into a high-fidelity design

      You will have high-fidelity Larkfield Clinic booking screens in Figma, coloured, typeset, with icons and one photo, every text and colour pair checked for contrast and ready to wire into a prototype.

      Intermediate · 20 min

    5. Build a click-through prototype in Figma

      You will have the six high-fidelity Larkfield Clinic screens linked into a named Figma flow that plays from Home to Booked on a phone-sized device, with a link you can send to a colleague.

      Beginner · 12 min

    6. Add overlays, transitions and scroll behaviour to a prototype

      You will have a Larkfield Clinic booking prototype that moves like a phone app, with push transitions forward, working back controls, a date picker that slides up as an overlay and a header that stays put while the time slots scroll.

      Beginner · 14 min

    7. Animate between screens with Smart animate

      You will have the Larkfield Clinic appointment card growing smoothly into a details view and shrinking back again, driven by matched layer names and an easing and duration you chose by comparing them.

      Intermediate · 15 min

    8. Get a prototype ready for a usability test

      You will have a Larkfield Clinic prototype that a participant can open from one link, finish every test task in, and never get stuck in, with a saved version to fall back on.

      Beginner · 16 min

    9. Test a Figma prototype with users and log what breaks

      You will run short test sessions with the Larkfield Clinic prototype on a phone and a laptop, sort every problem into a prototype glitch or a real design problem, and end with an issue log where each row links to the frame it happened on.

      Beginner · 17 min

    10. Revise the design after a prototype test

      You will have a revised Larkfield Clinic prototype that fixes the worst problems from the first test, a page that shows each change before and after beside its evidence, and a change log that tells the second round of testing what to watch.

      Intermediate · 16 min

  5. Make components respond to hover and tap with interactive components

    You will have a time-slot chip that toggles when tapped and a button that shows hover and pressed states, wired once inside their component sets so every instance in every prototype behaves the same way.

    Intermediate · 13 min

  6. Prototype a booking form with variables and conditional logic

    You will have a one-frame Figma prototype of a booking form that remembers the chosen time, refuses to book until every field is filled, and shows a confirmation summary built from what the tester picked.

    Advanced · 18 min

  7. Observe people at work with a contextual inquiry

    You will have timestamped field notes from watching someone do their real work, and a numbered sequence of the work steps that marks every workaround and breakdown you saw.

    Intermediate · 15 min

  8. 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

  9. Run a two-week diary study

    You will have run a two-week diary study on how people try to see a doctor, with a tested entry form, a reminder schedule, a mid-study check-in and a tidy sheet of entries ready to analyse.

    Intermediate · 17 min

  10. 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

  11. Moderate a remote usability test

    You will run a usability session over a video call, with the participant sharing their screen, observers in a separate chat channel and a consented recording, and finish with that recording and a page of time-stamped notes.

    Intermediate · 16 min

  12. Run an unmoderated usability test

    You will have results from at least ten unmoderated sessions on one prototype, cleaned of low-quality sessions, with a short write-up that says what the data shows and what it cannot.

    Intermediate · 15 min

  13. Score a design with the System Usability Scale

    You will have SUS scores for two versions of a design, worked out by hand and in a spreadsheet, with confidence intervals and a written statement of what the numbers do and do not show.

    Intermediate · 16 min

  14. Code open-ended survey answers into themes

    You will have around 200 free-text survey answers coded against a written codebook that you and a colleague tested for agreement, and a theme table with counts and example quotes.

    Intermediate · 16 min

  15. Read survey results without fooling yourself

    You will check who answered your survey, put a margin of error on each headline number, decide which group differences are too small to report, and write a results summary that states its own limits.

    Intermediate · 15 min

Stage 04

Job-ready

Assumes: You have taken at least one product from research to a tested prototype.

Work the way design teams do: hand off cleanly, share and maintain components, report research so it gets used, and measure what you ship.

  1. Hand off a design with Figma Dev Mode

    You will have the Larkfield Clinic booking screens cleaned up, grouped in one section, checked from the developer's side in Dev Mode, marked ready for dev and sent with a short note that lets a developer build without a handoff meeting.

    Intermediate · 14 min

  2. Annotate a design for developers

    You will have one Figma screen with its error, empty and loading states beside it and notes on validation, truncation, focus order and responsive behaviour, so a developer can build it without asking you what happens when things go wrong.

    Intermediate · 14 min

  3. Export assets from Figma for web and mobile

    You will have a folder of icons and images exported from Figma in the right format and pixel size for a website, an iOS app and an Android app, with names a developer can drop straight into a project.

    Beginner · 14 min

  4. Publish a team library and push updates to other files

    You will have the Larkfield Clinic components in their own library file, used by the booking app file, with one published change reviewed and accepted on the other side.

    Intermediate · 15 min

  5. 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

  6. 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

  7. Keep research findings in a searchable repository

    You will have a small spreadsheet repository holding every finding from one study, each row tagged by topic, study and date and linked to its evidence, plus a tag list and house rules a colleague can follow without asking you.

    Intermediate · 15 min

  8. 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

  9. Combine interview and analytics findings into one story

    You will have one finding that rests on both interviews and product data, with a confidence level, the reason for any disagreement between the two, and a note on what evidence would change it.

    Advanced · 17 min

  10. 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