Standardized reason codes for platform exits
EXIT uses a controlled taxonomy to classify exit reasons. This ensures data consistency, enables aggregation, and makes migration patterns analyzable for researchers and businesses.
Each exit must select one primary reason from the taxonomy. Users can also add custom detail to provide context.
The taxonomy is designed to be comprehensive yet concise, covering the most common patterns observed in software abandonment.
The platform became a source of interruption or attention drain, interfering with focus or productivity.
Examples: Constant notifications, infinite scroll, addictive features
Pricing was unsustainable, increased unexpectedly, or better value was found elsewhere.
Examples: Subscription price increase, found free alternative, budget cuts
The interface or workflow was overly complicated, making the tool harder to use than necessary.
Examples: Too many menus, unclear navigation, steep learning curve
The platform suffered from crashes, bugs, downtime, or declining output quality.
Examples: Frequent crashes, slow loading times, buggy features
A superior tool was discovered that better met the user's needs or preferences.
Examples: Switched to Notion from Evernote, moved to Linear from Jira
The user's circumstances changed, making the platform irrelevant or unnecessary.
Examples: Changed jobs, finished project, simplified lifestyle
Data practices, surveillance, or lack of control over personal information drove the exit.
Examples: Data breach, invasive tracking, changed Terms of Service
Excessive alerts, emails, or push notifications became overwhelming or annoying.
Examples: Email overload, badge fatigue, alert spam
The platform was sluggish, laggy, or unresponsive, impacting usability.
Examples: App freezes, long load times, laggy interface
A reason not covered by the standard taxonomy. Use the detail field to specify.
Examples: Vendor shut down service, regional unavailability, ethical concerns
The current taxonomy focuses on the most common reasons. Additional categories from the EXIT methodology include:
Cost
Too expensive, found free alternative, pricing change
UX/Workflow
Too complex, slow performance, confusing interface, too many notifications
Performance/Reliability
Crashes, downtime, poor quality, slow performance
Feature Gap
Missing features, found better alternative
Ecosystem Fit
Poor integrations, incompatible file formats, platform lock-in
Policy/Trust
Privacy concerns, Terms of Service changes, data practices
Vendor Friction
Billing issues, poor support, difficult cancellation
Social/Team
Organization mandate, team migrated, network effects
Personal Change
No longer needed, role change, lifestyle shift, too distracting
When recording an exit, choose the primary reason that best describes why you left. If multiple reasons apply, select the most significant one.
Use the “Other (specify)” option for edge cases not covered by the taxonomy. Over time, frequently-used custom reasons may be promoted to standard codes.
Be specific in your optional detail. Instead of “bad UX,” write “too many clicks to complete basic tasks.” This improves the usefulness of the data for everyone.
This taxonomy evolves with user feedback. If you notice gaps or have suggestions, contact the EXIT team.