PM Portfolio Thinking
Version 4 · Last Updated 2026 Jun 29
It has been updated as my thinking changed. See the Changelog at the bottom for what shifted and when.
Core Idea
A platform for product managers to build and present their portfolio — structured around the thought process and evidence that hiring managers and HR actually look for during interviews, not just a resume or LinkedIn profile.
The platform works as you go, not retrospectively. The portfolio is a byproduct of honest, ongoing documentation — not a reconstruction after the fact.
State of Thinking
Most PM portfolios fail because they are built from the PM’s perspective, not the interviewer’s. The platform addresses this by imposing a structured format that forces PMs to document their work in the way interviewers want to see it.
The positioning:
- Not a LinkedIn replacement — LinkedIn is too big and too general, this does not compete with it
- Closer to PMI’s project experience format — structured fields, standardised presentation, a loose but consistent format that scales across different PM backgrounds
- The target user is new or aspiring PMs who do not yet know how to present their work in a way that lands in interviews
The core insight: A PM portfolio is not about listing what you did. It is about demonstrating the thinking behind what you did — the problem framing, the trade-offs, the decisions, the outcomes. The format should make this structure unavoidable, not optional.
What the format should capture:
- The problem or opportunity
- The approach and key decisions made
- Trade-offs considered
- Outcomes and evidence
- Reflection — what would you do differently
This mirrors what a strong PM interview answer looks like, so the portfolio becomes interview preparation as much as a showcase.
PKM-first, portfolio-second (new):
Researching PM portfolio best practices (external sources, synthesized via NotebookLM) surfaced a clear tension: traditional portfolio advice assumes the primary function is presentational — curated, audience-facing, polished. But within an Evergreen PKM system, the primary function is different — atomic, honest, evolving thinking that you own over time.
These two functions are not fully compatible. A curated portfolio prioritises what looks good to an interviewer. An Evergreen node prioritises what is true about how you think. Where they conflict, the PKM function wins. The portfolio output should emerge from the PKM, not impose structure onto it.
This means: nodes about PM work should be built for honest ongoing thinking first. If they become useful portfolio material later, that is a byproduct — not the goal.
Dual-mode design (new):
The platform needs to support two modes simultaneously:
- Portfolio mode — structured, interviewer-facing, curated presentation of work
- Working mode — ongoing documentation of thinking as it happens, not filled in retrospectively
Retrospective filling is a failure mode, not just a limitation. When PMs reconstruct their thinking after the fact, the content becomes less honest, less specific, and less useful — both to interviewers and to the PM themselves.
The insight from building a public thinking space (Quartz site): using the platform as you go means the portfolio becomes a natural output of how you work, not a separate task. A PM who documents thinking in real time shows something a polished retrospective portfolio cannot — how they actually think under uncertainty.
Thinking Trace
- Researched PM portfolio dos and don’ts from online sources, organised via NotebookLM — the conventional advice (curate 3–5 projects, lead with outcomes, show the “how” and “why”, protect confidentiality) is sound for traditional portfolios but assumes curation-first. That’s not how this system works.
- The research made the tension explicit: portfolio advice optimises for the interviewer’s lens; an Evergreen node optimises for honest evolving thinking. Recognising the conflict made it easier to decide the hierarchy — PKM function is primary, portfolio output is downstream.
- LinkedIn exists and is not going away — the goal is not to replace it but to fill a gap it does not address
- PMI’s format came to mind as a reference — it forces structured documentation of project experience in a way that is comparable across candidates
- The key insight is that the portfolio should be built with the HR or hiring manager’s lens, not the PM’s — most PMs do not know what interviewers are actually looking for
- New and aspiring PMs are the clearest target — they are the ones most lost on how to present their work
- Still very early — the format and feature set are not defined yet
- Building a personal public Quartz site (both portfolio and thinking space) surfaced the tension directly: the pull between curating for an audience and thinking honestly as you go. The platform needs to hold both without forcing a choice.
What changed?
v4
The dormakaba portfolio extraction process is complete. The garden now contains validated, sanitised, public-safe case study material across six cases. Two flagship PM Case Study nodes (API Product Arc, Analytics Architecture Correction) have been created. Insights - Case Study.md updated to v2. A concrete publishing plan now exists as a separate Plans node.
v3
The purpose hierarchy is now explicit: PKM function is primary, portfolio function is secondary. Where they conflict, honest evolving thinking wins over curation for an audience.
v2
The design philosophy shifted from portfolio-as-output to portfolio-as-byproduct.
v1 framed the platform as a place to present work structured for interviewers. v2 adds that the platform must be used during the work, not after — so the portfolio emerges from honest ongoing documentation rather than retrospective reconstruction. Retrospective filling is now identified as a failure mode.
v1
— skip —
Why it changed?
v4
The project shifted from thinking about how a portfolio could work to having actual publishable material ready. The gap is no longer process or quality — it is publishing execution. A separate Plans node has been created to track the operational steps; this trunk node returns to being about the concept and direction.
v3
Researching traditional PM portfolio advice and comparing it against how Evergreen nodes work made the conflict visible. The conventional approach is curation-first; the PKM approach is thinking-first. Trying to serve both equally would compromise both. Naming the hierarchy removes the ambiguity.
v2
Building a personal public thinking space (Quartz site) made the tension felt, not just theorised. Structuring work for an external audience while also thinking honestly in public revealed that the two goals reinforce each other when documentation happens in real time — and undercut each other when one is retrofitted onto the other.
v1
— skip —
Evidence / Signals
- PM portfolio advice is a common topic in PM communities — the gap between what candidates present and what interviewers want is a known frustration on both sides
- Building a personal Quartz site as both a PM portfolio and a public thinking space surfaced this tension directly: retrospective curation feels less honest and loses important context that was only visible during the work
Open Questions
- What are the exact fields and structure that best mirror what interviewers look for?
- How does this sit alongside LinkedIn — is it a link in a LinkedIn profile, a standalone site, or something else?
- Who creates the profile — the PM themselves, or is there a guided interview-style flow that helps them build it?
- How do you keep the format loose enough to cover different PM backgrounds but structured enough to be useful?
- Is there a verification or credibility layer — can outcomes be evidenced or endorsed?
- What is the monetisation model — free for candidates, paid for recruiters, or something else?
- How does the platform surface the difference between in-progress thinking and completed work — should both be visible to interviewers, or only the latter?
Connections
- (none yet — first node in this tree)
Changelog
- v4 — work experience extraction complete; two flagship nodes created; publishing plan separated into Plans node
- v3 — Established PKM-first, portfolio-second hierarchy; added tension between the two functions to State of Thinking
- v2 — Shifted design philosophy from portfolio-as-output to portfolio-as-byproduct
- v1 — Initial node