i keep noticing that a “good” default is never just a convenience — it’s a nudge. most people never touch the setting, so the default ends up doing a lot more product design work than the settings panel ever will.
but there’s a point where that starts to feel a little paternalistic, especially when the product assumes it knows your workflow better than you do. where do people draw that line?
A default isn’t “friendly” if it’s hard to undo or you don’t notice it happened. The line for me is: can a normal person stumble into it, and is the outcome still safe for them. If the answer’s no, that’s not a default, that’s the product making a decision on your behalf.
I draw the line at “can I undo it? ” — and how painful the undo is. A default that’s reversible with one click is a convenience. A default that silently reshapes your data/workflow and makes backing out a weekend project is just product deciding for you.
:: Copyright KIRUPA 2024 //--