How to Lose Your Feature Overload
summary
Discusses causes and remedies for product feature bloat, arguing that unprioritised essential complexity drives bloat and it’s cheaper to guide future features than continually remove old ones. Describes a workshop pipeline using card sorting and dot-voting to prioritise, five-second and usability tests to identify confusing screens, Six Hats to choose lightweight workflows, and analytics (Google Analytics, Hotjar, Flint) plus heatmaps to monitor impact; gives results such as a reduced 7–8 step campaign form with lower drop-off and a FogBugz rewrite that produced a successful new product.
AI-written summary · about
chapters (11)
- 0:00Start
- 3:08WHO WAS ADDING FEATURES
- 5:31SOLUTION 2: MANAGING TECHNICAL DEBT
- 6:19IN THE MEANTIME, ESSENTIAL COMPLEXITY INCREASES!
- 6:34FEATURE OVERLOAD
- 7:08SOLUTION 1: REMOVING FEATURES
- 12:37APPLICATION - HUMAN?
- 15:54WHY BUT HOW WITH WHAT?
- 21:26DOT VOTING
- 23:00COGNITIVE-BEHAVIORAL THERAPY (CBT)
- 40:03THE PILLARS OF SIMPLIFICATION
related talks
37mHow to Lose Your Feature Bloat?
37mHow to Lose Your Feature Overload
31mBalancing New Features While Maintaining Quality
41mFeature Flags: A Boon or a Brake for a Team
38mFrom Conversation to Software
24mThe Feature Nobody Used & What It Taught Me About Product Engineering
29mDriving clarity in ambiguous projects
30mAre You Doing Product Management or Bullshit Management?