How many metrics should I include per case study in a PM portfolio?

One primary metric, plus at most one or two supporting signals if they add real context. Listing every number that moved makes it unclear which one you actually cared about, which reads as less rigorous, not more.

What if my project doesn't have a clean percentage or metric?

Don't force one. State the qualitative outcome precisely — for example, the number of steps a process went from and to — rather than reaching for a vague quantitative claim. A precise qualitative result is more credible than a soft quantitative one.

Should I mention other things that could have caused the result?

Yes, in one line. Acknowledging a confound — a pricing change in the same window, seasonal lift, a parallel launch — and how you accounted for it builds more credibility than presenting a single clean number as the whole story.

Where should metrics appear in a portfolio: the summary or the case study?

Inside the case study narrative, next to the decision the metric was measuring. Save the compressed, resume-style version ("improved activation 12%") for your resume; the portfolio's job is to show the reasoning behind the number, not just restate it.

Is it bad to include a baseline and timeframe with a metric?

It's the opposite — leaving them out is what makes a metric untrustworthy. "20% increase" means different things as a relative versus absolute change, and over different timeframes. Stating both in the same sentence as the result costs one clause and removes the ambiguity.

What Metrics to Put in a Product Manager Portfolio (and Which to Cut)

Product Leader.

We use cookies for analytics and to remember your preferences. "Necessary" is always on.

💬