STORIES

10 Stories to Tell Your Design Students
10
An Educator's Anthology

10 Stories to Tell
Your Design Students

Real stories. Real lessons. Real transformation.

Begin
01

The Wrong Door

Why Norman doors changed how designers talk about humans

It is 1988. Don Norman, a cognitive scientist, is standing in front of a glass door. He pushes. Nothing happens. He tries again — harder. He feels the familiar, quiet embarrassment of a grown adult defeated by a door. Then he notices: the door is a pull door. There is no handle, only a flat plate. His brain said push. The design said push. The door said pull. Nobody told him.

He goes home and writes about it. Not about the door — about himself. About the ten thousand times he has watched humans fail at objects and quietly blamed themselves for it. The toaster that burns your hand. The light switch panel that controls nothing you expect. The software that destroys an hour of work with one wrong click. Every time, he writes, we blame the user. Every time, we are wrong.

"If an everyday object requires instructions, the design has failed."

He coins the term affordance — the quality of an object that tells you, without words, how to interact with it. A door handle affords pulling. A flat plate affords pushing. When the two mismatch, the door lies. And when a door lies, the person who pushes when they should pull is not stupid — they are doing exactly what the design told them to do.

His book, The Design of Everyday Things, goes on to become the most-read design book on earth. And the flat-plate pull door is renamed — forever, in design circles — a Norman door. His shame becomes the entire discipline's lesson.

The Lesson
"When the user fails, the designer failed first. Your job is to design apologies out of existence."
How to Teach It
Ask students to spend one day photographing Norman doors — objects that confuse them. Have them present one photo and explain: What did the design tell me? What should it have told me? This exercise builds the habit of externalizing blame — the foundational mindset shift of every good designer.
02

The $300 Million Button

The single UI change that earned a company three hundred million dollars in one year

A major US retailer has a problem. Their checkout is leaking money. Customers fill carts, reach the payment screen, and vanish — millions of them, every year. Nobody understands why. They hire a UX researcher named Jared Spool to find the answer.

Spool watches people try to buy things. And he notices something remarkable. The checkout screen has two buttons: Register and Sign In. Customers who want to buy something for the first time are forced to create an account before they can pay. Many of them — especially first-time buyers — don't want to. They don't want a relationship. They want to buy a blender. They leave. 45 million customers had abandoned their carts at this screen.

Spool's fix is almost embarrassingly simple. Remove the Register button. Replace it with one that says: Continue. Below it, in small text: "You do not need to create an account to make purchases." A single button. A single line of copy. Eight words.

"It was the most expensive button in the history of design."

In the first year after the change, the retailer earns $300 million in additional revenue. The next year, $1.5 billion. The button that was asking customers for a commitment they hadn't agreed to simply disappears — and people, trusted at last to be just customers, buy things.

The Lesson
"Every step you make a user take is a bet that the value ahead is worth the friction right now. Most bets fail. Remove steps before you add them."
How to Teach It
Give students a real checkout flow (any e-commerce site). Ask them to map every step between "I want this" and "I have this." For each step, ask: Who does this serve — the user or the business? Can it be removed, delayed, or skipped? The audit reveals the invisible friction tax on every experience they've ever designed.
03

The OXO Peeler

How a man watching his wife struggle in the kitchen created universal design

Sam Farber is retired. His wife Betsey has arthritis. One afternoon, he watches her try to peel an apple with a standard vegetable peeler — the thin metal kind with the flimsy handle — and he sees her wince. Not in great pain. Just in the small, everyday indignity of a thing designed by someone who has never considered her hands.

Farber is not a designer. He is a housewares businessman. But he is furious — not at Betsey, not at arthritis, but at the peeler. He decides to make a better one. He hires a design firm called Smart Design. He gives them one instruction: Make a peeler that works for Betsey. And for everyone like Betsey.

The designers don't start with sketches. They start with observation. They watch people cook — elderly people, children, people with wet hands, people wearing oven mitts. They prototype 40 different handle shapes. They land on a soft, ovoid, rubber grip — wide enough to hold without gripping, comfortable even with arthritic fingers. They call the company OXO. The peeler launches in 1990.

"Designing for the margins doesn't limit you. It frees you to design for everyone."

