Opening Strategy — AJ Crabill’s Signature Hooks

Validated against actual corpus (May 2026). AJ’s instinct was correct; the analysis below applies nuance so the pipeline uses the right opening for the right context.

Long Writing (Book Register)

Pattern: Story-Led Openings

AJ opens persuasive/reframing chapters with a true story — personal experience, professional coaching anecdote, or historical analogy. The story has a clear parallel to the framework point he’s about to make. The bridge sentence is characteristic: “I share this story because it illustrates…”

Examples from corpus

When NOT to use

Definitional/instructional chapters — where precision in defining framework terms (inputs vs outputs vs outcomes) is the primary purpose. These open direct.

Ch1 = direct analytical. Ch1 “Trained to Fail” = data-driven analysis, no story.

Variant: Pattern-Recognition Hook (Taxonomy Chapters)

For chapters structured around a set of named categories (archetypes, types, patterns), use a short personal hook that establishes the author’s pattern-recognition credibility rather than a full story or a framework statement:

“By the time I’d been at [school system] for about a year, I could walk into the boardroom and tell you, within the first ten minutes, what was going to happen. Not because I was psychic. Because I had learned something that took me embarrassingly long to figure out: every [board member] operates from a pattern. Once you learn the pattern, you stop reacting and start leading.”

This is a third opening type distinct from:

Story-led (persuasive/reframing chapters — full narrative with bridge)

Framework-direct (definitional/instructional chapters — precision statement)

Pattern-recognition hook (taxonomy chapters — short credibility tease)

Use when: the chapter is about classifying and responding to a set of archetypes. Examples: Chapter 13 of “From the Driver’s Seat” (seven board member archetypes), or any chapter where the body consists of “for each type: how to spot it + what to do about it.”

Rule for the pipeline

Lead with story when making a persuasive or reframing move. Lead direct when defining framework terms. Lead with a pattern-recognition hook for taxonomy/archetype chapters (where the body consists of categories with identification → strategy → trap). Use the bridge sentence “I share this story because it illustrates…” to explicitly connect the anecdote to the framework point.

Short Writing (Newsletter Register)

Pattern: Unexpected Contradiction / Non-Obvious Statement

AJ opens standalone newsletter articles with a statement that contradicts a common assumption. The reader thinks “wait, what?” — and then the rest of the article explains why the contradiction resolves to make perfect sense.

Examples from corpus

When NOT to use

Q&A format responses — the question itself provides the tension. Opening direct (“It depends on what you mean by…”, “This varies by board…”) is the right move.

Tight single-paragraph responses where the answer is all the reader needs.

Why this works

The contradiction technique works because it:

Catches the reader’s attention by violating an unstated assumption

Establishes AJ as someone who thinks independently, not just repeating common wisdom

Creates a puzzle the reader wants resolved — which the rest of the article solves

Makes the reader feel smarter for understanding the resolution

Rules for the pipeline

Standalone articles: lead with an unexpected contradiction or non-obvious statement. Test: does the opening contradict a common assumption a board member would hold? If not, scrap it and try again.

Q&A responses: lead with the answer. The question already hooked the reader. Reserve the contradiction move for multi-paragraph framing if one emerges naturally.

Quick test

If the opener can be summarized as “Here’s a framework concept,” it needs to be rewritten. The opener should make a board member think “wait, really?” — and the body should make them think “oh, of course.”