Learn with Phoebe Β· System & Product Design

Learn Product Design with Phoebe

Six sessions, 45 minutes each, and one real screen you take from a problem statement to an engineering handoff. Not a tour of design theory and not a tools course. The craft itself: working out what the problem actually is, doing research that changes your mind, giving a screen a structure, and then defending it in a critique. In session 4 you meet a scorer that computes the contrast ratio of the pixels you just changed, which is a harder audience than any opinion.

6sessions
1screen, end to end
7levers on the scorer
100points to reach
45min per session

The six sessions 🎨 · one screen, designed across all of them

The running project is Daybreak's "Manage your subscription" area - the screen where a coffee subscriber pauses, skips, changes their grind or cancels. It is the highest-stakes surface the company owns, because it is the only screen where the customer is actively deciding whether to keep paying, and right now the button that saves the relationship is buried two taps behind the one that ends it.

🎯 Session 1 · easy

Before pixels

What the problem actually is, who is hurting, and the one number that would move if you solved it. No screens allowed in this session at all, which is the point of it.

β–Ά Start here
🎧 Session 2 · easy

Research that changes it

Five interviews, questions that do not lead, and the quotes-to-insights move. Plus the discipline that makes research honest: write down what you expect to find before you go and find it.

the pre-registered guess
πŸ—‚οΈ Session 3 Β· medium

Structure and flow

Information architecture as the cost of nesting, task flows before screens, deliberately ugly wireframes, and the empty-loading-error trio that is the common case on a screen like this one.

grey boxes on purpose
πŸ“ Session 4 Β· medium

The visual system

Type scale, spacing scale, hierarchy and colour - graded by a live scorer that reads the real rendered pixels and computes the WCAG ratio. Then you meet the anti-lever, and it costs you 42 points.

β˜… the scorer
πŸ’¬ Session 5 Β· hands-on

Interaction and copy

Feedback within a second, microcopy as interface rather than decoration, forms improved mainly by deletion, a motion budget, and confirmations that name the consequence instead of asking if you are sure.

words are the UI
🀝 Session 6 · hands-on

Critique and handoff

Running a critique that produces decisions instead of opinions, receiving one without defending, the handoff pack that survives you, and writing down the debt you knowingly shipped.

πŸ”’ the ship gate
easy - everyone medium hands-on hardest

Your passport 🎫

Clear all three quiz questions in a session and it gets stamped. Six stamps means you have taken one screen from a complaint to a handoff. Stamps live in this browser only.

What this course is not, so you land in the right place 🧭

If your question isGo here instead
How do I use AI tools to make design assets faster?learn-ai-design-with-phoebe
How does product management change when drafting is free?learn-ai-pm-with-phoebe
How do I actually build the front end?learn-html-with-phoebe
How do I test whether the change worked, statistically?learn-experimentation-with-phoebe
How do I design something that works for the person using it, and hand it over so it survives?you are in the right place

This course is deliberately AI-agnostic. Every judgement in it is one a tool cannot make for you, which is exactly why it keeps its value.

Choose your path πŸ—ΊοΈ

Three doors into the same conviction: design is a series of decisions you can defend with evidence, not a matter of taste you either have or do not.

⏱️ I have ninety minutes 1β†’ 4 find the real problem, then watch a screen go from 0 to 100 on measured criteria
πŸ§‘β€πŸ’» I am an engineer who keeps getting vague specs 3β†’ 5β†’ 6 states, edge cases, copy and the handoff pack you wish you were given
🎨 The whole journey 1β†’ 2β†’ 3β†’ 4β†’ 5β†’ 6 one screen, from a complaint in a support ticket to a handoff a developer can build

What is honest here 🧾

The scorer in session 4 is half measurement and half teaching model, and it tells you which is which on its own footer.

ClaimStatus
The contrast ratio on the scorerReally measured. It reads the rendered elements' computed colours, resolves the background, and applies the WCAG 2.1 relative-luminance formula. Change a colour and the number changes because the pixels changed
4.5:1 for body text, 3:1 for large text, 7:1 for AAAWCAG 2.1 contrast minimums, as specified
Hierarchy, spacing, copy, states and findability scoresA teaching model with a stated rubric, calibrated so each trade is visible. Not a measurement of your product
"Time to find pause", in secondsModelled, not observed. It exists to make nesting cost visible, and the page says so where it appears
Daybreak's numbersA teaching scenario. The company is fictional and every figure about it is part of the exercise

The knowledge map 🧠

The whole course at a glance - hover a session to spotlight its concepts, click any node to jump in.