Performance Support and Job Aids: Complete Guide to Workflow Learning [2026]

Traditional training happens before the job. Performance support happens during the job. Organizations that embed learning into workflow see 63% higher productivity, 71% fewer errors, and 58% faster task completion—because employees get exactly what they need, exactly when they need it.

This comprehensive guide explores performance support and job aids: what they are, why they work, and how to design workflow learning that transforms employee performance. For foundational training design, see our guide on creating effective online training programs.

What is Performance Support?

Performance support provides just-in-time information and guidance to help employees complete tasks at the moment of need. Rather than requiring prior training and recall, it delivers:

• Immediate access to information
• Step-by-step guidance during tasks
• Context-specific help
• Embedded in workflow
• Available on-demand

The 5 Moments of Need

Dr. Conrad Gottfredson's framework identifies when employees need support:

1. Learning for the first time (New)

• Onboarding new employees
• Introducing new systems or processes
• Teaching novel skills
• Initial training

2. Learning more (More)

• Expanding knowledge
• Building advanced capabilities
• Deepening expertise
• Continuous development

3. Applying what you've learned (Apply)

• Performing infrequent tasks
• Using rarely-needed skills
• Executing complex procedures
• Following policies

4. When things go wrong (Solve)

• Troubleshooting errors
• Diagnosing problems
• Finding solutions
• Recovery procedures

5. When things change (Change)

• Adapting to updates
• New versions or features
• Process modifications
• Organizational changes

Traditional training addresses moments 1 and 2 (New and More).

Performance support excels at moments 3, 4, and 5 (Apply, Solve, Change)—which represent 80% of workplace learning needs.

Why Performance Support Works

The science and business case for workflow learning:

Cognitive Benefits

Reduces cognitive load:

• External reference vs. memory recall
• Focus on task, not remembering steps
• Fresh information vs. forgetting
• Confidence through support

Enables complex performance:

• Break complex tasks into steps
• Provide guidance at decision points
• Offer calculations and tools
• Support without expertise

Accelerates learning:

• Learning through doing
• Immediate application
• Contextual understanding
• Repetition builds retention

Research from Gartner shows employees using performance support learn new tasks 50% faster than those relying on training alone.

Business Impact

Improved productivity:

• 63% faster task completion
• Less time searching for information
• Fewer interruptions to workflow
• Reduced dependency on experts

Better quality:

• 71% reduction in errors
• Consistent process execution
• Compliance with standards
• Fewer costly mistakes

Cost efficiency:

• Reduce training time by 40-60%
• Lower support call volume
• Decrease reliance on formal courses
• Just-in-time vs. just-in-case learning

Employee experience:

• Reduced frustration
• Increased confidence
• Greater autonomy
• Less disruption to work

Types of Performance Support

Different formats serve different needs:

1. Job Aids

Quick reference tools for specific tasks:

Checklists:

• Step-by-step task lists
• Quality verification
• Process compliance
• Pre-flight inspections

Example: Surgical safety checklist

• Patient identity confirmed ✓
• Procedure site marked ✓
• Equipment sterilized ✓
• Allergies reviewed ✓

Quick reference cards:

• Key information at-a-glance
• Keyboard shortcuts
• Common codes or formulas
• Emergency procedures

Decision trees:

• Guide complex decision-making
• If/then logic flows
• Diagnostic paths
• Routing and escalation

Templates and forms:

• Structured formats
• Reduce errors
• Ensure completeness
• Standardize outputs

Worksheets and calculators:

• Mathematical computations
• Data collection
• Analysis frameworks
• Planning tools

2. Digital Performance Support

Technology-enabled workflow assistance:

Embedded help:

• Tooltips and hover hints
• Contextual help panels
• Inline instructions
• Guided tours

Example: Software tooltip Hovering over "Merge cells" button shows: "Combine selected cells into one. Use for headers or labels. Note: Only the top-left value is retained."

Search and knowledge bases:

• Searchable repositories
• FAQ databases
• Troubleshooting guides
• Policy and procedure libraries

Chatbots and virtual assistants:

• Natural language queries
• Instant answers
• Conversational guidance
• Escalation to humans

Mobile apps:

• Field reference guides
• Photo-based instructions
• Augmented reality support
• Offline access

3. Workflow Learning

Learning integrated into business systems:

In-application guidance:

• Walkthroughs and wizards
• Progressive disclosure
• Smart defaults
• Validation and warnings

Digital adoption platforms (DAPs):

• Overlay guidance on existing software
• Interactive walkthroughs
• Task automation
• Analytics on user behavior

Examples: WalkMe, Whatfix, Pendo

Adaptive interfaces:

• Personalized based on role
• Hide complexity until needed
• Recommend next actions
• Learn from user behavior

Automated workflows:

• Reduce manual steps
• Pre-populate data
• Sequential guidance
• Error prevention

4. Expert Access

Human performance support:

Help desks and hotlines:

• Phone or chat support
• Expert advice
• Troubleshooting assistance
• Escalation pathways

Mentoring and coaching:

• Scheduled guidance
• Skill development support
• Career advice
• Problem-solving partnership

Communities of practice:

• Peer-to-peer help
• Discussion forums
• Shared knowledge
• Collective expertise

Shadow systems:

• Side-by-side support
• Temporary assistance
• Skill transfer
• Confidence building

Designing Effective Job Aids

Create performance support that actually works:

Design Principles

1. Minimal and focused:

• One task or concept per aid
• Remove non-essential information
• Clear, concise language
• No extraneous design elements

Bad example (cluttered): "Welcome to our comprehensive guide for the quarterly expense reporting process. This document will walk you through the many steps involved in submitting your expenses, including important policies you should be aware of, helpful tips from experienced employees, and common mistakes to avoid..."

Good example (focused): "Expense Report Submission

