How to present learning outcomes and proof in your ID portfolio.

A recruiter clicks into your portfolio, lands on your best project, and reads: "Worked on a large compliance initiative for a major client. Results were positive." She bounces in four seconds. The work behind that sentence was genuinely good — a branching scenario build that moved a real number — but you buried it under an NDA and a fog of hedging, and now it reads like you have nothing to protect.

Presenting outcomes is the part of the portfolio that separates an author from a strategist. It's also where instructional designers panic, because half the time the best numbers are confidential. Here's how to show proof you legally can't name, write outcome language that survives a legal review, and pair the quote with the metric so a hiring manager believes both.

An NDA almost never blocks you from describing your role, your audience, and your outcome category. It blocks the client's name. Those are different things.— the line that reframes the whole problem

Showing proof you're under NDA for.

Start by reading the actual contract, not your anxiety about it. Most NDAs restrict three things: client names, proprietary data, and internal processes. They rarely block you from describing your role, the type of audience, or the general outcome category. A line like "designed scenario-based compliance training for 600+ frontline workers in a regulated manufacturing environment" tells a hiring manager everything they need and reveals nothing about who signed the check. When you're unsure, email your former client contact for written permission to use an anonymized description. Most say yes — it costs them nothing and it gets their training program a quiet bit of credit.

Swap real names for descriptive stand-ins that carry industry signal: "Fortune 500 financial services firm" or "mid-size healthcare network, 12 facilities." Skip vague labels like "a large company" — they strip out the context a reviewer uses to judge difficulty. Name the regulatory framework when it's public knowledge — HIPAA, OSHA, SOX, PCI-DSS — because the framework itself isn't confidential even when the client is. Then pair the stand-in with one concrete constraint, like "multi-state rollout under a 90-day audit deadline," so reviewers can read your problem-solving without you leaking the account.

When you can't show the live module

If even the build is off-limits, you still have two honest ways to prove the craft. Ranked by how much design signal they preserve:

Outcome language that survives legal.

When exact figures are off-limits, write directional statements that still carry weight: "reduced average onboarding time by more than 30 percent" or "cut policy-related errors by double digits in the first quarter post-launch." Ranges let legal sleep while giving a hiring manager something concrete to discuss. And always add the baseline context — going from 45 percent to 82 percent is a different story than 90 percent to 94 percent, and the range can make that clear without exposing the client's real number.

Anchor every outcome to the business problem you named in your Situation section. If the challenge was slow ramp time for new sales reps, the outcome should speak that language: "new hires reached quota-ready status two weeks earlier than the prior cohort." If the challenge was audit risk, say "zero critical findings in the subsequent annual audit."Mirror the stakeholder's vocabulary so the result reads like it came from their post-project review, not from your marketing copy.

Indexed improvements work especially well when you tracked a metric over time: "pilot cohort scored 1.4x higher on the post-assessment than the control group" or "policy-related help-desk tickets dropped to 60 percent of the pre-training baseline within 90 days." Index language signals you measured before and after, which lands as more credible than a standalone figure. If you used the Kirkpatrick model, name the level your data represents — a Level 2 knowledge check is not a Level 3 on-the-job observation, and a reviewer who knows the model will notice if you blur them.

Where you can share a process artifact, staple it to the claim. A blurred LMS completion report from Cornerstone or Docebo, sitting next to "completion rose from 61 percent to 89 percent after we shortened the path and added mobile bursts," is far more persuasive than the sentence alone. If your artifact is a storyboard, annotate the before-and-after so the reviewer sees the exact design decision that moved the number. Proof stacked on narrative is how you graduate from "author" to "strategist"in the reader's mind.

Pair the quote with the number.

A completion rate of 94 percent sounds great until someone asks "but did behavior change?"Quantitative metrics alone read as sterile and disconnected from the learner. Qualitative signal answers the question the number can't: a manager saying "my team stopped calling me for password resets after the training" ties the metric to something observable. Place the quote directly below or beside the metric so a reader absorbs both in one scan.

Collect the qual deliberately during the pilot rather than hoping someone says something quotable. Build two or three open questions into your pilot survey — "What did you do differently on the job after this?" and "What would you change about the experience?" — in a tool like Qualtrics or even a plain Google Form. Pull one direct quote per project and attribute it by role, not name, when privacy matters: "Floor supervisor, manufacturing site." Pair it with a metric like "escalations dropped 22 percent in 30 days"and you've handed the reviewer two kinds of evidence that reinforce each other.

For projects where you have both, structure them as a simple before-and-after table: the left column is the baseline state with its metric and quote, the right is the post-training state. Skimmers absorb the delta in three seconds. In Storyline or Rise you likely tracked quiz pass rates and gathered free-text feedback off the results slide — export both into your project archive now, so the proof is sitting there when you update the portfolio months later.

Claims that collapse in the interview.

The fastest way to lose a hiring manager is an outcome that falls apart under one question. Four habits to cut:

1. ROI you can't explain.

If you write "saved the company millions in compliance fines,"be ready to show the math — the fine risk, the training's contribution versus legal and ops changes, and who validated the figure. If you can't, scale the claim to what you controlled: "training was one of three interventions that reduced audit findings from 14 to 3." Shared credit is still credit, and it sounds honest instead of self-serving.

2. Weak outcomes hidden in vague language.

"Learners found the experience valuable" is a smile-sheet summary, not a portfolio-grade result. If smile sheets are all you have, extract the most specific item: "87 percent rated the scenario practice as directly applicable to their daily workflow" ties satisfaction to a design choice you made. If the data was thin, say what blocked deeper measurement and what you recommended for next time — reviewers are testing your judgment, not your luck.

3. The recycled outcome paragraph.

Don't copy one results paragraph across projects with minor word swaps. Anyone who reads two or three of your case studies will spot the recycled language and assume the outcomes are invented. Every project had a different constraint, audience, and timeline — the results should reflect that. If two genuinely landed in the same place, differentiate them by the unique design decision: one used branching scenarios, the other spaced practice with job aids.

4. Framework and tool names as decoration.

Don't drop Kirkpatrick, Phillips, or Brinkerhoff as ornaments. If you name a model, show how you applied it: "we designed Level 3 observation checklists that managers used during ride-alongs two weeks post-training" proves the work. The same goes for your stack — "tracked in Docebo" or "exported from Cornerstone" tells a technical reviewer something real, while "used our LMS" tells them nothing. And the most mature line in any portfolio is the honest one: "we couldn't measure completion due to client LMS limits" reads as confidence, not weakness.

Frequently asked questions.