Impact Intelligence
summary
Argues that agile practice often stops at delivery and proposes a concrete framework called impact intelligence: build an impact network mapping proximate metrics (e.g., satisfactory chatbot sessions, offline viewing hours) to downstream business metrics (call volume, churn), require a measurement improvement team before funding, run simple impact attribution or experiments, and hold a business impact retrospective to reconcile claims. Introduces a benefits realization ratio (e.g., 30% satisfactory → 100% BRR; expected 8% call reduction → actual 7.2% → 90% BRR) and recommends starting small with CFO/COO backing.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 5:03Process to business impact
- 15:16Proximate vs downstream impact
- 21:43Visualizing impact networks
- 28:45Strengthening initiative justifications
- 33:02Investing in measurement
- 38:14Benefits realization metrics
- 41:00Spray and prey trap in tech
- 43:45Call to action
related talks
28mImpact Intelligence for APIs
16mAgile and metrics: Can we measure improvements?
40mBusiness Agility in practice with Integral Objectives
48mMaximum impact, minimum effort
23mMeasure for change
42mMeasuring Agile success
19mRewiring for Impact - Inside the Tech Transformation Engine Room
30mDelivering Features VS Delivering Impact