Methodology: Kolb's Experiential Learning Cycle Facilitation Model: "I Do, We Do, You Do" gradual release Duration: 165 minutes (2 hours 45 minutes) including one 15-minute break and 15-minute buffer Practice Allocation Target: 90–105 minutes (60–70% of session time)
Version: 2.0 Date: 2026-01-30
- Copy this template for each new session
- Fill in all bracketed
[placeholder]sections with session-specific content - Verify timing adds up to ~165 minutes (150 min instruction + 15 min buffer) with practice time >= 90 minutes
- Run through the Accessibility Checklist before finalizing
- Have a colleague or pilot tester review the facilitation script
Date: [Delivery date] Duration: 165 minutes (includes 15-minute buffer) Bloom's Level: [Remember / Understand / Apply / Analyze / Evaluate / Create] Prerequisites: [Previous sessions required] Materials Needed: [List all materials — slides, handouts, demo repos, devices]
By the end of this session, learners will be able to:
- [Objective 1 — use Bloom's action verb]
- [Objective 2]
- [Objective 3]
- [Objective 4]
- [Objective 5]
| Time | Duration | Phase | Activity | Mode |
|---|---|---|---|---|
| 0:00 | 10 min | Welcome & Hook | Why This Matters for YOUR Farm | Instructor |
| 0:10 | 15 min | Concrete Experience | Instructor Demo ("I Do") | Instructor |
| 0:25 | 20 min | Reflective Observation | Guided Practice ("We Do") | Paired |
| 0:45 | 25 min | Abstract Conceptualization | Concept Explanation & Discussion | Instructor + Group |
| 1:10 | 15 min | BREAK | Stretch, questions, tech help | — |
| 1:25 | 35 min | Active Experimentation | Independent Practice ("You Do") | Individual |
| 2:00 | 10 min | Reflection | What Did You Learn? + Farm Application | Group |
| 2:10 | 10 min | Wrap-Up | Preview Next Session + Feedback Survey | Instructor |
| 2:20 | 10 min | Buffer | Catch-up, 1-on-1 help, survey collection | Open |
Practice Time: 80 min (Guided 20 + Independent 35 + Reflection activity 10 + parts of other phases) = ~60% minimum Lecture Time: ~40 min maximum
Note: Adjust timing based on session complexity. Sessions introducing entirely new concepts (Sessions 1, 4, 7) may need more demo time. Sessions building on prior skills (Sessions 3, 6, 9) can allocate more practice time.
"Why This Matters for YOUR Farm"
Purpose: Connect today's topic to a real farm problem. Build motivation before introducing any technology.
Facilitation Script:
"Good [morning/afternoon]. Before we touch any computers today, let me ask you a question..."
[Insert farm-relevant question that surfaces the problem this session solves]
"Today we're going to learn [topic], which is GitHub's way of [farm analogy]. By the end of this session, you'll be able to [key outcome in plain language]."
Key Elements:
- Open with a farm question, not a technology statement
- Share the farm analogy for today's concept
- State 1–2 learning outcomes in plain language
- Acknowledge any anxiety: "This might feel new, and that's completely fine"
- Connect to prior session: "Last time we learned [X]. Today builds on that."
"I Do" — Watch Me
Purpose: Demonstrate the skill live so learners see the complete workflow before attempting it.
Facilitation Script:
"I'm going to show you exactly how to [skill]. Watch my screen — I'll go slowly and explain each step. You don't need to follow along yet, just watch."
Demo Steps:
- [Step 1 — describe what to show and what to say]
- [Step 2]
- [Step 3]
- [Step 4]
- [Step 5]
Key Elements:
- Project screen clearly visible to all learners
- Narrate every click and decision ("I'm clicking here because...")
- Use farm scenario from the use case library
- Pause after each step: "Does everyone see where I am?"
- Point out common mistakes: "A lot of people try to click here instead — that's normal"
"We Do" — Let's Do It Together
Purpose: Learners follow along step-by-step with instructor guidance and peer support.
Facilitation Script:
"Now it's your turn. Open your browser to [URL]. I'll walk through each step and you follow along. If you get stuck, ask your partner first, then raise your hand."
Guided Steps:
- [Step 1 — include exact instructions learners should follow]
- [Step 2 — include "checkpoint: you should see [X] on your screen"]
- [Step 3]
- [Step 4]
Pair Activity:
- Partners compare screens at each checkpoint
- If one partner is ahead, they help the other catch up
- Instructor circulates to check progress
Key Elements:
- Provide exact URLs and click paths
- Include screen checkpoints ("You should now see...")
- Pair learners for mutual support
- Circulate the room — don't stay at the front
- Have a "stuck?" recovery path for each step
Troubleshooting Guide:
| Problem | Solution |
|---|---|
| [Common issue 1] | [Fix] |
| [Common issue 2] | [Fix] |
| [Common issue 3] | [Fix] |
"Now Let's Understand Why"
Purpose: After experiencing the skill, explain the underlying concepts and connect to broader farm use cases.
Facilitation Script:
"You just [did the skill]. Let's talk about why this works and when you'd use it on your farm."
Concept Points:
- [Concept 1 — use farm analogy]
- [Concept 2 — connect to prior session knowledge]
- [Concept 3 — address common misconception]
Discussion Prompts:
- "When on your farm would you use this?"
- "What's different about doing this on GitHub vs. how you do it now?"
- "What questions do you have about when to use this vs. [alternative]?"
Key Elements:
- Maximum 10 minutes of instructor talking; rest is discussion
- Use farm analogies for every technical concept
- Include at least one "turn to your partner and discuss" moment
- Address misconceptions proactively
- Show slide with key vocabulary and farm analogy equivalents
"Take 15 minutes. Stretch, grab a drink, ask me any questions. We'll start back at [time]."
During break:
- Circulate to help anyone who fell behind
- Answer individual questions
- Note any widespread confusion for post-break review
- Check that all devices are still connected to Wi-Fi
"You Do" — Try It On Your Own
Purpose: Learners practice independently with a farm scenario. This is where skill acquisition happens.
Exercise:
[Title of Exercise]
Scenario: [Farm scenario from use case library]
Instructions:
- [Step 1]
- [Step 2]
- [Step 3]
- [Step 4]
- [Step 5]
Success Criteria: You have completed this exercise when:
- [Observable outcome 1]
- [Observable outcome 2]
- [Observable outcome 3]
Stretch Challenge (for those who finish early):
- [Additional task that extends the skill]
Farm Context Options (UDL — learner choice):
- Option A: [Crop farming scenario]
- Option B: [Livestock scenario]
- Option C: [Equipment/maintenance scenario]
Fallback Task Suggestions (for open-ended steps):
- [List 3-4 specific task examples to reduce decision paralysis]
Key Elements:
- Exercise uses a real farm scenario
- Instructions are numbered and specific
- Success criteria are observable (instructor can verify by looking at screen)
- Stretch challenge available for faster learners
- 2+ farm context options for learner choice (UDL)
- Instructor circulates, observes, and provides L2 assessment notes
"What Did You Learn?"
Purpose: Consolidate learning and connect to farm application.
Facilitation Script:
"Before we wrap up, take a moment to think about what you learned today."
Reflection Activities (choose 1–2):
- Partner Share: "Tell your partner one thing you learned and one thing you'll try on your farm this week"
- Whole Group: "Who can share one thing they'll use from today?" (volunteer-based, not cold-call)
- Written: "On your feedback card, write one thing you learned and one question you still have"
- Application Pledge: "Write down one specific farm task you'll try using [today's feature] for"
Key Elements:
- Give learners time to think before sharing
- Celebrate specific accomplishments: "I saw [Name] do [specific thing] — great work!"
- Never cold-call anxious learners
- Collect "one question" cards for next session's opening
Facilitation Script:
"Great work today. Here's what we covered: [brief summary]. Next session we'll learn [topic preview]. Before you go, please fill out the feedback survey — it only takes 2 minutes and it helps me make this training better for you."
Key Elements:
- Summarize key concepts (3 bullet points max)
- Preview next session topic and connection to today
- Distribute feedback survey (paper or digital)
- Mention optional between-session practice: [specific task]
- Thank learners for their time
Purpose: Catch-up time for learners who fell behind, 1-on-1 help, survey collection.
- Help any learner who didn't complete the exercise
- Collect remaining feedback surveys
- Note learners who may need extra support
- Answer any remaining questions
Complete this checklist for every session before delivery:
- All slide text is 18pt+ (body) and 24pt+ (headers)
- Color contrast ratio is 4.5:1 or higher (use WebAIM Contrast Checker)
- No information conveyed by color alone (use shapes, labels, or patterns)
- All images have descriptive alt text (not just "image" or "screenshot")
- Slide backgrounds are high contrast (dark text on light background preferred)
- All verbal instructions are also displayed visually (on slides or handouts)
- Videos have captions or transcripts
- Instructor faces the audience when speaking (for lip reading)
- Room acoustics tested; microphone available if needed
- All exercises can be completed using keyboard only (no mouse-only actions)
- Exercise instructions include keyboard shortcuts where applicable
- Touch-screen alternatives noted for tablet/phone users
- Sufficient time allocated — no time-pressured exercises
- Written materials use plain language (grade 6–8 reading level)
- Technical jargon defined with farm analogies on first use
- New concepts limited to 3–5 per session
- Content chunked into digestible segments with clear transitions
- Slides use proper heading hierarchy (H1, H2, H3)
- Lists are formatted as actual lists (not faked with dashes)
- Reading order is logical when navigated by screen reader
- Handouts available in both print and digital formats
| Signal | Meaning | Action |
|---|---|---|
| Multiple hands raised | Pace too fast | Pause, re-demonstrate, add checkpoint |
| Learners looking around | Confusion | Stop and ask "What's on your screen right now?" |
| Learners chatting, looking at phones | Pace too slow or content not engaging | Move to practice phase, add stretch challenge |
| One learner far behind | Individual difficulty | Pair with advanced partner, provide 1-on-1 during break |
| Whole group energized, asking questions | Good engagement | Extend discussion, add bonus demo |
- Session 1 Rule: No one fails. Every exercise is designed so all learners succeed.
- Normalize mistakes: "I click the wrong thing all the time — watch me fix it"
- Celebrate specifics: "Maria just created her first Issue — that's a real skill!"
- Avoid jargon: If you catch yourself using a technical term, immediately follow with the farm analogy
- Check in frequently: "Thumbs up if you're with me, thumbs sideways if you need a moment"
- Rule of Three: Introduce, practice, reinforce. Don't move on until the majority has it.
- One screen at a time: Don't show your screen while learners are working on theirs
- Written backup: Every verbal instruction is also on a slide or handout
- Break momentum: If energy drops, call a 2-minute "stand and stretch"
Every session must implement all three UDL principles:
- Visual: Projected slides with high-contrast text and diagrams
- Verbal: Instructor narration with farm analogies for every concept
- Written: Printed take-home reference guide (cheat sheet, step-by-step guide, or checklist)
- [Session-specific mode]: [e.g., Kinesthetic, Photographic, Spatial, Tabular]
- Scenario choice: 3 farm options (crops, livestock, equipment) in lab exercises
- "Why This Matters for YOUR Farm" opening connects to personal experience
- Optional stretch challenges for fast finishers
- Partner work available throughout — learners choose when to collaborate
- Fallback suggestions provided for any open-ended steps
- L1 Reaction: Feedback survey (paper or digital)
- L2 Observation: Skill checklist (3-6 observable skills per session)
- Hands-on product: Learners produce an observable artifact (Issue, Project board, file, etc.)
- Verbal sharing: Partner discussion + volunteer whole-group sharing
- Written reflection: At least 1 written reflection question in the lab exercise
- Collect all feedback surveys
- Note attendance count
- Write debrief notes while fresh: what worked, what to adjust, timing accuracy
- Record L2 assessment observations (who demonstrated skills, who struggled)
- Identify learners needing extra support
- Enter feedback data into tracking document
- File debrief notes to
delivery/session-[NN]-debrief.md - Adjust next session materials if needed based on today's observations
- Send follow-up resource to learners (optional practice suggestion)
These patterns were identified during Sprint 4 pilot testing of Sessions 1-3 and should be applied to all future sessions:
- Build a 15-minute buffer into every session. Real classrooms encounter Wi-Fi issues, device differences, CAPTCHA struggles, and questions that consume more time than estimated.
- Timing estimates are 15-20% optimistic. Account creation, photo uploads, and drag-and-drop interactions take longer than planned.
- Rebalance lab exercise sections so that more complex parts get more time. Simple review sections can be shortened.
- Use "right side of the page" instead of "sidebar" — farmers don't use this term.
- Match GitHub's UI text exactly. When GitHub displays "Todo" (no space), don't write "To Do." Zero-tech learners match handout text to screen text character by character.
- Define every technical term at first use with a parenthetical farm analogy.
- Avoid compound jargon like "custom field." Use plain language first, then introduce the term: "extra columns you create yourself (GitHub calls these custom fields)."
- Always teach a fallback method alongside the primary method. For drag-and-drop, teach the dropdown alternative first so learners have a reliable backup.
- Provide fallback task suggestions for open-ended steps. When learners go from structured examples to "choose your own," decision paralysis is common. List 3-4 examples.
- Add editing guidance early. Learners will make typos. Tell them immediately: "You can edit anything — click the three-dot menu."
- Clarify implicit UI behavior. For example: "Adding a comment does NOT close an Issue — you must click 'Close issue'."
- Photo upload is the highest anxiety action. Provide device-specific guidance (phone camera icon, Downloads folder, email-to-self workflow).
- Make photo upload optional on first attempt: "If it's not working, skip it. You can add a photo later."
- Specify sample photo filenames in the facilitation script pre-session checklist.
- Split dense slides. If a slide introduces 6+ concepts, split into two slides with 3 each.
- Add "turn and talk" activities to break up concept-heavy sections. Two minutes of pair discussion re-engages learners after 15+ minutes of instructor-led content.
- Lead with people, not numbers. Instead of "40+ million people use GitHub," say "Farmers, teachers, and researchers use GitHub" — then mention the number.
- Address data privacy proactively in Session 1. Learners worry about who can see their information. Tell them: "Your repositories can be private — only you can see them."
- Reinforce "you can't break anything" at every practice phase. Technology anxiety is real and persistent.
- The demo repository must exist before delivery. All lab exercises reference specific files, folders, and data. See
sessions/demo-repository-spec.mdfor the full specification. - Pre-create Issues with labels before Session 2.
- Clean up test data between session deliveries.
- L2 observation checklists should be practical — instructors can't observe and fill forms simultaneously. Use quick checkmark-style sheets, not detailed rubrics.
- Checkpoints in guided practice are essential. "Raise your hand when you see X" gives the instructor a real-time completion count.
This template is version 2.0, updated after Sprint 4 pilot testing. Apply these lessons to all sessions 4-12.