Teardown
[Placeholder] Teardown: [App Name]'s onboarding flow
[One or two sentences on why you picked this product and what the core issue is.]
Overview
What this product does
[1–2 sentences: who it's for, what job it does, and where it sits competitively.]
Working well
What's working
- [Placeholder — a genuine strength. Being fair here builds credibility for the criticism that follows.]
- [Placeholder — another strength.]
Broken
What's broken
- [Issue 1] — [what happens, why it's a problem, who it affects.] High severity
- [Issue 2] — [what happens, why it's a problem, who it affects.] Medium severity
- [Issue 3] — [what happens, why it's a problem, who it affects.] Low severity
Prioritization
Where I'd focus first
Plotting the fixes above by impact and effort makes the prioritization explicit rather than a gut call.
Issue 1
Issue 2
Issue 3
[Placeholder — hover the dots above once you've replaced them with your own issues. Top-left quadrant (high impact, low effort) is where you'd argue for starting.]
Recommendation
What I'd ship first, and why
[1–2 paragraphs tying it together: which fix you'd prioritize, the expected effect, and how you'd measure whether it worked.]