A.'s Stories Don't End So Badly: Offboarding or the End of the...
summary
Offboarding is treated as a product-design problem constrained by law and legal requirements: companies must allow easy contract termination and document which steps are essential. Concrete solutions include offering a pause or a delete-with-data-export option, using a confirmation email as legally valid, showing clear timelines (e.g., preserving preferences for 10 months), avoiding dark patterns like multi-page traps, mapping all exit moments with service and legal teams, and building a single mobile-friendly flow tested with variations (one food-box case used instant pause/resume plus confirmation).
AI-written summary · about
chapters (7)
- 0:00Introduction
- 2:31Ending relationships
- 6:47Bad offboarding practices
- 12:31Good offboarding practices
- 19:31Happy ending examples
- 22:29User-centered offboarding
- 27:26Case study and conclusion
related talks
29mHow to… End: Designing and delivering great closure experiences for products and business
39mFiring People
57mEthical Design: Is it possible?
50mYou, Ex. Breaking up with bad design
18mSupporting employees through redundancies and business closures
28mThe Graceful Exit: Approaches for Changing One's Role in an Open Community
34mUser Onboarding for the Long Run
23mHitting Ctrl+N: How to work through a design breakup