The OXO peeler sells millions. It wins every design award available. It gets added to museum collections. And here is the thing nobody saw coming: people without arthritis love it too. The grip that works for Betsey works for the teenager with small hands, the cook with wet fingers, the person holding a phone in the other hand. Inclusive design had not shrunk the market. It had found the entire market — by starting at the edge.

The Lesson
"The person your design currently fails is not the exception. They are the future majority of your users. Design for the margins and you design for everyone."
How to Teach It
Run the "Non-Dominant Hand Day" exercise: students use their computer, phone, and kitchen tools with their non-dominant hand for 30 minutes. Then: debrief. What broke? What held up? Whose hands did the designer assume? This visceral experience is more powerful than any lecture on accessibility.
04

The Blue Bottle Brief

The design studio that said no to every client assumption — and created a category

In 2012, Blue Bottle Coffee is a small roaster with a cult following in Oakland, California. They are growing fast. They need a website. They brief a design studio and walk in with the assumptions every client walks in with: Show the product prominently. Make it easy to buy. Communicate quality. Build trust with imagery.

The design team does something unusual. Instead of nodding, they push back. They ask: What does a Blue Bottle customer already know? What does someone who loves you believe? The answer is: almost everything. The people who seek out Blue Bottle already know coffee. They don't need to be convinced. They need to be respected.

The team proposes a website with almost nothing on it. No hero image of a steaming cup. No lifestyle photography. No trust-building paragraph about craft and passion. Just a white field, a menu, and a way to order. The design assumes intelligence. It treats the visitor as someone who already knows why they're here.

"Designing for your actual customer — not your imagined customer — takes more courage than any visual choice."

The client is frightened. Their instinct says: More. More pictures. More words. More reasons to buy. The design team holds the line. The site launches. It becomes one of the most discussed retail websites of the decade — studied in design schools, referenced in case studies, copied by a hundred brands. What it proves is this: restraint is a statement. And the courage to make that statement is the rarest skill in a client relationship.

The Lesson
"The brief is the beginning of a conversation, not a contract. Your job is to discover what the client needs — which is almost never what they asked for."
How to Teach It
Give students a "maximalist brief" — a fictional client who wants everything: big headlines, bold colours, lots of copy, photos everywhere. Students must create two versions: one that executes the brief literally, and one that fulfills the brief's true intent with the fewest possible elements. Present and debate: Which earns more trust?
05

The Dark Pattern

The designer who named the manipulation — and started a movement

Harry Brignull is a UX designer who has spent years watching companies use design to trick people. The unsubscribe button hidden in grey text on a grey background. The "free trial" that charges you on day 15 unless you find the cancel option buried four menus deep. The pre-ticked checkbox that signs you up for a mailing list you never wanted. The fake countdown timer that resets when it reaches zero.

He knows what these are. He knows they are intentional. Someone sat in a meeting, looked at the data, and said: If we make this harder to find, fewer people will cancel. Someone else nodded. A designer built it. It shipped.

In 2010, Brignull names them. He calls them dark patterns — user interface designs that trick people into doing things they didn't intend. He catalogues them: the roach motel (easy to get in, impossible to leave), confirmshaming ("No thanks, I don't want to save money"), misdirection, hidden costs. He publishes a website. He starts a public hall of shame.

"Naming something gives people power over it. Designers had been building dark patterns for years. Nobody had told them what they were doing."

The naming changes things. Designers now have a word for what they'd been asked to build. They have a way to say in meetings: That's a dark pattern. I won't design that. Regulators begin using his taxonomy. The EU bans several named dark patterns in 2022. One designer's decision to name the manipulation becomes — slowly, genuinely — a turning point in how the industry understands its own power.

The Lesson
"Design is never neutral. Every choice you make either respects your user or exploits them. The question is not whether your design has power. The question is what you do with it."
How to Teach It
Show students 10 real screenshots. Ask them to identify the dark pattern in each — and then redesign it honestly. The redesign often converts less but builds more trust over time. Discuss: If you were the designer asked to build this, what would you do? This is not hypothetical. They will be asked.
06

The Knoll Chair

How Florence Knoll refused to design anything she hadn't sat in — and built a furniture empire on that principle

Florence Knoll has one rule. Before she designs any piece of office furniture, she must live in the space it will occupy. She doesn't interview the workers. She doesn't study photographs. She sits at the desk. She takes the meetings. She feels the chair. She notices when her back hurts at 2pm, when her arm cramps reaching for the phone, when the light hits the wrong way and she can't see her papers.