1. Open Finance Portal
2. Click 'New Expense Report'
3. Enter expenses with receipts
4. Submit to manager Due: Last day of quarter"

2. Action-oriented:

• Start with verbs
• Imperative voice
• Numbered steps
• Clear outcomes

3. Easily accessible:

• Available when needed
• Quick to find
• Searchable
• No login barriers when possible

4. Visual and scannable:

• White space for readability
• Bullets and numbers
• Icons and images
• Highlighted key information

5. Tested with users:

• Watch someone use it
• Refine based on confusion
• Validate effectiveness
• Iterate continuously

Step-by-Step Process Aids

Structure for procedures:

Title: Clear, descriptive task name

Purpose/When to use: Brief context

Steps:

1. First action (with result expected)
2. Second action (with decision point if applicable)
3. Third action ...

Tips or warnings: Critical information

Related resources: Links to more detail

Example: Password Reset Job Aid

Resetting Employee Passwords

When to use: Employee forgot password and can't login

Steps:

1. Open Admin Portal → Users section
2. Search for employee by name or email
3. Click employee name → Account tab
4. Click "Send Password Reset Email"
5. Confirm employee received email (check spam)

⚠️ Warning: Only IT staff can reset passwords. Don't share temporary passwords via email or chat.

Related: Account Security Policy | Locked Account Procedure

Decision Support Aids

Structure for complex choices:

Decision tree format:

• Start with initial question
• Branch based on yes/no or multiple choice
• Follow path to recommendation
• Include rationale when helpful

Example: Customer Refund Decision Tree

Can we issue a refund?

Purchase within 30 days?

• No → Explain return policy, offer store credit
• Yes → Continue

Product unopened/unused?

• No → Defective?
  • Yes → Issue refund + escalate to QA
  • No → Offer exchange only
• Yes → Continue

Original payment method available?

• Yes → Issue refund to original method
• No → Issue store credit

Matrix format:

For multiple criteria decisions:

Reference Information Aids

Structure for quick lookup:

Tables and charts:

• Organized logically (alphabetically, by frequency, by category)
• Clear headers
• Searchable when digital
• Highlighted key info

Example: Email Etiquette Quick Reference

Key codes or formulas:

• Most common listed first
• Clear labeling
• Examples shown
• Calculation tools embedded

Example: Discount Code Reference

• FIRST15: 15% off first purchase (new customers only)
• LOYAL20: 20% off for loyalty members
• SAVE25: 25% off orders > $100
• FREESHIP: Free shipping, no minimum

Enter at checkout. Cannot combine offers.

Implementing Performance Support

Build workflow learning into your organization:

Step 1: Identify Performance Support Opportunities

Analyze where traditional training falls short:

High-frequency tasks:

• Infrequent but critical procedures
• Complex multi-step processes
• Tasks with many exceptions
• Compliance requirements

Common errors:

• Where mistakes occur regularly
• Quality issues
• Safety incidents
• Customer complaints

Information searches:

• Frequent help desk tickets
• Repeated questions to managers
• Time spent finding information
• Workflow interruptions

Performance support indicators:

