How to Lose Your Feature Bloat?
summary
The talk argues that product bloat stems from essential vs. accidental complexity and recommends pruning features rather than just refactoring code. It describes using methods like cover-story workshops, a persona called the “octopus,” card-sorting, five-second tests, per-button analytics (Google Analytics and aujjar), and session heatmaps; a prototype with per-button tracking and simple user tests exposed navigation issues and deleting three low-use, high-cost features improved things short-term, while ongoing iterative user validation plus analytics is needed to prevent future feature overload.
AI-written summary · about
chapters (11)
- 0:00Start
- 6:14WHILE WE SPEAK, ESSENTIAL COMPLEXITY IS INCREASING!
- 6:47FEATURE BLOAT
- 8:42SOLUTION 2: LET YOUR APP DIE
- 14:03COVER STORY
- 20:33CARD SORTING
- 23:20PSYCHOLOGIST = UX DESIGNER?
- 32:50ANALYTICS TOOLS
- 34:05GOLDEN CIRCLE V2
- 34:36THE 4 PILLARS OF SIMPLIFICATION
- 36:115 PHASES, ITERATIVE!
related talks
43mHow to Lose Your Feature Overload
37mHow to Lose Your Feature Overload
01h 03mHow to defeat feature gluttony
38mFrom Conversation to Software
41mFeature Flags: A Boon or a Brake for a Team
31mBalancing New Features While Maintaining Quality
24mThe Feature Nobody Used & What It Taught Me About Product Engineering
52mBeyond Features