Delivering Features VS Delivering Impact
summary
Companies move from shipping output to measuring outcomes by forcing engineers to own product experience and combine qualitative and quantitative signals: engineers meet a customer once a week, use a defined North Star and check whether releases move metrics before iterating. Examples: Amplitude tracks weekly collaborative users metric and evaluates a Slack integration by adoption change. Build iteratively — skateboard then scooter then bike then car — and ruthlessly kill or remove parked projects before they become tech‑debt maintenance burdens.
AI-written summary · about
chapters (7)
- 0:00Introductions
- 2:27Business outcomes vs. output
- 5:53Connecting engineers to users
- 11:23Defining done and iteration
- 17:25Motivating teams during downturns
- 22:03Managing technical debt
- 26:02Balancing roadmap priorities
related talks
52mBeyond Features
52mShifting into continuous delivery
47mContinuous Deprovement will eat your product for breakfast
45mThe Goldilocks Problem of Software Delivery
34mBuilding a Culture For Developer Productivity
31mBalancing New Features While Maintaining Quality
47mMaster the 10x Delivery System for Superior Software Engineering
29mBuilding alignment with Eng & Product