Designing Business Outcomes (#noprojects)
summary
Argues organizations must stop funding outputs and start funding measurable outcomes with a clear profile: metric, baseline, time‑bound target, budget, dependencies and owner. Shows examples: active subscribers defined as logged‑in users with 80% profile completion — target 100,000 in ~3 months with a $6M envelope; zero breaches for data centers as a hard target; spend $1M to save $5M as an investment decision. Uses five whys, biweekly outcome checks, outcome‑led DevOps and constraint principles (MoSCoW applied to rules) so teams pivot or stop when value isn’t delivered.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:00Project Management History
- 2:10No Projects
- 3:05Continuous Culture
- 3:54How much does it cost
- 7:07Whos a project
- 11:19Defining outcomes
- 12:34Examples
- 16:24Staff Satisfaction
- 24:23Measure
- 26:30Call it
- 27:23Debugger
- 28:03Comments
- 29:43Outcomes
- 30:43Benefits
- 41:13Advice
related talks
19mThe Why, How & What of an Outcome centric team
28mOrganizing for Outcomes
19mEncounters and Solutions While Facing Outcomes
29mFrom Agile to Outcome-Driven
44mOutcome-based Product Planning
20mMaking the Case for Change
10mFocus on project value using businesses strategy
44mCreating ValueFirst Product Organisations