đ§ Donât Make Me Think
Hello! Adam Thornhill here. âThe Podcast Guyâ saving you 10 hours a month.
Today, youâll learn about setting smart defaults thanks to Lennyâs Podcast.
You canât build great products by letting users do whatever they want.
Sometimes, your job is to protect them from themselves.
Whether itâs misusing features or or getting lost in settings, the problem usually isnât friction, itâs comprehension.
And if people donât understand your product, they wonât stick around.
Slackâs âDonât be a cockâ principle
We had this feature @everyone, which caused a notification to be sent to every member of the channel when a message was sent.
Someone would find this feature inside of an organization.
They would @everyone, everyone would get a notification, then the next person to send the message was like:
âMy thing is more important than Bob, Iâm going to also @everyone.â
It became really obnoxious. People would complain about it.
So we came up with the shouty rooster.
Internally, we said âdonât be a cockâ. But we didnât obviously say that publicly.
When you @everyone, a little rooster would pop up and have these sound waves coming out of its mouth. It would say:
âHey, this is going to cause a notification for 147 people in eight different time zones. Are you sure you want to send this message with @everyone?â
This worked amazingly and the behavior dropped off.
We shaped the communication culture inside organizations.
Stewart Butterfield, Co-founder of Slack
Comprehension beats friction
70â80% of product design is comprehension.
People rarely open preferences. And even when they do, they donât know what half the options mean.
If they donât understand it, they wonât use it.
So when youâre designing something unique, something your product does differently, the challenge isnât reducing the number of clicks. Itâs clarity.
Stewart Butterfield, Co-founder of Slack
Why it matters
The customer isnât always right.
If you give users too much freedom, theyâll abandon or misuse your best features.
Thatâs why great products do 3 things:
Set smart defaults. Most users never change them.
Shape behaviour. Use nudges, warnings, constraints, and delight.
Prioritise comprehension over friction. Itâs not about making every path shorter - itâs about making it obvious.
No one uses what they donât understand!
Next steps
Adopt a âdonât make me thinkâ mindset in your product and growth teams:
Default first. Design for what most people should do, not what they might do.
Use nudges to teach. Think modals, tooltips, inline feedback, just-in-time education.
Reduce cognitive load. Make it easier to decide, not just faster to click.
Kill confusion early. If it takes a help article to explain, it probably needs a redesign.
Your thoughts?
Want to connect? Connect on LinkedIn or Twitter
Want to advertise? Click here


