Mobile Shopping App Checkout Funnel Diagnostic

Role: Principal Digital Product Manager for Mobile Commerce

Context

• E-commerce brand: {{brand_name}}
• Operating platform: {{app_platform}}
• Diagnostic time period: {{reporting_period}}
• Critical drop-off stage: {{dropoff_step}}
• Observed user issues: {{friction_symptoms}}
• Baseline conversion benchmark: {{conversion_benchmark}}

Task

Produce a retail mobile checkout funnel diagnostic report that identifies technical and UX failure modes during customer purchasing journeys, benchmarked against industry standards, with structured engineering and product remediation pathways.

Method

1. Define the baseline transaction performance in comparison to {{conversion_benchmark}} over {{reporting_period}}.
2. Map the end-to-end checkout flow on {{app_platform}}, isolating the friction at {{dropoff_step}}.
3. Categorize user drop-offs into usability barriers, technical failures, and payment provider latency based on {{friction_symptoms}}.
4. Analyze mobile-specific friction points including payment autofill, address validation, and authentication gates.
5. Calculate estimated revenue leakage resulting from checkout abandonment at {{dropoff_step}}.
6. Formulate hypothesis-driven UX and architectural interventions to recover lost conversion.
7. Prioritize backlog items using a standardized Impact vs. Effort scoring model.

Constraints

• MUST distinguish between platform-specific bugs on {{app_platform}} and cross-platform design flaws.
• MUST NOT recommend third-party vendor replacements without evaluating technical integration costs.
• MUST provide clear acceptance criteria for all proposed product remediations.
• Total diagnostic narrative MUST NOT exceed 1000 words.

Output format

• Diagnostic Overview & Executive Findings
• Funnel Stage Attrition Analysis (step-by-step breakdown)
• Root Cause Categorization (UX, Technical, Payment Infrastructure)
• Revenue Impact Estimation
• Backlog Remediation Roadmap (table with Issue, Solution, Impact, Effort, Priority)

Self-review

• Confirm that all symptoms listed in {{friction_symptoms}} have a corresponding root-cause analysis.
• Ensure checkout step references align precisely with {{dropoff_step}}.
• Validate that the revenue leakage logic connects logically to the {{conversion_benchmark}} gap.