This sounds obvious. In 1950, it is radical. The furniture industry designs for aesthetics. For showrooms. For photographs in catalogs. Florence Knoll designs for the person who will spend 40 hours a week in the thing. She calls her method total design — and what she means is not that she designs everything, but that she considers the entire experience: the chair, the desk, the room, the person, the hour, the light, the posture, the fatigue.

When Knoll receives a commission to redesign CBS's offices in New York, she doesn't present mood boards. She checks in for a week. She rides the elevator. She attends editorial meetings. She eats in the cafeteria. When she finally sits down to design, she is not designing for an imagined CBS employee. She is designing for the person she watched drop their coffee because there was nowhere to put it during a standing meeting.

"You cannot design a good chair by thinking about chairs."

The Knoll collection becomes the defining aesthetic of the mid-century American office. More than that, it becomes the proof that rigor precedes beauty — that the most elegant solutions grow from the most intimate understanding of a problem. Not the problem as stated. The problem as lived.

The Lesson
"You cannot design a chair by thinking about chairs. You design a chair by understanding what it feels like to sit in one — badly — for 8 hours."
How to Teach It
Assign "shadow research" — students spend 3 hours living as a user of whatever they're designing. Designing for a hospital? Sit in a waiting room. Designing for students? Attend a class as if you know nothing. The debrief question is always the same: What did your research plan miss? What did your body discover?
07

Target & The Pregnancy

When a company's data was so accurate it revealed something a father didn't know

In 2012, a man walks into a Target store in Minneapolis and asks to speak to the manager. He is holding a mailer that Target sent to his teenage daughter. It is full of coupons for cribs, diapers, baby clothes, and prenatal vitamins. He is furious. Is this some kind of joke? he demands. Are you encouraging my daughter to get pregnant?

The manager apologises. He doesn't know why the mailer was sent. A few days later, he calls to apologise again — and this time the father is quiet for a moment. I owe you an apology, he says. There was information I didn't have. My daughter is due in August.

Target had known before the father did. Their data scientist Andrew Pole had built a pregnancy prediction model using purchasing patterns — unscented lotion, cotton balls, hand sanitiser, a second handbag. Women buying these products together, in this sequence, were pregnant with high probability. Target's algorithm had detected the signals. It had acted on them. It had been right.

"The algorithm had no ethics built in. Only the human reading the story could feel the weight of what it had done."

Target changes its strategy after the story breaks publicly. They learn to mix their targeted coupons with random, unrelated items — lawn mowers, wine glasses — so the pattern is harder to detect. They don't become less creepy. They become invisible. This, they decide, is acceptable. The designer who built the system was never in the room for that conversation.

The Lesson
"Data is not neutral. Every system you build knows something about someone they did not choose to share with you. What will you do with that knowledge?"
How to Teach It
Ask students: What does your design know about its users that the users don't know it knows? Map every data point a product collects. Then ask: Who gave permission for each one? Who benefits? Who is at risk? This exercise surfaces the invisible power dynamics baked into every product from day one.
08

The Two Elevators

The hotel that solved a complaint without fixing a single thing — and what that says about design

A luxury hotel in New York is receiving complaints. The elevators are too slow. Guests are waiting three, sometimes four minutes — an eternity in the time-sick culture of Manhattan. The hotel hires engineers to study the problem. The engineers have three options: install a new elevator shaft (expensive, impossible), upgrade the motors (expensive, marginal gain), or stagger the elevators algorithmically (cheaper, still inadequate). None of the solutions are satisfying. None are affordable.

A junior consultant on the project has a different idea. He doesn't look at the elevators. He looks at the people waiting for them. He watches their faces. He watches what they do with their hands. He watches their eyes. And he notices: they have nothing to look at. Three minutes of staring at a brushed steel door, watching the floor numbers tick, is a very long three minutes.

His suggestion costs almost nothing. Install full-length mirrors in the elevator lobbies. Give people something to do while they wait — to straighten their collar, check their hair, examine their reflection. Make waiting feel occupied rather than empty.

"Time does not change. The experience of time does."

The mirrors go up. The complaints about slow elevators stop entirely. The wait time does not change by a single second. The elevators remain exactly as slow as they were. But nobody is bored anymore. The problem was never the elevators. The problem was the experience of waiting — and the experience of waiting is a design problem, not an engineering one.

