How to make a portfolio when you are not a designer

Because it was written by designers, for a field where the artefact and the evidence are the same object. A designer shows the screen and the screen is the work. Almost nobody else is in that position.

So the advice arrives in a form you cannot use. Show your process, when the process was six months of meetings. Lead with visuals, when the output is a query and a decision. Curate your best pieces, when the pieces belong to your employer and you signed something about them. Following it produces the thing everyone recognises: a page of stock imagery wrapped around a job history.

The useful translation is that a portfolio is not a gallery. It is a place where you get more than a bullet point to explain what you did, which is a format advantage that has nothing to do with whether the work is visual.

Write the decision, not the deliverable. What was the situation, what did you choose, what did it cost, and what happened. That is a shape that works for a migration, a campaign, a care plan, a budget, or a hiring process, and it is more interesting than a screenshot of any of them would have been.

Be specific where you can be. Latency you cut, a process you took from days to hours, a campaign that stopped because you argued it should, a metric a team started tracking differently because of your analysis. Specifics are the most credible thing on a page and vague scale claims are the least, and the fix for not having numbers is to describe the work rather than to reach for adjectives.

Name what changed because of you specifically. On any team of reasonable size the honest version of your contribution is narrower than the project, and stating that narrower thing plainly reads as more senior, not less. Everyone reading has been on a team and knows how it works.

Describe the shape of the result rather than the result. "A low single-digit percentage improvement in retention" is honest, safe, and tells a reader nearly as much as the real figure would. Inventing a specific number to sound better is neither honest nor safe, and the person most likely to catch it is the person interviewing you.

Where the output genuinely cannot be described, substitute. A small, well-written analysis of a public dataset proves the same abilities as the confidential one: framing a question, picking a method, and stating a conclusion you can defend. In regulated and clinical work, describe the skill and never the case, including anonymised anecdotes with identifying specifics.

When in doubt about what you can publish, ask before you post rather than after. The cost of checking is a message; the cost of not checking is a conversation with your employer about a public page.

Where the credential is the screen. In licensed professions, a lot of first-round filtering is a check that your licence and certifications are current and in the right jurisdiction, and no amount of good writing moves that step. A page can still be genuinely useful later, as one link that collects your licence, certifications, settings and continuing education for a recruiter or an interview panel, but it will not get you past a filter that is not looking at it.

It also adds little if you are applying exclusively through large-company processes where a resume is parsed by software and a human sees you late or never. That is a real chunk of the job market and pretending otherwise would be dishonest.

The rest of the time, the argument for having one is that you control it, it does not disappear when a company is acquired, and it gives you more than a bullet point. If your content already exists in a resume, the build is not the obstacle it looks like: DebutPage drafts the page from the PDF and publishing is free, so what is left is the writing that only you can do.