BUILD A PORTFOLIO PEOPLE ACTUALLY FINISH
- Jul 31
- 4 min read
3 PROJECTS, 1 PAGE EACH
MOST PORTFOLIOS ANSWER THE WRONG QUESTION
I have built portfolio pages I was proud of that did absolutely nothing for me. The work was good. The pages were pretty. They just answered a question nobody had asked — "can you make things?" — when the question on the other side of the table is "can you figure out what to make, and why?"
When hiring managers in my field were asked to rank what they look for inside a portfolio, the winner wasn't polish. It was the ability to solve real-world problems, and it won by a clear margin (Peck, 2023).
Their open-text comments sharpen it further. They wanted breadth of solution types instead of six variations on the same eLearning module. They wanted the design rationale — why you chose what you chose. They wanted evidence of the consulting work with the SME or the client, not just the finished asset. And they wanted a plain statement of the business problem the thing was built to solve.
None of that describes a gallery. All of it describes case notes.
PICK 3. THEN CONSIDER CUTTING ONE.
Three projects, chosen for range rather than for your best work:
One where you built something genuinely technical.
One where the real work was the negotiation — the SME who wouldn't release content, the stakeholder who wanted a course when what they needed was a job aid.
And one where something went sideways and you fixed it, because that's the only category that demonstrates judgment instead of execution.
If you don't have client work yet, this is not a dead end. Roughly 62% of the hiring managers in that same survey said they'd consider candidates with no formal instructional design experience (Peck, 2023) — which means the portfolio is being asked to stand in for the track record. Build the projects. Redesign a real piece of bad training you've suffered through, name the actual performance problem it failed to solve, and document the whole decision trail. A self-directed project with rigorous thinking beats a client project you can't explain.
Then hold each one to a single page.
That isn't a style preference. The most consistent employer complaint in the ePortfolio research isn't quality — it's the time required to review one, alongside excessive information and difficulty telling whether the work is genuinely yours (Mitchell et al., 2021). Every page you add makes it likelier that nobody finishes the first one.
You are not building a museum. You're building something a tired person can get through between meetings.
LEAD WITH THE PROBLEM, NOT THE ARTIFACT
Here's the structure I'd use for each of the three:
The move that matters most is the first one: open with the business problem in plain language, before a single screenshot. "Call handle times rose 40% after a system migration" tells a hiring manager more in one line than a beautifully rendered course tile ever will. The artifact comes afterward, as proof. It is not the argument.
Write the rationale even when it's unflattering. "We shipped a job aid instead of the course they asked for, because the failure was findability rather than knowledge" is close to the most hireable sentence you can put in a portfolio, and almost nobody writes it. Anyone can show a finished module. Far fewer can show the thinking that decided what the module should be.
Leave out the process diagram of ADDIE. Leave out the tool logos. Leave out the paragraph about your passion for learning. None of it answers the question being asked, and all of it spends the reviewer's attention before you've made your case.
One more reason to bother, and it's the one that surprised me: the benefit accrues whether or not anybody opens the page. Constructing the narrative — deciding what the work was for and why you chose what you chose — is what prepares you to answer "tell me about yourself" out loud (Rafanello-Bazar, 2026). You aren't only publishing. You're rehearsing.
THEN MAKE IT FINDABLE
A portfolio nobody can find is a private document with extra steps.
You don't need to be everywhere. You need to be findable and consistent. Pick the platforms that match what you actually make. I post on LinkedIn most often, because demonstrating expertise in my field genuinely lands there. My art goes on Instagram, because I'm a designer and it fits. The longer thinking lives here and on Substack.
Then make the profiles match. Same name, same headline, same photo, same portfolio link, everywhere you appear. It sounds fussy. It reads as trustworthy — and trust is most of what you're being assessed on before anyone speaks to you.
Finally, keep the link in front of people. Résumé header, email signature, LinkedIn featured section. Then bring it into the interview and walk someone through it, rather than hoping they clicked.
So I'll ask you this. If a hiring manager gave your portfolio ninety seconds and read only the opening paragraph of one project, what would they learn about how you think? And is that actually what you'd want them to know?
Comments