Playbook Creation¶

Situational playbook — instantiates Emergent Formalization

Codifies situational judgment as a navigable guide of cues, options, and escalation paths — for work that branches on the situation rather than following one fixed sequence.

Playbook Creation formalizes a practice whose value is judgment under varying conditions: it captures the cues a skilled responder reads, the plays available for each situation, worked examples, and when to escalate — organized so a user can navigate to the right response in the moment. Its defining move, versus the linear SOP, is that it embraces branching: it does not pretend every case follows one sequence, so its structure is situation → cues → options → escalation rather than step 1 → step 2. What makes it THIS mechanism is that it codifies decision-making, not execution.

Example¶

A support team's best agents can turn a furious customer around, and the new hires cannot — the skill is real but lives in a few people. Playbook Creation captures it as a de-escalation playbook built around situations, not steps: for "customer is angry about a repeat failure," the playbook lists the cues that tell you which kind of anger you are facing (venting vs. threatening to churn vs. wanting a specific fix), the plays for each (acknowledge-and-pause, offer a concrete remedy, or route to retention), a couple of transcribed real examples, and a clear escalation line — if the customer mentions legal action or a chargeback, stop improvising and hand to a manager. It is not a script to read top to bottom; it is a guide the agent navigates by reading the situation. A new agent now has the veterans' judgment in a form they can consult live, and knows exactly where their authority ends.

How it works¶

Its distinguishing organization is around recognition, not sequence. The core work is codifying the cues that let a user classify the situation, pairing each with a small menu of proven options rather than a single mandated action, and drawing bright escalation lines where the situation exceeds the user's competence or authority. It leans on examples and non-examples because situational judgment transfers better through cases than abstract rules. It presumes the reader is competent and choosing, not a novice being walked through steps.^[1]

Tuning parameters¶

Branch resolution — how finely the situations are cut. Finer branches give more precise guidance but bloat the playbook and blur which one you are in; coarser branches stay usable but under-specify.
Prescriptiveness — a menu of options vs. a recommended play per situation. More prescription helps novices but erodes the judgment the playbook is meant to build; more optionality trusts the user but can leave them stranded.
Escalation threshold — how early to hand off. Low thresholds are safe but train dependence and swamp escalation; high thresholds build autonomy but risk in-over-their-head calls.
Example density — how many worked cases per play. Rich examples transfer tacit judgment; too many turn the playbook into a casebook nobody finishes.
Cue explicitness — how much of the "how do I know which situation this is" is spelled out versus left to the reader's read of the room.

When it helps, and when it misleads¶

Its strength is that it transfers situational judgment at scale, gives less-experienced people the veterans' options without pretending the work is mechanical, and makes the boundary of someone's authority explicit through its escalation lines.

Its failure mode is that a playbook can flatten genuine judgment into pattern-matching — users force the live situation into the nearest documented branch and stop actually thinking, which is worst exactly when the case is novel. It also goes stale as situations evolve, and an over-branched playbook becomes unnavigable under pressure. The classic misuse is running it as an SOP — demanding the "recommended play" be executed regardless of the read — which reintroduces the rigidity the playbook form exists to avoid. The discipline that guards against this is to keep branches recognizable, preserve real optionality within each, and treat the playbook as a scaffold for judgment, not a substitute for it.

How it implements the components¶

Playbook Creation realizes the judgment-codifying side of the archetype — the components that turn situational expertise into a navigable, teachable guide:

tacit_context_capture — encodes the cues and situational read that let a user recognize which case they are in.
exception_rule — the escalation lines are its backbone: explicit markers of when to deviate, hand off, or suspend the play.
codification_process — transforms situational judgment into a navigable situation→options→escalation structure that can be taught and inspected.

It does not detect and elicit the raw expert judgment in the first place — that is Apprenticeship-to-Protocol Capture, which often feeds it — nor validate that the practice is worth keeping, which is Governance Rule Creation's usefulness test.

Instantiates: Emergent Formalization — the codifier for judgment-heavy, situation-dependent practice.
Consumes: Apprenticeship-to-Protocol Capture often supplies the captured cues and deviation patterns a playbook is written from.
Sibling mechanisms: Standard Operating Procedure · Checklist Conversion · Apprenticeship-to-Protocol Capture · Community Norm Codification · Design Pattern Documentation · Governance Rule Creation · Legal Custom Formalization · Protocol Standardization from Usage · Style Guide Creation

References¶

[1] Gary Klein's recognition-primed decision model describes how experts act by matching a situation to a repertoire of recognized patterns rather than weighing options from scratch — which is why a playbook is organized around cues and situations, the units expertise actually runs on. ↩