Description
A product review that hunts for features, flows and documentation that drain users' limited attention and self-control, asking whether each is a draining 'cake' or cheap 'fruit' feature.
Sierra treats attention and willpower as one limited account that every confusing control, poor manual or forced choice draws on, leaving less for learning the task users care about. The audit walks the product looking for leaks: features that drain more than they give, open loops users must hold in mind (the Zeigarnik effect), small uncertainties about whether an action worked, forced choices and second-guessing, memorisation, and behaviours that depend on willpower. Each feature gets four questions: does it drain resources, is it worth it, does it directly build expertise, and can it be hidden until users are ready. Remedies include putting knowledge in the world, trusted defaults and presets, unambiguous confirmation, affordances that make the right action the obvious one, and habits in place of willpower. The underlying ego-depletion claim has replicated poorly, so the audit is a design heuristic rather than a measurement.
Attributes
- Discipline
- Design & Product Practice
- Loss type
- Latent
- Goal
- Evaluate usability, Prioritise
- Stage
- Design, Evaluation
- Data
- Analytical / expert
- Effort
- Days
Steps
- List the features, flows, help content and support touchpoints in scope.
- For each feature ask the four questions: does it drain attention, is it worth the drain, does it directly build skill in the user's goal, can it be deferred or hidden until needed.
- List open loops users must keep in mind and add trustworthy confirmation, delegation or reminders.
- Find small uncertainties (did it save, is it on, did it send) and add clear state feedback.
- Check where users rely on memory or the manual and move that knowledge into the interface (labels, cheat sheets, inline hints).
- Replace required early choices with trusted defaults or recommendations.
- Identify behaviours that rely on willpower and redesign them as habits or remove them.
- Record each leak, its remedy and a priority, and verify the worst ones with users.
Sources
- Badass: Making Users Awesome (Sierra, 2015)
Also known as
- Cognitive Resource Leak Audit (cake-or-fruit feature review)
- Cake feature or fruit feature
- Cognitive leak review
- Willpower drain audit
Categories
- Design
- Design & Product Practice