The Lesson
"The problem the client names is almost never the problem you need to solve. The first skill of design is to find the real problem — which usually lives one level deeper than the complaint."
How to Teach It
Give students a problem statement from a real or fictional client. Ask them to write down the "real problem" — the human experience underneath the stated complaint. Then ask: Can you solve the real problem without touching the stated one? This breaks the habit of solution-first thinking — the most expensive habit a designer can have.
09

The Broken Gates

How an MIT study on "desire paths" changed the way we think about who leads whom

When a new campus is built, the architects face a question: where should the paths go? The standard answer is: between buildings, in straight lines. The efficient answer. The logical answer. The answer that makes the map look clean and considered. They pour the concrete. They plant the grass. They open the gates.

Within three months, students have created their own paths. Not on the concrete. Across the grass. In diagonals. Through corners. In lines that the map does not show, between destinations the architects didn't anticipate — the good coffee machine, the sunny spot, the shortcut to the bike racks. Worn into the lawn by thousands of feet, day after day, these paths have a name: desire paths. The paths people actually want.

The story is often told to point out a design failure. But the more interesting version happened at a campus that did something different. They built the buildings. They planted the grass. And then they waited a year before pouring any concrete. They watched where the desire paths formed. Then they paved those paths.

"The user is already telling you what to build. You just have to learn how to listen to footprints."

In digital design, desire paths are everywhere. The search bar used to navigate instead of the menu. The spreadsheet built to compensate for the missing feature. The workaround repeated ten thousand times a day by users who have given up asking for a fix. Every desire path is a design brief. The question is whether the designer is humble enough to read it.

The Lesson
"Users are always co-designing your product — through their workarounds, their hacks, their abandoned sessions. Listen to what they build in the gaps. That is your next feature."
How to Teach It
Ask students to find three digital desire paths in any product they use — workarounds, unusual uses, features repurposed for something else. Document and present: What did users build that the designer didn't build for them? What does this reveal about the gap between the designed experience and the lived one?
10

The Empty Chair

Jeff Bezos' ritual that made Amazon obsessively, sometimes terrifyingly, customer-first

At Amazon, in the early 2000s, Jeff Bezos begins a practice. In every important meeting — product reviews, design reviews, strategy sessions — there is one chair left empty. It sits at the table. It has no nameplate. Nobody sits in it. It is the chair of the customer.

Bezos explains the practice to his teams: That chair represents the most important person in this room. Everything we decide must be defensible to whoever sits in that chair. It is a performance, yes. But performances can change behaviour. The empty chair becomes a question that hangs over every meeting: What would the person sitting there say about what we're building?

Over time, the chair becomes less of a ritual and more of a discipline. Amazon's designers and product teams begin writing what they call "working backwards" documents — press releases written from the customer's perspective, describing the product as it will be experienced, before a single line of code is written. You start with the customer experience and you work backwards to the technology. Not the other way around.

"The empty chair asks the only question that matters: is the person this is for actually in the room when you decide what it is?"

The story is uncomfortable in its lessons. Amazon's customer-obsession has costs — for workers, for competitors, for society. But the ritual itself carries a truth that transcends the company: in most design meetings, in most critiques, in most client presentations, the user is not in the room. And every decision made without them is a guess dressed as a choice. The empty chair is the reminder that design is not about us.

The Lesson
"In every critique, every review, every studio decision — leave one chair empty. That chair belongs to the person who will live inside what you build. Ask what they would say. Then answer honestly."
How to Teach It
Do this literally in your next critique. Place an empty chair. Tell students whose it is — name the user, describe them. Before any critique begins, ask: "From her chair, what is the first thing she notices?" It reorders every conversation that follows. Students stop defending their work. They start listening to it.
What All 10 Stories Share

The Real Lesson
Behind Every Story

Every story here is, at its core, about the same thing: the gap between what designers assume and what users actually experience. That gap is your curriculum.

Story 01Don't blame the user. Blame the design.
Story 02Friction is a tax. Remove it before adding anything.
Story 03The margin is where the real brief lives.
Story 04Restraint is a design decision. Courage makes it.
Story 05Naming bad design is an act of design courage.
Story 06You cannot design what you haven't lived.
Story 07Data knows things users didn't choose to share.
Story 08The stated problem is rarely the real problem.
Story 09Users design in the gaps. Listen to their footprints.
Story 10Leave a chair for the person who isn't in the room.

Comments

Popular posts from this blog