Your Portfolio Shows What You Built. It Should Show How You Think.
A Pretty Portfolio Isn't a Portfolio. It's a Highlight Reel.
Let me start with something uncomfortable: AI can now generate a polished eLearning sample in less time than it takes most designers to write a single learning objective. It can produce Articulate Rise outputs that look professionally designed; it can build Storyline interactions with clean branching logic; it can generate slide decks with consistent color palettes and thoughtful typography; and it can design job aids that are clear, well-organized, and visually appealing.
None of that tells you whether the person who submitted it can actually do the job.
This isn't an argument against AI in instructional design. It's an argument about what a portfolio is supposed to demonstrate — and why the rise of AI-assisted output has made that question harder to answer and more important to ask.
What a Portfolio Is Actually For
A portfolio exists to display a creator's abilities and complement the résumé in the application process. The résumé is designed to quickly convey the applicant's experience and qualifications — where they've worked, what they've done, what credentials they hold. The portfolio is meant to show something the résumé cannot: that person's style, their design sensibility, and the depth of their abilities in practice.
The problem is that "style and abilities" means different things depending on who is doing the evaluating. A hiring manager reviewing an instructional design portfolio isn't just trying to determine whether the candidate has taste. They're trying to determine whether the candidate can diagnose a performance gap, design a solution that addresses it, build something that delivers on that design, and evaluate whether it worked. They're also evaluating whether the candidate's design aesthetic and production capabilities would be a good fit within the existing team and meet the demands of the work that needs to be built.
That is the ADDIE process combined with a practical assessment of fit. And a portfolio that only shows the D — the developed artifact — is hiding four-fifths of the job.
What AI Changes About Portfolio Evaluation
Before AI-assisted design tools became widely accessible, a polished output was at least weak evidence of skill. Producing something that looked professional required some combination of design sense, tool proficiency, and time investment. It wasn't proof of instructional thinking, but it wasn't nothing.
That signal is now nearly worthless. The same tools available to every instructional designer today can write a well-constructed A-B-C-D learning objective from a rough topic description. They can generate a complete Articulate Rise course — modules, interactions, knowledge checks, and all — in a matter of minutes. They can write custom JavaScript for a Storyline branching scenario that would have required a developer or significant self-study not long ago. They can clean up an existing lesson by standardizing fonts throughout, adjusting color combinations to meet WCAG contrast requirements, and reorganizing content structure — all from a single prompt.
None of that requires the person submitting the prompt to understand why the learning objective is structured that way, whether the Rise course addresses an actual performance gap, how the branching scenario connects to a behavioral outcome, or whether the color changes actually make the content more accessible to the learners who need it most.
A candidate with six months of experience and the right tools can produce output that rivals the work of a seasoned designer. The output looks identical whether it came from someone who deeply understands learning design or someone who has learned to write good prompts. This doesn't make AI-assisted portfolios dishonest. It makes them incomplete. And it makes the evaluator's job significantly harder if they're only looking at outputs.
What a Portfolio Should Actually Show
If the output alone no longer tells the story, the portfolio needs to show the work behind the output. Specifically:
The needs analysis. What problem was this designed to solve? Was there a genuine performance gap, or was training the solution someone assumed before the analysis happened? Does the portfolio include a Performance Gap Analysis showing that a training solution was — or was not — the correct response, along with the supporting documentation that led to that conclusion? A portfolio piece that includes this level of documentation tells you immediately whether the candidate understands that training is a solution to a specific type of problem, not a default response to any problem.
The design documentation. A design blueprint, a storyboard, a content outline — something that shows the candidate made intentional decisions before opening their authoring tool. What were the learning objectives? How were they connected to the performance gap? How was the content structured and why? These documents reveal instructional thinking in a way that a finished module cannot.
The evaluation plan. How was effectiveness measured? What did Level 1 look like, and did it go beyond a five-question satisfaction survey? Was there a Level 3 plan — any attempt to measure whether behavior changed after training? A candidate who includes evaluation documentation is demonstrating that they understand training is a means to an end, not the end itself.
The reflection. What would they do differently? What constraints shaped the final product? What did they learn from building it? A short written reflection on a portfolio piece separates a practitioner who thinks critically about their work from one who is simply presenting deliverables.
On My Own Portfolio
I put real effort into making my portfolio visually appealing and engaging — the design decisions were intentional, and I care about the experience someone has when they review my work. And yes, I used AI to help me create the samples. I will always be honest and upfront about that fact. I am incorporating AI into my content creation process, but it is not a crutch. It is a tool — one that allows me to produce work more efficiently without replacing the thinking, the analysis, or the design decisions that make the work effective. What I also made sure to include is the full picture of how I work: from the needs analysis and supporting documentation through the design and development to the evaluation plan. I included those documents not because every portfolio needs to look exactly like mine, but because I wanted anyone reviewing my work to see that I understand the entire process, not just the part that renders in a browser.
What Hiring Managers Should Be Asking
If you're evaluating instructional design portfolios right now, the question to ask isn't "does this look good?" It's "can I see how this person thinks?"
Ask candidates to walk you through a portfolio piece from analysis to evaluation. Ask what the performance gap was and how they confirmed it. Ask what they would change if they built it again. Ask what the evaluation data showed — or, if there wasn't any, ask why not.
The answers to those questions will tell you more about a candidate's actual capabilities than any number of polished Storyline modules. And in an environment where AI can generate the module in twenty minutes, those are the only questions that still reliably separate the practitioners from the prompt engineers.