21 ID portfolios worth stealing from.

I have reviewed somewhere north of two hundred instructional design portfolios — hiring for my own team, judging a freelancer roundup, getting tagged in "can you take a look" threads. Here is the uncomfortable truth: I do not read them. I scan. I give the first screen about ten seconds, click the strongest-looking thumbnail, and decide inside two minutes whether you can ship. Most portfolios lose me before the second project.

So this is not a gallery of pretty homepages. It is the pattern I keep seeing in the ones that actually get interviews — twenty-one of them blur together after a while — plus the things even the good ones quietly fudge. Steal the structure. Skip the mistakes.

Nobody reads your portfolio. They scan it, then they click one thing. Build for the scan, and make the one thing unmissable.— what I tell every ID who asks me to review their site

Hiring managers do not move through a portfolio linearly. We hunt for three signals: a clear value proposition, three to six strong projects, and evidence you can take a course from kickoff to a working SCORM package without hand-holding. If your hero just says "Instructional Designer" with no specialty and no proof, you are asking me to invent a reason to care. I usually won't.

Treat the first screen like a resume headline. "Scenario-heavy compliance for healthcare" tells me what job you want. "Passionate learning experience designer" tells me nothing. If you have several specialties, pick the one you want next and thread the rest underneath — trying to be everything to everyone always reads as a generalist with no edge. Early-career? Show growth across two real projects instead of claiming expert status on six.

Then there are the thumbnails, which is where most people quietly throw the game. A crisp project title, tool tags (Storyline, Rise, Captivate), and a one-line outcome — "cut time-to-competency by 22%" — beat a mystery box labeled "Compliance Course 2" every time. Crop the thumbnail to a real interaction frame, not a title slide, so it signals scenario or simulation at a glance.

The one pattern every good one shares.

Here is the structural thing I promised, and it is boringly consistent across the best portfolios I have seen: they lead with the outcome, not the biography. Challenge, your role, the tools, the measurable result — in that order, on the first screen of every case study. The weak ones open with a slideshow of pretty slides and bury the "so what" three scrolls down. By then I have already clicked away.

The cleanest way to enforce this on yourself is the STAR skeleton — Situation, Task, Action, Result. It reads the way a hiring manager thinks, and it stops you from skipping straight to screenshots like a production vendor. I keep a copy pinned and refuse to publish a project without it. (We wrote up the full version in the STAR case study template.)

// Situation — the business problem, in one sentence a non-ID gets.
Situation: New-hire reps took 9 weeks to hit quota; onboarding was 40 PDFs.

// Task — what YOU owned. "Lead ID" reads very differently from "supported".
Task: Lead ID. Redesign ramp into a branching, scenario-based SCORM module.

// Action — process + tools. Where you earn the "owner" label, not "author".
Action: 3 SME passes, legal sign-off, Storyline 360 build, pilot with 40 reps.

// Result — the number. Date it so it never sounds retrofitted.
Result: Time-to-competency 9 → 7 weeks (2025 pilot). Hosted demo below.

Notice the last line: hosted demo below. The portfolios that convert do not make me imagine the interaction — they let me click it. A reviewer who can play through your branching scenario understands your level faster than anyone reading a bullet list about "interactivity." That is the whole game: pair the STAR write-up (the thinking) with a live, hosted module (the proof).

The three projects worth stealing.

Strong portfolios show range without chaos. After enough of them, the winning lineup is almost always the same trio — it answers "depth," "modern tooling," and "can you ship under pressure" in three clicks. Ranked by how much they move a hiring decision:

Resist the urge to pad this with seven more medium projects. I remember one strong story far longer than a wall of competent-but-forgettable thumbnails. If you are still deciding whether a portfolio even earns its place next to your resume, we argued that out in resume vs portfolio.

What the good ones quietly fudge.

Now the part nobody writes down. Even the portfolios I admire bend the truth in small, mostly forgivable ways — and a few unforgivable ones. Knowing the difference keeps you on the right side of it.

The forgivable fudges.

Redacted client work with obviously fake branding and made-up data is fine — expected, even — as long as you labelit as anonymized so I never mistake it for live metrics. Neutral placeholder logos instead of a client's mark you are not allowed to show: smart, do it. A "parallel" project that mirrors a real engagement's patterns without naming the client: a perfectly honest way to prove a skill under an NDA.

The ones that cost you the offer.

Stale copy is the big one. If your write-up references interactions that no longer exist in the shipped module, and your interview deep-dive contradicts it, trust evaporates. When you fix a module after client feedback, update the portfolio text to match. Same with metrics: date the improvement so it does not sound retrofitted. And the verbs — "owned" versus "supported" should match exactly what your references will say when someone checks.

Before you send the link.

Run this from a logged-out incognito window, on a phone and a laptop, before the URL goes in an email signature or a LinkedIn bio:

• Every project states audience, constraint, your role, tools, and at least one proof point.
• Every thumbnail opens the right project; every video plays on mobile; every SCORM launches without a surprise login wall.
• Spell-check the client names you are actually allowed to display, and align screenshots to the story you tell in interviews.
• Two talking points per flagship: one design decision you would defend, one trade-off you would redo. Interviewers go deep when the work looks strong.
• One stable URL you reuse every time — refresh the underlying projects without breaking conversations already in flight.

That stable-URL discipline is the quiet superpower of a hosted portfolio. The strongest IDs I know stopped forwarding expiring Review 360 links and put hosted SCORM, structured case studies, and view tracking behind one address — so they know which demos actually get clicked. If you are still living in Review threads, the case for retiring them is in sharing Storyline the modern way, and you can browse what proof-first project pages look like in our public examples gallery.

Then do the bravest thing on this list: ask a peer who will hurt your feelings for a blunt five-minute pass. "What's still unclear?" Fix those gaps. Clarity beats polish when a recruiter is giving you ninety seconds — and ninety seconds, honestly, is the whole job.

Frequently asked questions.