UI/UX Designer to Product Designer
A comprehensive roadmap taking designers from static wireframes to end-to-end product leadership. Learn to frame hypotheses, analyze product analytics, build scalable tokenized design systems, and partner seamlessly with engineers.
What You Will Master:
Curriculum & Interactive Lessons
Module 1: The Product Mindset & Business Foundations
How top product designers align interface decisions with business viability and user delight.
Connecting Design Decisions to Business Metrics
25 minGreat product design is never decorative—it solves an economic problem for the business while solving an experiential problem for the user. When proposing a redesign or workflow change, frame your rationale around measurable indicators: ### Key Metrics Every Product Designer Must Know: 1. **Activation Rate:** The percentage of new signups that reach the "Aha!" moment. 2. **Time to Value (TTV):** The elapsed seconds/minutes from registration to the user achieving their primary goal. 3. **Churn vs Retention:** Identifying whether friction is driving users away after Day 1, Day 7, or Day 30. 4. **Task Success Rate:** Measuring error frequency and completion speed on critical transactional paths. Always pair your Figma deliverables with a 1-page hypothesis doc: *"We believe that simplifying the signup modal to 1 step will increase mobile activation from 38% to 52% because users currently abandon during phone OTP."*
The Hypothesis-Driven Design Framework
30 minInstead of guessing which layout works better, formulate clean hypotheses that can be validated with prototypes or A/B tests. ### The 4-Part Hypothesis Formula: - **Observation:** "We observed that 64% of visitors click the pricing toggle but only 8% click Start Free Trial." - **Hypothesis:** "We hypothesize that visitors are confused by annual vs monthly billing savings." - **Solution:** "We will add an explicit 'Save $48/yr' badge and show the effective monthly cost." - **Validation Metric:** "Success will be measured by a 15% increase in trial initiations over a 2-week testing window."
Module 2: Scalable Design Systems in Figma
Build atomic, scalable tokens and components that translate directly to React and Tailwind CSS.
Token Architecture & Semantic Color Variables
40 minDesign tokens are the contract between Figma and code. In modern product teams, tokens are structured in three tiers: 1. **Global (Primitive) Tokens:** Raw values like `color-green-500: #4ade80`, `font-size-base: 16px`. 2. **Semantic (Alias) Tokens:** Contextual meanings like `color-accent: var(--color-green-500)`, `color-surface: #ffffff`. 3. **Component Tokens:** Scoped variables like `button-primary-bg: var(--color-accent)`. By separating primitive values from semantic aliases, toggling Dark Mode or rebranding an enterprise client becomes a 2-minute token update instead of weeks of manual frame edits.
Semantic CSS tokens matching Figma variables
:root {
/* Primitive Tokens */
--green-500: #4ade80;
--dark-900: #0a1612;
/* Semantic Tokens (Light) */
--brand: var(--green-500);
--bg: #f3f8f4;
--surface: #e8f5e9;
--ink: var(--dark-900);
}
[data-theme="dark"] {
/* Semantic Tokens (Dark Mode) */
--bg: var(--dark-900);
--surface: #0f221c;
--ink: #eaf6ec;
}