A launch screenshot tells me what shipped. It rarely tells me why that version shipped, what the team left out, or whether the result was worth the effort. Those are the parts I want to see in a product manager portfolio.
My own portfolio is deliberately playful: a 3D robot, career sections, and product-decision games. That is a choice about presentation. The underlying job is still to make my work and judgement easier to understand.
You do not need a 3D website to get started. You need a clear introduction, a small number of credible examples, and an easy way to contact you. Product School similarly distinguishes a portfolio from a CV and recommends treating the portfolio itself as a product. 1
What belongs in a product manager portfolio?
Think of your portfolio as two layers.
The first layer is a quick introduction: who you are, what kind of work you do, which projects matter, and how someone can reach you.
The second layer is evidence. For each selected project, explain:
- Problem: What was difficult for the user or business?
- Your responsibility: What did you own, and what did the team own?
- Constraints: What limited the decision - time, money, technology, compliance, or available evidence?
- Options: What could you have done instead?
- Decision: What did you choose, and why?
- Result: What changed, and how was it measured?
- Reflection: What would you keep or change next time?
This structure turns “worked on onboarding” into something a reader can evaluate. It also makes your contribution clearer without claiming the team's entire achievement as your own.
A case-study example without invented success metrics
Consider a fictional learning app. This is an illustrative case, not a claim about a product I shipped.
A learning app sees people abandon setup before their first lesson. The team can shorten the form, add a tutorial, or rebuild the recommendation flow. Engineering capacity is limited.
A useful case study would describe the evidence for the drop-off, explain why the team selected one change, and name the success measure before describing the result.
If the change has not launched, say so. Write “proposed experiment” rather than “improved activation.” If the experiment produced an uncertain result, explain the uncertainty rather than turning it into a victory.
The interesting part is not a polished final screen. It is the decision that connected the problem to the work.
What if your work is confidential?
Do not publish internal dashboards, customer names, unreleased plans, or private documents just to make a portfolio look convincing.
Instead, use material you have permission to share. You might describe the problem at a higher level, recreate a simplified diagram, or use a clearly labelled fictional example. Even anonymised numbers may need employer approval.
If you cannot share an outcome, explain the decision process and the limit on what you can disclose. A missing number is better than a made-up one.
Can a playable portfolio show product thinking?
Yes, but an interaction and a case study answer different questions.
My playable portfolio pairs a reactive 3D robot with career information and three product-decision games:
- The War Room explores competing stakeholder choices.
- Sprint Rush turns backlog choices into a capacity-limited challenge.
- Friday 5PM asks players to separate urgency from importance.
These interactions make the portfolio itself something visitors can explore. They do not prove that a particular business outcome happened, and a player's score is not a hiring assessment. My work history sits alongside the games, so you can read the professional background without playing.
Keep the reader's shortest path intact
A founder might enjoy exploring an interactive site. A hiring manager might want the relevant facts immediately. Both should be able to identify the person, find the work, and make contact without completing a game.
Before adding another animation or project, ask: does this make my judgement easier to understand?
If I were starting again with one afternoon to spare, I would write one decision clearly before choosing a website template. A modest page with a good explanation gives a reader something to discuss. A beautiful page that says only “strategy, execution, leadership” leaves them guessing.