Build a portfolio that shows how you think

Choose a small problem you can investigate

A first portfolio project does not need to be an entire onboarding program. Pick a bounded task you can understand well: helping a volunteer handle a visitor question, teaching someone to use a feature, or supporting a new team member through a recurring decision.

Find people who perform the task and ask about recent examples. If you cannot access real learners, label the project as a concept and list the assumptions you would test. Do not present fictional personas or invented outcomes as research.

Write the case study as a chain of decisions

Explain the performance gap, what you learned, the objective, the practice design and the evidence you used to revise it. A reader should be able to connect the artifact to the problem. Include a rejected alternative and why it was less appropriate.

For example: “I considered a narrated walkthrough, but the task required choosing between similar cases. I prototyped a decision activity with immediate feedback instead.” This explains a design choice without needing to claim that your project transformed an organization.

Show the unpolished work that mattered

Include a brief, a storyboard excerpt, a test observation and the revised screen or activity. Keep participant details private and obtain permission before sharing client material. Re-create sensitive examples with clearly labeled fictional content when needed.

Screenshots should have short captions explaining what changed and why. A beautiful final screen tells only part of the story. An annotated before-and-after can demonstrate how you respond to evidence.

• Problem and audience: who needed to do what?
• Evidence: what did you observe, and what remained an assumption?
• Design: how did practice and feedback support the objective?
• Iteration: what changed after review or testing?
• Limitations: what would you measure next?

Explain AI’s role plainly

If you used AI, identify the bounded tasks it supported: generating variations, critiquing wording or helping produce a prototype. Explain how you checked the output and which decisions you made. A prompt screenshot alone is not evidence of instructional design skill.

Do not upload confidential work to an assistant solely to make the portfolio easier to write. Keep the same permissions and data boundaries you would use in the project itself.

Report evidence without stretching it

If three people tried the prototype, describe it as a small formative test. Say what you observed and what changed. Do not turn that into a claim of proven learning effectiveness or a percentage improvement for a whole workforce.

A useful ending is: “Next, I would test independent performance on a new case and follow up after participants use the skill at work.” That shows you understand the difference between a promising design and demonstrated results.