In June 1942, a Japanese “Zero” fighter jet, flipped into a bog on Akutan Island, Alaska, and the pilot never got out.
Zero crashed in the Akutan bog. US Navy / NARA.
The island sits in the Aleutians, a chain that looks, on a map, like someone spilled gravel between Russia and Alaska. Fog sits on the water for days. The ground that pretends to be a landing strip is often marsh.
Petty Officer Tadayoshi Koga, flying off the carrier Ryūjō during the raid on Dutch Harbor, put his Mitsubishi A6M down on what he thought was flat ground. The plane somersaulted and Koga died still belted in, hanging inverted in the wreck.
His wingmen circled and the standing order said to destroy a downed Zero so the enemy couldn’t study it. They didn’t fire because they hoped he might still be alive.
He wasn’t, but the plane mostly was.
US crew inspects the recovered airframe on Akutan Island. US Navy.
That single intact airframe, later recovered by the U.S. Navy, shipped south, rebuilt, and flight-tested in San Diego, taught American pilots more about beating the Zero than months of briefings that described the same fighter from a distance.
The Zero loaded onto a ship for transport south. US Navy.
I keep thinking about that Zero when I sit with founders who already “know” what their employees are dealing with.
They have the reports. They don’t have the Zero.
What the briefings already said
By mid-1942, American pilots had met the Zero in the air and hated the experience.
It climbed past them
It turned in between them
In a climb-and-turn fight, they kept losing
Intelligence even had a detailed file which reported light construction, exceptional low-speed agility, thin armor, no self-sealing tanks.
But here was the problem…
A briefing can tell you a plane is light. It cannot tell you what the stick feels like when you push past 200 knots.
In September 1942, Navy test pilot Eddie Sanders took the repaired Akutan Zero up for its first flight at Naval Air Station San Diego. He flew about two dozen tests scenarios over the next few weeks.
On the very first flight, American pilots saw and experienced, exposed weaknesses they could immediately use.
Eddie Sanders taxis the captured Zero at NAS San Diego. US Navy.
The stick stiffened hard at high speed
Rolling at that velocity was slow and created heavy force on the stick.
The plane rolled left more easily than right
Under negative G, the engine cut out because of the float-type carburetor
None of that transferred in the briefing like it did up in the air.
It’s stick feel. Asymmetry. An engine that quit when you asked for a specific kind of acceleration.
In mid-fight, pilots don’t get time to think about facts.
They have fractions of a second to react. A briefing in a folder doesn’t help when another plane is already on you. What helps is body knowledge you can fire without a meeting.
During The dive, open range while the Zero’s engine is coughing, and at about 200 knots roll hard right before he can settle his sights, because his high-speed roll is a slow brick and yours isn’t.
That’s what the intact plane bought.
The Zero in U.S. markings on a test hop over San Diego. US Navy.
The war already had piles of intel. It needed one plane you could put a test pilot in.
Your company already has Zeros
If you run a team that sells, coaches, installs, supports, or closes anything complex, you live on a version of this problem every week.
Buried in your processes is your Zero.
These are the moments hidden in plain sight. They live in coaching calls, brainstorms, sales calls…anywhere that a person is problem-solving and tapping into their expertise…their unconscious competence. Many times, we feel them when things don’t go according to plan but we keep the conversation going anyways.
And the craziest part, it often happens without knowing why…we “just knew”.
When we try to investigate we will review our slides. Webinar decks. Meeting agendas. CRM stages. But those are all briefing material.
What you almost never think to look at is the intact plane.
One moment preserved with enough detail that you can spot the seemingly invisible.
My favorite place to go hunting is the call logs. A transcript gives you more than a label.
The sentence where the prospect’s energy dropped.
The ten-second pause your best rep stayed quiet…and then the prospect answered their own objection.
The implicit expectations that when you deliver on, makes you look like a mind-reader.
I work with businesses who are drowning in this frontline intelligence and still lose the same fight on a loop.
The knowledge exists. It lives in our har drives and in the cloud. They are full of “you had to be there” stories that stay hidden or forgotten unless you go in an extract them.
It’s time to find your Zero
You now know why America needed the Akutan Zero more than another folder of Zero reports. Field knowledge beats distant description when you can re-fly the machine. Your company is full of these moments that die in Slack threads and pipeline adjectives. One intact story, captured with handling detail, can teach more than a quarter of debriefs.
The Intact Capture is the prompt that turns one story (a sales call, a coaching session, a site visit, a support recovery, an ops near-miss) into a reusable knowledge object. It forces the scene, the handling secrets, the asymmetries, and the exact moment the engine cut. It writes a green-lie check (what your CRM or checklist will still mark as fine), a stop rule, and a “Do this tonight” block so the knowledge leaves the call and enters the team the same day.
Below the paywall is the full machine. Path A if you can interview the person who lived it. Path B if you only have a recording, transcript, or messy notes. Run it once this week on a real fight you’re still losing. Get the plane on the ground. Then let someone else fly the test.
How to run it
Pick one live fight… a deal, install, escalation, or renewal where your average process keeps losing.
Choose Path A (15-minute interview with the person who was there) or Path B (recording, transcript, or notes).
Paste the prompt. Fill the capture target fields with ugly honest detail. Run it.
Do the “Do this tonight” block the same day. Send the message. File the knowledge object. Try the one behavior on the next similar call.
After one real re-flight, answer the recovery questions and run the prompt once more. Keep the second version.
The Intact Capture
Copy everything below into a fresh chat with your AI of choice. Replace the bracketed sections with your real situation. You should get a “Do this tonight” block first, then a knowledge object a second person can use without you in the room.
Prompt
You are helping me run The Intact Capture: extract ONE story or working moment into a reusable knowledge object. Think like the Navy recovering one intact fighter so test pilots could learn stick feel, not like an analyst summarizing “lessons learned” from a distance.
The goal is NOT a polished case study, a win writeup, or a campaign brief.
The goal is a machine other people can re-fly:
- the scene (where the wheels actually touched down)
- handling secrets (what stiffens when speed goes up)
- asymmetries (which way it rolls easy vs hard)
- when the engine cuts (negative-G moment where energy dies)
- what briefings and CRMs will still call “fine” while the fight is already lost
## How I am running this (pick one)
- [ ] Path A: live or recent interview with the person who lived it (I will paste their answers)
- [ ] Path B: I only have a recording / transcript / call notes / Slack dump (pasted below)
If Path A: interview first if needed. Ask short questions. Stay in objects, times, sentences said, body language. Do not accept morals (”they weren’t serious”) until the scene exists.
If Path B: treat the transcript/notes as wreckage you are recovering. Quote short lines. Do not invent dialogue, room objects, body language, or “what they felt” that is not in the artifact. If a detail is missing, mark it UNKNOWN and ask me for it.
## My capture target (fill this in)
Company / team context (one line, no secrets you shouldn’t share):
Role of the person who lived it:
When it happened (month or “last week” is fine; no fake Tuesday):
What “the Zero” is in plain language (the situation that keeps beating our average process):
What we already “know” from reports / CRM / pipeline language:
What I want a second person to be able to do after reading this capture:
Who should receive the capture tonight (role):
Optional CRM / checklist snapshot (stage, next step, amount, missing fields, green checkboxes):
## Optional source material (Path B or Path A notes)
Paste transcript excerpt, call notes, Slack, or interview answers here. If none yet, write “none. Ask me the interview questions first and stop after the questions.”
---
[PASTE SOURCE OR WRITE none]
---
## Constraints
- Do not invent client names, dollar amounts, product specs, or fake-specific days.
- Prefer objects, quoted lines, room details, and timestamps over abstract principles.
- No hype words (leverage, unlock, game-changer, fascinating).
- No “most people/founders” claims.
- Short sentences. Concrete nouns. Contractions OK.
- If the story arrives as a moral with no scene, REJECT it and ask for the bog details.
- Output must be usable tonight without redesigning your structure.
- Separate (a) what happened from (b) what we should do next.
- WIN-THEATER RULE: If the source is a #wins post, “great energy,” “feels solid,” “closed the loop,” pipeline emoji, or any polished win writeup, treat it as HIGH green-lie risk until you recover (1) who was NOT in the room, (2) the social-pressure sentence, (3) the incomplete CRM fields, and (4) the engine-cut moment. A clean win message is wreckage until proven intact.
- CRM LIE RULE: If this is sales/pipeline, name the fields that still look healthy (stage, next step, probability, “send proposal”) while commitment is fake or missing. Incomplete CRM is evidence, not a side note.
- Do not invent a 120-word room when the artifact is three Slack lines. Partial + UNKNOWN beats a fake scene.
## Build the capture in this exact structure
### Path label (one line)
State which path you ran: Path A (interview) or Path B (artifact recovery).
### 0. Source quality check (REQUIRED before Do this tonight)
- Intact enough to fly? yes / partial / no
- What is still UNKNOWN (bullets). Must include social pressure / missing people / incomplete systems fields when the source is a clean win or green checklist.
- Green lie risk: what existing CRM field, checklist, Slack #wins language, or meeting language will mark this as fine while the real failure already happened
- Stop rule: one line. If X is true on a future call, do not keep “educating” / do not mark healthy pipeline / do not leave without Y
If intact = no: write ### Do this tonight as a RECOVERY plan only (who to interview, 5 questions, where to file the answers), then ### 7. Interview recovery questions, then STOP. Do not invent a full knowledge object.
If intact = partial or yes: continue with Do this tonight + full sections 1–8. Keep every invented-looking detail marked UNKNOWN if it was not in the source.
### Do this tonight (REQUIRED after section 0)
If intact = no (recovery mode), four blocks:
1. Who to interview in the next 24 hours (role + name if known)
2. Exact message / calendar note to book 12 minutes (paste-ready, under 80 words)
3. The 5 recovery questions you will ask (short, object-level)
4. Where the answers will be filed (filename + 3-line project/instruction paste)
If intact = partial or yes, four blocks:
1. Who to send the capture to (role)
2. The exact message to send them (paste-ready, under 80 words)
3. The one behavior to try on the next similar call/visit (one sentence)
4. Where to file this so it is findable (suggested filename + 3-line project/instruction paste)
If you cannot fill these from my inputs, ask for the missing fields and stop.
### 1. Scene title
One line. Physical, not clever.
### 2. The room (only if intact = partial or yes)
If source is rich: 120–220 words, shoulder-cam, 5–8 object bullets, end with what was almost about to happen.
If source is thin (Slack win, 3–10 lines): 40–80 words max. Quote only what exists. List UNKNOWN object slots as bullets. Do not pad with invented furniture.
### 3. Handling secrets
List 3–5 stick-feel facts.
Each MUST use this shape:
- **When speed/pressure increased:** [what got hard or stiff]
- **What a briefing would have said instead:** [the sanitized version]
- **What the hands/ears actually needed:** [the usable cue]
### 4. Asymmetries (roll left vs roll right)
Two columns in bullets:
- Rolls easy toward...
- Rolls hard toward...
Then one line: “If we only practice the easy roll, we will keep losing when the hard roll is the real exit.”
### 5. When the engine cut
Name the negative-G moment in one short paragraph.
Include the exact sentence, silence, glance, or non-decision if known.
If unknown, write UNKNOWN and give the question that would recover it.
### 6. Reusable knowledge object (paste-ready)
Output as a fenced block the user can drop into Notion/Drive/Slack:
```text
// FILE: intact-capture/<short-slug>.md
Title:
Scene (5 lines max):
Handling secrets (bullets):
Asymmetry:
Engine cut:
Green lie:
Stop rule:
Next-flight tactic (one behavior, one sentence):
Who else should read this:
```
### 7. Interview recovery questions (always include)
5 sharp questions that would make the next revision more intact.
At least 2 must probe for objects, quoted lines, or the engine-cut moment.
If Path B, at least 1 must ask what the artifact cannot show (what they felt in their hands, what they almost said).
### 8. Capture scorecard
| Check | Pass? | Note |
| :---- | :---- | :-- |
| Physical scene a stranger could sketch | yes/no | |
| At least one handling secret is stick-feel, not a moral | yes/no | |
| Asymmetry named (easy vs hard) | yes/no | |
| Engine-cut moment named or marked UNKNOWN with a recovery question | yes/no | |
| Green lie named | yes/no | |
| Stop rule is operational (if X, don’t Y) | yes/no | |
| Do this tonight is paste-ready | yes/no | |
If any critical row is no, fix the capture before finishing or list exactly what you still need from me.
## After you draft
Ask me only the highest-value missing pieces (max 5 questions). Then stop. Do not expand into a training program, battle card suite, or multi-week enablement plan unless I ask.