Product analytics tools like PostHog make it easy to see how users interact with features.

You can track events such as:

• users starting a feature
• users opening a new workflow
• users interacting with product capabilities

But product teams often notice a common pattern:

Users start using a feature but never complete the intended action.

For example:

• users open a feature but never finish setup
• users begin a workflow but abandon it halfway
• users try a feature once and never return

Analytics clearly shows where usage stops.

But it rarely explains why users abandon the feature.

Most teams try to investigate this by:

• analyzing additional events
• watching session recordings
• reviewing support conversations
• guessing what went wrong

A better approach is to ask users directly when the abandonment happens.

This playbook shows how to use PostHog workflows and short user interviews to understand feature abandonment.

Best For

• Product managers
• Growth teams
• SaaS founders
• Product analytics teams

Setup time

• about 5–10 minutes

Problem

Product analytics often shows that users start interacting with a feature but never complete the intended workflow.

Example patterns:

• feature_started
• feature setup initiated
• feature_completed event never occurs

These signals reveal where adoption breaks down, but they don’t explain the user’s experience.

Without direct feedback, teams often speculate whether the problem is caused by:

• confusing UI
• unclear instructions
• missing functionality
• unexpected behavior

Short interviews triggered when users abandon a feature can quickly reveal the real issue.

Event Trigger

This workflow begins when a feature abandonment signal occurs.

Example event pattern:

feature_started
but
feature_completed does not occur

Other common triggers include:

• setup started but not finished
• workflow exited before final step
• feature used once but never again

When this pattern occurs, a PostHog workflow can send a short interview request.

Workflow Overview

The workflow looks like this:

• feature_started event occurs
• completion event never happens
• PostHog workflow sends a message
• user receives a short interview link
• user explains what happened
• responses are summarized automatically

This workflow helps product teams move from observing feature usage to understanding user friction.

Example Insight

Even a few feature feedback interviews can reveal clear patterns.

Teams commonly discover insights such as:

• users didn’t understand what the feature does
• the feature required too many setup steps
• the value of the feature was unclear
• key integrations were missing

These insights are difficult to identify through analytics dashboards alone.

A small number of conversations can quickly reveal the true cause of feature abandonment.

Interview Template

Keep feature feedback interviews short and focused.

Example questions:

• What were you trying to do when you started using this feature?
• What part of the experience felt confusing or difficult?
• What would have made this feature more useful?

These interviews usually take two to three minutes to complete.

Short conversations provide deeper insights than traditional feedback surveys.

Message Template

Your PostHog workflow can send a short message when feature abandonment occurs.

Example message:

Subject: Quick question about a feature you tried

• We noticed you started using this feature but didn’t finish.
• Could you share what made it difficult?
• It only takes about two minutes.

Include the interview link in the message.

Users can quickly explain what prevented them from completing the feature.

Why This Works Better Than Analytics Alone

Analytics tools are excellent at showing what users do.

But they rarely explain why users behave that way.

For example, analytics might show:

• many users start using a feature
• very few complete the workflow

Without user feedback, teams cannot know whether the issue is caused by:

• confusing interface design
• unclear product instructions
• missing capabilities
• unexpected product behavior

Short interviews provide the context that analytics cannot capture.

When to Use This Playbook

This workflow is especially useful when:

• a new feature is launched
• feature adoption is lower than expected
• users start but do not complete workflows
• product usage patterns change unexpectedly

Product teams can quickly investigate these signals by asking users directly what happened.

Try This Workflow

If you use PostHog, you can experiment with triggering short interviews when users abandon a feature.

Even a small number of conversations can reveal patterns behind feature friction.

Try this workflow

Create a short interview and add the interview link to your PostHog workflow.

Create interview →

Create Your Interview

Create a short feature feedback interview and add the interview link to your PostHog workflow.

Once responses arrive, you’ll begin seeing clear patterns behind feature abandonment.

Create interview

Related Playbooks

You can use the same workflow approach to investigate other product signals:

• Investigate onboarding drop-off using PostHog workflows
• Capture churn reasons using PostHog workflows

• How to Use PostHog Workflows to Understand User Behavior

Together, these playbooks help product teams move from tracking user behavior to understanding user motivation.

‍