When devs intend to leave a project and no one knows about it
summary
An NPS survey shows Net Promoter score -12.5 and one-on-one interviews reveal half the core devs planning to quit within weeks; five days of company-wide data collection and root-cause analysis surface broken change management, missing product vision, no ready backlog and missing test servers. Actions include one-on-one interviews, buying prioritized tools, market salary adjustments and created a Kanban pipeline with a clear Definition of Done. Outcome: nobody leaves and improvements start, though momentum later slows and sustainment remains uncertain.
AI-written summary · about
chapters (13)
- 0:00Intro
- 0:19Context
- 0:44Audit
- 2:12Exodus
- 3:06Management
- 3:45Sense of urgency
- 4:28Problems
- 4:38No real improvements
- 6:27Product Ownership
- 8:02I have no tools !
- 9:31Team
- 10:23All hands meeting
- 11:06Epilog
related talks
47mDeveloper first – a new Leadership Mindset
49mWhy Developers Quit
32mDeveloper productivity 2.0
30mDeveloper First – A New Leadership Mindset
25mSurviving DevOps
37mHow to Lose an iOS Developer in 10 days
31mMinimize Your Circus Factor: Building resilient teams
58mDeveloper Joy – How Great Teams Get S%*t Done