Discussion about this post

User's avatar
John Michael Thomas's avatar

Setting intelligent defaults is one of the superpowers of a good Product Manager.

On the side of helping customers, one of the most important things you can do to maximize ease of use is to ensure that the task settings have intelligent defaults (the values that most users would choose if they thought about it - so most users don't have to think about it). But on the side of helping the vendor, some of the most important things you can do to maximize revenue and reduce liability are to choose the most profitable financial and privacy defaults (even if - or especially if - they're not the options most users would choose).

The point of all this is that, as you said, the defaults are chosen for you, and ultimately *all* of them are designed to help the vendor, not you. This is even true of the ease-of-use defaults; the reason they're designed to help you is because that makes you a happier (and thus stickier) customer, which means you'll contribute more to the company bottom line over time.

The interesting thing is that this legerdemain of choosing the defaults that help the vendor most have become so bad in many industries that regulations sometimes explicitly define the default behavior that vendors must use.

For example, in the GDPR (EU privacy regulation), non-essential cookies require opt-in and consent boxes can't be pre-checked. And in the U.S. banking industry, customers can't be enrolled in overdraft coverage by default (they must affirmatively opt in). These regulations were written as a reaction to vendors' self-serving behavior around defaults (or not giving you a choice at all).

So, it's best to take the time to review all those settings. The alternative is to wait for it to get so bad that regulations force vendors to behave.

No posts

Ready for more?