On the importance of leaving
summary
Leaving core roles in large projects requires planning not drama: announce intent months ahead, give about six months to transfer work, use an all-at email address for confidential team-wide notices, and set clear standards for how leaders exit. Concrete gains from stepping down include resolved conflicts of interest, space for new contributors, and better personal well‑being; a realistic view shows individual impact often near 1/300th. Train leaders for exit conversations and recognize emotional labor so departures stay constructive.
AI-written summary · about
chapters (21)
- 0:00Intro
- 2:08Florians background
- 2:38Helping others leave
- 3:26Positive experience
- 3:48Project members leaving
- 4:19Why people push out the discussion
- 4:53Shame
- 5:29Friends
- 6:13skewed selfimage
- 9:06structural issues
- 10:04external ghosts
- 10:46good contributors
- 11:43normalizing discussion
- 15:20having a plan
- 16:22retrospective
- 16:53why did you leave
- 18:04criticism of your communication
- 18:56examples
- 19:35what did you leave
- 21:06how to leave boring
- 21:47questions
related talks
28mThe Graceful Exit: Approaches for Changing One's Role in an Open Community
27mExit plans and how to talk about them
25mKnowing When To Walk Away
31mPassing the Baton: Succession planning for your project
29mThe Fine Art of Letting Go (Just Enough)
13mTeam Empowerment: When it is time for you Lead Dev to let go of responsibilities?
45mHow to Create a Sustainable Community
16mFrom Leading to Lagging How to Stay Relevant?