My Product Had 47 Settings. I Removed 31 and Support Tickets Dropped 40%
by•
I counted once. Forty-seven settings. Toggles, dropdowns, preference fields. The kind of thing you accumulate over years of small decisions.
Thirty-one of them had never been changed from the default. I could see it in the data. Not once, by anyone.
I removed them. Not the features. Just the toggles that controlled how the features worked, locked to the default that everyone was already using.
Support tickets about configuration dropped 40% the next month. The product hadn't changed. The number of ways to get it wrong had.
How many settings do you have that nobody has ever touched?
5 views
p/runevr
p/producthunt
p/google-cloud-platform
p/aperture-7
p/raycast
p/kodlo
p/kuc-kuc
p/ai-context-flow
p/lasso-11
p/offiai
p/many-displays
p/dino-kids
p/reso
p/supabase
p/jev
p/dex-by-exmergo
p/murror
p/htmldrag
p/nexupira
p/duckfightclub
Replies
This is a great reminder that defaults are part of the product experience. Did removing any setting surprise users, or did the usage data make the safe defaults pretty clear?