Not content. Not slide decks. Not a PDF that gets printed and ignored. Curriculum that moves people from where they are to where they need to be — measurably, efficiently, and without waste.
The best learning experiences don't feel like training. They feel like solving a puzzle — because they are.
Early in my teaching career, I handed high school CAD students a complete Rubik's Cube kit — fully disassembled, no drawings, no instructions, no reference of any kind. Not as a gimmick. As a curriculum.
Students started with a parts list challenge — how many unique components does a 3x3 Rubik's Cube actually have? The answer surprises most people: only about 7 distinct parts. From there, students used digital calipers and engineering scales to measure each component precisely and create the technical drawings themselves — then drafted every part in SolidWorks with correct draft angles and tolerances, the way an actual injection mold engineer would. They created bills of materials, full assemblies, and technical animations of the mechanism. And then — only then — they followed the solution algorithm to actually solve the cube.
Competitions followed. My personal best: 1 minute 14 seconds. Some students learned to solve in under a minute. Every single one left the unit with hands-on technical skill they could articulate, demonstrate, and build on.
That's not a cute classroom activity. That's Bloom's Taxonomy executed in a single project arc — from knowledge to synthesis, wrapped in something that didn't feel like work.
That philosophy drives every curriculum I design. The gap between where your people are and where they need to be is real. The bridge should be worth crossing.
What happens when you convert the right training to eLearning — and stumble onto a discovery that changes everything.
Toyota's Engineering Data Management operation trained design engineers across 23 departments — sometimes hundreds at a time. The format was large-scale instructor-led sessions: engineers pulled away from their workstations and into a classroom or auditorium for two full weeks. The training covered the systems and procedures that kept Toyota's design data accurate, version-controlled, and production-ready.
The sessions ran quarterly as new waves of engineers came through. Nobody questioned the format. Nobody measured the outcomes. The seats were filled, the hours were logged, and people went back to their desks.
Then someone asked the question that changed everything: "How do we know what they're actually learning?"
The stakes were concrete. When a design engineer didn't follow proper Engineering Data Management procedure — saving a part under the wrong number, wrong revision, or in the wrong location — the consequences weren't administrative. A production line could go down. Real downtime. Real cost. And when that happened, the training team had to step in, identify the gap, and retrain individually — which meant the original training hadn't worked in the first place.
Run the math on the status quo: 300 engineers off the job for 80 hours, at a conservative loaded cost of $45/hour. That's over $1,000,000 in lost productivity per training cycle — before a single dollar of delivery cost. Quarterly. That's what wasn't being measured.
Steeped in methodologies including 8D Problem Solving, Kepner-Tregoe, and Toyota Production System Management (TPM), the approach was clear: identify the real problem, measure what matters, and build a system that produces verifiable results — not just attendance records.
The mandate became: rebuild the training so comprehension could be measured, enforced, and proven. The production workflow became a two-tool pipeline. TechSmith Camtasia handled demonstration and narration — screen capture, software walkthroughs, and voiceover recorded with precision. Those finished assets were then imported into Adobe Captivate, where the real instructional architecture was built.
Inside Captivate, each module got real-time knowledge checks embedded throughout — not just at the end. Learners couldn't skip ahead. Forced progression meant a module had to be passed successfully before the next one unlocked. No skimming. No checkbox compliance. Actual demonstrated comprehension, gate by gate.
Once a learner completed the full sequence, all modules reopened for free navigation — so the content became a permanent performance support library, not a one-time event. An engineer six months later could return to exactly the module they needed, exactly when they needed it.
While building one of those Camtasia demonstration modules, I hit a wall. I needed to show a complex software process in reverse — stepping backward through a workflow to illustrate the "undo" logic. The capability didn't exist in Camtasia at the time. Not as a feature. Not as a workaround. I contacted TechSmith directly.
Their answer: "No, that can't be done."
That was fuel.
I don't accept "impossible" as a fact. I've always understood it as an opinion — usually someone else's opinion about what they haven't tried hard enough to figure out yet. So I went back into Camtasia and started pulling it apart. Not looking for a hidden button. Looking for the raw mechanics — what the tool was actually doing at the timeline level — and whether those mechanics could be assembled differently than anyone had assembled them before.
They could. Through a technically demanding, manual process of working with individual clip segments on the timeline, I constructed a reverse clip. Frame by frame. It wasn't easy the first time. But once I understood the logic, I could replicate it efficiently — and what looked impossible became a repeatable technique that accelerated production across the entire project.
TechSmith later built the feature into the software. After I had solved it, replicated it reliably, and documented the process — I called them back. Not to complain. Not to ask for compensation. Just to show them what I'd figured out. They were, by their own account, genuinely amazed. No bonus. No recognition. Just gratitude — and eventually, a new feature in the product that thousands of Camtasia users now take for granted.
That story is not really about Camtasia. It's about how I work. When a tool, a system, or a person tells me something can't be done, I hear a dare. Impossible is not a fact. It's an opinion. Impossible is not a declaration. It's a dare. Impossible is potential. Impossible is temporary. Impossible is nothing. That's not a motivational poster. That's how I've built everything I know how to do.
Every modality, every format — matched to the learning objective and the audience, not the other way around.
Deep fluency across the full production pipeline — from storyboard to deployment. Including AI tools that actually accelerate quality, not just output.
ADDIE is the foundation. Experience is the accelerant.
ADDIE is a framework, not a religion. On fast-turnaround projects I compress the phases and apply SAM (Successive Approximation Model) principles — rapid prototyping, early stakeholder feedback, and iterative development that gets to something testable faster. The methodology serves the project, not the other way around.
Transparent, predictable pricing. Scoped to your project before a dollar is committed.
Tell me where your people are, where they need to be, and what's in the way. The rest is what I do.
Start the Conversation See the Portfolio 🧮 Estimate Your Project Cost