How to present learning outcomes and proof in your portfolio

Under NDA

TrainingOS supports NDA-friendly disclosure: show role and impact categories without exposing confidential titles or client names when required.

Describe industry vertical, audience size band, and risk level without naming the account. Reviewers with domain experience will still read signal.

Start by checking your contract language for what you can actually say. Most NDAs restrict client names, proprietary data, and internal processes—but 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 without revealing who signed the check. When in doubt, ask your former client contact for written permission to use anonymized descriptions—most say yes because it costs them nothing.

Swap real client names with descriptive stand-ins that signal industry: "Fortune 500 financial services firm" or "mid-size healthcare network, 12 facilities." Avoid vague labels like "a large company" because they strip useful context. Name the regulatory framework when it is public knowledge—HIPAA, OSHA, SOX, PCI-DSS—since the framework itself is not confidential even when the client is. Pair the stand-in with one concrete constraint: "multi-state rollout under a 90-day audit deadline" gives reviewers enough to judge your problem-solving without leaking the account.

Build a redacted sample in Storyline or Captivate that mirrors your real interactions but uses obviously fictional branding: made-up company logos, placeholder product names, and synthetic data. Keep the branching logic, variable structure, and feedback patterns intact so reviewers can feel the design quality. Label the sample clearly—"Anonymized replica of a production compliance module"—so nobody confuses it with client IP. Store the original client approval email in a folder you can reference if anyone questions your right to show the work.

If you cannot show even a redacted build, record a narrated walkthrough in Loom or OBS where you talk through design decisions while showing wireframes or storyboard excerpts instead of the live module. Focus the narration on why you chose scenario branching over click-next, how you structured remediation paths, and what the pilot data suggested. A five-minute video with clear thinking beats a locked-down portfolio gap that leaves reviewers guessing whether you have anything worth protecting.

Keep a private "NDA reference sheet" for each restricted project: client name, contract dates, what you can say publicly, what you cannot, and who approved the anonymized version. When you update your portfolio six months later, that sheet prevents you from accidentally revealing details that were fine in conversation but violate the written agreement. If your NDA expires after a set period, calendar the date so you can upgrade the case study with real names and metrics once the restriction lifts.

Outcome language

Use ranges or indexed improvements when exact numbers are sensitive. Pair with process artifacts when you can share them.

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 hiring managers something concrete to discuss. If you write "improved completion rates," add the baseline context—going from 45 percent to 82 percent is a different story than going from 90 percent to 94 percent—and the range makes that clear even without exposing the exact client numbers.

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

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

When you can share process artifacts, pair them directly with the outcome claim. A screenshot of your LMS completion report in Cornerstone or Docebo—with client data blurred—next to the statement "completion rose from 61 percent to 89 percent after we shortened the path and added mobile-friendly bursts" is far more persuasive than the sentence alone. If your artifact is a storyboard excerpt showing how you restructured branching, annotate the before-and-after so reviewers see the design decision that drove the number. Proof stacked on narrative is how you move from "author" to "strategist" in the reader's mind.

Pair qual + quant

Qualitative quotes from pilots ("managers stopped escalating tier-1 issues") complement KPIs. Together they show business literacy, not just authoring skill.

Collect qualitative data deliberately during pilots rather than hoping someone says something quotable. Build two or three open-ended questions into your pilot survey: "What did you do differently on the job after completing the module?" and "What would you change about the learning experience?" Pull one direct quote per project for your portfolio—attribute it by role, not name, if privacy matters: "Floor supervisor, manufacturing site." Pairing that quote with a quantitative metric like "escalations dropped 22 percent in 30 days" gives reviewers two kinds of evidence that reinforce each other.

Quantitative metrics alone can feel sterile and disconnected from the learner experience. A completion rate of 94 percent sounds good until someone asks "but did behavior change?" Qualitative signals answer that question: a manager saying "my team stopped calling me for password resets after the training" ties the metric to observable impact. When you write your case study, place the qualitative quote directly below or beside the metric so the reader absorbs both in one scan. If you used a survey tool like Qualtrics or even a simple Google Form during the pilot, mention it—process credibility matters.

If your client did not run formal evaluations, create your own lightweight data-capture plan for the next project and retroactively describe what you would have measured. Write something like: "Formal L3 evaluation was outside project scope; pilot feedback from 40 learners indicated reduced reliance on the reference manual during the first week." That sentence is honest, shows measurement thinking, and still gives the reader a qualitative signal. Silence about measurement reads as indifference; even a small proxy beats nothing.

For projects where you have both qual and quant, structure them in a simple before-and-after table in your case study: left column is the baseline state with metric and quote, right column is the post-training state. This visual format lets skimmers absorb the delta in three seconds. In Storyline or Rise, you might have tracked quiz pass rates and gathered free-text feedback from the results slide—export both and keep them in your project archive so you can reference them months later when updating your portfolio.

What to avoid

Do not claim ROI you cannot explain. Do not hide behind jargon. A concise "we could not measure completion due to client LMS limits" reads as mature.

Avoid inflated claims that collapse under a single interview question. If you write "saved the company $2M in compliance fines," be ready to show the math: what was the fine risk, what was the training contribution versus legal and ops changes, and who validated the number. If you cannot answer those questions, scale the claim to what you actually controlled: "training was one of three interventions that reduced audit findings from 14 to 3." Shared credit is still credit, and it sounds honest rather than self-serving.

Do not bury weak outcomes 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 of learners rated the scenario practice as directly applicable to their daily workflow" is better because it 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—hiring managers test your judgment, not your luck.

Avoid copying the same outcome paragraph across multiple projects with minor word swaps. Reviewers who read two or three case studies will notice recycled language and assume the outcomes are fabricated. Each project had a different constraint, audience, and timeline—your results should reflect that specificity. If two projects genuinely had similar outcomes, differentiate them by naming the unique design decision in each: one might have used branching scenarios while the other used spaced practice with job aids.

Do not use acronyms or framework names—Kirkpatrick, Phillips, Brinkerhoff—as decoration. 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 you did the work. Dropping "Kirkpatrick Level 3" without evidence sounds like you memorized a textbook. The same applies to tools: saying "tracked in Docebo" or "exported from Cornerstone" is useful; saying "used our LMS" tells them nothing—name the platform so technical reviewers know you have hands-on experience with their stack.