WalkMe Learning Arc Console & Content Organization Guide

Last Updated August 3, 2026

Workspace & Folder Management

1. Use Workspaces Strategically

  • Group by Business Unit or Region: HR, Sales, Support, EMEA, APAC
  • Designate “Sandbox” or “Dev” workspaces for testing before content goes live

2. Standardize Folder Structures

  • Organize by learning areas or applications, not by people
  • Example Structure:
    • Business Architecture
      • Domain / Department / Audience → Business area / Topic → Workflow / Tasks (Action/Outcome) → Products / Role Based
  • Risk & Compliance
    • Ethics Training, Security Training, Policy Training
  • Skills & Development
    • Presentation Skills, Development Skills, Industry Specialty Skills
  • Programs
    • Project A, Project B

Naming & Metadata Standards

1. Naming Conventions for Clarity

  • Format: [Audience] – [Topic] – [Action/Outcome]
    • Example: "Sales – Pipeline Basics – Qualify a Lead"
  • Use version tags when needed:  "Sales – Pipeline Basics – Qualify a Lead V2.0

2. Tag Everything Thoughtfully (optional)

  • Consistent metadata tagging:
    • Region
    • Role
    • Product / Instance
    • Release Cycle (e.g., Q1 FY26)

3. Use Statuses to Manage Progress

  • Provided by Learning Arc

4. Maintain a Master Index (Only if required)

  • Unique Number Identification System

Content Lifecycle Maintenance

1. Structured Migration & Build Strategy

  • Review & Author: Evaluate existing content and revise as needed
  • Approve & Publish: Use defined workflows before content goes live
  • Migrate or Build:
    • Copy legacy content from SAP Enable Now (SEN)
    • Decide whether to wrap or rebuild
    • Use WalkMe Producer tools for editable content

2. Content Design in Learning Arc Format

  • Combine:
    • AI-generated content
    • Manual simulations
    • Quizzes & self-checks
  • Reorder and tag content clearly to improve search and discoverability

3. Clean As You Go

  • Archive outdated or underperforming content
  • Schedule quarterly audits of folders and learning units

Deliver in the Flow of Work

  • Trigger content at the moment of need, not on a fixed schedule
  • Use role- or behavior-based Segments to target content to the right audience
  • Embed guidance in the actual screen or step — don't redirect learners to a portal
  • Prioritize compliance and behavior-change moments Migration & Build Strategy
  • Position Learning Arc as reinforcement, not an LMS replacement
  • Measure behavior change — not just completion rate

Microlearning Design Principles

  • One objective per unit: If you need “and” to describe the objective, split it into two units
  • End every unit with a retrieval moment: Close with a recall question or task — not a summary slide
  • Sequence as a series, not one-offs: Space units over days or weeks; show learners what's next
  • Make it action-oriented: End with something the learner can try on the job
  • Know the limits: Blend with longer courses for skills that need sustained practice and track a behavior or on-the-job measure, not just completion
  • Sweet spot: 3–10 minutes per unit
    • Floor (~3 min): shorter units often skip the retrieval step
    • Ceiling (~10 min): longer becomes a lesson, not a micro-unit
    • Scope drives length — right-size the objective first
  • In-workflow content (Learning Arc): lean 3–5 minutes
    • Learners are mid-task — keep it tight, but never cut the practice step

Was this article helpful?

Thanks for your feedback!

Be part of something bigger.

Engage with peers, ask questions, share ideas

Ask the Community
×
×