Psyched about Outcomes
summary
Argues that measuring business outcomes beats counting features and shows how Mobius outcome delivery loop aligns engineering to revenue goals. Runs discovery workshops, uses event storming and value‑stream maps, scores options by ease/impact/confidence, and runs five-day experiments to validate hypotheses. Builds a skeleton automation framework in a real case, pivots tools midstream at week 14, and after a 26-week engagement reports faster regression cycles, more automated checks and elimination of an annual manual accounts task — outcomes measured and delivered.
AI-written summary · about
chapters (23)
- 0:00Intro
- 0:38What is your purpose within an organization
- 3:32What is best practice
- 6:00Feature factories
- 6:55Bridging the gap
- 8:16Mobius
- 14:58Pet options
- 17:17Delivery learnings
- 18:10User stories
- 21:44In the workplace
- 22:25Production problems
- 23:59Usability problems
- 25:26How the team worked
- 27:45Constraints
- 28:05Reducing Process Time
- 28:46Avoiding Arguments
- 29:53Measuring Outcomes
- 30:26Keeping it Real
- 32:24Automation Framework
- 32:55Process Maps
- 33:20Events Storming
- 33:39Triggers
- 35:53Results
related talks
45mHypothesis → Experiment → Verify → Learn... Learning and Practicing Mobius Outcome Delivery to Move Product Development Forward
51mMaximim Impact, Minimum Effort
42mOutcome Not Output
43mMeasuring Developer Productivity: The Good, the Bad and the Data
09m“Deliver & Measure Automation ROI”
44mCreating flow at Waters out of thin air
12mGamify the Metrics, Amplify the Impact
33mBeyond developer productivity: what's next?