Performance Support
Performance support is a category of learning intervention designed to help employees complete a specific task or make a specific decision at the precise moment they need assistance. Unlike training, which builds capability in advance, performance support delivers targeted guidance within the workflow itself, reducing reliance on memory and enabling accurate task execution without prior knowledge recall.
The confusion between training and performance support is common and consequential. Training is designed to build durable knowledge and skills that an employee can carry forward, apply independently, and adapt across contexts. Performance support is not trying to do that. It is trying to help someone do one thing, correctly, right now.
This is the distinction that Bob Mosher and Conrad Gottfredson articulated through their Five Moments of Need framework, which identifies the moment of applying a skill as distinct from learning it for the first time or extending it. Performance support targets the apply, change, and solve moments specifically. A checklist that guides a compliance officer through a reporting workflow is not teaching that person about compliance regulation. It is ensuring they follow the right steps in the right order, under real time pressure, without error.
The question performance support asks is not "what should this person know?" but "what does this person need to do right now, and what would make them more likely to do it correctly?"
This reframing has significant implications for how learning functions allocate resources. Organizations that treat performance support as a lesser form of training consistently underinvest in it, expecting brief, informal assets to cover situations that actually require careful task analysis, content architecture, and delivery strategy. The result is performance support that exists in name only, while employees continue working around it.
The Formats Performance Support Takes in Practice
Performance support is not a single format. It describes a functional intention, applied across a wide range of media and delivery mechanisms. The appropriate format in any given situation depends on the nature of the task, the context in which it occurs, and the cognitive load the performer is already carrying.
- Job aids and reference cards: Single-page guides, decision trees, and quick reference cards employees retrieve on demand.
- Step-by-step guides: Structured walkthroughs for procedural tasks with low tolerance for error or variation.
- Embedded UI prompts: Tooltips, contextual help, and in-app guidance surfaced at the exact point of task execution.
- Workflow notifications: Timely alerts, reminders, and micro-guidance delivered at defined moments in a process.
- Performance dashboards: Data surfaces that give employees real-time visibility into performance against expectations.
- AI-assisted guidance: Conversational agents and recommendation engines that respond to task context dynamically.
The distinction between push and pull delivery is worth noting. Pull performance support is content the employee actively retrieves when they recognize a gap. Pull resources are only effective when employees know they exist and can locate them quickly. Push performance support is surfaced for the employee at the right moment, typically through workflow integration, without requiring any search behavior. Push mechanisms tend to be more reliable in high-stakes or high-frequency task environments, but they require closer integration with operational systems.
How Performance Support Is Actually Designed and Scoped
Effective performance support begins with task analysis, not content creation. The design process requires a clear understanding of what the employee is trying to accomplish, what information or guidance they are missing, what errors are most likely to occur, and what the consequences of those errors are. Without this foundation, performance support assets often answer the wrong questions, arrive in the wrong format, or provide a level of detail that either overwhelms the performer or leaves critical steps ambiguous.
- Task identification and scoping. Define the specific task or decision the asset will support. Avoid covering related topics. The narrower the scope, the more directly useful the output.
- Performer and context analysis. Understand the conditions under which the task occurs: time pressure, available devices, distractions, frequency, and the performer's level of familiarity. A field technician completing a safety check on a mobile device needs different support than a financial analyst working through a complex approval workflow at a desktop.
- Error mapping. Identify where mistakes typically happen and why. This is often the most valuable input a subject matter expert can provide, and it is frequently the piece most overlooked in content development.
- Format selection. Choose the delivery format based on context constraints, not preference. The format that works best for a customer service agent on a call is not the same as the format that works for a surgeon reviewing a pre-procedure protocol.
- Integration planning. Determine how the asset will be surfaced, maintained, and updated. Performance support that exists in an unlinked document repository fails. Support that is integrated into the tools employees already use has a fundamentally higher chance of being used.
Design principle: Performance support should assume no prior recall. If the performer has to remember something to use it correctly, the design has transferred cognitive load back to memory, which is exactly what performance support is trying to eliminate.
Embedding It in Real Workflows
The most technically sound performance support asset will fail if it is not positioned at the right point in the workflow. Integration is not a delivery afterthought. It is a design requirement. Understanding where in a process an employee encounters difficulty, makes a decision, or experiences a meaningful pause is the prerequisite for placing performance support where it will actually be encountered.
In practice, this means collaboration between learning designers and the teams who own operational systems: the CRM platform, the ERP, the quality management system, the production floor software. Many organizations have found that embedding performance support directly within enterprise tools, rather than in a separate learning platform, substantially increases access and usage rates. The difference in reach between a job aid posted to an intranet and a tooltip surfaced inside the transaction screen an employee uses twelve times a day is not marginal. It is the difference between an asset that exists and one that performs.
| Positioned outside workflow | Embedded in workflow |
| Employee interrupts task to search for guidance. High cognitive cost. Lower likelihood of use. Often located too late, after an error has already been made. | Guidance surfaces at the precise task moment. No search required. Maintains task context. Reduces time-to-correct-action and error frequency. |
| Common in intranet knowledge bases, SharePoint repositories, and standalone LMS resources. | Common in digital adoption platforms, in-app guidance layers, and CRM or ERP-integrated support. |
Timing matters as much as placement. Performance support that arrives after the step it governs has passed is not useful. In automated workflow environments, this requires mapping asset triggers to specific process events rather than general task categories. This level of precision is achievable, but it requires closer collaboration between L&D and technology teams than most organizations currently maintain.
Where Performance Support Breaks Down
Performance support fails in predictable ways. Understanding these failure patterns is as important as understanding its potential, because organizations that implement performance support without addressing these risks tend to accumulate large libraries of assets that are neither used nor maintained.
Common failure mode: Performance support is treated as a documentation task rather than a design task. Content is accurate but unusable under real task conditions, and no one is responsible for keeping it current.
The most pervasive failure is content that was accurate at launch and never updated. Organizations operating in dynamic environments, where processes, systems, regulations, and products change frequently, generate a constant stream of invalidation events for existing performance support assets. Without governance structures that connect process change owners to content update workflows, the support library begins to drift from operational reality. Employees who encounter outdated guidance quickly learn to distrust the system, and usage drops accordingly.
A second common failure is scope creep at the design stage. Performance support assets are often drafted by subject matter experts who are understandably reluctant to leave out relevant information. The result is job aids that have become reference documents, checklists that have become training modules, and in-app guidance that addresses three adjacent topics rather than the one the employee is trying to act on. The instructional design principle of task specificity requires discipline that is harder to maintain when content development happens without dedicated design oversight.
A third failure mode is discovery. Even well-designed performance support is ineffective if employees cannot locate it when they need it. Organizations that treat content organization as a secondary concern consistently report low voluntary access rates for performance support assets. The discoverability requirement differs from that of training. A learner can plan when to take a course. A performer needs guidance in the moment, which means the time available to locate it is measured in seconds, not minutes.
Enterprise Scale and the Complexity It Introduces
Performance support is conceptually straightforward at small scale. A single team, working with a clearly defined task environment and a limited set of roles, can produce, maintain, and distribute support assets with relatively modest coordination overhead. The complexity compounds rapidly as organizations grow, particularly when they operate across multiple geographies, languages, regulatory environments, and technology stacks.
At enterprise scale, the number of discrete task contexts that require dedicated support expands significantly. A global organization might have customer service operations across fifteen countries, each with distinct compliance requirements, local language needs, and regional product variations. The performance support assets required to cover these contexts are not fifteen translations of a single document. They are fifteen different content problems, some of which share structural components and some of which do not. Many organizations that have reached this scale extend their capabilities through modular content architecture and structured authoring practices, allowing core assets to be adapted across contexts without being rebuilt from scratch.
Localization is a particularly underestimated dimension of enterprise performance support. Accurate translation is a necessary condition, but it is not sufficient. A performance support asset adapted for a local market needs to reflect local process variations, regulatory language, job title conventions, and in some cases fundamentally different task workflows. Organizations that treat localization as a translation project consistently underestimate both the effort required and the downstream costs of support assets that do not fully apply to the contexts they are meant to serve.
Volume pressure is a related challenge. The demand for performance support assets in large organizations tends to outpace the capacity of centralized L&D functions to produce them, especially when process change velocity is high. Organizations that have successfully managed this pressure typically rely on a combination of distributed content ownership, where frontline managers or operations leads maintain assets within their domains, and centralized quality governance, where design standards are enforced at the template and review level rather than through central production. This hybrid model requires more sophisticated governance than most L&D teams initially anticipate.
Tools, Ecosystems, And What They Can and Cannot Do
The performance support technology landscape has expanded considerably in recent years. Digital adoption platforms enable in-application guidance to be built and deployed without engineering resources. Learning experience platforms increasingly support performance support formats alongside traditional course content. AI-powered knowledge management tools can surface contextually relevant guidance based on the employee's current activity. These capabilities are genuinely valuable, and they have lowered the barrier to entry for embedded performance support in ways that were not possible a few years ago.
The appropriate caution is that tools solve the delivery problem, not the design problem. A digital adoption platform can surface a tooltip at precisely the right moment in a workflow, but it cannot determine what that tooltip should say, how much guidance is sufficient, or whether the task it supports is being mapped correctly to the performer's actual experience. The same limitation applies to AI systems. A conversational agent that can answer questions about a product in natural language is only as useful as the knowledge base it draws on, and that knowledge base requires the same task analysis, content design, and governance infrastructure that any other performance support system requires.
Ecosystem integration is also more complex in practice than vendor materials typically suggest. Embedding performance support inside enterprise systems requires access to those systems at an architectural level, cooperation from IT security and procurement functions, and ongoing maintenance as the underlying platforms are updated. Organizations with mature digital operations tend to have clearer pathways for this kind of integration. Organizations still consolidating their technology landscape often find that performance support implementation becomes entangled in broader digital transformation timelines.
Frequently Asked Questions
What is performance support in L&D?
Performance support in L&D refers to on-demand resources that help employees perform tasks correctly at the moment of need. These resources may include checklists, job aids, quick guides, videos, decision trees, knowledge articles, or in-app prompts.
How is performance support different from training?
Training prepares employees before they perform a task, while performance support helps them during the task. Training builds knowledge and capability. Performance support helps employees apply that knowledge in real work situations.
What are examples of performance support?
Examples include a troubleshooting checklist for technicians, a call-flow guide for customer service teams, an in-app walkthrough for software users, a compliance decision tree, a product comparison sheet for sales teams, or a QR-code-enabled safety guide near equipment.
When should organizations use performance support?
Organizations should use performance support when employees need quick guidance, when tasks are complex or infrequent, when information changes often, or when errors can affect productivity, compliance, safety, or customer experience.
Can performance support replace formal learning?
Performance support can reduce the need for some forms of training, but it should not replace formal learning entirely. It works best when combined with training, practice, coaching, and assessment.
What tools are used for performance support?
Common tools include LMSs, LXPs, authoring tools, knowledge bases, digital adoption platforms, AI assistants, video tools, and enterprise search systems. The tool matters less than the quality, accuracy, accessibility, and relevance of the support content.
Why is performance support difficult to scale?
Performance support becomes difficult to scale when content ownership, SME review, localization, version control, searchability, and governance are not clearly managed. As the volume of assets grows, organizations need structured processes to keep resources accurate and usable.