TYPENORMSchool Library

How-tos

Step-by-step procedures for common UX tasks, written as workbooks you can follow on your own product and check your work against. Each how-to is the one canonical procedure for its task, and every one has the same shape: the outcome you will have at the end; when to use it and when not to; what you need before you start; numbered steps, each saying what to do and what you should have once it is done; a worked example taken through every step; a checklist to run against your own result; the mistakes people commonly make; and the related laws, patterns, Pulse templates and courses. Where a Pulse template exists for the task, the how-to ends in it, so you finish with a filled-in persona, journey map, empathy map, survey or brief rather than a page of notes. The articles keep the reasoning behind each method and link here for the steps.

Research

  • Create a user persona

    Turn eight to twelve interviews into a one-page persona, derived from behaviour, that settles a design decision your team is stuck on.

  • Create an empathy map

    Sort research notes about one user into says, thinks, does and feels, then read the gaps between them to find what to design for next.

  • Create a customer journey map

    Map one persona's path to one goal across stages and channels, built from research, and cut it down to the moments a team will act on.

  • Write a UX survey

    Write a short survey that measures how usable your product is, with neutral rating statements and one targeted open question, tested before it goes out.

  • Run a user interview

    Plan, run and debrief a thirty-minute interview about the last time someone did the task, so a set of eight conversations adds up to a decision instead of a pile of opinions.

  • Write a usability test script

    Write the one document a moderator reads from in every session — the introduction, the background questions, three to five tasks that give nothing away, and the debrief — and pilot it once.

Information architecture

  • Run a card sort

    Give fifteen or more people your content as cards, let them group and name the cards, and read the groups that recur into a draft set of categories and labels.

  • Run a tree test

    Give people tasks against a bare text version of your navigation and measure where they look, so you can fix the labels and branches that mislead them before anything is designed.

Evaluation

  • Run a heuristic evaluation

    Have three to five reviewers inspect the main flows alone against the ten usability heuristics, then merge their findings into one severity-rated list of fixes.

Writing

  • Write error messages

    List every way a flow can fail, then write each message to say what happened and what to do next, in plain words, placed where the person is looking.

Planning

  • Write a design brief

    Agree the problem, the users, the scope and how success is measured on one page, signed off before anyone starts designing.

Accessibility

  • Check colour contrast

    Measure text and interface colours against the WCAG contrast thresholds, and fix the pairs that fail.