Skip to content
10 Modules · Problem to design defence

The complete UX process,
module by module.

Ten modules, each mirroring real work done inside product teams. AI runs through the workflow rather than sitting in a module at the end, and the whole thing finishes with you defending what you built. Click any module to see what is inside.

Curriculum overview.

M1

Product Thinking in the AI Era

What UX actually is Symptom vs problem The complete UX workflow AI: prompt a complete screen in seconds, then identify every decision it quietly made for you without any evidence behind it.
M2

User Research

Running user interviews Personas and user models Journey mapping AI: cluster hours of interview notes into themes in minutes, then check each theme against what the participant actually said rather than what it inferred.
M3

Information Architecture

Content organisation Navigation design Card sorting and validation AI: generate three competing structures for the same product, then let a card sort decide between them instead of picking the tidiest one.
M4

Wireframing & Prototyping

Low and mid-fidelity wireframes Interactive prototypes Visual hierarchy and layout AI: produce five layout directions from one brief, then write down why you killed four of them.
M5

Usability Testing

Writing a test plan Running test sessions Iterating from evidence AI: draft your test script and summarise the sessions, then prove each finding by pointing at what someone did, not at what the summary claims.
M6

Interaction Design

User flows States, errors and edge cases Feedback systems AI: brief it to attack your flow for dead ends, missing states and unhandled errors before you show it to a single real person.
M7

Responsive Design

Mobile-first UX Responsive layout behaviour Designing within real constraints AI: check how the layout should behave across breakpoints, then open the awkward ones on an actual phone and see what really happens.
M8

Accessibility & Inclusive Design

WCAG 2.1 AA in practice Designing for diverse users Inclusive design practices AI: run automated contrast and markup checks, then find everything they missed using only a keyboard and a screen reader.
M9

Design Systems & Collaboration

Design systems and components Figma workflows Developer handoff AI: draft component documentation and handoff notes from your file, then correct everything it guessed wrong about your intent.
M10

Design Defence

Decision, reason, evidence Defending a choice under questioning Success metrics AI: brief it as a hostile stakeholder and let it tear into your decision privately, before a room full of people does it publicly.

How this curriculum
is structured.

The ten modules run in the order a real project runs. You do not open Figma in week one and reverse-engineer a rationale afterwards. You start where product teams start, with the people using the thing, and every module hands its output to the next.

That ordering is why the modules cannot be taken out of sequence. Each one produces something the next one needs, and skipping ahead breaks the case study you are assembling.

Every artifact you produce carries three things: the decision, the reason, and the evidence behind it. That habit is what module ten tests.

  • 01 Research feeds personas
  • 02 Personas feed structure
  • 03 Structure feeds flows
  • 04 Flows feed wireframes
  • 05 Wireframes feed testing
  • 06 Testing feeds the defence

How AI is taught
here.

AI is taught as capability, not as tools. Naming a specific tool as permanent curriculum would be dishonest, because the tool you learn today may not exist in eighteen months. You learn what AI is for at each stage of the work, then apply it with whatever is current. When the tools change, your workflow survives.

Three kinds of AI exercise run through the modules. The third is the one that changes how people think, and it is why the final module is a defence rather than a presentation.

  • 01 Accelerator: generate five alternatives, then evaluate them
  • 02 Critic: review your flow for usability risk, then verify it
  • 03 Challenger: argue against a decision you already made

You leave with a
real case study.

  1. Problem Framing
  2. User Research
  3. Personas
  4. Journey Mapping
  5. Information Architecture
  6. Wireframes
  7. Interactive Prototype
  8. Usability Testing
  9. Design Defence

Curriculum questions

Do the modules have to be taken in order?
Yes, and deliberately so. Each module produces something the next one needs. Research feeds personas, personas feed information architecture, and so on. Taking them out of sequence would break the case study you are building.
Which AI tools do you teach?
Whichever are current when your batch runs, but the tool is not the lesson. You learn what AI is genuinely useful for at each stage of the work, how to check its output against evidence, and where it stops being reliable. Naming a specific tool as permanent curriculum would be dishonest, because it may not exist in eighteen months. The judgement transfers. The tool does not.
Is Figma taught from scratch?
Yes. No prior tool experience is assumed. Figma is introduced at the point you actually need it, in the wireframing module, rather than as a standalone software course at the start.
Do I work on a real project or a set exercise?
A real one. You choose a problem early and carry it through every module, which is what produces a coherent case study rather than a folder of disconnected screens.
Is accessibility really part of a beginner curriculum?
It is, because it is part of professional work. Accessibility is taught as a design constraint alongside responsive behaviour, not as an optional advanced topic bolted on at the end.

10 modules.
One decision you can defend.

Work through every module live, with your reasoning critiqued while you are still making it.

Enroll now