Honest Subscription Cancellation
Design a cancellation journey that explains service, data, billing, and team consequences without obstructing a customer's choice.
The brief
Understand the problem
Background
A project documentation service offers monthly and annual plans. Customers may lose editing access, storage, integrations, or promotional pricing when they cancel, but those consequences should inform rather than frighten.
User context
Ravi owns a three-person workspace that no longer needs the service. He wants to stop renewal, export important projects, and know whether collaborators will retain read access.
Product problem
Ravi needs a direct exit with precise consequences, while the product should provide reasonable recovery options without manipulative friction.
Objective
Create plan review, consequence explanation, export choice, and cancellation confirmation for a team subscription.
What to design
Define the experience
Required experience
- Open subscription controls and see the renewal terms
- Review dated consequences for billing, members, and data
- Choose whether to export or transfer ownership
- Confirm cancellation and understand reactivation
Screens and states
- Subscription overview
- Cancellation consequence review
- Data and ownership choices
- Cancellation receipt
Core user flow
Follow the critical path
- 01
Ravi opens billing and chooses to cancel renewal
- 02
The service explains that editing ends on 30 September while read access lasts another month
- 03
He starts a workspace export and keeps cancellation available
- 04
Ravi confirms, receives a receipt, and sees the remaining access period
Product rules
Requirements and constraints
Requirements
- Keep the cancellation action findable from billing
- Use exact dates, amounts, and affected capabilities
- Make retention offers optional and easy to dismiss
- Allow export without forcing the user to delay cancellation
- Provide a receipt and reversible reactivation window when policy permits
Constraints
- Annual charges already paid may be nonrefundable under the stated terms
- Only a billing owner can cancel a team plan
- Export preparation may finish after cancellation is confirmed
Reality check
States worth considering
Finish line
What to deliver
- Four responsive screens with an honest primary cancellation path
- A consequence table covering billing, access, data, integrations, and reactivation
If you want more
Optional extensions
Optional direction
Visual resources
Use these as a starting constraint if you want one. They are not part of the required solution.
Theory to review
UX principles for this brief
Use these as decision lenses, then validate the design with the people and context in the brief.
effectEndowment EffectOwnership or a sense of possession can increase the value assigned to an item relative to the value assigned before ownership.
effectRecency EffectRecently presented items often receive a recall advantage when they remain accessible at the time of test.
biasStatus Quo BiasPeople may prefer an existing state or previously chosen option beyond what its attributes alone would predict.