What Entrepreneurs Can Learn from The Design of Everyday Things
Priya launched her meal-kit subscription with pride: a clean checkout page, a tidy dashboard, a pause button tucked into a settings menu three taps deep. Within a month, refund requests piled up, each one accusing her company of "hiding" the cancel option. She hadn't hidden anything on purpose — she'd simply designed the dashboard around what she, as the founder, already knew was there. Customers who couldn't find the pause button assumed they'd been tricked, and left one-star reviews calling the service a scam. Priya read every review convinced her customers were careless. Then she watched a new user's screen-share and saw the truth: nothing on the page told anyone a pause option existed at all. The feature had never been invisible to her. It had only ever been invisible to everyone else, and that gap had quietly cost her both revenue and reputation.
The whole book, compressed
This edition works through 4 core lessons — take them one at a time, not all at once.
What's different for your conditions
Tap whichever ones sound like you. Nothing here is sent or saved — it's just for your own noticing.
0 of 5 selected
The core lessons, applied to you
Making the possible visible at a glance
A founder's interface, form, or storefront should show its own options through what's on screen, not require a tour or a tooltip to explain them. If a customer has to hunt for a control, the product is asking them to already know something only the builder knows.
A booking app buries its "reschedule" option inside a generic "more" menu, so customers who can't find it simply no-show instead, assuming rescheduling isn't allowed.
Hand your product to someone who has never seen it, say nothing, and time how long it takes them to find your three most important actions unaided.
Giving feedback the instant someone acts
Every click, payment, or submission a customer makes needs an immediate, unmistakable signal that it worked, failed, or is still processing. Silence after an action reads as failure, and a customer who feels ignored rarely gives a growing company a second chance.
A checkout button shows no change after being tapped, so a nervous customer taps it four more times and is charged four times over.
Walk through your three highest-stakes actions — payment, cancellation, signup — and confirm each one produces a visible response within one second, every time.
Matching your product to what people already expect
New businesses often invent their own clever conventions instead of following the patterns customers already carry in from everywhere else. A shopping cart icon, a swipe-to-delete gesture, or a red cancel button all borrow trust that a brand-new pattern has to earn from scratch.
A founder replaces the familiar trash-can delete icon with a custom star icon meant to feel friendlier, and customers start starring items they meant to remove.
Before shipping a novel interaction, ask whether an existing convention already does the job, and default to convention unless you have a strong reason not to.
Treating a confused customer as a design signal, not a complaint to dismiss
When several customers hit the same wall, the honest conclusion is rarely that they were careless; it is that the product asked something of them it never clearly explained. Founders who treat repeated confusion as market feedback about their own design fix the actual problem, while those who treat it as a customer failing keep losing customers to the same silent dead end, quarter after quarter.
Visibility and simplicity often pull against each other: showing every option at once can clutter a screen, while hiding options to keep things clean can make them invisible. The balance is to surface only what a first-time customer needs right now, and let feedback after each step reveal the next layer instead of exposing everything up front.
Name one thing, honestly
Where in your product or process are you relying on a customer already knowing something that only you know?
Good. Now look back at the "Try this" line under whichever lesson feels most connected to what you just wrote, and treat that as this week's actual assignment — not all 4 at once.
The practices from this edition
0 of 3 selected
Run this for seven days
Before shipping a novel interaction, ask whether an existing convention already does the job, and default to convention unless you have a strong reason not to.