High Order Bit
summary
Software tends to be good for the first few versions then balloons into bloat by version four or five unless someone curates it; the team treats features like museum pieces and says no to keep a product focused. A CRM prototype (Highrise) became unusable and was thrown away and rebuilt; a separate tool (Campfire) succeeds by being only text chat. The company rejects tens of thousands of options to preserve simplicity.
AI-written summary · about
chapters (8)
- 0:00The software advantage
- 1:47Invisible product feedback
- 3:21Feature creep dangers
- 5:00Be a product curator
- 6:43Balancing customer demands
- 8:49Lessons in simplification
- 11:55Curation and saying no
- 13:22Q&A and final thoughts
related talks
31m“Good Enough” Architecture Part 1
26mAccept Complexity or Reject It? — Reflections Facing a Monolith Raised Alongside Business Growth
39mMinimal Viable Architecture
05mDesign and Architecture: Special Dumpster Fire Unit
27m“Good Enough” Architecture Part 2
57mStop writing software like it's 1999!
51mMicroProcess Architectures: Planning for Change, & Retaining Flexibility
01h 01mKeynote: Why are you making a new platform?