Chase Hughes says clients would call his coaching line with a real problem — a hard conversation coming up, a specific person they needed to move — and ask for the same thing every time: the phrasing. The magic script. What exact words to say. He'd have to explain, in one form or another, that handing someone a pilot's flight checklist doesn't make them a pilot.1 What clients actually needed wasn't a script; it was a repeatable method for building the right script for their specific situation, on the spot, from the models they already had. The Technique Creation Protocol is that method — a "coach-in-a-box" formula for minting new pieces of tactical language and behavior out of the book's existing model stack, rather than fishing for a pre-written line that happens to fit.
The protocol runs the operator through four stacked models in a fixed order, each one narrowing the plan toward an actual monologue.2
Subject Persona Development comes first: build a hypothesis-driven Behavior Compass for the subject (or two — one for a group's decision-maker, one for the group's average, if the tradecraft is aimed at a crowd rather than an individual). Where the subject is unknown, Hughes's default is to assume Acceptance and Significance as the operative Needs and build the linguistics around those, using bold or underlined text so the plan can be corrected fast if new intelligence arrives. Each hypothesized position gets a "Fuzzy Compass" — a nearby, semi-likely secondary trait developed as backup tradecraft, on the logic that the operator's first read of the subject may simply be wrong and the plan needs a fallback that doesn't require starting over.
The PCP Model Framework comes second, functioning as the outline for the whole interaction: three boxes, one each for how Perception, Context, and Permission will be shifted. The Context box gets built backward from extremity — start with the most extreme scenario that would make the desired action look automatic and rational, then work down through progressively less severe versions until you have a believable on-ramp. The Permission box is built from a battery of questions aimed at the subject's likely internal resistance: what fears, social repercussions, and identity conflicts would this specific person have about taking this specific action.
The FATE Model comes third, aimed specifically at influencing "the mammal" — Focus, Authority, Tribe, and Emotion triggers developed as a set, the same way, Hughes notes, you'd build a training plan for a dog: reward focus, responsiveness to authority, membership in the pack, and the emotional payoff that makes the animal want to come back.3
The Six-Axis Model comes fourth, used here as a prioritization tool rather than a full six-front assault: reorder the six axes (Focus, Openness, Connection, Suggestibility, Compliance, Expectancy) by relevance to the specific scenario, develop at least five concrete methods with word-for-word scripts for each of the top four, and trust that the remaining two axes rise on their own as a byproduct.
The Interrogation Protocol closes the formula, repurposed here as the architecture for a short closing monologue rather than a literal interrogation: Socialize, Minimize, Project, Rationalize, Emphasize Action.4
Each move gets a one-line design brief and a bank of interchangeable phrases:4
A closing resource bank ties Emphasize-Action language to six named Decision Map categories — Deviance, Novelty, Social, Conformity, Investment, Necessity — with five interchangeable phrases each, letting an operator swap the entire persuasive register to match a subject's actual decision style rather than running one script on everyone.5
You're building a piece of tradecraft for a real, specific upcoming interaction — a hard ask, a negotiation, a sales call, a difficult conversation with a family member. Start with Subject Persona Development: what do you actually know about this person's likely Needs, and what's your fallback hypothesis if you're wrong? Move to PCP: write out, in three boxes, how you'll shift what they perceive as true, what context makes the ask feel normal, and what internal permission barriers stand between them and yes. Layer in FATE: what's the ancestral-script trigger, the authority signal, the tribe cue, the emotional payoff you're building toward. Prioritize four of the Six Axes and write five real scripts for each — not placeholders, actual sentences you could say out loud. Only at the end do you draft the closing monologue, using Socialize/Minimize/Project/Rationalize/Emphasize Action as the shape, pulling phrases from the Decision Map bank that matches this specific subject's decision style. The order matters: skipping straight to the closing script, the thing every coaching-call caller wanted first, produces exactly the flight-manual-without-a-pilot problem Hughes is warning against.
Evidence: The protocol is a synthesis tool built entirely from other models already documented elsewhere in this book (PCP, FATE, Six-Axis, the Interrogation Protocol) rather than an independently evidenced technique in its own right — its validity is fully derivative of whatever validity those component models carry individually.1 [SINGLE SOURCE]
Tensions: Hughes frames the protocol as a corrective to "magic pill" thinking — clients wanting a script instead of a method — but the Emphasize Action phrase banks are, functionally, exactly the pre-written scripts the whole protocol claims to move people beyond. The formula produces its own flight-manual pages at the very last step, after four stages of ostensibly bespoke analysis.
Behavioral-Mechanics — The ACSS Tradecraft Troubleshooting Framework. That page documents Hughes's diagnostic tool for why an operator's tradecraft isn't landing; this page is the generative counterpart — the tool for building tradecraft in the first place. The insight the pairing produces: read together, the two form a full production-and-repair loop — Technique Creation builds the artifact, ACSS diagnoses it when the artifact fails in the field — which means an operator who has only learned one half of this pair either can't build new techniques for novel situations, or has no way to fix a technique once it stops working, and won't know which.
Psychology — Cognitive Dissonance (Festinger). The Project move ("it's not your fault, and it can be your success") is a direct dissonance-reduction intervention performed for the subject rather than left to them: instead of letting the subject resolve the discomfort of "I want this but haven't done it yet" on their own (which might resolve toward rejecting the desired action instead of taking it), the operator pre-supplies the exculpatory narrative. The insight the pairing produces: this reframes the Interrogation Protocol's five moves as a sequence explicitly engineered to control which direction a subject's dissonance resolves in, rather than simply reducing dissonance in general — Project doesn't remove the discomfort, it aims it.
Sharpest implication: A protocol whose entire stated purpose is teaching operators to stop reaching for pre-written scripts ends its own formula with a bank of pre-written scripts. That's not necessarily hypocrisy — it may be an honest admission that even a fully custom-built persuasion architecture still needs a closing register that's been pressure-tested across many uses. But it does suggest the "flight manual doesn't make you a pilot" framing oversells how much of this system is actually bespoke versus assembled from interchangeable parts at the final, highest-stakes moment.
Generative Questions: