---
name: product-education
description: "Build product education that raises activation, adoption and retention: help centres organised around jobs, task-based articles, contextual in-product help, short tutorial videos, academy courses and learning paths, certifications, webinars and office hours, community Q&A, maintenance after releases and impact on tickets and behaviour. Use whenever someone asks about a help centre, knowledge base, product academy, customer education, tutorial videos, certifications, reducing support tickets through self-service or teaching users to adopt features."
license: CC-BY-4.0
metadata:
  author: Afeez Adebayo
  author_url: https://afeezadebayo.com
  author_linkedin: https://www.linkedin.com/in/afeez-adebayo/
  author_x: https://x.com/za_icon
  source: https://afeezadebayo.com/skills-md/marketing/product-led-growth/product-education/
  category: marketing
  subcategory: product-led-growth
  version: "1.0.0"
  created: "2026-10-10"
  updated: "2026-10-10"
---

# Product Education and Academy

In product-led businesses, education replaces much of what a salesperson or trainer would do: help centres answer questions at the moment of need, short videos show how to get value, academies and certifications turn users into experts and advocates, and webinars and office hours support teams adopting the product. Good education raises activation, feature adoption and retention while lowering support costs. Poor education is a help centre full of outdated articles nobody can find.

This skill builds product education programmes: help centre structure, contextual help in the product, video tutorials, academies and courses, certifications, webinars and office hours, community education, search and maintenance, and measurement against activation, adoption, retention and support.

## Operating principles
1. **Answer the question in context.** Help should be available where users get stuck, inside the product.
2. **Teach outcomes, not buttons.** Organise around jobs users want to do, not menu items.
3. **Short first, deep when needed.** Quick answers and two-minute videos before long courses.
4. **Keep it current.** Outdated help is worse than none.
5. **Measure impact on behaviour.** Activation, adoption, retention and ticket deflection, not just views.

## Education formats
| Format | Best for | Notes |
|---|---|---|
| Help centre articles | Specific how-to questions | Task-based titles, screenshots, search-friendly |
| In-product help widget | Questions while working | Suggest articles based on page |
| Short tutorial videos | Showing workflows | 1 to 3 minutes, captions, chapters |
| Academy courses | Deeper skills and best practices | Modules by role or outcome |
| Certifications | Power users, partners, consultants | Builds advocates and an ecosystem |
| Webinars and office hours | Live help, new features | Recordings repurposed |
| Community Q&A | Peer answers at scale | Moderated, linked to help centre |
| Templates with guidance | Learning by doing | Embedded tips |

## When to use, and when not to
Use it when support tickets repeat the same questions, when activation or adoption is limited by understanding, when launching complex features, when building a partner or consultant ecosystem and when help content is outdated.

Don't use it for marketing content aimed at prospects (the Content, Copy and PR skills) or onboarding flows (`in-product-onboarding`), though they should link together.

## Inputs to ask for, in one message
1. Current help centre, videos, courses and their analytics.
2. Top support ticket topics.
3. Activation and feature adoption data.
4. Search queries inside the help centre, including failed searches.
5. Roles and segments of users.
6. Team capacity for writing, video and maintenance.

## Workflow

### Step 1. Find the gaps
Top ticket topics, failed help searches, features with low adoption and onboarding drop-offs.

### Step 2. Structure around jobs
Categories by outcome ("Set up your workspace", "Automate reporting") rather than menu names.

### Step 3. Write task-based articles
Titles phrased as questions or tasks, steps with screenshots, short videos where helpful.

### Step 4. Add contextual help
Link help from relevant screens; a help widget that suggests articles by page.

### Step 5. Build learning paths
Courses by role or goal: getting started, admin, advanced workflows.

### Step 6. Add live education
Webinars for launches, office hours for questions, recordings in the academy.

### Step 7. Consider certification
For power users, partners and consultants who recommend the product.

### Step 8. Maintain
Owners per section, review after every release, retire outdated content.

### Step 9. Measure
Ticket deflection, help search success, article ratings, course completion and their link to activation, adoption and retention.

## Article template
```
Title: How to [task]
Who this is for and when you need it (1-2 sentences)
Before you start (permissions, plan)
Steps (numbered, with screenshots)
Tips and common problems
Related articles
Was this helpful? (rating)
```

