Enablement Strategy
User Enablement Channel Guide
A best practices framework for knowing when to use Pendo guides, your LMS, knowledge base, customer community, process docs, and async comms.
What channel should I use?
Answer two questions and get a recommendation with specific tactics for your scenario.
Step 1 -- What is the user's situation?
Select one
Step 2 -- What outcome do you need?
Select one
Use Pendo Guides
Use Your LMS
Use the Knowledge Base
Use the Customer Community
Use Multiple Channels
Use Case Matrix
Quick reference for every common enablement scenario -- with the right channel(s) for each.
| Scenario | Channel(s) | Why | Format / Length |
|---|---|---|---|
| First-time user app orientation | Pendo | Wayfinding tour of navigation -- orient, don't train; snooze option required | 3-5 steps |
| Release notification on login | Pendo | Intercepts user at the right moment; links out to KB article or LMS course | 1-2 steps |
| New feature spotlight | Pendo KB | Pendo announces in-app; KB article provides full feature detail for self-serve learners | 2-3 steps + article |
| User stuck mid-workflow | Resource Center KB | Always-on help hub surfaces KB articles at point of need without interrupting flow | Link-out |
| Deep workflow training | LMS | Structured course with sequential steps, certification, and completion tracking | Full course |
| Post-training in-app reinforcement | Pendo LMS | LMS delivers the course; Pendo fires on first use of that feature afterward | 1-3 steps |
| Pre-go-live readiness / certification | LMS | Gate system access behind prerequisite course completion | Full course |
| Beta feedback collection | Pendo Community | Pendo polls collect in-app sentiment; community captures richer discussion and ideas | 1-step poll + thread |
| User wants peer advice or workarounds | Community | Peer-to-peer knowledge sharing; no internal team resource required | Forum thread |
| User searching for answer independently | KB Community | KB for authoritative how-to; community for edge cases, tips, and user-generated context | Article / thread |
| Support ticket deflection | KB Resource Center Community | Surfacing the right KB article or community thread before a ticket is submitted | Search / link-out |
| Building user advocacy and product champions | Community | Power users answer questions, share use cases, and increase product stickiness organically | Ongoing engagement |
| Complex SOP documentation | Process Docs KB | Auto-capture workflows; publish to KB so users can self-serve and share in community | Step-by-step article |
| Scheduled release guide | Pendo KB | Pendo auto-publishes at go-live; KB article ready to link before anyone asks | 1-2 steps + article |
| Multi-language user support | Pendo KB | Pendo guide localization + KB articles translated for regional user segments | As needed |
Best Practices
Principles from practitioners across product, CS, and enablement -- what works at scale.
Keep Pendo guides 3-5 steps max
Drop-off happens fast after step 3. If you can't say it in 5 steps, it belongs in the LMS or KB -- not a tooltip carousel.
PendoSeparate wayfinding from training
Guides show users where things are. The LMS teaches how they work. The KB explains why and covers edge cases. Each channel has a lane.
All ChannelsAlways offer opt-in for tours
Give users a snooze option on onboarding guides. They may have logged in for a specific task and aren't ready for a walkthrough.
PendoSegment relentlessly
Target Pendo guides by role, first login, training cohort, or feature usage count. Generic guides shown to everyone get dismissed by everyone.
PendoEvery word in a guide earns its place
Evaluate every word. Over-messaging trains users to dismiss guides automatically. Concise and contextual wins every time.
PendoOne gatekeeper for guide publishing
A single person or small group pushes guides to production. Prevents sprawl, ensures consistency, and keeps the user experience from feeling noisy.
PendoKB is the long-form answer to every guide
Every Pendo guide that mentions a feature or process should have a corresponding KB article. The guide gets them started; the KB gets them proficient.
Knowledge BaseOptimize KB for search before anything else
Users who are stuck search first and ask second. KB articles that match natural language queries deflect tickets and reduce CSM interruptions before they start.
Knowledge BaseLet the community carry peer knowledge
Power users answering questions in a community forum scale your enablement without adding headcount. Seed early discussions and recognize contributors to build momentum.
CommunityConnect community back to KB
When a community thread solves a common problem, turn it into a KB article. When a KB article is missing depth, link to the community thread. The two reinforce each other.
Community KBLMS first, Pendo second
Gate system access behind prerequisite LMS courses. Let Pendo reinforce in-app the moment users encounter what they just learned.
LMSPre-schedule release guides and KB articles
Build and schedule both before the release ships. The Pendo guide fires at go-live; the KB article is already live when users search for it.
Pendo KBDon't script beta users
In beta, use light wayfinding only. Spotlighting specific features before users discover them naturally changes behavior and contaminates feedback signal.
PendoSet guide goals and track KB deflection
Tag features you want guides to drive. Track guide completion rates alongside KB article views and support ticket volume -- together they tell the full enablement story.
All ChannelsSurface KB and community before tickets
Link the Pendo Resource Center to KB search and community threads. Users who find answers in self-serve channels don't need to submit a ticket -- or wait for one to be resolved.
KB CommunityGotchas and Anti-Patterns
Common mistakes teams make across channels -- and how to avoid them.
Don't build a guide for every feature release
Product teams creating a guide every time they ship leads to sprawl, user fatigue, and dozens of unnamed drafts. Every guide needs strategic justification. The KB article should be the default; a Pendo guide is the exception for high-impact moments.
Name your guides immediately
Every Pendo subscription gets littered with "Unnamed Guide -- 2024-03-14" entries. Give it a real name the moment you create it. No exceptions.
Over-messaging trains users to ignore you
Too many guides, too many email blasts, too many community notifications -- users start dismissing everything. Govern all channels actively and retire content that's no longer serving a purpose.
A KB with no search strategy is just a filing cabinet
If users can't find the article, it doesn't exist. Write KB titles and summaries using the words users actually type when they're stuck -- not internal product terminology.
Don't launch a community and then go dark
A community with no moderation, no content seeding, and no response from the vendor dies fast. Assign an owner, post regularly, and respond to every thread in the first 90 days to establish momentum.
Don't use Pendo to replace training on complex workflows
Multi-step processes cannot be taught in a tooltip. Guides are for wayfinding and reinforcement -- not a substitute for structured courses. That path leads to incomplete comprehension and increased support load.
Beware of biasing beta users
Spotlighting features before users discover them organically changes their behavior. In beta, use Pendo for light navigation orientation only -- save the announcement guides for GA.
The Pendo launch URL doesn't restrict where a guide shows
The URL entered when building a guide is only your designer starting point -- page restrictions are a separate setting. Missing this is one of the most common guide configuration mistakes.
Tip: Community threads are your best KB source material
When a community question gets answered well, turn it into a KB article. When a KB article is too thin, link to the community thread for real-world context. The loop between them compounds over time.
Tip: Poll users with meaningful feature usage, not first-timers
Feedback from a user who's touched a feature once is noise. Segment sentiment polls to users with enough usage history to have a real opinion.
Tip: Tie Pendo + LMS data via your data warehouse
Guide completion and course completion can be joined in a shared data warehouse via Pendo Data Sync. Combined with KB view data and community engagement, you get a full-channel picture of user activation.
Your Enablement Channel Stack
Six channels, each with a distinct role. Clarity on the role prevents duplication and wasted effort.
Pendo Guides
In-app, in-the-moment
- Release notifications on login
- Wayfinding -- orienting users to navigation
- Feature spotlights -- here's what's new
- Behavioral triggers -- user going off happy path
- Beta feedback -- NPS polls, open text
- Resource Center -- always-on help hub
LMS
Structured learning, pre-login
- Pre-go-live prerequisite courses
- Deep workflow training on complex processes
- Certification and completion tracking
- Role-based learning paths
- Compliance and audit trails
Knowledge Base
Self-serve, always-on reference
- Feature how-to articles
- Troubleshooting guides
- Release notes and changelogs
- SOP documentation for complex workflows
- Ticket deflection -- answers before users ask
- Linked from Pendo Resource Center
Customer Community
Peer learning and advocacy
- Peer Q&A -- users helping users
- Use case sharing and best practices
- Beta feedback -- richer than polls alone
- Feature requests and idea voting
- Power user recognition and advocacy
- Feeds KB article creation
Process Documentation
SOP capture and reference
- Auto-capture complex workflows
- Publish to KB as searchable articles
- Link from Pendo Resource Center
- Share in community for peer reference
Async Comms
Push, broadcast communication
- Release announcements linked to KB articles
- Community digests -- top threads this week
- Complements in-app guides, doesn't replace them
How the channels connect
The power is in the handoffs between channels, not any single channel in isolation.
Pre-login: LMS prerequisite course → user earns system access
First login: Pendo wayfinding guide → 3-step nav orientation → snooze available
Stuck in-app: Resource Center → KB article or community thread → answer found, no ticket submitted
New release ships: Scheduled Pendo guide auto-publishes → links to KB release notes article → community thread seeded for discussion
Post-feature use (threshold reached): Pendo poll fires → in-depth feedback continues in community → feeds roadmap
Community solves an edge case: Thread promoted to KB article → KB article linked from Pendo Resource Center
Analytics layer: Pendo + LMS + KB views + community engagement joined in data warehouse → full-channel activation picture
User Journey Map
How the channels map to each stage of the user lifecycle -- from pre-onboarding to advocacy.
Stage 1 -- Pre-Onboarding
User has been provisioned but hasn't logged in yet. Goal is to build readiness before they touch the product.
Stage 2 -- First Login
User enters the product for the first time. Orientation and wayfinding take priority -- not deep training.
Stage 3 -- Active Learning
User is building skills on core workflows. This is where structured training matters most.
Stage 4 -- Day-to-Day Use
User is productive but occasionally gets stuck or encounters new functionality. Self-serve is the priority at this stage.
Stage 5 -- Power User and Advocate
User is proficient and becoming a resource for others. Community is now the primary channel -- they're adding value, not just consuming it.
Need help with your enablement strategy?
Balboa helps enterprise teams build the right mix of Pendo guides, training programs, and self-serve resources -- all connected into a seamless user journey.
Let's Talk