The Rest

Same Word, Different Toast

"I need a menu page." Didn't you mean: you need to replace a phone call?

"Add a notification system." Didn't you mean: what are you interrupting them from?

"Make it more intuitive." Didn't you mean: what did you expect to find here?

"We need a dashboard." Didn't you mean: you want to feel in control?

I rephrase everything. Someone says something to me, I reply with "didn't you mean X?" and they get annoyed — they could tell I understood from context. But I still had to be pedantic about it.

I used to think this was a flaw. People don't like being corrected, and rephrasing feels like correction even when it isn't.

But that instinct is the entire foundation of how I think about design. The gap between what someone said and what they meant is where all the interesting work lives. Most people accept the first framing. They build the dashboard. They add the notifications. They try to make it "intuitive" without asking what that word means in this specific context, for this specific person, in this specific moment.

Ask a room to draw "how you make toast." Americans draw a toaster. Europeans draw a frying pan. A student draws a stick figure holding bread over a campfire. Same word. Different toast.

Now imagine what happens when you say "build me a dashboard."

Every button you've ever clicked made a promise. Where it sat on the screen, how it looked, what it was called — all of that told you something before you read the label. Most of the time you didn't notice, because the promise was kept.

This book is about the times it wasn't. And about learning to see the promises before they break.