Design training sessions from intake to concept map to breakdown. Pulls from Notion. Use for "design a session", "new training", "build a workshop".
Design training sessions by gathering structured context, producing a high-level concept map (5-6 core concepts), then breaking each concept down on request. Optimized for Tim's cognitive style: big concepts first, details on demand, no text walls.
INTAKE (structured brief)
↓
CONCEPT MAP (5-6 high-level concepts, visual)
↓
BREAKDOWN (one concept at a time, on request)
↓
RUN OF SHOW (time-stamped, delivery-ready)
Before designing anything, collect ALL of this. Do not proceed with gaps.
Ask for what's missing. Use AskUserQuestion with specific options, not open-ended prompts.
SESSION BRIEF
─────────────
Client/Host: [Who's paying for this?]
Event Name: [What's it called?]
Session Title: [What Tim's session is called]
Date & Time: [Start time, end time — hard stops?]
Duration: [Total minutes]
Session Type: [Keynote | Workshop | Learning Lab | Webinar | Course Module]
Q&A: [Yes/No, how long, when?]
AUDIENCE
────────
Size: [Number of people]
Titles/Roles: [Who's in the room?]
Industry: [Sector, context]
Experience Level: [Beginner | Intermediate | Advanced | Mixed]
Why They're There: [What motivated attendance?]
Their Pain: [What problem do they have?]
CONTEXT
───────
Pre-Call Notes: [What was discussed in pre-meeting calls?]
Agreed Outcomes: [What success looks like — be specific]
Past Trainings: [Has Tim done this topic/audience before? Pull from Academy]
Constraints: [Topics to avoid, format requirements, brand rules]
Survey/Post-Survey: [Is there one? What does it measure?]
LOGISTICS
─────────
Slides Platform: [Canva — pull deck if exists]
Materials Needed: [Handouts, worksheets, templates?]
Tech Setup: [In-person, virtual, hybrid? What tools?]
Connector Integration:
From the brief, distill 5-6 core concepts. Present them as a visual map, not a text wall.
Format — the concept map:
SESSION: [Title] — [Duration] for [Audience]
┌─────────────┐
│ 1. [CONCEPT]│ ← [one-line description]
└──────┬──────┘
│
┌──────┴──────┐
│ 2. [CONCEPT]│ ← [one-line description]
└──────┬──────┘
│
┌──────┴──────┐
│ 3. [CONCEPT]│ ← [one-line description]
└──────┬──────┘
│
┌──────┴──────┐
│ 4. [CONCEPT]│ ← [one-line description]
└──────┬──────┘
│
┌──────┴──────┐
│ 5. [CONCEPT]│ ← [one-line description]
└──────┬──────┘
│
┌──────┴──────┐
│ 6. CLOSE │ ← [CTA + callback]
└─────────────┘
THROUGHLINE: [The single sentence that connects all concepts]
Rules for concept selection:
Wait for Tim's approval of the concept map before breaking anything down.
When Tim says "break down concept 3" (or similar), expand that concept into:
CONCEPT 3: [NAME]
──────────────────
TIME: [X min]
STORY LAUNCH: [What story opens this section? — use story-finder if needed]
CORE IDEA: [The one thing they must understand]
EVIDENCE/EXAMPLE:[What makes this credible?]
ENGAGEMENT: [What does the audience DO here? — use engagement-check format]
TRANSITION: [How does this connect to the next concept?]
SLIDE NOTES: [What slides support this? Anchor vs. narrator check]
DELIVERY NOTE: [Specific guidance for Tim's style]
Only break down what Tim asks for. Don't dump all 6 at once. This respects his working memory.
When all concepts are broken down, produce the run-of-show:
RUN OF SHOW: [Session Title]
DATE: [Date] | TIME: [Start]–[End] | DURATION: [X min]
AUDIENCE: [Who] | SIZE: [N]
TIME | MIN | SEGMENT | WHAT HAPPENS | DELIVERY NOTE
──────|─────|──────────────────|─────────────────────────────────|──────────────