This is the final article in a six-part series examining what I learned about customer education by completing ten professional certifications in thirty days. If you missed any previous articles in the series they are all linked at the end of this one.
This entire exercise began because I love to learn and wanted to expand my knowledge in a few specific areas. AI is impacting fields that have been mostly stagnant for years and I wanted to get a better understanding of what those impacts are or projected to be. Having worked behind the scenes of customer education over the last six years I better understood what good could look like and that made me look at these programs differently. Much like my time working in construction made me see every defect in every home I walk into. Though in that case I have stopped saying anything unless asked. Have no fear, if given the opportunity all you will hear from me is you have a lovely home.
I’m going to wrap this series up with a summary of what I have shared so far and some final thoughts. I hope it serves you well as you set forth to build programs of your own. Here is what I took away.
Design around outcomes not features. Learners don’t take your programs because they are desperate to know every nook and cranny of your software. They have jobs to do and now in addition to those jobs they also have to learn a new tool. Focus on the key outcomes they need to achieve and build the training to get them there. Aan encyclopedic explanation of your products already exists. If that is what a user needs then point them towards the documentation.
Accuracy is the floor and currency is the standard you build above it. Warmth, personality, and production value all matter. However, a program that doesn’t accurately depict your product doesn’t just fail to help learners, it can actively damage their trust in your organization. In a SaaS environment where products evolve constantly the gap between what your program teaches and what your product actually does can expand faster than most teams realize. Get the accuracy right first. Then chase everything else. Remember, publishing is the starting line not the finish line. Every program in your library is either earning its place or quietly misleading the learners who trust it. Build the maintenance infrastructure before you need it. Establish content review cadences tied to your product release schedule. If you are consistently unable to prioritize a program for updates then why is it in your library?
The learner experience layer deserves the same investment as the content itself. Navigation clarity, progress indicators, completion mechanics, and a clear sense of what comes next are not cosmetic details. They are the framework that holds the learning experience together. A novel handed to you as loose pages in a freezer bag may not make or break the quality of the book, but it is a difficult presentation to get past. Test your program with a real learner before you launch it. Where do they hesitate, where do they get confused, where do they give up? These are the friction points that will also frustrate your users. Identify them and eradicate them.
Understand your constraints before making production decisions. The tension between human warmth and scalable AI-assisted delivery is real but it is more often a constraint management problem than a philosophical choice. The size of your team, the pace of your product evolution, and the budget available will shape what is possible more than your preferences will. Be honest with yourself about those constraints and design the most effective and helpful programs those constraints allow. Remember, sometimes you need more jugglers or fewer balls in the air.
Your learners will always tell you whether you got it right. Engagement rates, completion rates, satisfaction scores, and ultimately the adoption and retention metrics that customer education exists to support, these are the only measures that matter. All the production decisions, the platform choices, the AI integrations, and the instructional design frameworks in the world mean nothing if the learner on the other end is not getting what they came for. Start with their needs and let everything else follow.
Thirty days. Ten certifications. Five themes. And one conclusion that keeps coming back to me as I reflect on what I observed: the best customer education programs are not built around what companies want to teach. They are built around what customers need to learn to get value from the platform. That distinction, simple as it sounds, is harder to execute consistently than you might think. It’s way too easy to chase the shiny object rather than focus on the fundamentals. The programs that get it right are the ones that create the kind of customer confidence and product adoption that every SaaS company is ultimately chasing.
Well, this is it. You either stuck with me through this journey or cheated and skipped ahead to the ending. Either way I’m grateful for your readership and participation.
Missed an earlier article in this series? Catch up here:
Part 1: The Research and Why It Matters
Part 2: The Philosophy Question – Are You Teaching Features or Outcomes?
Part 3: Human Warmth vs. Scalability – A False Choice
Part 4: Currency is a Feature, Not a Footnote
Part 5: The Learner Experience Layer – Content Alone Is Not Enough
Leave a Reply