About

I’ve always been drawn to making complex things easier to understand.

Long before I was creating software training, I noticed that the difference between success and frustration often came down to whether people had the right information at the right time. Throughout my career – whether working in manufacturing, software, customer success, product management, or AI – that observation has remained constant.

Early in my career I became frustrated by how often employees were expected to succeed with incomplete training, scattered documentation, or processes that made work harder than it needed to be. Rather than accepting that as “the way things are,” I began creating better systems myself: documenting workflows, writing training manuals, building quick-reference guides, redesigning onboarding programs, simplifying complex software, and improving business processes.

Over time I realized these weren’t separate interests; they were all part of the same goal: removing friction between people and the work they’re trying to accomplish.

That philosophy eventually led me to launch my YouTube channel, where I created concise software tutorials after growing frustrated with long, unfocused training videos that buried the information people actually needed. More than 2.3 million views later, the feedback has remained remarkably consistent: people appreciate instruction that is clear, practical, and respectful of their time.

Today I continue applying those same principles while expanding my expertise in AI, instructional design, and knowledge management. Whether I’m designing a learning program, documenting a complex system, evaluating AI-generated content, or improving a business process, I start with the same questions:

  • What does success look like?
  • Where are people getting stuck?
  • How can we make this easier?
  • What information do they actually need?

I believe the best instructional design isn’t measured by the amount of content we create—it’s measured by how confidently people can apply what they’ve learned.

My Approach:

  • Start with the outcome, not the deliverable.
  • Design for people, not processes.
  • Reduce friction before adding features.
  • Make knowledge easy to find and easy to apply.
  • Different audiences need different pathways.
  • Measure success by adoption, not completion.
  • Continuously refine based on real user behavior.

What I Bring:

  • I design learning around how people actually learn.
  • I simplify complex systems without oversimplifying them.
  • I create documentation people actually use.
  • I identify and remove barriers to adoption.
  • I help organizations preserve knowledge while embracing change.
  • I believe technology succeeds when people feel confident using it.

What I’ve Learned:

  • The best instructional design starts by understanding where learners get stuck, not by explaining every feature.
  • Analytics should shape curriculum, not just measure it.
  • Documentation should reduce dependency, not create it.
  • Different audiences require different pathways to the same goal.
  • Small improvements that remove friction often create bigger gains than large feature additions.
  • AI is most valuable when it strengthens human expertise rather than replacing it.