The Trapped Intelligence Diagnostic
Start here. This is the top-level diagnostic — the other tools are deep dives into specific findings from this one.
What this does: Walks you through finding exactly where intelligence is stuck in your organization — and what kind of intervention would actually release it.
The business outcome: You stop applying generic fixes (restructuring, training, new hires) and start matching the intervention to the actual problem. Different traps need different keys.
Quickstart
Pick a specific failure you’ve seen — a decision that went wrong, a capability that isn’t being used, a pattern that keeps repeating. Walk it through the four checkpoints below in order. The first checkpoint that fails is where the intelligence is trapped, and each checkpoint has its own class of fix. For detailed instructions see “How to use it” below.
Template
| Checkpoint | Question | Status | If this is where it’s stuck |
|---|---|---|---|
| 1. SEE | Does the right information reach the right people? | ☐ Yes ☐ No | Fix the information flow — routing, channels, Topology |
| 2. UNDERSTAND | Can the people who receive it make sense of it? | ☐ Yes ☐ No | Fix the modeling — training, tools, expertise, translation |
| 3. REACH | Can the people who understand it actually act? | ☐ Yes ☐ No | Fix the authority — permissions, budget, position, mandate |
| 4. SELF-MODEL | Does the team know what it’s capable of? | ☐ Yes ☐ No | Fix the self-model — awareness, visibility, honest assessment |
The checkpoints are ordered by dependency. There’s no point fixing Understand if the information never arrives (See). There’s no point fixing Reach if nobody can interpret what they’re seeing (Understand). Run them in order and stop at the first failure.
How to use it
Step 1: Name the specific instance. Don’t diagnose “communication is bad.” Diagnose “the product team shipped the wrong feature because they didn’t know customers were asking for something different.” Specific instances have diagnosable causes. Vague complaints don’t.
Step 2: Walk Checkpoint 1 — SEE.
- Did the relevant information exist inside the organization? (If it didn’t exist at all, this isn’t Trapped Intelligence — it’s a genuine gap in capability.)
- Did it reach the people who needed it to make the decision?
- If not: where did the signal stop? Who had it? What channel was supposed to carry it? Why didn’t it?
- Common See failures: reports that get summarized until the signal disappears, teams that don’t talk to each other, information that lives in one person’s head and never gets shared, data that arrives too late to matter.
If the signal never arrived, stop here. The intervention is at the information-flow layer: routing, meeting structure, reporting cadence, direct channels. Don’t restructure authority when the problem is that the right data isn’t reaching the right people.
Step 3: Walk Checkpoint 2 — UNDERSTAND.
- The information arrived. Could the people who received it make sense of it?
- Did they have the domain knowledge, the analytical tools, or the experience to interpret what they were seeing?
- If not: what was missing? Training? A different kind of expertise in the room? A better analytical tool? A translation layer between the people who gathered the data and the people who need to act on it?
- Common Understand failures: the competitive intelligence report arrives but nobody can interpret pricing trends, the engineering team sees the customer data but doesn’t know how to read churn signals, the executive gets the financial model but doesn’t understand the assumptions behind it.
If the signal arrived but nobody could interpret it, stop here. The intervention is at the modeling layer: hire the right expertise, provide the training, build the analytical tool, or create the translation layer. Don’t fix the authority structure when the problem is that the people in the room can’t make sense of what they’re seeing.
Step 4: Walk Checkpoint 3 — REACH.
- The information arrived, and the right people understood it. Could they act?
- Did they have the authority, the budget, the mechanism, or the organizational position to do something about it?
- If not: what was blocking them? Wrong level in the org chart? No budget? No mandate? A governance process that prevents timely action?
- Common Reach failures: the middle manager who sees the train coming but has no lever to pull, the analyst who knows the answer but has no way to get it to the decision-maker, the team that understands the problem but can’t get approval to fix it.
If they understood it but couldn’t act, stop here. The intervention is at the authority layer: change who has the mandate, adjust the budget, restructure the decision rights. Don’t invest in training when the problem is that the trained people can’t do anything with what they know.
Step 5: Walk Checkpoint 4 — SELF-MODEL.
- If all three prior checkpoints pass — the information arrived, the team could interpret it, and they had the authority to act — but the failure still happened, the problem might be in the self-model.
- Does the team know what it’s capable of? Does the leader know what his people can do?
- Common Self-Model failures: the senior engineer whose deployment expertise nobody knows about (invisible capability), the executive who thinks he understands a domain he doesn’t (overconfidence), the team that underestimates its own ability to enter a new market (learned helplessness).
If the self-model is wrong, the fix is awareness. Make invisible capabilities visible. Reality-test overconfident self-models before they cause damage. This is often the cheapest intervention — you don’t need to hire, build, or restructure. You need to see what’s already there.
Where to learn more
Other tools:
- The Team Trade-Off Matrix — Diagnose where combining people created the contraction you just found.
- The Franz Ferdinand Check — If Checkpoint 3 passed but the action produced unintended consequences, this finds where authority exceeded understanding.
- The Capability Reality Check — Deep dive into Checkpoint 4 (the self-model problem).
Vocabulary: Trapped Intelligence, Computational Boundary, Cognitive Boundary, Causal Boundary, Frame