What Creators/Innovators Can Learn from The Design of Everyday Things
Leo spent six months building a prototype garden sensor that texted people when their plants needed water. He was especially proud of its single control: a small dial with no markings, because he thought a clean, minimal look would feel premium. When he handed the first units to beta testers, most of them turned the dial randomly, unsure which direction increased sensitivity, and several assumed the device was simply broken when it didn't behave the way they expected. One tester, Priya, spent a week convinced her unit was defective and quietly stopped using it rather than ask what should have been an easy question. Leo read her silence as disinterest in the product itself. It wasn't until he watched someone else fumble with the same dial in front of him that he realized his "clean" design had never told anyone which way was which, and his most promising early tester had walked away believing the fault was hers.
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 a new invention visible at a glance
An original object or interface should show its own logic through its shape, markings, or layout, especially because a brand-new invention offers no existing convention for people to fall back on. If a control needs a caption or a demo video to be understood, the object itself hasn't finished communicating its function.
A creator ships a device with two identical unmarked buttons that do opposite things, and testers press the wrong one at roughly even odds every time.
Cover every label and instruction on your prototype, hand it to someone new, and note exactly which controls they operate correctly by sight alone.
Giving feedback the instant someone interacts
When someone presses, turns, or adjusts a new invention, it needs an immediate and unambiguous signal that the action registered and did something specific. Without that signal, a curious first-time user has no way to tell whether they've broken something or simply not touched anything at all.
A dial has no light, sound, or visible movement when adjusted, so testers assume the device is unresponsive and give up within seconds.
For your prototype's main control, add one immediate, unmistakable signal that a change occurred, even something as simple as a click or a small light.
Matching your invention to what people already understand
Even a genuinely new product benefits from borrowing familiar shapes and conventions wherever the underlying action resembles something people already know, like a dial, a switch, or a slider. Reserving true novelty for the parts of your idea that actually need it keeps the rest of the experience free of unnecessary learning.
A creator designs a custom rotating gesture for volume control that resembles no existing interaction, and testers can't discover it without being shown.
List every control on your prototype and mark which ones could instead use a familiar convention without losing what makes your idea original.
Treating tester confusion as unfinished design, not tester error
When early testers repeatedly misuse a new invention, the honest read is rarely that they weren't paying attention; it is that the invention hasn't yet learned to explain itself. Creators who treat this confusion as a design signal keep refining until the object speaks for itself, while those who dismiss it as user error often ship the same silent flaw to a much larger, less forgiving audience.
Originality and clarity can pull against each other for creators: a genuinely novel interaction is often part of what makes an invention exciting, but novelty always costs a first-time user some learning. The balance is to spend that novelty budget carefully, reserving it for what truly needs to be new and keeping everything else instantly familiar.
Name one thing, honestly
Which control or feature in something you've built have you never actually watched a stranger touch for the first time?
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
List every control on your prototype and mark which ones could instead use a familiar convention without losing what makes your idea original.