learning-journey-builder

majiayu000's avatarfrom majiayu000

This skill should be used when designing complete learning journeys that integrate formal training with work-based learning and social learning. Use this skill to create 70:20:10 ecosystems, design coaching plans, establish peer learning structures, and ensure sustained support.

⭐5stars🔀1forks📁View on GitHub🕐Updated Jan 11, 2026

When & Why to Use This Skill

The Learning Journey Builder is a specialized skill designed to create comprehensive, multi-modal learning ecosystems based on the 70:20:10 framework. It moves beyond traditional workshops by integrating formal training with structured work-based experiences and social learning components to ensure long-term skill retention and business impact.

Use Cases

  • Corporate Training Architecture: Designing 6-week+ learning pathways that transition learners from initial theory to independent workplace mastery.
  • 70:20:10 Model Implementation: Creating a balanced mix of stretch assignments (70%), coaching/peer structures (20%), and formal instructional content (10%).
  • Social Learning Design: Establishing communities of practice, peer-to-peer learning circles, and structured coaching plans to facilitate knowledge sharing.
  • On-the-Job Application: Mapping out specific workflow integrations and 'just-in-time' support tools to help employees apply new skills to real-world projects.
  • Post-Training Sustainability: Developing long-term support structures and measurement frameworks to track the continuous application of learned behaviors.
namelearning-journey-builder
descriptionThis skill should be used when designing complete learning journeys that integrate formal training with work-based learning and social learning. Use this skill to create 70:20:10 ecosystems, design coaching plans, establish peer learning structures, and ensure sustained support.

Learning Journey Builder

Overview

The Learning Journey Builder skill helps design complete learning ecosystems that extend far beyond the workshop. It integrates formal training (10%), work-based learning (70%), and social learning (20%) into cohesive journeys.

When to Use This Skill

  • Designing complete 6-week or longer learning programs
  • Creating stretch assignments and work-based practice
  • Planning coaching and peer learning structures
  • Building communities of practice
  • Designing sustained learning pathways
  • Mapping workflow integration for new skills
  • Planning for application support post-training

70:20:10 Model Overview

70% - Work-Based Learning

  • Real projects and stretch assignments
  • Graduated complexity over time
  • Peer collaboration on actual work
  • Just-in-time support when stuck

20% - Social Learning

  • Embedded coaching (1-on-1 or manager-led)
  • Peer learning and pair programming
  • Communities of practice
  • Retrospectives and reflection

10% - Formal Training

  • Workshop (just-enough content)
  • Online learning (supplemental, job aids)
  • Quick references and on-demand support

Journey Design Components

  1. Kickoff: Workshop that frames all learning
  2. Phase 1 (Weeks 1-2): Coached work, high support
  3. Phase 2 (Weeks 3-6): More independent, peer collaboration
  4. Phase 3 (Weeks 7+): Sustained practice, lower support
  5. Measurement: Continuous tracking of application and results

Resources

Reference templates for:

  • Complete 70:20:10 journey maps
  • Stretch assignment designs
  • Coaching conversation guides
  • Community of practice charters
  • Application tracking frameworks
  • Learning ecosystem sustainability plans

Integration with Other Skills

  • training-designer: Use together to design sessions
  • training-reviewer: Validate materials
  • training-content-creator: Generate actual content
  • Use these alongside learning-journey-builder for complete programs

Best Practices

✅ Do:

  • Focus on learner outcomes and business impact
  • Use real work examples and scenarios
  • Design for application, not knowledge recall
  • Measure what matters

❌ Don't:

  • Train what doesn't drive behavior change
  • Use simulated practice over real work
  • Over-design solutions for simple problems
  • Ignore the business context