Loading
🦺
Delegated Decisions
Psychology used by:
You need to be a BFM+ member to save things to your library
There are downsides to delegating key decisions to your users.
👀
Introduction
If you, as the product builder, are unsure of your user's needs (or desires), it can be tempting to simply delegate those decisions onto them.
For example, imagine that you're building a dashboard, and don't know what the "ideal" layout would be.
So, you just let the user have full customisation over how it looks, and which components go where.
It sounds okay in principle, but you:
- Give the user more decisions to make (you've just delegated it to them).
- Allowing the user to create rubbish dashboards (low efficiency, lower value).
🧵
Deeper dive
Common ways of avoiding delegation
- Default filters and settings — this is removing the initial decision of "how should I be viewing this content".
- Default views and layouts — e.g., when you use Stripe, you don't create your dashboard from scratch. They've optimized one for you.
- Features on by default — e.g., autocorrect is turned on by default, it'd be a waste of time to ask every user if they wanted it.
🔥
Potential impacts
BFM+
Unlock this instantly with BFM+
- Access the entire library
- Track your progress through collections
- Receive premium weekly newsletters
- Build a library of ideas
Team plan perks include:
- Share links with your entire team. No paywalls or logins.
- Get discounts for upskilling your entire product team
Written by Peter Ramsey
Published
Last edited
Related Bites
Abandoned your basket
The first time you abandon a checkout, Shop will teach you that your basket will be synced between Shop and the online store.
Onboarding, on time
When creating a private folder in Granola, they’ll show contextual onboarding inline.
Squeezing onboarding into the feed
When looking at your achievements on Waze, if you haven’t used the “report by voice” feature yet, it’ll show onboarding in the carousel.
