How to Lose Your Feature Overload
summary
The talk addresses feature overload in products and argues that refactoring alone won’t remove the core complexity. It presents a practical method: deliberately remove features using workshops (cover story, personas), prioritize by impact with creative techniques like Six Thinking Hats, and validate removals with moderated user tests, 5‑second tests, task completion, and analytics (Google Analytics, heatmaps, session recordings).
AI-written summary · about
chapters (10)
- 0:00Introduction
- 5:23Feature overload discovery
- 9:35Burnout parallels
- 12:01Empathy and whiteboard
- 16:13Define and prioritize needs
- 17:37Identify frustrations
- 24:03User feedback and testing
- 29:05Automation to prevent overload
- 32:34Bilan and design thinking
- 35:26Q&A
related talks
43mHow to Lose Your Feature Overload
37mHow to Lose Your Feature Bloat?
41mHow to Lose Your Feature Bloat?
38mFrom Conversation to Software
41mFeature Flags: A Boon or a Brake for a Team
31mBalancing New Features While Maintaining Quality
30mAre You Doing Product Management or Bullshit Management?
41mEliminate waste..are we doing it all wrong?