Think like a designer. Ship like a builder.
A hands-on path through research, flows, interface decisions, accessibility, design systems, product data, AI-native UX, prototyping, testing, and portfolio storytelling. Figma is a tool. Your judgment is the skill.
AI can generate screens quickly. That makes problem framing, judgment, evidence, edge cases, accessibility, and validation more valuable—not less.
What you’re actually training
Not “how to make screens.” The transferable skills underneath modern UX work.
Find the real problem
Research behavior, surface friction, separate evidence from assumptions, and frame the right problem.
Make decisions
Turn needs into flows, states, hierarchy, content, components, and interaction patterns—with rationale.
Prove what works
Prototype, test, read behavior and product data, learn, and iterate instead of defending your first idea.
Your progress
The goal is evidence of skill, not course completion theater.
Short concepts + immediate application.
Real practice artifacts you can keep.
Your first case study, built as you learn.
Badges
Small proof that you’ve practiced a behavior, not just read about it.
From instinct → professional UX judgment
10 tracks · 40 lessons · learn them in order or jump where you need.
Do UX, don’t just read UX
Short, concrete missions that build the muscles employers actually care about.
Find one frustrating website and make one thing clearer.
Observe → name the friction → propose one change → explain why.
Mission board
Save your answers locally. Finish the mission when you have something concrete.
Critique arena
Practice seeing problems before reaching for solutions.
What’s the biggest UX problem?
Use AI without outsourcing your thinking
Learn two different skills: designing with AI and designing AI experiences.
Turn “make me a screen” into a UX-quality brief
Fill this in, then use the generated prompt in an AI prototyping tool.
Before you call it “done”
AI UX pattern: confidence without pretending certainty
For generative or predictive experiences, avoid designing the system as an all-knowing oracle. Give users context, editable outputs, clear provenance when relevant, recovery paths, and a way to say “this is wrong.”
Designer language: “The model’s output is a suggestion. I’m designing the interaction around appropriate trust, user control, and recovery.”Build evidence, not pretty case-study theater
A credible case study shows what you noticed, why you chose, what changed, and what you learned.
Use tools to support thinking—not replace it
A compact shelf for when a lesson needs deeper reference.
UX glossary
Words you should understand well enough to explain without jargon.