Portfolio design approach (or, "Why not include full courses?")
I’ve worked with rapid e‑learning tools like Storyline, Rise, Captivate, and Camtasia in many roles and I’m comfortable using them. I’ve chosen not to showcase full, tool‑specific courses here on purpose.
Here's why:
- Learning design first, tools second
My long‑standing mantra is “just because you can do something, doesn’t mean you should”, which comes from seeing the risks of “shiny kit syndrome” up close. It’s tempting to reach for the newest interaction or feature just because it’s available, but that can pull time and budget away from what actually improves performance and knowledge transfer. In most cases, clear structure, plain language, and well‑designed practice do more for learners than elaborate widgets. The pieces on this site focus on the analysis, structure, and storyboard decisions that move the needle: strategic work that travels well across tools and trends.
- Accessible, tool-agnostic, self-contained samples
I want people to be able to look at my work quickly, without plug‑ins, trial licenses, or a specific LMS. Keeping everything on my own site, in standard web formats, means it’s fast to load, screen‑reader friendly, and simple for me to update or annotate. That way, access to my work never depends on a specific tool, license, or platform.
- AI and the shift in what matters
With AI, it’s easier than ever to spin up something that looks like a finished course in the major tools. But remember, just because someone can do something, doesn't mean they should! The prevalence of AI in industry standard tools has significantly reduced production time and reduced the requirement for the user to have a strong technical background to effectively use the tools. This change shifts the value of an instructional designer toward what happens before and after development: clarifying the problem, defining performance outcomes, shaping content, and designing practice, feedback, accessibility, assessment and performance evaluation. The examples here are meant to show that thinking, not just that I can operate a particular piece of software.
- Development is one small slice of the work
Building screens in a rapid authoring tool is only one step in a larger curriculum and instructional design process. In most projects, needs analysis, solution design, content architecture, and iteration based on feedback and evaluation results take more time and have more impact than the final build. This portfolio focuses on those parts of the work, with the understanding that specific tools can be learned or refreshed as needed.