SkilsMVP

PM portfolio guide

How to do a product teardown

A product teardown is a structured analysis of an existing product — what problems it solves, how it solves them, what it does well, and what you would improve. It is one of the best ways to show PM thinking before you have a PM job.

Why do a teardown for your portfolio?

A teardown proves you can think like a PM without needing a PM title first. Hiring managers are not looking for insider information — they are looking for how you think. Here is what a strong teardown signals.

Product sense—Can you identify what a product is actually trying to do — and whether it is succeeding?
Structured thinking—Do you analyze problems in a logical sequence, or do you jump to solutions before understanding the problem?
User empathy—Do you describe users as real people with real goals, or as abstract demographic buckets?
Prioritization—Can you pick one improvement and defend it — rather than listing every possible thing that could be better?

The 7-step teardown framework

Follow these steps in order. Each one builds on the previous — jumping ahead to improvements before understanding the user is the most common mistake.

  1. 1

    Choose a product you use and genuinely understand

    Start with something you interact with regularly. Familiarity gives you real observations, not guesses. The goal is depth, not novelty — a teardown of Gmail done well beats a teardown of an obscure startup done poorly.

  2. 2

    Define the target user (1–2 personas)

    Give each persona a name, a context, and a goal. Keep it tight — one or two personas force you to make real trade-off decisions instead of trying to serve everyone. Vague personas produce vague analysis.

  3. 3

    Identify the core job-to-be-done

    Use this structure: 'When I [situation], I want to [action] so I can [outcome].' The job-to-be-done is not a feature — it is the underlying progress the user is trying to make. Getting this right is what separates product thinking from feature listing.

  4. 4

    Map the key user flows

    Walk through three flows: how new users get started (onboarding), what the product has users do repeatedly (core loop), and how it brings users back (retention loop). You do not need a design tool — a numbered list of steps is enough.

  5. 5

    Identify 3 things the product does well — and why

    Do not just say 'the design is clean.' Explain the mechanism. 'The onboarding flow works because it shows value before asking for any personal information' is a PM observation. 'It looks nice' is not.

  6. 6

    Identify 2–3 friction points or gaps

    Where does the product fail its own users? Look for dropped flows, missing features, confusing UX, or jobs the product promises to do but handles poorly. Tie each friction point back to a real user impact.

  7. 7

    Propose 1 concrete improvement

    State the problem clearly, describe the solution, and define a success metric. One improvement done rigorously beats five done vaguely. This is where hiring managers see whether you can close — from observation to decision.

Example teardown structure: Notion

Here is what a completed teardown looks like using the framework above. This is the level of specificity to aim for — not vague observations, but grounded claims with real examples.

User

Knowledge workers who want to capture, organize, and share information without switching between multiple tools.

Job-to-be-done

When I need to document a decision or project, I want to write and organize information flexibly so I can share it with my team without losing context.

Key flows

Template gallery → new page creation → share link. The template gallery reduces blank-page anxiety; sharing is a single click.

What works

Flexibility of the block-based editor — users can mix text, databases, embeds, and code in a single page. Aesthetic — the sparse design makes users feel smart for using it. Collaborative linking — internal links make it feel like a company wiki, not just a note-taking app.

What does not work

Search is weak — keyword-only with no semantic matching, so you must remember exact wording to find old notes. No offline sync — one brief internet drop and the page is uneditable. Mobile experience is slow — block-based editing translates poorly to touch.

Proposed improvement

Smarter search with semantic matching. Problem: users cannot reliably retrieve information they know exists. Solution: add vector-based search that matches concepts, not just keywords. Success metric: search-to-click rate improves 20% within 60 days of rollout.

Format for your portfolio

Pick one format and do it well. Include screenshots, user flow diagrams, and clear headings regardless of which format you choose.

Notion page

3–5 pages

Best for text-heavy analysis. Organize with headings, callout blocks, and a summary table. Easy to share via link.

Google Slides

8–10 slides

Best for visual storytelling. Include screenshots, annotated user flows, and one recommendation per slide. Feels polished in interviews.

LinkedIn article

800–1,200 words

Best for visibility. Recruiting teams find you; the format proves you can communicate complex ideas in plain language.

Next steps

Apply this framework in the PM track

Product teardowns are one skill in a full PM toolkit. The product manager track covers user research, prioritization, roadmapping, stakeholder communication, and more — with practice projects you can add to your portfolio.

Explore the PM track