How Much of Good UX Is Really Just Good Defaults
Most users never touch your settings panel, which means your defaults are the actual product.
Every product has a thousand small decisions baked into it before a single user opens the app. What font size. What color the primary button is. Whether notifications are on or off. Whether the cursor lands in the search box or the name field. Nobody asks for these choices to be made for them, but they get made anyway, and almost nobody changes them afterward.
That last part is the whole story. Across products we have built, the percentage of users who ever open a settings screen is small, usually under ten percent, often under five. The other ninety-plus percent experience your product exactly as you shipped it. They are not using your app. They are using your defaults.
This changes how you should think about the design process. Teams spend enormous energy debating flexibility: let the user choose, give them control, add a toggle. Flexibility feels responsible. But every toggle you add is also a tacit admission that you could not decide, and you are outsourcing that decision to someone with less context than you have. The user does not know what "aggressive caching" or "compact view" really costs or means. You do.
We have watched teams ship a feature, get complaints, and respond by adding an option instead of picking a better default. That fixes the complaint from the person who complained. It does nothing for the silent majority who hit the same friction and just left. A support ticket is not a representative sample; it is a sample of people angry enough to write to you, which is a very different population from people quietly deciding your product is not for them.
Good defaults are hard because they require actually deciding, and deciding requires understanding your users well enough to bet on their behalf. That is more uncomfortable than offering a menu of options, because a menu spreads the risk of being wrong across many small choices instead of concentrating it in one visible, ownable call. But concentrated and ownable is exactly what good design is. Complexity that is handled well does not look like more controls. It looks like fewer decisions the user ever has to make, because you already made the right ones.