LearnHill UX, Free Course Contents

Good to see you again! :) A persona isn't a profile of the "average user." It's a design model that expresses the goals, behaviors, and context found repeatedly in your research — through one fictional person. You began this series with a proto-persona: A guess, written down so you could test it. Then you interviewed, clustered, and mapped. You have evidence now. This is where the guess grows up.

Welcome back! Missed you :) An empathy map isn't a table where you imagine a user. It's a tool for connecting evidence from research into a single point of view. Last lesson, your affinity diagram found patterns across many users. This one moves the opposite way — down into one user's experience, connecting what they say, do, think, and feel. And it draws a line most beginners skip: The line between what you heard and what you're guessing.

Module 1. AI Fundamentals for the UX Workflow An AI workflow isn't a list of tools you happen to have open. It's a connected system — an insight engine — that carries information across research, ideation, prototyping, and testing, and helps you make sharper decisions at every step. This lesson is about building that system: choosing tools that fit the way you actually work, evaluating them honestly, and wiring them together into one coherent UX workflow.

Welcome back! Good to have you :) An affinity diagram groups scattered qualitative data by shared meaning, so a team can see the themes and needs hiding inside it. You come back from five interviews with two hundred fragments. Quotes, half-observations, moments where someone hesitated. The temptation is to skim them, spot something that confirms what you already suspected, and announce what to build. That isn't analysis. That's your existing opinion wearing evidence as a costume. An affinity diagram is the slow way. It's also the only way that survives contact with a stakeholder asking "what makes you say that?"

Welcome back — always :) The best question in an interview is rarely one you wrote down beforehand. It's the one you find inside what the participant just said. A participant tells you the checkout was confusing. You write it down, nod, move to your next scripted question — and you've just walked past the interview. Confusing how? What were you looking at? What did you do next? The answer they gave you was a door. Good interviewing is knowing to open it.

Good to see you again! :) The goal of a user interview isn't to collect opinions. It's to understand what someone actually did in a real situation, and why they did it. Ask a user "would you use a search feature?" and they'll say yes. People are agreeable, and they're optimistic about their future selves. Then you ship the search bar and watch the analytics: nobody touches it . The problem wasn't the answer. It was the question. A good interview doesn't ask people to predict — it asks them to remember.