Marcus Andrey Study
Ler em português Library

UX Foundations · 9 min read

UX Design Foundations

The craft underneath everything, for people starting out and for designers who want to ground what they already do: framing problems, understanding people, structure, interaction, visual design and accessibility, with hands-on labs.

Eight steps, in order, for people starting out and for designers who want to name and ground what they already do. Each lesson ends with a short part for those who already practise, and the labs turn it into practice.

  1. Step 1 · What UX is

    • What UX design is (and isn't)User experience is everything a person goes through with a product or service, not only the screen. Where the term came from, how it differs from UI and usability, what UX designers actually do all week, and a first exercise you can do on the way home.
    • The design processHow UX work moves from a vague problem to something people can use: the Double Diamond's four phases, the human-centred design activities in the ISO standard, why iteration beats getting it right first time, and how to adapt the process to a small, real project.
    • Users, tasks and contextThe three things every design decision depends on: who the users are, what they're trying to achieve, and where and how they do it. Goals versus tasks, the five parts of a context of use, and how to describe them on one page before you design anything.
    • Who does what on a product teamUX design is a team sport. The roles you'll work with (product manager, engineers, researchers, content designers, design systems, QA, data), the product trio at the centre, what the usual team ratios really mean, and how to agree who decides what.
  2. Step 2 · Frame the problem

    • Problem statements and "How might we"Before you design, write down the problem: who has it, what they need, why it matters, without a solution hidden inside. How to write a problem statement, turn it into "How might we" questions that open up ideas, and check it with your team.
    • User needs and jobs to be donePeople don't want features; they want progress in their lives. How to tell a need from a request, what "jobs to be done" means and where the milkshake story comes from, how to write job stories, and how to use them to judge design ideas.
    • Personas and archetypesA persona is a short, evidence-based portrait of a group of users that helps a team design for real people instead of "everyone". Where personas came from, the three kinds, what to put in one (and leave out), why demographics mislead, and how to keep personas alive.
    • Journey mapsA journey map shows what one person goes through to reach a goal, step by step: what they do, think and feel, and where things go wrong. Its parts, how it differs from a service blueprint, how to make one from research, and how to turn it into opportunities.
    • Defining successDecide how you'll know a design worked before you design it. Outcomes versus outputs, Google's HEART framework and Goals, Signals, Metrics, simple measures anyone can use (task success, time on task, SUS), and how to write success criteria into a brief.
  3. Step 3 · Understand people

    • How people thinkA few facts about human attention and memory explain most usability problems. Mental models, cognitive load, recognition versus recall, Hick's and Fitts's laws, and why "seven, plus or minus two" is usually misused, with what each one means for a screen.
    • Short user interviewsA 30-minute conversation with the right person can save weeks of design. How to plan a short interview, ask about real past events instead of opinions and predictions, avoid leading questions, decide how many to do, and turn your notes into findings.
    • Usability testing with five peopleWatching a few people try your design is the fastest way to find what doesn't work. Why five participants is often enough (and when it isn't), how to write tasks, the think-aloud method, how to run a session without helping, and what to do with what you see.
    • Heuristic evaluationReviewing a design against ten well-known rules of thumb finds many problems before any user sees it. Nielsen's ten usability heuristics in their current wording, with an everyday example of each, how to run an evaluation with a few colleagues, and how to rate how serious each problem is.
  4. Step 4 · Structure

    • Information architectureBefore people can use something, they have to find it. What information architecture is, its four parts (organising, labelling, navigation and search), how it differs from navigation design, and why it should follow people's mental models instead of the org chart.
    • Navigation patternsNavigation is the part of the structure people can see. Global and local navigation, breadcrumbs, utility links, tabs, menus and search: what each one is for, when to use it, and what NN/g's research says about hiding navigation behind a hamburger icon.
    • Card sorting and tree testingTwo simple methods to build a structure people understand. Card sorting shows how people group your content; tree testing checks whether they can find things in your proposed structure. Open, closed and hybrid sorts, how many participants NN/g recommends, and how to read the results.
    • Content firstDesign with the real words and data, not with placeholder text. How to take a content inventory and audit, why lorem ipsum hides problems, and how to write labels, links and microcopy that people can find, scan and trust.
  5. Step 5 · Interaction

    • Affordances, signifiers and feedbackWhy some things feel obvious to use and others need a sign. Affordances, signifiers and feedback as Don Norman uses them, the famous "Norman door", how a screen shows what can be clicked, and the three response times that decide what feedback people need.
    • FormsForms are where people sign up, pay and apply, and where many give up. How to ask fewer questions, label every field, start with one thing per page, and show errors next to the field with a way to fix them, based on GOV.UK Design System guidance, NN/g research and Luke Wroblewski's Web Form Design.
    • Interface states: empty, loading, error, successA screen is never just the version in the mockup. Before there is data, while it loads, when something fails and after the job is done, people see other states. What each state should say and do, with NN/g guidance on empty states, progress indicators and error messages.
    • Patterns and when to break themMost interface problems have been solved before. What a design pattern is, where to find good ones (Material Design, Apple's Human Interface Guidelines, GOV.UK), why Jakob's Law makes familiar patterns so strong, and how to decide, with evidence, when breaking one is worth it.
  6. Step 6 · Visual design

    • Visual hierarchyBefore a screen looks good, it has to say what matters most. How size, contrast, position and whitespace set the order in which people see things, the squint test to check it, and how to give each screen one clear first thing.
    • Gestalt principlesPeople see groups before they see details. Six Gestalt principles (proximity, similarity, common region, continuity, closure, figure and ground) explain which things look related on a screen, and how to use them on purpose instead of by accident.
    • Typography for interfacesMost of an interface is text, so typography is most of its design. Body size, line length, line height, a type scale for headings, system fonts versus brand fonts, and the WCAG text-spacing rule, with starting numbers you can use today.
    • Colour and contrastColour guides attention and carries meaning, but only if people can see it. WCAG 2.2 contrast ratios (4.5:1 for text, 3:1 for large text and controls), why colour must never be the only signal, and how to build a small palette where every colour has a role.
    • Layout, grids and spacingA grid and a spacing scale turn hundreds of small layout choices into a few rules. Columns, gutters and margins, a spacing scale built on 4 and 8, how layouts adapt to phones, tablets and desktops, and what WCAG's reflow rule means for your designs.
    • What a design system isA design system is more than a component library: it's tokens, components, guidelines and the people who look after them. What each part does, Brad Frost's atomic design, design tokens and the 2025 standard, and why governance decides whether a system lives or dies.
  7. Step 7 · Accessibility and inclusion

    • Accessibility fundamentalsAbout one in six people lives with a significant disability. The four WCAG 2.2 principles, levels A, AA and AAA, the criteria designers own (contrast, focus, target size, labels, headings, alt text), assistive technologies, and the laws that require it.
    • Inclusive designAccessibility sets the minimum; inclusive design is the way of working that gets you there and further. Microsoft's three principles, permanent, temporary and situational needs, the true story of the curb cut, designing with people instead of for them, and how language, culture, age and reading skills change a design.
  8. Step 8 · From design to product

    • Prototype fidelityA prototype is a question you can put in front of people. Low, mid and high fidelity, from paper sketches to coded prototypes, what each one can and can't answer, and how to choose the cheapest prototype that still answers your question.
    • Handoff to developersA design is a set of decisions, and developers can only build the ones you made visible. What to specify (states, edge cases, behaviour, spacing through tokens, accessibility notes), why working with developers early beats a big handoff at the end, and how tools like Figma Dev Mode can help.
    • Design critique in practiceShowing unfinished work to colleagues is uncomfortable, and it's the fastest way to improve it. What a design critique is and how it differs from general feedback, how to present your work, how to give comments linked to goals, and a simple format your team can start next week.
    • Case studies and your portfolioA portfolio is a product for a busy reader, and each case study is a short story about a problem. The structure of a UX case study (problem, role, process, decisions, outcome), how to show your process honestly, how to describe work under NDA without screens, and what hiring managers say they look for.
  9. Labs

    • Heuristic review of a real appA guided lab: review three screens of an app you use against Nielsen's ten heuristics, write each problem with its location and a fix, rate its severity, and present the top three. About an hour, with paper or any notes app.
    • Test with three peopleA guided lab: run a small usability test in an afternoon. Write three tasks, find three people who match the users, run 20-minute think-aloud sessions without helping, and turn what you saw into three fixes.
    • Run a card sortA guided lab: run an open card sort with paper cards. Choose 20 to 30 pieces of content, ask three to five people to group and name them, photograph the results, find the patterns and draft a simple structure. About an afternoon, with index cards and a pen.
    • Redesign a formA guided lab: take a real form you've filled in, question every field, rewrite the labels and error messages, split it into simple steps, and sketch the new version on paper with its error and success states. About an hour and a half, with paper and a pen.
    • Build a type scaleA guided lab: choose a base size and a ratio, build a scale of five or six text sizes with line heights, apply it to one real screen and test it on a phone at arm's length. About an hour, with paper, a calculator and any notes or text app.
  10. Reference

    • Glossary184 terms defined in this course's lessons, A to Z.
    • Frameworks20 frameworks and techniques this course's lessons use, by area.
    • Library211 books, articles, videos and courses cited in this course, grouped by the step they appear in.
Saved only on this device.

↑ ↓ to move · Enter to open · Esc to close