Improve your Product Roadmap with DevOps
summary
Argues that system logs and monitoring must feed roadmaps with five concrete tactics: escape vanity metrics, visualize data, find user patterns via jobs‑to‑be‑done, monitor from within, and measure culture. Gives examples: Best Buy API traces a Harvard hackathon cluster that reveals signup→activation gaps and fixes onboarding so activation climbs; site outages cut store visits by up to 75%; Netflix finds <1% public API traffic; Stripe estimates a $3 trillion developer efficiency opportunity and $85 billion lost to bad code; uses Jenkins and CI to keep stability.
AI-written summary · about
chapters (16)
- 0:00Start
- 9:03Story Hell
- 11:17The Software Engineering Efficiency Opportunity
- 12:20Conway's Law
- 14:37Learning Organizations
- 18:29Escaping Vanity Metrics
- 23:07Visualize the Data
- 26:43The Job To Be Done
- 27:04Scrum Story
- 33:17Monitoring from within
- 33:51Tdd
- 38:00Team Manifesto
- 42:22Changing Priorities
- 43:56Leadership Prioritization of Projects and Tasks
- 45:35Equifax Breach
- 47:20Book Recommendations
related talks
01h 00mImprove your Product Roadmap with DevOps
30mA Story of DevOps Transformations
24mBringing Product Thinking into DevOps
29mMeasuring Devops Success with Pipeline Analytics
28mThe DevOps Pipeline
25mBringing Product thinking to DevOps
26mTen Product Mindset Rules for DevOps Teams
28mBringing DevOps to Product