Skip to content

Coaching Check-In

A recurring human feedback ritual — instantiates Formative Feedback Loop

A recurring one-to-one conversation that reads recent evidence of progress together and turns it into concrete next actions — some the learner takes, some the coach commits to.

A Coaching Check-In is a scheduled, recurring conversation in which a coach and a learner look at recent evidence of progress together, work out what it means, and leave with specific next actions. Its defining feature is that it is relational and two-sided: the diagnosis is negotiated out loud rather than delivered, and the output splits into things the learner will do and things the coach will change — more practice on X, yes, but also a different scaffold, a removed blocker, a re-taught concept. Where a rubric or dashboard hands feedback to a learner, the check-in is the human ritual where evidence becomes a shared plan — and where the coach can hear the tacit friction a metric never shows.

Example

A support-team lead meets a three-week-old agent every Friday for twenty minutes. This week the evidence is a handful of the agent's ticket transcripts plus her own note that refund cases stress her out. Reading two transcripts together, they don't stop at "handle time is high" — they locate the actual gap: she re-reads the entire policy page mid-chat because she doesn't trust her memory of the refund rule. That diagnosis forks into two commitments. The agent will draft a one-line refund cheat-sheet and use it on her next five refund tickets (her action); the lead will pair her with a senior agent on two live refund chats and stop routing angry escalations to her for one more week (his action). Next Friday opens by checking those, not by starting over.

How it works

  • It runs on a cadence and always opens against recent, concrete evidence — transcripts, a work sample, the learner's own read — not a general "how's it going."
  • Diagnosis is joint: coach and learner name the gap together, which surfaces causes (fear, an unclear policy) a one-way review would miss.
  • Every session closes with actions on both channels — learner tasks and coach commitments — and the next session opens by checking them.

Tuning parameters

  • Cadence — weekly, biweekly, or milestone-triggered; tighter cadence catches drift early but costs time and can start to hover.
  • Evidence discipline — how firmly the talk anchors on concrete artifacts versus impressions; anchoring keeps it honest, over-formalizing kills candor.
  • Directiveness — how much the coach prescribes versus draws the diagnosis out of the learner; drawing-out builds self-diagnosis but is slower.
  • Channel balance — how much of the plan lands on the learner versus on the coach's own support changes; a check-in that never adjusts the coach's side is just assigning homework.
  • Psychological safety — how protected the conversation is from evaluation; the more it feels like appraisal, the less honest the signal it runs on.

When it helps, and when it misleads

Its strength is reaching the gaps instruments can't: fear, confusion, motivation, the reason behind the number — and producing a plan both parties own, where the two-sided commitment is what actually makes support change.

Its failure mode is decay into status reporting or a pep talk with no diagnosis and no committed action. If the coach also controls the learner's evaluation, honesty collapses and the "evidence" gets curated for the audience. The classic misuse is running the check-in to look supportive while the real judgment happens elsewhere and unchanged. The discipline that keeps it honest is to anchor every session on concrete evidence, write down actions on both sides, and open the next one by checking whether they happened.

How it implements the components

  • gap_diagnosis — coach and learner jointly name the cause behind the evidence, not just the symptom.
  • actionable_feedback — the session's output is specific next steps, not a score or praise.
  • learner_response_channel — the learner leaves with owned actions and a clear path to act on them.
  • instructional_response_channel — the coach leaves with committed changes to the support itself (pairing, scaffolds, routing).

It does not capture the raw progress signal (progress_signal — Low-Stakes Quiz, Exit Ticket), supply the explicit standard (criteria_reference — Formative Rubric), or enforce a compressed recheck cadence (recheck_cycle — Rapid Feedback Cycle).

  • Instantiates: Formative Feedback Loop — it is the human ritual that turns interim evidence into a shared, two-sided plan before final judgment.
  • Consumes: progress signals from Low-Stakes Quiz, Exit Ticket, or a Progress Dashboard — the check-in interprets evidence it usually doesn't gather itself.
  • Sibling mechanisms: Progress Dashboard · Formative Rubric · Adaptive Practice Set · Draft Feedback Cycle · Exit Ticket · Low-Stakes Quiz · Misconception Probe · Peer Review Protocol · Practice Review · Rapid Feedback Cycle