From learning designer to builder.
On paper, “instructional designer” and “software developer” look like two different people. They’re not — at least not anymore. Here’s how one became the other.
I came up through software startups, where wearing every hat meant earning a seat in product and design decisions — testing, demoing, and shaping roadmaps as the voice of the customer. That product and UX foundation shaped the next fifteen years: leading training, instructional design, and quality inside large, regulated operations, always asking not just whether a course was finished, but whether it actually changed what people could do.
The one thing that always stood between my ideas and real, working tools was code. AI removed that wall — and I put it straight to the test. Teaching myself as I went, I designed and built a suite of live, AI-powered products in a single stretch:
An authoring platform, an assessment engine, a knowledge base, a course-design tool, a multi-industry business platform, a caregiver-support product, and an AI photography coach — plus a library of technical documentation written from my own production code.
Here’s the part that connects the two halves: the hard part of building was never the code. It was the judgment — the research, the design decisions, the domain rigor, the quality bar — and that is exactly what fifteen years in learning and development trains you to do. AI handled the execution; the thinking stayed mine. So this isn’t a career change. It’s a learning designer who can finally build the things he used to only be able to specify. AI didn’t make me a creator — it unleashed the one I already was.