Documenting your software’s last days
summary
Delineates concrete steps: count your users (daily actives, API tokens, billing clients), inventory every channel (email, transactional notices, blog, UI banners, support scripts), stop marketing outreach before announcing, map an escalation schedule backwards from the final deadline (strike weekends/holidays), announce exact milestones (last bill, API shutdown, data deletion), offer migration paths and clear exit instructions, and keep tone calm, direct, and factual while thanking affected users.
AI-written summary · about
chapters (8)
- 0:00Start
- 6:37Catch your breath
- 7:38Count your users
- 8:21ARE NOT
- 8:53Make a plan
- 16:37Let them down easy
- 18:20Our Incredible Journey
- 20:37Exit
related talks
30mWriting Backwards: Documenting the End-of-Life of a Product
24mHow to delete everything: The clean-slate approach to technical strategy
28mWe Launched the Site! Now What?
37mTaking a step back: Analysing your documentation
21mIntroducing The API Lifecycle
31mHow We Deprecated 500+ Articles: Cleaning Up Documentation at Scale
41mLong-term Documentation Maintenance
31mMinimize Your Circus Factor: Building resilient teams