✓ Task performed infrequently (< monthly) ✓ Steps are procedural, not requiring judgment ✓ Information is stable (doesn't change weekly) ✓ Immediate access improves speed or quality ✓ Errors have significant consequences ✓ Currently requires interrupting others

Data sources:

• Help desk ticket analysis
• Process error rates
• Training evaluation feedback ("I forgot how to...")
• Time-motion studies
• Employee interviews
• Manager observations

Step 2: Choose Appropriate Support Types

Match format to need:

Simple procedures → Checklist or quick reference

• Linear steps
• Few decision points
• Quick completion

Complex decisions → Decision tree or flowchart

• Multiple paths
• Conditional logic
• Requires judgment

Infrequent software tasks → Embedded help or walkthrough

• Software-based
• Visual guidance helpful
• Step-by-step needed

Troubleshooting → Search knowledge base or decision tree

• Many possible causes
• Diagnostic approach
• Solution database

Calculations → Calculator or worksheet

• Mathematical operations
• Data input and output
• Accuracy critical

Policies and reference info → Searchable database

• Lots of information
• Lookup by keyword
• Frequently updated

Step 3: Design and Develop

Creation process:

1. Work with SMEs:

• Interview expert performers
• Observe tasks being done
• Document actual steps (not idealized)
• Identify decision points and exceptions

2. Draft initial version:

• Use appropriate format
• Follow design principles
• Keep it minimal
• Include only what's needed at moment of use

3. Test with users:

• Watch someone perform task using aid
• Note where they struggle or get confused
• Ask what's missing or unclear
• Don't intervene—observe

4. Refine based on feedback:

• Clarify confusing language
• Add missing steps
• Remove unnecessary detail
• Improve visual design

5. Publish and promote:

• Make easily accessible
• Train on how to find it
• Integrate into workflow
• Communicate availability

Development tips:

Start simple:

• Text document or PDF
• Basic formatting
• Quick to create
• Easy to update

Use templates:

• Consistent structure
• Faster development
• Professional appearance
• Reusable across organization

Collaborate digitally:

• Google Docs or Confluence
• Version control
• Multiple contributors
• Easy updates

Leverage visuals:

• Screenshots with annotations
• Icons for actions
• Arrows showing flow
• Color coding for emphasis

Step 4: Integrate into Workflow

Make support frictionless:

Embed where work happens:

• Links within software
• Posted at workstations
• On mobile devices
• In communication tools (Slack, Teams)

Examples:

• CRM system: "How to escalate" link in support ticket interface
• Manufacturing: Laminated card at each workstation
• Sales: Job aids in sales enablement app
• Remote workers: Searchable knowledge base bookmarked

Reduce access barriers:

• No login required (if not sensitive)
• Mobile-friendly formats
• Offline availability when needed
• Fast load times

Make discoverable:

• Centralized repository
• Effective search
• Categorization and tagging
• Links from related content

Promote awareness:

• Manager communication
• Team meetings
• Email announcements
• Onboarding introduction

Step 5: Maintain and Update

Keep content current:

Establish ownership:

• Assign content stewards
• SME responsibility
• Regular review schedule
• Update authority

Monitor for changes:

• Process updates
• System changes
• Policy modifications
• New regulations

Update workflow:

• Change request process
• SME review and approval
• Version control
• Communication of updates

Track and retire:

• Usage analytics
• Outdated content removal
• Archive vs. delete
• Redirect to current versions

Best practice: Review all job aids quarterly, update as needed, archive those no longer used.

Performance Support Strategies

Advanced approaches for workflow learning:

Layered Support

Progressive detail:

Layer 1: Minimal reminder

• For experienced users who need quick reminder
• Checklist or brief steps
• Fast reference

Layer 2: Detailed procedure

• For occasional users who need full guidance
• Step-by-step with screenshots
• Explanations included

Layer 3: Comprehensive resource

• For learning and troubleshooting
• Background information
• Examples and scenarios
• Related topics

Example: Software Feature Support

Layer 1 - Quick tip: "Create report: Data → Reports → New → Select template → Generate"

Layer 2 - Step-by-step: Detailed walkthrough with screenshots of each step, field explanations, common options

Layer 3 - Full guide: Report types, customization options, scheduling, sharing, troubleshooting, best practices

Implementation:

• Start with minimal aid visible
• "Learn more" links expand to detailed
• "Full guide" available but not required

Adaptive Performance Support

Personalized based on user:

Role-based:

• Show relevant information for job function
• Hide irrelevant options
• Customized workflows
• Appropriate detail level

Skill-based (aligned with skills-based learning):

• Beginners get more guidance
• Experts get minimal interference
• Adaptive based on behavior
• Progressive reduction of support

Context-aware:

• Anticipate next need
• Proactive suggestions
• Relevant to current task
• Time or location-sensitive

Technology enablers:

Digital adoption platforms:

• Overlay guidance on existing apps
• Track user behavior
• Adapt based on proficiency
• A/B test different approaches

AI-powered assistants:

• Natural language queries
• Conversational guidance
• Learning from interactions
• Predictive support

Embedded Learning

Workflow-integrated development:

Learn by doing:

• Minimal upfront training
• Guided first-time use
• Support for practice
• Gradual competency building

Example: New employee learning CRM

Traditional approach:

• 4-hour CRM training class
• Practice exercises
• Reference manual
• Start using next week (forgetting already started)

Embedded learning approach:

• 15-minute CRM overview
• Performance support for each task
• Guided walkthroughs on first use
• Tooltips and help always available
• Learn features as needed

Microlearning moments:

• Brief tips at point of use
• "Did you know?" features
• Best practice suggestions
• Shortcuts and efficiency tips

Certification through performance:

• Tasks completed successfully
• Quality metrics met
• Support usage decreases
• Competency demonstrated

Community-Powered Support

Leverage collective knowledge:

User-generated content:

• Employees create and share tips
• Real-world examples
• Workflow hacks
• Problem solutions

Peer assistance:

• Internal Q&A platforms (like Stack Overflow)
• Expert networks
• Communities of practice
• Mentoring pairs

Curated wisdom:

• Best practices surfaced
• Most helpful answers highlighted
• Expert validation
• Continuous improvement

Tools:

• Slack or Teams channels
• Enterprise social networks (Yammer, Workplace)
• Knowledge management systems (Confluence, Notion)
• Dedicated community platforms

Technology for Performance Support

Platforms and tools:

Digital Adoption Platforms (DAPs)

Overlay guidance on existing software:

Key capabilities:

• Interactive walkthroughs
• Contextual tooltips
• Task automation
• In-app announcements
• Analytics on user behavior

Leading platforms:

WalkMe:

• Enterprise-focused
• Robust analytics
• Multi-application support
• Workflow automation

Whatfix:

• Self-service creation
• Interactive guides
• Performance support and training
• Content analytics

Pendo:

• Product analytics + guidance
• In-app messaging
• User feedback
• Feature adoption tracking

Appcues:

• User onboarding
• Feature announcements
• Targeted tooltips
• Easy implementation

Use cases:

• Software onboarding
• Feature adoption
• Process compliance
• Change management
• Support deflection

Knowledge Management Systems

Centralized information repositories:

Core features:

• Content creation and editing
• Search and discovery
• Organization and structure
• Version control
• Access permissions

Popular platforms:

Confluence (Atlassian):

• Team collaboration
• Structured spaces
• Integration with Jira
• Templates and macros

Notion:

• Flexible workspace
• Databases and pages
• Team wiki functionality
• Modern interface

SharePoint:

• Enterprise document management
• Intranet capabilities
• Microsoft ecosystem integration
• Robust permissions

Guru:

• Browser extension
• AI-powered search
• Verification workflows
• Slack/Teams integration

Best practices:

• Consistent structure and templates
• Clear naming conventions
• Regular content review
• Search optimization
• Easy contribution process

Chatbots and Virtual Assistants

Conversational support:

Capabilities:

• Natural language understanding
• Answer common questions
• Guide through processes
• Escalate to humans when needed
• Learn from interactions

Implementation approaches:

FAQ bots:

• Answer predefined questions
• Keyword matching
• Quick setup
• Limited flexibility

AI-powered assistants:

• Understand intent
• Handle variations
• Contextual responses
• Continuous learning

Hybrid (bot + human):

• Bot handles simple queries
• Seamless handoff to agent
• Human supervision
• Best of both worlds

Platforms:

• Microsoft Bot Framework
• IBM Watson Assistant
• Google Dialogflow
• Enterprise solutions (ServiceNow Virtual Agent, Salesforce Einstein)

Mobile Performance Support

Field and frontline worker support:

Mobile-optimized features:

• Offline access
• Quick search
• Photo/video instructions
• Voice input
• GPS-based content

Delivery methods:

Native apps:

• Best performance
• Device integration
• Offline capability
• App store distribution

Progressive web apps:

• No installation needed
• Cross-platform
• Updates instantly
• Offline with service workers

Mobile-responsive sites:

• Universal access
• Easy maintenance
• No app approval process
• Immediate availability

Use cases:

• Field service technicians
• Retail store associates
• Healthcare providers
• Manufacturing workers
• Remote teams

Measuring Performance Support Impact

Track workflow learning effectiveness:

Usage Metrics

Adoption and engagement:

Access frequency:

• Number of users
• Sessions per user
• Repeat usage rate
• Time spent with support

Content popularity:

• Most accessed job aids
• Search queries
• High-traffic pages
• Underutilized resources

Search analytics:

• Common queries
• Failed searches
• Time to find information
• Search abandonment rate

DAP analytics:

• Walkthrough completion rates
• Tooltip engagement
• Feature adoption
• Drop-off points

Performance Outcomes

Task effectiveness:

Speed improvements:

• Time to complete tasks
• Reduced search time
• Faster problem resolution
• Decreased rework

Quality improvements:

• Error rate reduction
• Compliance adherence
• Customer satisfaction
• First-time-right percentage

Before/after comparison:

Measure with and without performance support:

• Control group vs. support group
• Same users before/after implementation
• A/B testing different approaches

Example metrics:

Business Impact

Operational efficiency:

Productivity gains:

• Output per employee
• Tasks completed per day
• Revenue per employee
• Cost per transaction

Support cost reduction:

• Fewer help desk tickets
• Reduced training time
• Less supervisor intervention
• Decreased reliance on experts

Quality and compliance:

• Defect rates
• Audit findings
• Safety incidents
• Customer complaints

Employee experience:

• Job satisfaction scores
• Confidence levels
• Perceived support
• Retention rates

ROI Calculation

Benefits quantification:

Time savings:

• Hours saved per employee per month × number of employees × hourly cost
• Reduced training time × number of trainees × hourly cost + trainer cost

Error reduction:

• Error cost × error reduction percentage × volume

Support cost savings:

• Help desk tickets reduced × cost per ticket
• Training hours reduced × cost per hour

Example calculation:

Scenario: Performance support for customer service software

Benefits:

• 500 employees save 30 min/week = 250 hours/week
  • 250 × 52 weeks × $25/hour = $325,000/year
• Reduced training from 8 hours to 2 hours for new hires
  • 100 new hires × 6 hours × $25 = $15,000/year
• Help desk tickets reduced from 200 to 50 per month
  • 150 tickets × 12 months × $15/ticket = $27,000/year

Total benefits: $367,000/year

Costs:

• Digital adoption platform: $50,000/year
• Content development: $30,000 (one-time)
• Maintenance: $10,000/year

Total first-year costs: $90,000

ROI: ($367,000 - $90,000) / $90,000 = 308%

Common Challenges and Solutions

Overcome performance support obstacles:

Challenge 1: Content Creation Overload

The problem: Creating performance support for every task is overwhelming and unsustainable.

Solutions:

Prioritize strategically:

• Start with highest-impact tasks
• Focus on frequently-asked questions
• Address costly errors first
• Target new employee needs

Use 80/20 rule:

• 20% of tasks drive 80% of support needs
• Analyze help desk data
• Ask frontline managers
• Survey employees

Leverage templates:

• Standard formats for common aid types
• Quick to populate
• Consistent structure
• Scalable across organization

Empower SMEs:

• Train subject matter experts
• Provide creation tools
• Review and approve (vs. create from scratch)
• Recognize contributions

Start simple:

• Text documents before sophisticated graphics
• Iterate based on feedback
• Perfect is the enemy of done
• Continuous improvement over time

Challenge 2: Adoption and Awareness

The problem: Created great job aids, but employees don't know they exist or don't use them.

Solutions:

Make highly visible:

• Embed in workflow tools
• Add to bookmarks/favorites
• Post physically at workstations
• Include in email signatures

Integrate with onboarding:

• Introduce during new hire training
• Reference in initial tasks
• Include in welcome materials
• Demonstrate value early

Manager advocacy:

• Train managers to reference aids
• "Check the job aid first" culture
• Model usage in coaching
• Recognize when employees use support

Promote through multiple channels:

• Team meetings
• Email announcements
• Internal communications
• Help desk referrals

Demonstrate time savings:

• Show how much faster with support
• Share success stories
• Quantify productivity gains
• Celebrate efficiency wins

Challenge 3: Keeping Content Current

The problem: Performance support quickly becomes outdated as processes and systems change.

Solutions:

Clear ownership:

• Assign content stewards by domain
• SME responsibility for currency
• Manager accountability
• Documented roles

Trigger-based updates:

• Automatic review when process changes
• System update checklist includes content
• Policy changes prompt review
• New versions trigger updates

Regular review cycles:

• Quarterly content audits
• Annual comprehensive review
• Usage data identifies outdated content
• Proactive refresh schedule

Easy update process:

• Simple editing tools
• Streamlined approval workflow
• Version control
• Quick publishing

User feedback:

• "Was this helpful?" ratings
• "Report an issue" links
• Comment and suggestion features
• Crowdsourced updates

Challenge 4: Information Overload

The problem: Too much performance support creates noise, making it hard to find what's needed.

Solutions:

Effective organization:

• Logical categorization
• Consistent naming conventions
• Clear hierarchy
• Progressive disclosure

Powerful search:

• Keyword optimization
• Synonym handling
• Search filters
• Auto-complete suggestions

Contextual delivery:

• Surface relevant support based on task
• Role-based filtering
• Progressive proficiency (hide advanced for beginners)
• Personalized recommendations

Consolidation:

• Merge redundant content
• Single source of truth
• Link related topics
• Archive outdated materials

Curation:

• "Start here" guidance
• Featured/recommended content
• Most popular aids highlighted
• Expert picks

Challenge 5: Balancing Support with Learning

The problem: Employees become dependent on performance support without actually learning.

Solutions:

Design for learning:

• Explanations with steps (why, not just what)
• Encouragement to try without aid
• Reflection prompts
• Practice opportunities

Progressive reduction:

• Detailed support initially
• Reduce scaffolding over time
• Track proficiency
• Fade support as competency grows

Blend support and training:

• Formal training for complex skills (see blended learning)
• Performance support for infrequent tasks
• Spaced practice with decreasing support
• Assessment to verify retention

Right-sizing support:

• Deep learning: Formal training
• Infrequent tasks: Performance support
• Critical procedures: Support even for experts (e.g., aviation checklists)
• Policy reference: Always available

Encourage mastery:

• Recognize employees who no longer need aids
• Certifications for demonstrated competency
• Expert designation
• Opportunities to mentor others

Best Practices for Performance Support

Maximize workflow learning impact:

1. Design for the Moment of Need

Focus on immediate task completion:

• Assume no prior training
• Provide just enough information
• Enable quick scanning
• Minimize reading time
• Action-oriented language

2. Make It Ridiculously Easy to Access

Remove all friction:

• One click from point of need
• No login barriers (when appropriate)
• Mobile-friendly
• Fast load times
• Bookmark-worthy

3. Test with Real Users

Observe actual usage:

• Watch someone use it cold
• Don't intervene or explain
• Note confusion and errors
• Ask what's missing
• Iterate based on feedback

4. Embrace Simplicity

Less is more:

• Remove nice-to-know information
• Focus on need-to-know
• Use plain language
• Clear visual hierarchy
• White space for breathing room

5. Integrate with Workflow

Embed where work happens:

• In-application help
• Linked from tools
• Posted at point of use
• Available on mobile
• No context switching required

6. Maintain Rigorously

Keep content trustworthy:

• Regular review schedule
• Update triggers
• Version control
• Archive outdated content
• Clear ownership

7. Measure and Optimize

Use data to improve:

• Track usage analytics
• Monitor search patterns
• Survey user satisfaction
• Measure performance impact
• Continuous refinement

8. Balance Support and Learning

Don't create dependence:

• Support for infrequent tasks
• Training for core competencies
• Progressive reduction for learners
• Encourage mastery
• Recognize expertise

The Future of Performance Support

Emerging trends in workflow learning:

AI-Powered Performance Support

Intelligent assistance:

Predictive support:

• Anticipate needs before asked
• Proactive suggestions
• Pattern recognition
• Contextual recommendations

Natural language interaction:

• Conversational queries
• Voice-activated support
• Intent understanding
• Personalized responses

Automated content generation:

• AI-created job aids from documentation
• Video-to-step-by-step conversion
• Automatic updates from system changes
• Content optimization suggestions

Augmented Reality (AR) Performance Support

Hands-free, in-context guidance:

Applications:

Manufacturing and maintenance:

• AR glasses show assembly steps
• Highlight components to select
• Overlay instructions on equipment
• Remote expert assistance

Healthcare:

• Procedure guidance
• Patient information overlay
• Medication verification
• Anatomy visualization

Field service:

• Equipment diagnostics
• Repair instructions
• Parts identification
• Safety warnings

Retail and warehouse:

• Product location
• Restocking guidance
• Customer assistance
• Training simulation

Benefits:

• Hands-free operation
• Contextual precision
• Reduced cognitive load
• Faster task completion

Adaptive and Personalized Support

Dynamic based on individual:

Skill-based adaptation:

• Detailed guidance for novices
• Minimal interference for experts
• Automatic proficiency assessment
• Progressive support reduction

Role and context awareness:

• Relevant information for job function
• Task-specific guidance
• Time and location sensitivity
• Personalized workflows

Behavioral learning:

• Adapt based on usage patterns
• Anticipate common next steps
• Optimize for individual preferences
• Continuous improvement

Embedded Learning Analytics

Performance insights:

Real-time dashboards:

• Task completion metrics
• Error rates and patterns
• Support usage by employee
• Skill gap identification

Predictive analytics:

• Identify struggling employees
• Forecast support needs
• Recommend interventions
• Optimize content priority

Workflow optimization:

• Process inefficiency detection
• Bottleneck identification
• Automation opportunities
• Continuous improvement data

Frequently Asked Questions

Understanding Performance Support

Q: What's the difference between training and performance support?

A: Training happens before the job and focuses on building knowledge and skills for future use. Performance support happens during the job and provides just-in-time guidance for current tasks.

Key differences:

When to use each:

Use training when:

• Building core competencies
• Developing complex skills
• Frequent tasks requiring fluency
• Deep understanding needed
• Significant practice required

Use performance support when:

• Infrequent tasks (< monthly)
• Many procedural steps
• Reference information needed
• Quick refresh required
• Cognitive load reduction helpful

Best approach: Blend both—train for important frequent skills, provide performance support for everything else.

Q: When should we use performance support instead of training?

A: Performance support is ideal when:

Task characteristics:

• Performed infrequently (won't be remembered)
• Procedural with defined steps
• Reference information needed
• Too complex to memorize
• High consequence if done wrong

Learner situations:

• New employees learning systems
• Infrequent users of software
• Employees dealing with exceptions
• Anyone performing rarely-used procedures
• Workers needing quick answers

Business contexts:

• Rapid process changes
• System updates and new features
• Compliance requirements
• Cost-effective at scale
• Just-in-time learning culture

Rule of thumb: If employees are likely to forget it between uses, provide performance support instead of (or in addition to) training.

Example: Software password reset

• IT staff reset passwords multiple times daily → Training
• Managers reset passwords once every few months → Performance support

Example: Emergency procedures

• Firefighters respond to emergencies daily → Training (with job aids as backup)
• Office workers evacuate building once a year → Performance support (posted procedures)

Q: Does performance support mean employees don't actually learn?

A: When designed well, performance support actually enhances learning:

Performance support aids learning by:

Enabling learning through doing:

• Practice in authentic context
• Immediate application
• Realistic scenarios
• Builds competence through repetition

Reducing cognitive load:

• External reference vs. struggling to remember
• Focus on understanding, not memorization
• Confidence to attempt complex tasks
• Scaffolding for skill development

Supporting spaced practice:

• Repeated task performance over time
• With support initially
• Gradual reduction as proficiency grows
• Eventual internalization

Research evidence:

Studies show employees using performance support:

• Complete tasks 50% faster initially
• Achieve competency 30% faster over time
• Report higher confidence
• Make fewer errors during learning

Preventing dependence:

Design for progressive learning:

• Detailed support for first few uses
• Abbreviated support after practice
• Minimal reminders for experienced users
• Assessment of independent performance

Use training AND support:

• Training for foundational understanding
• Performance support during initial application
• Reduced support as skills develop
• Training for advancement

Example: Customer service software

• Training: 2-hour overview of key features and workflows
• Performance support: Step-by-step guides for each task
• Usage pattern: Frequent reference initially, decreasing over weeks
• Outcome: Independent proficiency in 3-4 weeks vs. 2-3 months with training alone

Performance support doesn't replace learning—it accelerates it by enabling safe, guided practice in the actual work context.

Creating Job Aids

Q: How do we decide what job aids to create first?

A: Use a prioritization framework based on impact and effort:

High-priority job aid opportunities:

1. High frequency of questions

• Analyze help desk tickets
• Ask managers what they're asked repeatedly
• Review training evaluation comments
• Survey employees on information needs

2. High-consequence errors

• Safety incidents
• Compliance violations
• Customer complaints
• Financial mistakes
• Quality defects

3. Infrequent but critical tasks

• Performed monthly, quarterly, or annually
• Complex procedures
• Easy to forget steps
• Significant if done wrong

4. Time-consuming information searches

• Employees spend significant time finding answers
• Multiple sources checked
• Workflow interruptions
• Expert time consumed

5. New employee struggles

• Onboarding pain points
• Common confusion areas
• Time to productivity barriers
• Frequent training questions

Prioritization matrix:

Data-driven approach:

1. Collect data:

   • Help desk ticket categories
   • Error logs and incident reports
   • Training feedback
   • Employee surveys

2. Calculate impact score:

   • Frequency × consequence × time cost
   • Prioritize top 10-20 opportunities

3. Assess effort:

   • Content complexity
   • SME availability
   • Information stability
   • Development resources

4. Create roadmap:

   • High-impact, low-effort first
   • Build momentum with quick wins
   • Tackle complex aids with proven process
   • Continuous pipeline based on needs

Starting recommendation: Begin with 5-10 job aids addressing the most common help desk questions or onboarding pain points. Quick wins build credibility and support for broader efforts.

Q: What tools should we use to create job aids?

A: Start simple and scale based on needs:

Basic tools (start here):

Microsoft Word / Google Docs:

• Simple text-based aids
• Easy collaboration
• Familiar to everyone
• Export to PDF
• Best for: Procedures, checklists, quick references

PowerPoint / Google Slides:

• Visual job aids
• Screenshots with annotations
• One-pager format
• Best for: Step-by-step visual guides, infographics

PDF:

• Professional appearance
• Universal access
• Print-friendly
• Version control
• Best for: Final published job aids

Spreadsheets:

• Tables and matrices
• Decision aids
• Calculators
• Best for: Reference information, data-driven aids

Intermediate tools:

Snagit (TechSmith):

• Screenshot capture
• Image annotation
• Simple video creation
• Best for: Software documentation

Canva:

• Design templates
• Visual job aids
• Infographics
• Best for: Attractive, branded materials

Visio / Lucidchart:

• Flowcharts
• Decision trees
• Process maps
• Best for: Complex logic flows

Advanced tools:

MadCap Flare / Adobe RoboHelp:

• Technical documentation
• Multi-format publishing
• Version management
• Best for: Large-scale documentation

Articulate / Adobe Captivate:

• Interactive simulations
• Software walkthroughs
• Branching scenarios
• Best for: Software training and practice

Knowledge bases:

Confluence / Notion / SharePoint:

• Centralized repository
• Search and organization
• Collaboration
• Version history
• Best for: Enterprise-wide performance support library

Guru / Bloomfire:

• AI-powered search
• Browser extension
• Verification workflows
• Analytics
• Best for: Modern, searchable knowledge management

Recommendation:

1. Start: Word/Google Docs + simple templates
2. Grow: Add Snagit for screenshots, Canva for design
3. Scale: Implement knowledge base (Confluence, Guru)
4. Advanced: Digital adoption platform (WalkMe, Whatfix) for in-app guidance

The best tool is the one your team will actually use. Start simple, prove value, then invest in more sophisticated solutions.

Q: How long should a job aid be?

A: As short as possible while still enabling task completion:

General guidelines:

One-page job aids (ideal):

• Single task or decision
• Fits on one page/screen
• Scannable at a glance
• No scrolling required
• Examples: Checklists, quick references, decision trees

2-3 page job aids (acceptable):

• Multi-step procedures
• Complex decisions with context
• Some background needed
• Examples: Detailed procedures, troubleshooting guides

Longer than 3 pages (probably not a job aid):

• Should be training material or reference guide
• Break into smaller, task-specific aids
• Link to comprehensive resources
• Alternative: Table of contents with bookmarks

Specific format lengths:

Checklist: 5-15 items

• Too few: Not useful
• Too many: Overwhelming, won't be used

Step-by-step procedure: 5-12 steps

• Too few: Probably doesn't need aid
• Too many: Break into multiple aids or sub-processes

Quick reference card: 1 page

• Most critical information only
• Frequently accessed items
• Designed for printing

Decision tree: 3-7 decision points

• More complex: Provide simplified version + detailed guide

The "glance test":

User should be able to:

• Understand format at a glance (3 seconds)
• Find relevant section quickly (5 seconds)
• Extract needed information (10 seconds)
• Return to task (not spend minutes reading)

When content is longer:

Use these strategies:

• Clear sections: Headers, visual breaks
• Table of contents: For guides > 3 pages
• Quick start: Minimal version at top, details below
• Layered approach: Brief aid + "more information" link

Red flags (too long):

• Paragraphs of explanation
• Background and history
• Multiple tasks covered
• Training-like content
• Requires sustained reading

Fix: Extract just the essential steps or decisions. Move context to separate training or reference material.

Remember: Job aids support performance, not learning. If it requires 10 minutes to read and understand, it's training content, not a job aid.

Implementation and Management

Q: How do we get employees to actually use job aids instead of asking others?

A: Make job aids easier and faster than asking:

Remove barriers to access:

Extremely easy to find:

• Searchable by task name
• Prominent links in tools
• Bookmarked browsers
• Posted physically
• Mobile accessible

No login required (when appropriate):

• Public for non-sensitive
• Single sign-on for internal
• No password obstacles
• Fast access

Faster than asking:

• Immediate answer
• No wait time
• Available 24/7
• No interrupting others

Build the habit:

Introduce during onboarding:

• Show where job aids are
• Practice using them
• Require for tasks
• Build early patterns

Manager reinforcement:

• "Check the job aid first" culture
• Redirect questions to aids
• Model usage themselves
• Recognize when employees use support

Make it rewarding:

Faster task completion:

• Demonstrate time savings
• Track before/after metrics
• Share success stories
• Celebrate efficiency

Increased confidence:

• Employees feel empowered
• Can complete tasks independently
• No fear of forgetting
• Reduced stress

Better outcomes:

• Fewer errors
• Consistent quality
• Compliance assurance
• Customer satisfaction

Address resistance:

"Asking is faster":

• Maybe initially, but expert not always available
• Builds self-sufficiency
• Respects others' time
• Good citizenship

"I prefer personal help":

• Job aids available when people aren't
• Consistent information
• Others are busy
• Try aid first, ask if stuck

"I'll remember next time":

• Research shows we forget
• Infrequent tasks especially
• Aid ensures accuracy
• No penalty for using support

Continuous improvement:

Collect feedback:

• "Was this helpful?"
• Quick feedback forms
• Usage analytics
• Iterative refinement

Show responsiveness:

• Update based on feedback
• Communicate improvements
• Thank contributors
• Demonstrate value

Key: If job aids aren't being used, the problem is usually discoverability or quality, not employee stubbornness. Make aids genuinely helpful and easy to access.

Q: How do we maintain job aids as processes change?

A: Build maintenance into your operational rhythm:

Assign clear ownership:

Content stewards:

• Each job aid has an owner
• Usually SME or process owner
• Responsible for accuracy
• Authority to update

Management accountability:

• Managers ensure team aids are current
• Review in team meetings
• Part of process change workflow
• Performance expectation

Trigger-based updates:

Process change checklist: When any process changes, checklist includes:

• Update procedure documentation
• Update training materials
• Update job aids
• Update knowledge base
• Communicate changes

System release process: Software updates automatically trigger:

• Review of affected job aids
• Screenshot updates
• Procedure validation
• Republishing

Scheduled reviews:

Quarterly content audit:

• Review all job aids
• Verify still accurate
• Check usage metrics
• Update or archive

Annual comprehensive review:

• Full inventory
• Major updates
• Retirement of obsolete content
• Strategic alignment

Easy update process:

Simplified workflow:

1. Anyone can flag content as outdated
2. Content steward notified
3. SME reviews and updates
4. Simple approval (or auto-publish)
5. New version live
6. Notification to users

User-friendly tools:

• Web-based editing
• No technical skills required
• Templates and formatting
• Version control automatic

Accountability and metrics:

Track freshness:

• Last reviewed date visible
• Automatic staleness alerts
• Dashboard of outdated content
• Manager reporting

Measure impact of updates:

• Usage before/after refresh
• Error rates
• User feedback
• Help desk tickets

Example governance model:

Roles:

• Content steward: SME who creates and updates
• Approver: Manager or process owner who validates
• Administrator: L&D or IT who manages platform
• Users: Employees who use and provide feedback

Review schedule:

• Weekly: New content requests reviewed
• Monthly: Flagged content addressed
• Quarterly: Usage data reviewed, low-value content retired
• Annually: Full audit and strategic review

Communication:

• Major changes announced to users
• Change log available
• Email alerts for critical updates
• "What's new" section

The key is making job aid maintenance part of normal process management, not a separate initiative.

Advanced Strategies

Q: Can performance support work for complex problem-solving, not just procedures?

A: Yes, with the right approaches:

Problem-solving support strategies:

1. Decision support tools:

Diagnostic flowcharts:

• Guide through troubleshooting logic
• If/then decision paths
• Narrow possibilities systematically
• Lead to solutions

Example: IT troubleshooting

• Is the device powered on? → Yes/No paths
• Is it connected to network? → Diagnostics
• Can you access other sites? → Isolate issue
• Follow path to likely solution

Decision matrices:

• Multiple criteria evaluation
• Weighted factors
• Consistent decision framework
• Reduced bias

Example: Project prioritization

• Score opportunities on impact, effort, strategic fit
• Compare options systematically
• Data-driven choices
• Documented rationale

2. Frameworks and templates:

Thinking frameworks:

• Structured problem-solving approaches
• PDCA, 5 Whys, Fishbone diagrams
• Step-by-step guides
• Examples and prompts

Analysis templates:

• SWOT analysis worksheet
• Cost-benefit calculator
• Risk assessment matrix
• Business case template

3. Expert system tools:

Rule-based guidance:

• If conditions met → recommendation
• Capture expert decision logic
• Consistent application
• Explainable reasoning

Example: Loan approval decision support

• Input customer data
• System applies underwriting rules
• Flags risks and opportunities
• Recommends approve/deny/review

4. Case libraries and examples:

Similar situation reference:

• Database of past problems and solutions
• Search by symptoms or context
• Learn from previous approaches
• Adapt to current situation

Best practice examples:

• Templates from successful projects
• Annotated samples
• What worked and why
• Pitfalls to avoid

5. Expert access:

Knowledge networks:

• Directory of experts by topic
• Quick consultation access
• Escalation pathways
• Collaborative problem-solving

Community Q&A (leverage social learning):

• Post problem to community
• Collective intelligence
• Peer experiences
• Curated solutions

When performance support works for complexity:

✓ Structured problem-solving approaches exist ✓ Decision criteria can be codified ✓ Expert logic can be captured ✓ Examples and patterns available ✓ Frameworks guide thinking

When training is better:

✗ Deep domain expertise required ✗ Intuition and experience critical ✗ Each situation is truly unique ✗ Creative problem-solving needed ✗ Judgment can't be codified

Blended approach:

Train for:

• Problem-solving frameworks
• Domain knowledge
• Analytical skills
• Practice with cases

Provide performance support for:

• Applying frameworks
• Decision tools and calculators
• Example library
• Expert consultation access

Example: Medical diagnosis

• Training: Extensive medical education, clinical experience
• Performance support: Diagnostic algorithms, drug interaction checkers, clinical decision support systems, specialist consultation
• Result: Expert judgment augmented by tools, not replaced

Complex problem-solving often benefits from performance support that scaffolds expert thinking while still requiring human judgment and creativity.

Q: How do we balance standardization with the flexibility people need?

A: Design support that provides structure without rigidity:

Layered guidance approach:

Core procedure (standardized):

• Required steps that must be followed
• Compliance and quality gates
• Non-negotiable safety checks
• Consistent outcomes

Flexible elements (adaptable):

• How steps are performed
• Tools and methods used
• Sequence when not critical
• Personalization options

Example: Sales call job aid

Standardized:

• Verify customer identity (compliance)
• Document call in CRM (required)
• Confirm next steps (quality)
• Required disclosures (legal)

Flexible:

• Conversation approach (adapt to customer)
• Product positioning (based on needs)
• Examples used (relevant to context)
• Relationship building (personal style)

"Guidelines" vs. "Rules" language:

Use "must" for requirements:

• "You must verify customer identity"
• "The safety checklist must be completed"
• Clear non-negotiable steps

Use "should" or "recommended" for flexibility:

• "You should start with rapport building"
• "Consider using these examples"
• Allows professional judgment

Support multiple pathways:

Scenario-based variations:

• Different approaches for different contexts
• "If X situation, try this approach"
• "For Y customer type, emphasize..."
• Flexibility within structure

Example: Customer complaint resolution

Standard: Empathy → Understand → Resolve → Follow-up

Variations:

• High-value customer: Escalation path, premium options
• Simple issue: Quick resolution, minimal process
• Complex problem: Detailed investigation, multi-step solution

Enable expert deviation with documentation:

Structured flexibility:

• Standard approach recommended
• Deviations allowed with rationale
• Document why and outcome
• Build knowledge from variations

Example: Underwriting decisions

• Standard criteria provided
• Exceptions permitted with justification
• Senior review for non-standard decisions
• Successful deviations inform policy updates

Continuous improvement from flexibility:

Capture variations:

• When do people deviate from standard?
• What works better in specific contexts?
• Emerging best practices
• Update support based on learning

Feedback loops:

• "Did this approach work?"
• Alternative methods suggested
• User contributions
• Evolving guidance

When to standardize:

✓ Compliance and regulatory requirements ✓ Safety-critical procedures ✓ Quality consistency needed ✓ Proven best practices ✓ New employee guidance

When to allow flexibility:

✓ Contextual adaptation needed ✓ Professional judgment required ✓ Creative problem-solving ✓ Personal style and relationships ✓ Emerging or evolving practices

Balance in practice:

Good performance support provides:

• Structure: Clear starting point, required elements, quality gates
• Flexibility: Adaptations for context, professional judgment, continuous improvement
• Clarity: Explicit about what's required vs. recommended

The goal is consistent outcomes (standardized results) through flexible methods (adaptable approaches), not rigid compliance that ignores context.

Conclusion

Performance support transforms employee effectiveness by delivering learning at the moment of need—when it matters most.

Organizations embedding support into workflow achieve:

• 63% productivity gains through faster, error-free task completion
• 71% error reduction via consistent, guided processes
• 40-60% training cost savings by focusing on just-in-time learning

Build your performance support system:

1. Identify high-impact opportunities where support beats training
2. Create focused job aids for critical tasks
3. Embed in workflow where employees actually work
4. Test and refine based on real usage
5. Measure impact on performance outcomes
6. Scale systematically across your organization
7. Maintain rigorously to ensure currency and trust

Performance support isn't about replacing training—it's about recognizing that most workplace learning happens during work, not before it.

The future belongs to organizations that support employees in the flow of work, not those that pull them out of work to learn.

Ready to transform how your employees perform? Explore Konstantly's performance support capabilities or start your free trial to experience workflow learning firsthand.