1
Product event
Track key product events with a simple JavaScript snippet.
Research triggers · Customer feedback moments
Understand Why Users Stop Using a Feature
Talk to users when they stop using an important feature. Learn what they expected it to do and why it didn’t stick.
2 to 5 minute interviewsWorks from events you already trackEvery interview is a real person
“I tried the feature once, but it didn’t really help with the task I needed to complete.”
What people say at this moment
Why it happens
Common Reasons Users Stop Using a Feature
Features lose adoption when they don’t fit naturally into a user’s workflow. Understanding the reasons behind declining usage helps teams improve feature design and value.
Common reasons include:
• the feature doesn’t solve the user’s actual problem
• the workflow is confusing or difficult to use
• the feature requires too much setup or configuration
• users expected different functionality
• the feature’s value isn’t clear or visible
Understanding these issues helps teams improve feature adoption.
The gap
Analytics Show Feature Usage, But Not Why It Drops
Product analytics can show how often a feature is used.
Teams can track:
• feature adoption rates
• usage frequency
• engagement trends
But analytics cannot explain why users stop using a feature.
Did the feature not solve the user’s problem?
Did it feel confusing or difficult to use?
Did users expect it to work differently?
Without understanding the reason behind the behavior, teams often struggle to improve feature adoption.
Timing
The Best Time to Learn Why Feature Usage Drops
The most useful feedback comes when users stop using a feature they previously tried.
At that moment, users still remember:
• what they expected the feature to do
• what they were trying to accomplish
• what felt confusing or frustrating
Capturing feedback right after usage drops helps teams understand the experience that led users to abandon the feature.
Instead of guessing why adoption declined, teams can hear directly from users about what didn’t work.
Key moments
Key Moments When Feature Adoption Fails
Feature adoption problems often appear in specific moments of the product journey.
Common moments include:
First feature attempt
Users try a feature once but never return to it.
Declining usage
Users initially use a feature but gradually stop.
Incomplete workflows
Users begin using a feature but abandon the process before completion.
Feature confusion
Users explore the feature but don’t understand how it helps them.
Each of these moments reveals valuable insight into why the feature didn’t become part of the user’s workflow.
How to capture it
Capture Feedback When Feature Usage Stops
Instead of relying only on product analytics, teams can capture feedback when feature usage drops.
For example:
User tries a feature
→ Usage declines or stops
→ Invite quick conversation
→ Ask what they expected the feature to do
Because the experience is still recent, users can clearly explain:
• what they hoped the feature would accomplish
• what felt confusing
• why they stopped using it
These insights help teams improve feature design and adoption.
What teams learn
What Teams Discover About Feature Adoption
When teams capture feedback from users who stop using a feature, several patterns often appear.
• users misunderstood what the feature was designed to do
• the feature did not solve the user’s actual problem
• the workflow was too complex or time-consuming
• the feature required too much setup or configuration
• users did not see enough value to continue using it
Understanding these patterns helps teams redesign features and improve adoption.
Questions to ask
Questions to Ask When Users Stop Using a Feature
When users abandon a feature, simple questions can reveal what went wrong.
Examples include:
• What were you hoping this feature would help you do?
• What happened when you tried using it?
• Was anything confusing about how it worked?
• Did the feature solve the problem you expected?
• What would make this feature more useful?
These conversations help uncover the reasons features fail to stick.
How it works
Turn customer moments into insights. Capture feedback as the event happens.
These insights often become clear when teams talk to users at the moment these events occur, while the experience is still fresh.
2
Research trigger
Use events from tools like PostHog, Mixpanel, Amplitude or GA.
3
Quick voice conversation
The event invites the user to a short voice chat with an AI interviewer.
4
Themes and insights
Interviews are transcribed, analyzed and summarized into themes.
Frequent questions
Frequently asked questions.
Why do users stop using product features?
Users often stop using features when they do not solve the problem the user expected, when the workflow feels complicated, or when the value is not clear.
How can teams improve feature adoption?
Improving adoption usually requires simplifying the feature workflow, clarifying its value, and helping users understand how the feature solves their problem.
What metrics indicate feature adoption problems?
Metrics like declining usage, low repeat usage, or users abandoning feature workflows can indicate adoption problems.
How can companies collect feedback about feature adoption?
Products can trigger feedback invitations when feature usage drops or when users abandon a feature workflow. These conversations help teams understand why the feature is not being adopted.
More moments
Other moments worth asking about.
Any product event can start a conversation. The research triggers page lists all ten.
Fix Onboarding Drop-Off
Talk to users when they abandon onboarding or setup. Find out exactly where people get confused and why they stop.
Improve Activation Rates
Interview new users who sign up but never get started. Learn what blocked them from taking the first meaningful step.
Turn Support Moments Into Insights
Talk to customers when they contact support. Understand the deeper product issues behind support requests.
Capture Feedback When Issues Happen
Talk to users when they hit an issue, error, or failed action. Understand what they were trying to do and where the experience breaks.
Understand Checkout or Purchase Abandonment
Talk to shoppers when they abandon checkout or a cart. Discover the friction that stops customers from completing a purchase.
Understand Why People Don’t Upgrade
Talk to users when a trial ends or a plan change happens. Learn what’s missing when customers decide not to upgrade.
Learn What Users Were Trying to Do
Talk to users after key actions like searches, failed tasks, or abandoned flows. Understand the job they were trying to accomplish.
Discover What New Users Expect
Interview users right after they sign up or create an account. Understand what they’re hoping to accomplish before they even start using your product.
Ask at the moment it happens. Hear why while it’s fresh.
Free to start. Your first trigger takes a few minutes to set up.