Strategy Checklist¶
Checklist — instantiates Metacognitive Monitoring Loop
A fixed menu of failure-mode checks and candidate reasoning moves you scan when stuck, turning a vague sense that thinking has stalled into a concrete next adjustment.
Knowing your thinking has stalled is not the same as knowing what to do about it — and a stuck mind is the worst-placed to invent the fix. Strategy Checklist solves that with a prepared artifact: a fixed, scannable list of the failure modes reasoning commonly falls into ("Am I anchored on the first idea? Have I looked for disconfirming evidence? Am I closing too early?") paired with the concrete moves that address each one ("broaden the differential," "seek a counterexample," "get a second read"). Its defining property is that both the diagnosis and the response are pre-loaded, authored in advance when the mind was clear, so that in the moment the thinker doesn't generate — they select. It converts an inchoate "something's off" into a named fault and a specific next adjustment, off a menu.
Example¶
An emergency physician has a patient with abdominal pain and a working diagnosis of gastritis that fits — mostly. Something nags, but the shift is busy and the diagnosis is plausible, and the pull toward closing the case is strong. Before signing off he runs the department's diagnostic checklist, a short prepared card of cognitive-forcing checks: Have I anchored on the first plausible diagnosis? What's the worst thing this could be, and have I ruled it out? Does anything in the presentation not fit?
The second question stops him. He has not excluded the dangerous mimics. The checklist doesn't diagnose the patient — it names the reasoning fault (premature closure toward a benign fit) and points to the move (broaden the differential, order the test that separates gastritis from the worst case). He orders it; it changes the disposition. The prepared list did what a tired mind at the end of a shift could not: it surfaced the fault it was primed to miss and handed over the corrective move. This is precisely the logic of cognitive forcing strategies — pre-committed checks that counter known diagnostic error at the moment it's most likely.[n1]
How it works¶
- Author it in advance, from known failure modes. The list is built when the mind is clear, encoding the reasoning faults this domain reliably falls into — not improvised under load.
- Pair each check with a move. Every failure-mode item carries a concrete corrective adjustment, so surfacing a fault immediately yields a next action rather than fresh anxiety.
- Run it at a trigger point. The checklist fires before a commitment, at an impasse, or on a schedule — a deliberate scan, not a background hum.
- Select, don't generate. The thinker's job is to scan the fixed set and pick the applicable fault and move; the artifact does the remembering.
Tuning parameters¶
- Length — a short card (three to five high-yield checks) versus an exhaustive list. Short lists get run and remembered; long ones are thorough but skipped under exactly the time pressure they're meant for.
- Specificity of moves — generic prompts ("reconsider") versus concrete actions ("order the D-dimer"). Concrete moves act faster but must be tailored per domain; generic ones travel but demand more of the user.
- Trigger discipline — always-on at a fixed gate versus judgment-invoked. A hard gate guarantees the scan but can become rote; a judgment trigger fires when it matters but relies on the stuck mind to invoke it.
- Coverage versus focus — covering many failure modes shallowly or a few deeply. Broad coverage catches more; narrow focus on the domain's top killers is likelier to actually change a decision.
When it helps, and when it misleads¶
Its strength is offloading both memory and invention to a moment when the mind had neither pressure nor stall: the fault you'd never think to check for is the one the list checks for you, and the move is already attached. It is the surest bridge from noticing a problem to doing something about it.
Its central failure is rote completion — the list run as a box-ticking ritual, ticked without the honest self-examination each item demands, so the form survives while the checking dies. It can also breed false comfort: a passed checklist feels like safety, but it only covers the failure modes its authors anticipated, and an unlisted one sails through unexamined. And a checklist that merely prescribes steps without any signal that the steps fit the current problem has drifted into procedure. The guarding discipline is to keep the list short enough to be run honestly, revise it as new failure modes surface, and treat a clean pass as "no listed fault found," never as proof the reasoning is sound.
How it implements the components¶
reasoning_failure_mode_label— it pre-enumerates the named reasoning faults (anchoring, premature closure, shallow search) so the thinker can match the current stall to one.strategy_adjustment— each fault on the list carries an attached corrective move, so a diagnosis converts directly into a concrete next action.monitoring_signal_set— the checks themselves are a compact, prepared signal set, a fixed inventory of the cues that indicate reasoning has gone wrong.
It is the acting artifact, not the gauge. It does not read continuous in-the-moment state — working-memory load or whether the reasoning is advancing (cognitive_load_signal, progress_marker) — through open questions; that surfacing sensor is [Reflection Prompt], its nearest twin, which asks an open question to notice a signal while this checklist offers a fixed list of faults and moves to select. Nor does it calibrate the confidence signal against evidence (confidence_check), which is [Confidence Rating Rubric].
Related¶
- Instantiates: Metacognitive Monitoring Loop — it is the loop's prepared bridge from a detected reasoning fault to a concrete adjustment.
- Consumes: Reflection Prompt — a prompt that surfaces a stall or overload is the natural trigger to reach for the checklist's moves.
- Sibling mechanisms: Reflection Prompt · Confidence Rating Rubric · Metacognitive Coaching · Decision-Process Review · Reasoning Retrospective · Learning Journal · Think-Aloud Protocol
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: Strategy Checklist is defined in the frozen evidence as: A fixed menu of failure-mode checks and candidate reasoning moves you scan when stuck, turning a vague sense that thinking has stalled into a concrete next adjustment. Its operative deployed or enacted form is therefore Assessment, Review & Assurance.
Nearest alternative: Interface, Display & Cue — Interface, Display & Cue can support this mechanism, but the evidence centers the concrete operation described above rather than the alternative family's defining operation.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Convergent development
Present-day reach: Universal
Rationale: A failure-mode menu scaffolds strategic problem solving.
Related originating lineages:
- Cognitive Science — External prompts overcome fixation.
- Systems Thinking & Cybernetics — Systems thinking, feedback control, and cybernetics supplies a parallel or contributing lineage for the mechanism's defining operation: a fixed menu of failure-mode checks and candidate reasoning moves you scan when stuck, turning a vague sense that thinking has stalled into a concrete next adjustment.
Review resolution: The blind reviewers agree that organizational_management is the primary origin and differ only on alternate origin disagreement. I preserve every independently explained alternate from both records rather than imposing a numeric cap. I retain convergent because the combined evidence shows independent disciplinary development. The broader reach of universal records portability separately from historical provenance; encyclopedia_synthesis=true preserves the affirmative synthesis judgment where either reviewer identified one.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; medium confidence.
Notes¶
[n1] Cognitive forcing strategies — described in diagnostic-reasoning work by Pat Croskerry — are deliberate, pre-committed mental checks (e.g., "always ask what the worst case is") designed to counter the specific cognitive biases that drive diagnostic error. A strategy checklist is the artifact form of that idea: the forcing checks written down and paired with moves, so they fire even when the clinician is tired, rushed, or anchored. ↩