funnel-drop-off-diagnosis
Funnel Drop-Off Diagnosis
Find out why users drop off at specific steps — then fix the right thing.
How to use
/funnel-drop-off-diagnosisApply funnel diagnosis constraints to this conversation./funnel-drop-off-diagnosis <funnel data>Diagnose a specific funnel with the provided conversion data.
Constraints
Funnel Definition
Before diagnosing, MUST ensure the funnel is:
- Sequential: each step logically follows the previous
- Measurable: exact user counts at each step
- Complete: no invisible steps between measured ones
- Time-bounded: define a reasonable window (same session? 7 days?)
Diagnostic Checklist
For the problem step, work through causes in this order:
- Technical issues: page loading? Broken elements? Cross-device/browser? Intermittent failures? Check here first — most common, easiest to fix.
- Clarity problems: does the user know what to do? Is the CTA obvious? Too many choices? Mismatch between promise and reality?
- Friction problems: too many inputs? Information user doesn't have ready? Unnecessary verification?
- Trust problems: asking for sensitive data without trust signals? Design inconsistency? No help available?
- Motivation problems: user doesn't see the value of completing this step? Effort exceeds perceived reward?
- Expectation mismatch: previous step set wrong expectations? Marketing promised something different?
- MUST work through in order. Don't jump to motivation problems before ruling out bugs.
Segment the Drop-Off
- MUST break down conversion by: acquisition channel, device type, geography, user segment, time
- If one segment converts dramatically differently, the fix is specific to that segment's context
- NEVER diagnose a funnel problem without checking segments first
Impact Estimation
For each diagnosis, estimate:
- Confidence: how sure is this the cause? (High/Medium/Low)
- Impact: if fixed, how much would conversion improve?
- Effort: how hard is this to fix?
- MUST prioritize: high confidence + high impact + low effort first
The Funnel Paradox
- Optimizing one step can hurt a later step
- Making signup easier may bring less-qualified users who churn faster
- MUST measure downstream impact, not just the step being fixed
Anti-Patterns
- Guessing causes without checking data or segments
- Fixing the page where drop-off happens when the problem started earlier
- Optimizing a step that already works well while ignoring the real bottleneck
- A/B testing without a diagnosis — you're guessing with more steps
More from dragoon0x/product-skills
prd-writing
Write product requirement documents that engineers want to read and can actually build from. Covers structure, scope discipline, and the balance between clarity and over-specification. Use when writing PRDs, reviewing spec quality, or when engineering keeps asking clarifying questions.
1freemium-vs-paid-gate
Decide whether a product should offer a free tier, free trial, or go straight to paid. Structured decision framework based on economics, distribution model, and competitive landscape. Use when launching a new product or reconsidering your pricing model.
1error-recovery
When things break, guide people forward instead of leaving them stranded. Error message copy, retry patterns, graceful degradation, and recovery flows. Use when building error handling or failed state UIs.
1cta-patterns
Design calls-to-action that people actually click. Covers button copy, placement logic, urgency without manipulation, and progressive commitment. Use when reviewing pages for conversion potential or when CTA copy feels generic.
1onboarding-flow
Design first-run experiences that create the aha moment fast. Reduces time-to-value by sequencing actions, progressive disclosure, and contextual guidance. Use when building signup flows, product tours, or empty states.
1user-psychology
Apply motivation, friction, and trust patterns to product decisions. Maps cognitive biases and behavioral triggers to specific UI and copy choices. Use when reviewing flows for drop-off points or when something feels right but doesn't convert.
1