Encounters and Solutions While Facing Outcomes
summary
Defines outcome as real changes in users’ world (not just features or revenue) and diagnoses three problems: teams prioritize outputs, outcomes are slow/hard to measure, and incentives ignore user change. Recommends concrete fixes: broaden team influence into adjacent areas, use user observation and proximal metrics (example: track add-to-cart rate to compare image vs text tweaks), make decisions using sprint-review metrics and customer voice, and adjust manager/HR practices to favor minimum output and maximum outcome.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:02Session goals
- 2:30Defining outcomes
- 6:48Challenges in outcomes
- 8:57Outcome measurement
- 10:22Lack of incentives
- 12:27Expanding influence
- 13:52Learning from users
- 14:57Shifting focus
- 15:59Outcome-focused environment
- 17:24Practical steps
- 18:48Passion for outcomes
related talks
19mThe Why, How & What of an Outcome centric team
42mOutcome Not Output
49mDesigning Business Outcomes (#noprojects)
28mOrganizing for Outcomes
29mFrom Agile to Outcome-Driven
53mOutcome-based product planning
46mPainful outcomes - 7 mistakes I made in the shift to value led development
35mHigher Expectations And More Opportunities