Building a Portfolio of Evidence Without a PM Job Title

A portfolio, for this purpose, isn’t a design-style showcase — it’s three or four documented examples of delivery work you can walk someone through in detail. Here’s how to build one from work you’ve already done.

Pick examples, not a full history

Two to four examples is plenty. Choose ones with a clear before-and-after: a system that was broken and got fixed, a launch that had a hard deadline, a cross-team effort that required real coordination. Avoid picking your smoothest project — a project with a complication you handled well is more convincing than one that apparently had none.

The structure for each example

1. Context: What was the situation, and why did it matter to the business?
2. Your scope: What were you actually accountable for — be specific about boundaries.
3. A complication: What went wrong or nearly went wrong, and what you did.
4. Outcome: What happened, ideally with a number attached (time, cost, scope, adoption).

Where to store it

A single document is enough — a couple of pages, one example per page. Don’t over-invest in formatting; the content is what gets you hired, not the template. (If you want a starting structure, our free Stakeholder Register template works as a companion artefact you can point to as a real deliverable you’ve produced.)

Use real artefacts as backup

If you have an actual RAID log, status report, or project plan from your work (with anything sensitive removed), keep a redacted copy. Being able to show a real document, not just describe one, is a strong signal in an interview.

Turning it into interview answers

Rehearse each example as a 90-second spoken answer using the same four-part structure. When an interviewer asks “tell me about a time you managed conflicting priorities,” you should already have an example loaded and ready, not be constructing one on the spot.