Workshop Outline Generator

Generate learner-centered workshop and training outlines using MECE structure, Training from Back of Room (TfBR), and VAK learning styles.

Purpose

Design effective workshop outlines that:

• - Apply MECE structure (Mutually Exclusive, Collectively Exhaustive)
• Use TfBR 4C design (Connection, Concepts, Concrete Practice, Conclusion)
• Include VAK elements (Visual-Auditory-Kinesthetic)
• Balance 70% activities / 30% content delivery
• Define measurable, action-based learning outcomes

When to Use

Trigger when users ask for:

• - Workshop or training outlines
• Course structures or agendas
• Training session designs
• 培训大纲 / 工作坊设计 / 课程结构

Design Process

1. Gather Requirements

Clarify before generating:

• - Topic: What is the training subject?
• Audience: Who are the learners? (level, background, pain points)
• Duration: Half-day, full-day, multi-day (default: 2 days)
• Format: In-person, virtual, hybrid
• Outcomes: What should learners be able to DO after training?
• Practical Level: Should learners bring real cases for practice?
• Reference Material: Existing course outline (if any)

2. Apply MECE Structure

Organize into non-overlapping, comprehensive modules:

CODEBLOCK0

3. Define Learning Outcomes

Use performance-based outcomes with action verbs (NOT "understand"):

CODEBLOCK1

Action Verbs: Apply, demonstrate, practice, create, design, analyze, evaluate, deliver

Example: "After this module, participants will be able to deliver constructive feedback to direct reports using the SBI model to improve performance without defensiveness."

4. Design Using TfBR 4Cs

Activity Types:

• - Assessment: Self-evaluations, diagnostics
• Experience: Simulations, role-plays, games
• Practice: Skill drills, rehearsals
• Reflection: Journaling, pair sharing, ORID debriefs
• Application: Real projects, action planning

5. Integrate VAK Elements

6. When Reference Outline is Provided

First, provide an optimization table with:

• - Assessment of original modules (strengths/weaknesses)
• Restructured module flow and sequence
• New SMART learning objectives per module
• Targeted additions/deletions
• Improved teaching methods and interactive elements
• Revised time allocations

Then generate the detailed outline.

Output Format

CODEBLOCK2

Typical Session Structures

Half-Day (4 hours):

• - Module 1: Foundation (60 min)
• Module 2: Core Skills (90 min)
• Module 3: Application (60 min)
• Closing (30 min)

Full-Day (7-8 hours):

• - Morning: Module 1-2 (90 min each)
• Lunch (60 min)
• Afternoon: Module 3-4 (90 min each) + Closing (30 min)

Multi-Day:

• - Day 1: Foundations and Awareness
• Day 2: Skills and Practice
• Day 3: Application and Integration

Quick Checklist

Before finalizing:

• - [ ] MECE structure verified (no gaps, no overlaps)
• [ ] Outcomes use action verbs (not "understand")
• [ ] Activity time ≥ 65%
• [ ] Each module has VAK elements
• [ ] Content is minimal (just-enough, just-in-time)
• [ ] ORID debriefs planned for activities
• [ ] Opening includes outcomes and agenda
• [ ] Closing includes commitments
• [ ] Materials list complete

Writing Tone

• - Professional, rigorous, confident
• Demonstrate consultant-level thinking and problem-solving
• Precise language (not colloquial)
• Coaching and guiding approach (not lecture-style)
• Practical and actionable (avoid theoretical fluff)

Integration

Reference jackyshen-list-methods skill for:

• - MECE structuring principles
• TfBR 4C design process
• ORID debrief templates
• VAK integration strategies