What Goes in a PM Portfolio in 2026

Most "portfolio checklist" posts give you a slide-deck outline — About, Case Studies, Skills, Contact — as if the format were the hard part. It isn't. The hard part is deciding what earns a place on the page when you have far more material than room. Here's the opinionated version: the eight things worth including, the four that don't belong, and why "impressive" and "convincing" are not the same goal.

1. One sentence that says what you're for

Not a mission statement. Not "passionate product leader with 7 years of experience." A single line that tells a hiring manager which problems you're good at solving — "I take 0-to-1 B2B products through their first paying customers" reads completely differently to a recruiter than "I scale platform products for enterprise teams," even though both are legitimate PM careers. If your one-liner could describe half the PMs on LinkedIn, it isn't doing its job yet.

2. Two or three case studies, not seven

A portfolio with seven thin case studies reads as sprawl; a portfolio with two or three deep ones reads as judgment. Each case study should answer four questions in order: what was broken, what you decided (and what you didn't do), what shipped, and what changed because of it. The "what you decided" step is the one almost everyone skips — it's the only part that actually shows product thinking instead of project management.

3. A real number in every case study, not an adjective

The metrics you choose say more about your judgment than the metrics themselves — a 40% conversion lift is worth nothing without knowing the baseline and sample size, and "significantly improved retention" is worth nothing at all. If a project genuinely had no measurable outcome yet, say that directly and explain what you're tracking instead of dressing it up. A hiring manager trusts one honest "too early to say, here's what we're watching" over three vague "greatly improved" claims.

4. The artifacts, not just the narrative

A prose summary of a project is a claim; a linked PRD, a Figma file, a dashboard screenshot, or a Loom walkthrough is evidence. You don't need all four for every case study, but each one should have at least one artifact a skeptical reader could actually click into. This is the single biggest gap between portfolios that get a callback and portfolios that get skimmed and closed.

5. AI projects — if you show them, show the work, not the vibes

By 2026 "I used AI to build a thing" is table stakes, not a differentiator, and a screenshot with no context reads as exactly that: a vibe. The bar for an AI project card is a working link, the actual prompt or spec you wrote, the decision the model couldn't make for you, and one real number — the same evidence standard as any other case study, applied to a newer kind of project.

6. A resume-shaped summary, even though this isn't a resume

Recruiters still scan for years of experience, company names, and titles before they read a single case study — a portfolio replaces the pitch, not the facts a resume conveys in five seconds. A compact work history section (companies, titles, dates) near the top means the person deciding whether to keep reading doesn't have to go hunting for it.

7. A way to hear your voice

Text case studies prove you can write; a short video — 60 to 90 seconds introducing yourself, or a 2-minute walkthrough of one project — proves you can communicate under normal, unscripted conditions, which is most of the actual job. It doesn't need production value. It needs to sound like a person a team would want in a room.

8. One clear next step, not five competing ones

End the page with a single obvious action — "book 15 minutes," "email me," "see my resume" — not a scattered mix of social links, a Calendly widget, a contact form, and a PDF download all fighting for the same click. Every extra option is a chance for the visitor to do nothing at all.

What doesn't belong

• A "skills" word cloud with no evidence behind it. "Strategic thinking, stakeholder management, data-driven" listed as tags proves nothing a case study can't prove better.
• Every project you've ever touched. A long list of logos you "worked with" reads as breadth without depth — the opposite of what a portfolio is for.
• Stock photography and template hero sections. They signal effort spent on the wrapper instead of the substance, which is the inverse of what you want a reader to conclude about you.
• Jargon that doesn't survive contact with a non-PM reader. If a hiring manager's recruiter or a founder can't follow a case study, it doesn't get forwarded to the next round.

Final thoughts

None of this is about cramming in more — it's about cutting until only the things that change a reader's mind are left. A portfolio with three real case studies, honest numbers, and one clear next step will outperform a comprehensive twelve-section site almost every time, because the goal was never to document your career. It was to make the case for the next one.

Build a portfolio structured this way in under a minute — free, no credit card.