Painful outcomes - 7 mistakes I made in the shift to value led development
summary
Seven concrete mistakes and pragmatic fixes for shifting to outcome‑led work: using discovery used as weapon to disprove executives (instead, buy time or build a low‑value MVP and minimize work done), letting product teams become perceived blockers (reframe communication around delivery), neglecting the stakeholder bank balance, and introducing change too fast. Shows a wins‑first approach: funnel and scroll analysis, prioritized hypotheses, then A/B tests that deliver an 11% conversion lift; the shift happens over ~2–2.5 years by starting at the end, assumption mapping, empathy mapping and incremental experiments.
AI-written summary · about
chapters (9)
- 0:00Value-led development intro
- 1:46Seven mistakes in change leadership
- 6:02Mistake 1: Discovery to disprove ideas
- 13:28Building trust incrementally
- 18:45Stakeholder relationships as bank balance
- 24:02Introducing change incrementally
- 31:33Avoiding blocker trap in delivery
- 35:05Self-care during change
- 40:24Q&A on research vs stakeholders
related talks
29mFrom Agile to Outcome-Driven
36mAgile Déjà Vu – Why Do We Keep Failing at Transformations?
28mOrganizing for Outcomes
15mDelivering value agility in a large company
01h 01mHow Agile Screwed Up Product Ownership and 5 Things You Can Do to Fix It
49mMaking Value Visible
43mChange Your Focus
45mLearning from Mistakes