Learners know principle of explaining content in own words or receive short introduction to technique before start.
Teach-back
Prerequisite
What needs to be finished first
Concrete, observable learning objectives for session exist, against which explanation back can be measured.
Preparation
What needs to be ready before start
Whiteboard or shared document for summaries; timer; teaching material of session as reference; checklist of learning objectives; optional flipchart for learner sketches.
One coach or trainer who teaches content and receives explanations back; two to six learners; for groups over six people, additional co-facilitator for breakouts.
List of learning objectives; taught content as bullet outline; learner prior knowledge (brief assessment beforehand); known misunderstandings from earlier sessions.
20-45 min per learning-objective block
Make learning objectives visible. State: Teach-back tests understanding, not knowledge. Wrong answers are diagnosis, not evaluation. Clarify learner order (random order prevents humiliation of first responders).
Core question
The one question this method answers
Can learners explain taught content in their own words so that a non-specialist understands core idea and could apply it?
Flow
Marker: Minute
| Step | Duration | Action | Hint |
|---|---|---|---|
10-10 min | 10 min | Teach content clearly bounded: one concept, one procedure or one model. Name learning objectives explicitly so explanation can be measured against them. | If block is longer than 10 min, half of learners forget the beginning. Better split into two Teach-back rounds than push through at once. |
210-12 min | 2 min | Set task: "Explain concept in own words to colleague who was not here today. Maximum 90 seconds." Give silent preparation time. | Calling directly without preparation creates reproduction instead of understanding. Plan at least 60 seconds silence, even if it feels long. |
312-25 min | 13 min | Each learner gives 90 s explanation. Coach listens, does not interrupt, notes gaps and misinterpretations. After each explanation, brief follow-up: what was new, what was unclear. | Correction in middle of explanation destroys learning effect. Take notes, then correct or re-explain deliberately at end of block. |
425-35 min | 10 min | Address gaps: re-explain identified misunderstandings with different analogy, example or sketch. Second short explanation by affected learners. | If same gap appears in more than half, first teaching was problem, not understanding. Change method, do not blame learners. |
535-45 min | 10 min | Application transfer: concrete task or case example requiring taught concept. Learners solve in pairs, present in one sentence. | Without transfer task, Teach-back stays at reproduction level. Application is real proof of understanding. |
Artifact
What comes out at the end
Coach notes with learning objectives, observed gaps per learner, adjustments made and transfer task with result. Optional audio or video recording of explanations for learner self-reflection.
Date, trainer and learning-objective block in header. New note per repetition of method, do not overwrite. On curriculum adjustments, cross-link previous session so learning path stays traceable.
- Markdown notes in trainer repo under docs/trainings/
- Shared Notion or Confluence document
- Learning platform with reflection entry per learner
- Voice note or Loom recording of explanation
teach-back-working-template.md
Compact working template for Teach-back with context, input, output artifacts, and next step.
Teach-back Working Template
Goal
Checks understanding by having learners explain content back in their own words.
Context
When and for what do we use this method?
Input
Which data, observations, decisions, or materials are available?
Execution
Short notes along the runsheet.
Output artifacts
- Understanding Check:
- Clarification Notes:
- Learning Gaps:
Assumptions and open questions
- ...
Decision / Next step
Owner, date, and success signal.
Example output
Concrete filled scenario, fictional example
teach-back-beispiel.md
Concrete filled scenario, fictional example
Teach-back — Module "REST API Design", 2026-05-12
Learning objective: Participants explain difference between idempotent and non-idempotent HTTP methods including example.
Explanations back
- Sabine: explained GET/PUT as idempotent correctly, confused POST with PATCH for partial updates. Gap: idempotency vs. safety.
- Tobias: correct including example with duplicated PUT. Transfer without follow-up.
- Marlene: named all methods, but could not formulate own example for idempotency.
Adjustment
New explanation with analogy "light switch (idempotent) vs. doorbell (non-idempotent)". Marlene's second explanation was correct with own example.
Transfer task
Group designed endpoint sketch for order API in 8 min; all three classified PATCH correctly as non-idempotent.
Pitfalls
Recognize symptoms and steer against them
Exam instead of learning setting
Learners formulate haltingly, look at notes, quote slides literally.
Explicitly reframe setting: explanation back diagnoses teaching, not person. Coach gives first explanation back as model, then voluntary order.
Reproduction instead of understanding
Explanation uses jargon without translation, sounds like slides, no own example.
Set constraint: no slide terms, at least one analogy or example from own work context. If absent, ask "How would you explain this to your brother?"
Correction interrupts explanation
Coach jumps in after 20 s and corrects, learners fall silent or become defensive.
Pen rule: coach only notes, corrects after 90 s. Address all corrections collected in block, referencing concrete examples.
Learning objective too broad
Explanations are 5 min long, cover many aspects superficially, no clear understanding visible.
Narrow learning objective to single concept. Maximum one learning objective per Teach-back block, several blocks sequentially instead of one large round.
Group dynamics dominate
First person sets tone and wording, everyone else repeats similar wording instead of own translation.
Draw order randomly (cards, dice) or parallel explanations in breakouts with one listener each. Plenary only for coach diagnosis, not sequential performances.
No transfer step
Explanation fits, but in next task learners do not use concept.
Transfer task as fixed part of session. No completion without application. Task must require concept, not merely allow it.
Stop criteria
Done signals checkable in under a minute
Finished the runsheet?
Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.