I'm tired of arguing over product development methodologies
summary
Argues that product success comes from clear principles not holy-method worship, claiming teams that prioritize shared understanding outperform strict-process teams. Uses concrete examples: a six-minute daily expanding to a 45-minute design session that actually speeds work, a hard rule to take a developer to usability tests at least once every six months, and quick team artifacts or off-site hackfests to start right. Recommends three guiding principles—shared vision, strong beginnings, and genuine care—over dogmatic methods.
AI-written summary · about
chapters (5)
- 0:00Start
- 10:17Always choose principles over methodologies.
- 12:41Start off right
- 15:13Care
- 17:54Thank you
related talks
43mDesigning the Right Product
40mUser Experience for Product Managers
43mDesign Beyond Deliverables
49mCo-creating with UX and Software
18mOn Product, Empathy and Creating a User Centric Culture
38mBuilding stronger teams for better user experience
01mSneaking agility back into Agile
31mEverything's Coming Up Dilbert: Building Product in the Enterprise - Emily Tate