Sometimes developers limit the choices that are offered to their users as a way to simplify. This can be a good thing; I’m a big fan of simplicity.
However, this strategy comes with an important caveat:
If you’re going to force all choices into a few predefined buckets, you better provide buckets that match the needs of your users.
Broken buckets will not earn you brownie points. Or revenue.
Today I was adjusting my 401k contribution. Here’s the broken buckets I saw when I logged in to the financial services website: