Failure in change management
summary
Lists four common failure modes: assume you know everything (implemented Scrum in two months with Jira cards moving but no behavioral change), fear of failure or success (stalling until deadline panic), poor coalition building (no early supporters), and scope creep (no defined scope or timing). Recommends starting with a minimum viable product, using retrospectives and surveys for feedback loops, timing changes around releases and vacations, and slowing the pace so experiments can be evaluated before wider rollout.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:05Change management pitfalls
- 6:03Failure assuming to know all
- 9:57Fear of failure and perfectionism
- 12:49Building early support
- 15:18Scope creep and goals
- 18:32Mistakes and trust in change
- 21:45Craig Ramsey success story
- 25:18Q&A on agile and PM
- 28:20Overcoming team resistance
- 31:13Leadership support for change
- 34:47Final thoughts and Q&A
related talks
28mChange Management for Humans
27mChange Management for Humans
51mCommon pitfalls in engineering teams and how to avoid them
40mInsights From Happy Change Agents.
43mMind the gap – incorporating the change agenda into scaled Agile.
27mChange Management for Humans
18mManaging Change
25mChange Management For Humans
