This article is Part 7 of my series on Customer Education from scratch.
The "big bang" launch, where a supposedly perfect, comprehensive programme is unveiled after months of secret development, is a recipe for failure. The goal of your initial launch is not to be perfect; it is to start learning from your users as quickly as possible. The key to sustainable growth is adopting an iterative mindset.
You have designed your journey, created your initial content, and selected your lean tech stack. Now, it's time to get your program into the hands of learners by launching an effective pilot.
If you like this article, and my other work, you can support me by buying me a coffee.Many thanks in advance!
Step 1: The Pilot: Your Foundation for Learning
Your first launch is a small, controlled experiment. Its primary purpose is to gather rich qualitative data and validate your core assumptions, not to generate statistically significant business impact. That comes later.
First, Manage Stakeholder Expectations: Before you do anything else, you must get internal buy-in for an iterative approach. Explain to stakeholders that the pilot is not a "beta" of a finished product, but a rapid learning exercise. Frame it as a low-risk way to ensure the final, scaled programme is effective and aligned with user needs, preventing wasted investment.
Define a Diverse Pilot Cohort: Select a small, purposefully diverse cohort to get well-rounded feedback. Include:
A Novice: To test if your core explanations are clear.
An Expert: To check for technical accuracy and identify subtle gaps.
A Friendly Follower: A loyal customer invested in your success.
Recruit and Incentivise Your Cohort: Give your pilot users a reason to participate. Offer a clear incentive, such as early access to new features, a direct line of communication with your product team, or a small discount on their next renewal.
Define Your Pilot's Learning Goals: Instead of focusing on quantitative metrics that are meaningless with a small sample size, define the critical assumptions you need to test. Your goals should sound like:
"Validate that our hands-on task is the most effective way to teach this concept."
"Confirm that the learning journey addresses the core problem for this user persona."
"Discover where users get confused or lose confidence in the onboarding module."
Establish a High-Fidelity Feedback Loop: Direct conversation is better than a simple survey. Ask probing questions:
"After reviewing this, what is the very next action you feel you should take?" (Tests if the content is actionable).
"Was there any point where you felt confused or that this content wasn't for you?" (Identifies clarity issues).
Step 2: Scale with Agile, Iterative Cycles
Once your pilot has validated your core approach, you can begin to scale. Adopt an agile methodology, using short work cycles (Sprints) and a Kanban board to visualise your workflow.
Each cycle should have a single, clear goal. To decide which goal to pursue, use a simple prioritisation framework, like an Impact vs. Effort matrix. When scoring "impact," consider factors like alignment with company goals, the number of users affected, and the potential to reduce support load. This helps you choose the work that delivers the most value for the least effort. Examples of cycle goals include:
"Launch the next module in the advanced learning journey."
"Improve the onboarding checklist based on pilot feedback."
"Curate and integrate three new articles to address a newly identified skills gap."
Step 3: Embed a Full-Circle Continuous Improvement Process
An education programme is a living product, not a static project. To ensure it remains effective, embed a process of continuous improvement.
Make Feedback Permanent: Keep the channels you opened during the pilot permanently available. Log all learner feedback and suggestions in a simple system to inform your future work cycles.
Close the Loop (at Scale): In the early days, a personal "thank you" for feedback is powerful. As your programme grows, this becomes untenable. Scale your communications by using release notes, newsletters, or in-app notifications to announce improvements based on user feedback.
Implement a Full Content Retirement Strategy: When content is no longer relevant, simply "archiving" it is not enough. A proper retirement process includes:
Identifying all internal and external links pointing to the old content.
Creating redirects to guide users to newer, more relevant material.
Communicating the retirement to internal teams who may have been using it.
Look Beyond Direct Feedback: Supplement direct user feedback with other data sources. Analyse support ticket trends, on-site search queries, and product usage analytics to get a complete picture of your users' needs.
This iterative methodology dramatically reduces risk and ensures your programme evolves based on real user data, builds momentum, and consistently demonstrates value to your stakeholders.
Your Challenge:
Define the scope for your first pilot launch. Who is the single, small group of customers you will release your Minimum Viable Learning Journey to? And what is the single most critical assumption you need to validate to prove your approach is on the right track?
What’s your take on today’s topic? Did I miss something, did something resonate?
If you found this post useful, subscribe to get more practical, no-fluff insights on learning and AI delivered to your inbox.