Design Is Storytelling

Lupton, a curator at Cooper Hewitt and a designer, imports narrative theory directly: the story arc, the hero's journey, the rule of three, character, emotion and point of view are treated as instruments a designer picks up.

Her claim is that design already tells stories whether or not the designer intends it, and that doing it deliberately is the difference between a sequence and an experience.

Design tells a story whether or not you meant it to. The choice is whether you decide which one.

Devmark’s reading — not a quotation from the book

Short chapters, heavily illustrated, on action and the arc; on emotion and Norman's three levels of processing; on co-creation; on scenarios and journey maps; on the rule of three and gestalt.

Each chapter ends with an exercise, and the exercises are practical enough to run in a workshop.

It is a designer's handbook rather than a theoretical text — closer to a deck of tools than an argument that builds.

Read alongside Lupton's Thinking with Type for the typographic side. This one is about sequence and emotion; that one is about the letterform.

Closer to a set of tools than to a continuous argument, and better for it.

Devmark’s reading — not a quotation from the book

The implicit target is design taught as composition: layout, hierarchy and visual system, with the user's experience over time treated as someone else's problem.

Lupton's counter is that almost every artefact is encountered as a sequence rather than as an image — you arrive, you look, you act, you leave with an impression — and that a designer who has not decided the shape of that sequence has still determined it, accidentally.

Lupton organises the book as action, emotion and sensation — what happens, how it feels, and what the eye actually does. The sequence is deliberate: she starts with narrative structure because it supplies the sense of progression that static composition cannot, then adds affect, then the perceptual mechanics that deliver both.

Her most useful import is treating a product's use as a sequence with rising tension and resolution rather than as a set of screens. Setup, complication, crisis and resolution map onto onboarding, difficulty, error and recovery, and naming them makes it obvious when a design has a middle with nothing in it.

The emotion section uses the established distinction between the immediate sensory reaction to how something looks, the response to how it behaves in use, and the later reflective judgement about what owning or using it says. Lupton's point is that designers optimise the first, are measured on the second, and are remembered on the third.

The look is judged in a second. The behaviour is judged for a year. The meaning is judged afterwards.

Devmark’s reading — not a quotation from the book

She draws on the well-established account of the two gulfs a user crosses — working out how to do the thing, and working out whether it worked — and treats each as a narrative problem of information supplied at the wrong moment. Framed that way, most usability failures become failures of storytelling rather than of layout.

Each chapter ends with a task: storyboard the sequence, write the scenario, map the journey, describe the emotional arc. They are designed to be done in a workshop rather than read, and the book is substantially less useful to someone who skips them, since the theory is thin by design and the exercises carry the content.

It is short and deliberately broad, borrowing from narrative theory, cognitive psychology and gestalt perception without developing any of them. Readers wanting depth in any one area will find it introductory, and the heavy illustration that makes it approachable also means a low ratio of argument to page.

Use it as a workshop handbook rather than a text. Its lasting contribution is the reframe from composition to sequence — asking what happens next, and what the person knows at each point, rather than only what the screen looks like — which is a question layout training does not teach.