Chapter 03
Setting Goals
Understanding Your Current State
A strong "why" for your CEd program isn't and shouldn't be based on a whim. It's not what you or others on your team think your customers want. It's also not about blindly chasing every business target. Your strategy must be grounded in concrete data about where users struggle, how they behave in your product, and which business outcomes truly move the needle.
This begins with a candid look at your current state: the real-world signals, usage metrics, and objectives that reveal both gaps and opportunities. Are customers consistently asking support for the same help? Are some product features going completely unused? Do you see a correlation between certain workflows and higher renewals?
Understanding your current state involves asking yourself three key questions. By answering these questions, you'll uncover where your customer education efforts can deliver the greatest impact - for both customers and the business. Then, you can pinpoint the specific areas worth investing in, rather than chasing hunches.
Let's look at these questions below.
Q1. What are your customers telling you?
Your customers are often the first to reveal where your product—and your education—might be falling short. The signals they provide can pinpoint both obvious issues (e.g., setup challenges) and hidden gaps (e.g., undiscovered features). Gathering and interpreting these "customer signals" gives you a direct line to their pain points and desired outcomes.
Where to Look for Signals
| Signal Source | Where to Look | What to Notice |
|---|---|---|
| Support Requests | Support tickets, help desk chats, customer support emails | Repeated questions about the same features, stumbling blocks during onboarding or advanced usage, requests for missing functionality |
| Customer-Facing Teams | Insights from sales, solutions engineering, or CSMs. Notes and opportunity fields in CRMs also often capture info | Common themes or objections heard during demos and deal negotiations, patterns in success check-ins |
| Direct Feedback | Customer interviews, surveys, NPS responses, community forums | Recurring pain points, learning preferences, success blockers, feature requests, or praise for certain workflows |
I start by talking to customer-facing teams - CSMs, onboarding specialists, and sales engineers - because these people help me understand what the problems are from the inside. I follow this up with what's called an **'empathy audit'**. I speak directly with customers to learn about their pain points and those moments of *business joy*. This helps me go beyond internal assumptions about customer pain points which are often incorrect, or have gaps.
Dave Derrington
Customer Education Manager, VAST Data
How to Know Which Signals Are Important: The Role of Customer Jobs-To-Be-Done (JTBDs)
The signals you gather from customers need to fit into the larger picture of what customers want to accomplish with your product. Your customers don't care about your product or its features; they care about solving their problems with your product. They've purchased your product to get specific jobs done that help them succeed. Instead of treating signals as isolated complaints or feature requests, interpret them through your customers' Jobs To Be Done (JTBD). The JTBD framework helps you dig into three key areas:
- Desired Outcomes: What does success look like for the customer? For example, a project manager might want to streamline workflows to deliver projects on time and within budget.
- Barriers: What's stopping them from achieving these outcomes? Perhaps they're bogged down by inefficient processes or lack of visibility into team workloads.
- Your Role: How does your product help them overcome these barriers? Your solution might automate task tracking, provide real-time collaboration, or offer analytics that clarify progress.
By using the JTBD framework, you ensure that your educational content speaks directly to customer challenges.
Use this template to map your own customers' JTBD:
How & How Often To Keep Track of Signals
Instead of trying to track everything, a good approach is to have regular monthly (or quarterly) check-ins where you collect recurring themes from support tickets, community forums, and direct customer interviews. This helps you track emerging trends without getting lost in every small request. Here's how:
Top 3 Support Themes
Track your most common support requests each month. Look for patterns. Then map these to the possible education opportunities.Example
Theme: Dashboard setup difficulties
Volume: 30% of tickets
User Type: New customers
Source: Support tickets, onboarding calls
↳Onboarding: Major blocker to initial success
↳Adoption: Preventing exploration of advanced features
Customer Conversation Digest
Have your customer-facing teams submit their key observations, focusing on patterns that indicate specific needs.Example
Sales Team Insights: Prospects asking about training for their teams; Integration capabilities key decision factor in deals
↳Onboarding: Need clearer team rollout guidance
↳Adoption: Integration documentation gaps
Direct Feedback Summary
Focus on feedback that suggests knowledge gaps.Example
Common Themes: "Didn't know this feature existed!"; "Need help with best practices"; "Training materials outdated"
↳Feature discovery needs improvement
↳Retention: Missing advanced use case examples
This monthly check-in helps you spot trends without getting overwhelmed by data. Focus on identifying patterns that reveal where education can make the biggest impact.
AI Tips and Tools
Use this monthly check-in template to track these insights consistently:
Q2. What is your product usage telling you?
While direct feedback is invaluable, it can be incomplete. Some customers might not openly share their struggles, or they might not realize what they're missing. That's where product usage data comes in - giving you objective clues about how customers are interacting with your product. It reveals bottlenecks in the user journey, highlights underused features, and even points to the behaviors tied to renewals or expansions.
To help you get started, we've compiled some common product usage patterns by company growth stage you should dive into.
Product Usage Patterns by Company Growth Stage
For Early-Stage Product (0-2 years)
At this stage, companies typically haven't rolled out a formal CEd program - they're still building out their product and processes. And that's okay; you can still gather valuable insights by tracking how users interact with your product.
Key Usage Patterns to Track:
- First-time user behaviors
- Feature discovery paths
- Team expansion patterns
- Support contact rates
- Return visit frequency
| Understanding Initial Usage | Understanding Drop-offs |
|---|---|
| Do new users complete their first key action within 24 hours? | Do you know where users most commonly abandon your product? |
| Are users returning to your product after their first session? | Can you identify which features users never discover? |
| Can users complete basic tasks without contacting support? | Do you know what separates users who stay from those who leave? |
| Are users inviting team members to collaborate? | Are you able to predict which users might churn based on their behavior? |
Possible Education Opportunities:
- If new users fail to complete the primary setup or task within 24 hours → Focus on onboarding resources that guide them through essential workflows, ensuring they reach their first major "aha" moment quickly.
- If support channels see repetitive questions about fundamental features → Focus on making onboarding materials more accessible or self-service documentation to reduce reliance on support.
- If users stick to 1-2 features → Focus on bridging the gap between basic and advanced usage.
For Growth-Stage Products (2-4 years)
| Understanding Feature Usage | Understanding Adoption Patterns |
|---|---|
| Are users progressing beyond basic features? | Can you identify your power users? |
| Do teams use your product collaboratively? | Do teams expand usage over time? |
| Are users creating their own workflows or processes? | Are users discovering features on their own? |
| Do different user roles engage with appropriate features? | Do users access help or educational content proactively? |
Possible Education Opportunities:
- Analytics show users mostly sticking to basic functionalities → You may need to create step-by-step guides or short videos highlighting the benefits of advanced features.
- If you notice that one user group (e.g., admins) is highly active, while others (e.g., managers or end-users) barely use the platform → Create role-specific "getting started guides".
- If there is high usage but team members not being added (i.e. low expansion) → Focus on learning content that better explains the steps and benefits of usage across teams or use cases.
Enterprise-Ready Product (4+ years)
| Understanding Advanced Usage | Understanding Strategic Value |
|---|---|
| Are enterprise or high-level features (like role-based permissions, advanced analytics, or complex automations) being utilized fully? | Can teams demonstrate ROI from your product? |
| Do multiple departments or business units actively use the product to collaborate? | Are departments expanding usage and finding new applications for your solution? |
| Are users building custom solutions (e.g., specialized workflows, integrations, or APIs) within your platform? | Do customers integrate your product with other major tools in their tech stack (e.g., CRM, ERP, BI platforms)? |
| Is your product deeply embedded into critical business processes (e.g., daily standups, project reviews, or executive reporting)? | Are customers expanding use cases over time? |
Education Opportunities:
- If advanced features are underutilized → Focus on creating targeted tutorials or certifications to help users extract more value from your product.
- Low or nonexistent integration usage might indicate that users aren't aware of these capabilities → Focus on helping users better understand how to implement them.
- If you notice high adoption depth signalling product "stickiness", but no champions are emerging → Focus on creating paths to expertise and knowledge sharing
Track these patterns regularly alongside your customer signals check-in to build a complete picture of your customers' educational needs across their journey with your product.
🤖 AI Tips and Tools: Your product teams may already be using tools like Mixpanel, Amplitude, or Gainsight PX to track and monitor product usage. These tools provide AI-powered reports and insights across a host of usage patterns mentioned above. Gathering these reports from your product teams or getting access to these dashboards will make it easier and more efficient for you to glean information about product usage patterns.
Q3: What are your business goals?
Finally, you have to factor in the business outcomes that leadership truly cares about: reducing churn, increasing expansion revenue, lowering support costs, and so on. While your overall "why" includes customer needs and product data, you must also align with core company objectives if you want your CEd program to have real strategic value.
Business outcomes differ depending on your company's stage and priorities - some might focus on quick wins (like slashing support tickets), others on deeper adoption (like driving advanced feature usage). Mapping your customer signals and product usage findings to these outcomes ensures your CEd strategy supports the bottom-line goals of the organization.
Let's look at common goals and what they mean for education:
Reducing Time to Value
Get customers to see value fasterExample (Design Tool)
Business Goal: Reduce time to first design from 2 days to 2 hours
Education Needs:
↳First-project tutorial
↳Template gallery
↳Basic design principles
Increasing Feature Adoption
Get customers using more product capabilitiesExample (Analytics Platform)
Business Goal: Increase advanced feature usage by 40%
Education Needs:
↳Advanced feature discovery paths
↳Power user certification
↳Best practice guides
Reducing Support Costs
Help customers solve problems independentlyExample (Email Marketing Tool)
Business Goal: Reduce support tickets by 30%
Education Needs:
↳Searchable knowledge base
↳Video tutorials
↳Common issue guides
Growing Account Revenue
Expand usage within accountsExample (CRM Platform)
Business Goal: Increase average deal size by 25%
Education Needs:
↳Team expansion guides
↳Advanced workflow training
↳Integration tutorials
Common Business Goal Patterns By Company Stage
Here are typical business goals companies usually have across growth stages:
| Stage | Primary Goals | Common CEd Focus | Education Priority |
|---|---|---|---|
| Early Stage | Prove product-market fit, Reduce churn, Build initial user base | Onboarding and early Adoption | Getting customers to initial success quickly |
| Growth Stage | Scale efficiently, Increase feature adoption, Grow account value | Adoption and Retention | Helping customers unlock more value |
| Enterprise Stage | Protect large accounts, Drive strategic value, Enable self-service | Retention and Advocacy | Creating deep product expertise |
We as learning leaders have to learn how to break down business goals into actionable learning initiatives, "Oh, you want to increase adoption? Hey, you know what? We don't have a course that teaches users how our product does this really important thing." This doesn't mean there's a problem with the product. It's just that we haven't built something better into the product to overcome this obstacle. So it's the ‘human side of our product that we're imbuing learning with’.

Dave Derrington
Customer Education Manager, VAST Data
Here's a sample Goal Assessment Template that you can use to start mapping your business goals. You can build on this to create your own.
Goal Assessment Template
Current Business Priority:
↳Activation/Time to Value
↳Feature Adoption
↳Support Cost Reduction
↳Account Growth
↳Other
Success Metrics (repeat for each):
↳Current: _____
↳Target: _____
↳Timeline: _____