## Help centre structure example
| Category | Example articles |
|---|---|
| Get started | Create your workspace, invite your team, import data |
| Build reports | Create a dashboard, schedule a report, share a live link |
| Automate work | Set up alerts, connect integrations, create rules |
| Manage your account | Billing, roles and permissions, SSO |
| Troubleshooting | Data not syncing, missing permissions, login problems |

## Video guidelines
- One task per video, one to three minutes.
- Show the result first, then the steps.
- Captions and chapters.
- Re-record when the interface changes significantly.
- Embed videos in the matching help article and in-product screens.

## Metrics
| Metric | Why |
|---|---|
| Help search success rate | Findability |
| Failed searches | Content gaps |
| Article helpfulness ratings | Quality |
| Ticket volume on covered topics | Deflection |
| Course completion | Engagement with deeper learning |
| Activation and adoption of learners vs non-learners | Behaviour change |

## Maintenance routine
- Each release lists affected articles and videos.
- Owners update content before or at launch.
- Quarterly review of top articles and lowest-rated content.
- Retire or redirect outdated articles.
- Track last-reviewed dates on every article.

## Certification programmes
Certifications work best for power users, admins, partners and consultants who recommend or implement the product. Keep them practical (real tasks, not memorised menu names), free or low-cost for customers, with badges people can share on LinkedIn and a public directory of certified experts. Certified users often become champions inside their companies and a source of referrals.

## AI help assistants
If you add an AI assistant to help content, ground it in current, reviewed articles, show sources, let users rate answers and route unanswered questions to support. Review common answers regularly, because outdated articles produce outdated answers.

## Office hours
A regular open session where users bring questions builds trust, surfaces confusing areas of the product and produces recordings and new help articles from real questions.

## Edge cases and judgement calls
| Situation | What to do |
|---|---|
| Fast-changing product | Short articles, version notes and quick reviews after releases |
| Many user roles | Role-based learning paths |
| Enterprise customers | Admin guides, training sessions, certification for champions |
| Several languages | Translate top articles first; localise screenshots |
| AI help assistants | Ground answers in current help content; review answers for accuracy |

## Handoffs to related skills
- Onboarding: `in-product-onboarding`
- Feature adoption: `feature-adoption`
- In-app help messages: `in-app-messaging`
- Community: the Social Media `community-building` skill
- Video: the Social Media `youtube-seo-growth` skill
- Help content in search and AI answers: the Content SEO and AEO & GEO skills

## Worked example
An analytics product received hundreds of tickets a month on the same setup questions, and many users never built a second dashboard. The team restructured the help centre around jobs, rewrote the top 40 articles with task titles, screenshots and two-minute videos, added contextual help links on setup screens, launched a free academy with a getting-started path and an advanced reporting course, and ran monthly office hours. Setup tickets fell substantially, help search success improved and users who completed the getting-started course activated and retained at higher rates.

## Output format
```
# Product education plan: <product>, <date>
## Gaps (tickets, failed searches, adoption)
## Help centre structure
## Contextual help placements
## Learning paths and courses
## Live education and certification
## Maintenance process
## Metrics
```

## Common mistakes
- Help organised by menu items, not tasks.
- Outdated articles after releases.
- Help only outside the product.
- Long courses before quick answers.
- Measuring views instead of deflection and adoption.

## Questions to ask before you build
- What do users ask support most often?
- What do users search for in help and fail to find?
- Which features need education to be adopted?

## Self-check before you answer
- Is content organised around jobs?
- Is help available in context?
- Is there a maintenance process?
- Is impact measured on behaviour and tickets?

## Further reading
- Nielsen Norman Group on help and documentation: https://www.nngroup.com/articles/help-and-documentation/

---
Created by Afeez Adebayo, Marketing, SEO & Growth Expert
Website: https://afeezadebayo.com
LinkedIn: https://www.linkedin.com/in/afeez-adebayo/
X: https://x.com/za_icon
Source: https://afeezadebayo.com/skills-md/marketing/product-led-growth/product-education/

Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). You may copy, share and adapt this skill, including for commercial use, as long as you credit Afeez Adebayo and link to the source URL above. Keep this notice in any copy or adapted version.