Books / Learning comic
The Product's Last Day
Theme: Business & Management
Asha has ninety days to retire Rill, a booking service used by forty community organizations. The engineering plan looks straightforward until Ruth, a hall coordinator, tries the export and discovers that a list of rows cannot run her hall. Recurring meetings lose their meaning, a time shifts, and an important cancellation nearly disappears. With support specialist Luis and engineer Ben, Asha must build a transition that customers can actually use without promising help forever. The story follows tested handovers, honest notices, reluctant customers, a paused cutover and the small responsibilities that remain after the servers close. For product managers, support teams and founders, this fictional workplace comic turns an abstract sunset plan into concrete choices about care, evidence, ownership and limits.
Start reading →View in the interactive libraryAbout this book
Rill is a small service that books rooms for community organizations. Its team can no longer maintain it alongside the company’s other work. Product manager Asha begins with a proposed ninety-day shutdown and a simple technical plan. Support specialist Luis sees a different problem: customers have future rehearsals, agreements and volunteer routines that depend on a service its makers are preparing to leave. The first chapter turns retirement into an accountable transition rather than a calendar event. Forty organizations need individual outcomes. Quiet accounts cannot simply be called inactive, and an unlimited promise to help with anything would exceed a three-person team’s capacity. After checking relevant obligations, Asha commits to honest notices, scheduled assistance and explicit go-or-pause criteria. The date matters, but it is no substitute for a workable plan. Ruth, a community hall coordinator, reveals what the initial export misses. Rows contain bookings but do not reliably preserve the distinction between a repeating series and one changed occurrence. A reminder is not proof of payment. Historical booking ownership is not permission to create a current account. Walking through the hall exposes physical handovers, separate records and everyday decisions that an export checklist alone would miss. Engineer Ben develops representative tests with invented information. A rehearsal finds duplicate bookings, an hour shifted by time interpretation and an attachment that does not transfer. The team learns to combine counts with content checks and real tasks. A successful pilot is evidence about that pilot, not permission to declare every customer ready. Different workflows need their own attention. Outreach brings further constraints. A delivered email is not proof that the recipient understood the plan, and a new contact must be authorized before receiving information. Ruth cannot afford the first suggested replacement. A theatre coordinator is overloaded rather than indifferent. The team adapts specific steps while keeping the assistance bounded. One archive transfer receives a controlled, reviewed read-only exception rather than an unspoken promise that the full service will continue. At the final rehearsal, a booking made after an earlier export exposes the need for a change window and a clear authoritative record. When another discrepancy appears, Asha follows the agreed pause rule. Investigation finds a cancellation whose exported state was wrong. The team fixes the cause, repeats the checks and verifies the final handover instead of allowing the scheduled hour to decide what is safe. The ending accounts for all forty organizations while keeping the remaining exception visible. Billing, signup links, public help pages, archive access and retention responsibilities receive their own checks. Ruth’s volunteer can complete a booking independently, although Ruth still dislikes losing Rill. The story does not mistake customer inconvenience for a problem solved by cheerful language. For product managers, support teams and founders, the book offers concrete ways to think about service retirement: define outcomes, map dependencies, test meaning, communicate limits, preserve authorization, reconcile changes and leave accountable follow-up. All organizations, figures and policies are fictional illustrations. The narrative does not prescribe legal notice periods or universal retention rules.