Vitaly πͺπΈπ¬π§
When deep divingπ:
Imagine that during the process of ordering a card, bunq has this oppertunity to ask the user if they want a digital-only or digital+real card.
Now the design challenge is, what is the default?
Here comes some creativity at play:
I wouldn't make the default either 100% opt-in or 100% opt-out.
We can make some assertions based on the user.
- If the user already has a physical card of the same type which can be switched to any sub-account, the would mean +1 for making digital only their default choice and making ordering a card the opt-in choice.
- Secondly, you have statistics on age-groups, user postal code and payment method usage (Apple Pay vs Card): Use the average usage to assign the +1 to the side the user is estimated to best-fit in.
- For users who have been your client for some while, use their usage to make an guestimate what they would prefer.
You combine these three (example) data points to offer the best-fit default to that specific user going through the card-order process.
So ultimately the choice is still up to the user, but the default is not static but depended on factors related to the user.
(Want to make it more complicated? Sure, if you have hard data, you could design four paths in stead of two: ask (default digital only), ask (default digital+real), do (default digital only), do (default digital + real).