← Back to guides
Product Manager Portfolio Examples: 5 Evidence-Led Formats

Product Manager Portfolio Examples: 5 Evidence-Led Formats

Five PM portfolio formats with example titles, artefacts and evidence checks. Show your contribution without invented results or confidential disclosures.

careerportfoliojob-searchinterview8 min read

Choose a portfolio example that matches the work you can actually demonstrate: a public-product teardown, a shipped B2B decision, a growth experiment, a leadership decision, or a compact project page. Make your contribution, evidence and limits visible before adding visual polish.

The five formats below are editorial examples to adapt, not profiles of real candidates or evidence of interviews and offers. Bracketed fields are prompts for your own records, not results to copy. For the broader writing process, use the product portfolio guide.

1. Career switcher: a public-product teardown

Use this when: you do not have a shipped PM project you can discuss. Analyse a public workflow and clearly label the work as an independent exercise.

Example title: Evaluating the first-use experience of [public product].

Build the case around a specific task, such as creating an account or finding a saved item:

  • Observation: show the public screens you inspected and the date. Separate what you saw from what you inferred.
  • Problem hypothesis: explain where a user might struggle. Without research, call it a hypothesis rather than a proven user need.
  • Alternatives: sketch different approaches and explain which assumption each would test.
  • Next test: describe how you would recruit relevant participants, what task you would set and what evidence would change your recommendation.

Useful artefact: an annotated journey with a small prototype. State that you did not work for the company, access its analytics or ship the proposal. Do not invent conversion improvements or customer interviews.

2. B2B PM: one decision with an evidence trail

Use this when: you can discuss a real project and have permission to share the material.

Example title: Choosing [workflow change] over [alternative] for [customer task].

Show the decision rather than a list of features:

  • Problem: identify the affected workflow and the evidence available at the time, such as approved support themes or research findings.
  • Your contribution: distinguish your analysis and decisions from design, engineering, sales and leadership contributions.
  • Tradeoff: explain the option you rejected, the constraint that mattered and the cost of your choice.
  • Outcome: report the measurement window and definition if you can publish a result. Otherwise say that the outcome is unavailable or confidential.

Useful artefact: an approved decision log or a newly drawn, non-confidential diagram. A reconstructed artefact should be labelled as a reconstruction, not passed off as the original document.

If prioritisation shaped the decision, expose the assumptions behind the score. Intercom's original RICE explanation defines reach, impact, confidence and effort, and explicitly allows dependencies or other constraints to override score order. A framework name alone does not explain your judgement.

3. Growth PM: an experiment, including an inconclusive one

Use this when: you can explain a genuine test and its limitations without disclosing protected data.

Example title: Testing whether [change] helps [audience] complete [task].

Keep the evidence chain readable:

  • Hypothesis: describe the expected behaviour change and why it seemed plausible.
  • Design: identify the control, treatment, eligibility rules, primary metric and guardrails that were actually used.
  • Execution: explain your role and any changes made during the test.
  • Readout: distinguish a measured result from a directional observation or an inconclusive test.
  • Decision: explain whether the team shipped, stopped or tested again, and why.

Useful artefact: an approved experiment brief paired with its readout. Do not manufacture sample sizes, significance claims or revenue impact to make the story feel complete. If you cannot disclose a result, focus on the decision process and state the limitation.

The GOV.UK Service Manual recommends combining performance metrics with user research and using multiple data sources rather than relying only on digital analytics. For a portfolio, that is a useful reason to explain both the behavioural measure and what qualitative evidence added.

4. Product leader: scope, decision rights and consequences

Use this when: the work you need to demonstrate concerns strategy, team coordination or resource allocation rather than one feature.

Example title: Reallocating product effort from [initiative] to [priority].

Make the leadership work concrete:

  • Scope: describe the product area, responsibilities and constraints you are allowed to disclose.
  • Decision rights: say what you decided, what you recommended and who held final approval.
  • Options: explain the alternatives and whose work would be affected.
  • Operating change: show how priorities, ownership or review cadence changed.
  • Consequences: distinguish observed outcomes from intended benefits and unresolved risks.

Useful artefact: a permission-cleared strategy excerpt or an original diagram explaining the decision. Do not publish internal org charts or attributed colleague quotes without permission.

Compare your chosen evidence with the scope in product leadership opportunities. Use actual role descriptions to calibrate the story, not the assumption that every Head of Product role has the same authority.

5. Minimal portfolio: a single readable project page

Use this when: you already have evidence but do not need a custom portfolio website.

Example layout: a short introduction, selected case studies and a clear next step. This is a recommended layout, not a claim about a particular candidate's hiring success.

For each project, make these answers easy to find:

  1. What problem was being addressed?
  2. What did you personally contribute?
  3. Which alternative did you reject, and why?
  4. What happened, and how do you know?
  5. What can the reader inspect or ask you about?

Useful artefact: one relevant, approved example beside the explanation. A decision log may be more useful than a wall of screenshots. Check the published page on mobile, test its links while signed out and remove any private document access requests.

Keep the portfolio focused on the roles you want. Compare current product opportunities with your project evidence, then create a builder profile so companies can request an introduction when there is a fit.

Confidential work: anonymisation is not permission

Do not assume that removing a company name, rounding a metric or putting a document behind a password authorises disclosure. The UK Intellectual Property Office describes an NDA as a legal contract whose scope can include information shared in presentations as well as recorded documents; see its confidentiality guidance.

Before using employer or client work, check the applicable agreement and obtain permission for the specific material and audience. If permission is unclear, withhold it and ask the appropriate owner or a qualified adviser. This is practical portfolio guidance, not legal advice.

An alternative is a clearly labelled independent exercise using public information and your own analysis. Do not quietly substitute invented numbers into a real-company case study or present a recreated example as shipped work.

A final evidence check

Before sharing, check that every result is traceable to a record you are allowed to use, each estimate is labelled, and team outcomes are not described as your sole achievement. Remove unsupported hiring guarantees, unverifiable testimonials and claims of customer research you did not conduct.

For hiring teams, use these formats as discussion prompts rather than a credential badge: ask about the underlying evidence, alternatives and the candidate's actual role. Browse builder profiles or use the company hiring path to explore fit; the existence of a portfolio does not independently verify its claims.

Get the weekly digest of top product people & jobs

One email a week. No spam.

Ready to get discovered?

Create your profile so companies can request an intro when there is a fit.

Create Your Profile