Transfer Prompt¶
Lightweight questioning method — instantiates Transfer Scaffolding
A few lightweight standing questions — what is the underlying idea, what is different here, what would make it fail — that trigger transfer thinking without building any heavy artifact.
Not every transfer warrants a full scaffold; sometimes you just need to pause and ask. Transfer Prompt is that pocket tool: a small, fixed set of standing questions — what is the underlying idea, what is different here, what would make it fail — asked on the spot to trigger transfer thinking before an old approach is reflexively applied. Its defining move is that it is minimal, self-serve, and general-purpose: it prompts the key transfer questions without producing any durable artifact — no correspondence map, no checklist, no curriculum — trading depth for near-zero cost and instant availability.
Example¶
A manager who ran an engineering team now manages a design team, and instinctively reaches for the old playbook — detailed tickets, velocity metrics, code-review-style critique. Before applying it, she runs the transfer prompt:
- What's the underlying idea? — "Give clear goals and fast, specific feedback."
- What's different in the target? — "Design work is more subjective; 'velocity' doesn't capture design quality; critique norms differ."
- What would make my old approach fail here? — "Treating a design like a pull request to nitpick line-by-line will kill trust."
In five minutes, without any artifact, she keeps the principle (clear goals, fast feedback) and drops the metrics and the line-by-line critique. It is a fast course-correction, not a rigorous analysis — and that is exactly its role.
How it works¶
- Ask a fixed, short question set, applied quickly and repeatedly rather than once and elaborately.
- Abstract the source with the first question — state the underlying idea in context-free terms.
- Probe the target with the next two — what differs, and what would break — surfacing the obvious mismatches.
- Escalate if the answers reveal real risk, handing off to a heavier scaffold rather than pretending to be one.
Tuning parameters¶
- Question count — three questions or a fuller set. More is thorough but heavier, which defeats the pocket-tool purpose.
- Framing — generic questions or a domain-tailored version that names the usual traps in that field.
- Trigger — self-prompted, or embedded in a workflow (a template field, a checklist gate) so it fires automatically.
- Depth expectation — a quick gut answer versus a short written reflection.
- Escalation rule — how much revealed risk should tip the user from prompt into a real checklist, mapping, or red team.
When it helps, and when it misleads¶
Its strength is near-zero cost and instant availability — it catches the obvious mis-transfers, and its best feature is triage: it tells you when a fuller scaffold is actually needed.[1]
Its failure mode is shallowness: it surfaces only what the user already half-knows, so a confident user answers superficially and walks away falsely reassured. The classic misuse is treating the prompt as sufficient validation for a high-stakes transfer that genuinely needs a boundary checklist or a red team. The discipline is to use it as a trigger, not a verdict, and to escalate the moment the answers reveal material difference.
How it implements the components¶
Transfer Prompt fills a lightweight slice of the archetype — the questions, not the artifacts:
source_abstraction_prompt— the first question ("what's the underlying idea") is exactly this: state the source principle in context-free terms.target_constraint_probe— the second and third questions ("what's different / what would break") lightly probe the target's constraints.
It only asks; the durable artifacts belong to siblings — the deep source articulation to Apprenticeship Reflection, the full applicability gate to Boundary Condition Checklist, and the adversarial trap-hunt to Negative Transfer Red Team.
Related¶
- Instantiates: Transfer Scaffolding — it is the minimal, always-available prompt that triggers transfer thinking and triages when more is needed.
- Sibling mechanisms: Apprenticeship Reflection · Boundary Condition Checklist · Negative Transfer Red Team · Analogical Mapping Prompt · Case Comparison and Contrast · Bridging Examples · Cross-Context Practice · Implementation Coaching · Near-to-Far Transfer Sequence · Transfer Debrief · Worked Example Variation
References¶
[1] Self-explanation prompts (Chi) — asking learners to explain to themselves what a principle means and how it applies — reliably improve understanding and transfer at very low cost. The transfer prompt is a compact, application-facing version of the same move. ↩