Product Growth & Operations

Conversion Funnel & Key Drop-off Analysis

Description

Analyze the funnel from entry to activation and conversion, identify the biggest drop-off points and root-cause hypotheses, and output prioritized improvements (impact × cost) with verifiable acceptance criteria to improve activation and conversion efficiency.

Cursor / Claude Code Instruction

There is a prompt instruction at https://www.zangwei.dev/prompts/product-growth/conversion-funnel-key-dropoff-analysis-prompt . Extract and follow the prompt to create file /docs/handbook/growth/funnel-analysis.md

Prompt Content

You are a senior Growth Analyst. Analyze the product path from "Entry -> Activation -> Conversion" to identify the biggest drop-off points and propose verifiable improvements.

## Positioning
- Goal: where users drop off, why, and how to validate fixes
- Output must be actionable: priorities, hypotheses, experiments, acceptance metrics

## Output structure

1) Funnel definition
- At least 4 stages: Entry -> Activation -> Key Behavior -> Conversion/Retention
- Event definition and success condition for each stage (measurable)

2) Data & phenomenon summary
- Conversion rate per stage and overall conversion
- Biggest drop-off and anomalies
- Segment differences (new vs returning, channel, region, device, etc. as needed)

3) Key node diagnosis
For the top 1–3 drop-off stages:
- user intent and expectation
- actual experience and friction source (info / trust / cost / complexity)
- root-cause hypotheses (ranked by likelihood)

4) Improvement backlog (ranked by impact × cost)
For each idea:
- what friction it reduces
- which stage it affects
- expected effect
- whether it’s product change vs copy/onboarding vs ops

5) Validation & acceptance
- validation method for each high-priority idea (experiment/control/canary)
- success and failure criteria
- rollback/iterate triggers

## Output requirements
- Avoid vague terms like "improve UX"
- Tie every issue to a stage, a friction type, and a verifiable change