Transfer Debrief¶

After-action review — instantiates Transfer Scaffolding

After a real transfer attempt, compares what was expected to carry with what actually happened in the target, and feeds the difference back to revise the scaffold for next time.

A transfer scaffold that is never checked against reality is just a confident assertion. Transfer Debrief is the retrospective ritual that closes the loop: after a real transfer attempt, it compares what was expected to carry with what actually happened in the target, and feeds the gap back to revise the scaffold and its adaptation rule. Its defining move is that it operates on outcomes — it is the only sibling that looks backward, learning from target results so the next transfer starts from evidence rather than from the original guess.

Example¶

An emergency-management agency applied its well-drilled wildfire incident-command tactics to a major flood, then held a transfer debrief comparing intended versus actual. The command structure (a standard incident-command system) transferred cleanly — the invariant was confirmed. But the wildfire habit of establish a perimeter and hold the line mapped badly onto water that rises everywhere at once, so the adaptation rule was revised: for floods, replace perimeter-holding with evacuation-zone laddering. And resource-staging assumptions built around road access failed when the roads themselves flooded — a new boundary condition.

The output is an updated scaffold — confirmed invariants, corrected adaptation rules, freshly discovered boundaries — captured so the next cross-hazard transfer starts from what was actually learned rather than from the original wildfire playbook.

How it works¶

Reconstruct the intended mapping — what the scaffold predicted would carry, adapt, or not apply.
Observe what actually happened in the target, component by component.
Attribute each gap to a bad mapping, a missing adaptation, or a wrong boundary condition.
Revise the artifacts — update the adaptation rule, the boundary set, or the structure map — and disseminate the change.

Tuning parameters¶

Cadence — a one-shot post-mortem, or a recurring review after every transfer attempt (the latter compounds).
Framing — blameless learning versus accountability. Psychological safety governs how honest the account is.
Comparison granularity — headline outcome only, or a component-by-component check of what the scaffold predicted.
Update scope — revise just the adaptation rule, or the boundary conditions and structure map as well.
Capture and dissemination — how revisions actually reach the next team rather than dying in a meeting.

When it helps, and when it misleads¶

Its strength is turning one-time transfer assertions into a compounding capability — it is the only mechanism that corrects the scaffold against reality, so the whole set gets better over time instead of repeating the same mis-transfer.^[1]

Its failure modes are hindsight bias and blame, which convert the ritual into theatre or scapegoating, and debriefs that produce insight but change no artifact — wasted learning. The classic misuse is running the debrief to assign fault or to justify the original plan rather than to improve the scaffold. The discipline is a blameless learning frame, a requirement that each finding alter a specific scaffold element, and real dissemination.

How it implements the components¶

Transfer Debrief fills the feedback-and-revision subset of the archetype:

feedback_and_revision_loop — it is the loop: learn from target-context outcomes and revise the scaffold accordingly.
adaptation_rule — its most common revision target, correcting how the source knowledge should be adjusted for the target based on what actually happened.

It closes the loop after the fact but does not author the initial applicability conditions (Boundary Condition Checklist) or run the live practice it reviews (Cross-Context Practice's guided_transfer_task); it consumes their outcomes to improve them.

Instantiates: Transfer Scaffolding — it is the feedback loop that revises the scaffold from real target results.
Consumes: the outcomes of any guided transfer — Cross-Context Practice, Implementation Coaching, or a live application — are its raw material.
Sibling mechanisms: Cross-Context Practice · Boundary Condition Checklist · Implementation Coaching · Negative Transfer Red Team · Case Comparison and Contrast · Analogical Mapping Prompt · Apprenticeship Reflection · Bridging Examples · Near-to-Far Transfer Sequence · Transfer Prompt · Worked Example Variation

Notes¶

This is the only backward-facing mechanism in the set: every other sibling builds the scaffold, and the debrief corrects it from evidence. Its output flows back into the others — updated boundaries into the checklist, corrected adaptation rules into coaching and practice — so a set that omits it can only ever transfer as well as its first guess.

References¶

[1] The After-Action Review, formalized as a practice by the U.S. Army, is a structured post-event comparison of what was expected against what happened, aimed at learning rather than blame. It is the archetypal instance of the feedback loop this mechanism implements for transfer. ↩