This is Part 2 of an article series examining what I learned about customer education by completing ten professional certifications in thirty days. Links to all articles are included at the end of this one.
One of the most fundamental decisions any SaaS customer education program makes happens before a single word of content is written: are you teaching people how to use your product, or are you teaching them how to drive meaningful outcomes?
These sound like the same thing, but they are not.
When building my first customer education program I made this very mistake. The well-intentioned advice I was given was to take everything I knew about this product and put it into a course. What I ended up with was an encyclopedia of product information rather than a manageable learning experience. What I didn’t understand at the time was that my learners didn’t need to know every possible way to interact with every feature, they needed to learn how to drive outcomes as quickly as possible. My biggest takeaway from that experience was that there is a difference between being aware of every product feature and being able to use it purposefully.
One program I encountered during this certification journey made the same choice I did. Every feature was documented thoroughly. Every possible path to every possible function was explained in detail. From a completeness standpoint the program was impressive. From a learner standpoint it was exhausting. By the time I reached the third explanation of how to navigate to the same report through a different menu path I wasn’t learning – I was fast forwarding. (I also learned that any program can be much more amusing at 2x speed.)
Contrast that with the program from Anthropic, the AI platform provider. At no point did I feel like I was being walked through a feature list. Instead I was being introduced to a new way of thinking, one that just so happened to make their platform the most natural tool to leverage. What made their approach distinctive wasn’t just what they taught but what they chose not to teach. Rather than documenting every capability they focused on the concepts and principles that make AI useful in real-world professional contexts. This content was designed to change how you think, not just where to click. That’s a fundamentally different and more effective instructional philosophy.
The lesson for anyone building a SaaS customer education program is straightforward: your learners have a job to do and they need to be able to do it quickly and effectively. They want results – not exhaustive tours of every nook and cranny of your tool. Keep the curriculum focused on outcomes if you want to improve time to value and help your customers win.
If a learner completes your program and walks away with some level of awareness of every feature but unable to tackle their essential tasks, have you actually educated them? Or have you simply documented your product and checked the training box?
Something else I have learned along the way that is worth mentioning. No matter how well intentioned and/or designed a feature is sometimes it won’t resonate with your customers. Perhaps it duplicates a capability they have elsewhere or are not permitted to use for other reasons. Don’t ignore these features in your training, but don’t make them roadblocks either. My suggestion is to cover them in your curriculum but make those modules optional and place them towards the end of your program.
Put yourself in the learner’s shoes and design for what they need to accomplish. Customer education programs that do this well see the results where it matters most – in training KPIs, platform adoption rates, and ultimately in enterprise renewal and growth metrics. The encyclopedias belong on reference shelves collecting dust, not in your curriculum.
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