The intelligence analyst's knowledge base has several properties that distinguish it from knowledge bases in other analytical professions. Intelligence knowledge entries must clearly separate what is known (collected) from what is assessed (analytically judged); they must document analytical confidence separately from the underlying evidence; they must track how analytical judgments have evolved over time rather than simply reflecting current best assessment; and they must capture what collection gaps tell the analyst as much as what collection shows.
Four knowledge domains constitute the intelligence analyst's professional knowledge base: collection and source intelligence (the intelligence picture built from collection, with its gaps and reliability assessments), analytical judgments and their evolution (the developed assessments on key topics, with confidence levels and judgment history), tradecraft and methodological expertise (the analytical methods and techniques that produce rigorous assessment), and professional and institutional knowledge (the institutional context that makes analysts effective within their professional environment).
Domain 1: Collection and Source Intelligence
Collection and source intelligence is the organized picture of what has been collected on key topics, how reliable different sources are, and what the collection gaps reveal as much as what collection shows. This domain is the empirical foundation for analytical work.
Organization by topic:
COLLECTION AND SOURCE INTELLIGENCE KB
BY TOPIC:
Topic: [Subject of intelligence interest]
Last updated: [Date]
WHAT COLLECTION SHOWS:
Core finding 1: [Most important collected fact] — Source: [Source], Date: [date]
Core finding 2: [Second key fact] — Source: [Source], Date: [date]
Corroboration: [Whether key findings are corroborated across sources]
WHAT COLLECTION DOESN'T SHOW:
Collection gaps: [What we're not seeing]
Why the gaps matter: [What we can or can't infer from them]
What the gaps tell us: [If silence from a normally-reporting source is itself significant]
SOURCE COVERAGE:
Sources reporting on this topic: [Collection lines with relevant reporting]
Sources not reporting on this topic: [Normally-reporting sources that have gone silent]
COLLECTION CONFIDENCE:
Overall: [ ] High — multiple reliable sources + corroboration
[ ] Moderate — good sources, some gaps
[ ] Low — limited collection, few sources
[ ] Very limited — single source, no corroboration
COLLECTION REQUIREMENTS:
What would most improve the picture: [Priority collection gaps to fill]
BY SOURCE:
Source: [Source designation]
Type: [Collection type]
RELIABILITY:
Overall track record: [Historical reliability]
Topic-specific reliability: [More or less reliable on specific subjects]
Known biases: [Motivations or perspectives that affect reporting]
INTERPRETATION GUIDANCE:
What absence of reporting means: [If silence from this source is significant]
How to weight against other sources: [Relative credibility guidance]
What this source can and can't tell us: [Capability and limitation]
"What collection doesn't show" is the analytical integrity field. Intelligence analysis that only presents what collection shows, without acknowledging collection gaps, creates a systematically distorted picture — because the analyst and the decision-maker are seeing only what collection has reached, not the full picture. The collection gap on a high-priority topic, properly noted, tells the analyst and the decision-maker something important about the limits of what can be assessed with confidence.
"What the gaps tell us" goes further: in some cases, collection gaps are themselves analytically significant. A source that normally reports on a subject and has stopped reporting may have been discovered; a collection gap in an area where collection should be possible but isn't may indicate denial and deception. Documenting what gaps tell us prevents the analyst from treating silence as simply the absence of information.
Domain 2: Analytical Judgments and Their Evolution
Analytical judgments are the assessed conclusions that intelligence analysis produces: not just what the collection shows, but what the analyst assesses it means, with what level of confidence, based on what assumptions. This domain must track not just current best assessments but how those assessments have evolved and what drove changes.
ANALYTICAL JUDGMENTS KB
BY TOPIC:
Topic: [Subject of analytical responsibility]
CURRENT ASSESSMENT:
Judgment: [The analytical conclusion]
Confidence: [ ] High [ ] Moderate [ ] Low [ ] Uncertain
Date of last revision: [When this judgment was last updated]
BASIS:
Key collection supporting this: [What grounds the judgment]
Key assumptions: [What this judgment depends on being true]
Alternative explanations considered: [What else could explain the collection]
Why the primary hypothesis is preferred: [The analytical reasoning]
WHAT WOULD CHANGE THIS:
Evidence that would shift toward a higher-probability alternative: [Specific]
Evidence that would increase confidence in the current judgment: [Specific]
COLLECTION GAPS AFFECTING CONFIDENCE:
What we'd expect to see if the hypothesis is correct: [Testable implications]
What's missing from collection: [Gaps that limit confidence]
JUDGMENT HISTORY:
Prior judgment: [Prior analytical position — if changed]
What collection or development changed it: [What drove the update]
Date of change: [When]
Prior prior judgment: [If there's been more than one revision]
[Continue as needed]
ANALYTICAL QUALITY NOTES:
Cognitive traps considered: [Mirror imaging, anchoring, confirmation bias — active consideration]
Alternative hypotheses genuinely engaged: [Whether alternative explanations received fair consideration]
"What would change this" is the analytical rigor field that distinguishes analytical judgment from fixed belief. Intelligence professionals must be able to specify what evidence would shift their assessment; the assessment that can't be updated by any conceivable collection is not analytical openness. This field also drives collection requirements: if the analyst knows what evidence would shift their judgment, that evidence is what the collection enterprise should prioritize acquiring.
"Judgment history" is the professional accountability and learning field. Recording prior judgments — not just the current best assessment — enables several important professional functions: tracking analytical accuracy over time; identifying patterns in how individual analysts update their assessments; and providing the honest account of how analytical understanding has evolved that professional rigor requires. Intelligence analysis that presents only the current judgment, without the evolution that led to it, loses the professional history that enables learning.
Domain 3: Tradecraft and Methodological Expertise
Analytical tradecraft is the accumulated expertise about how to conduct intelligence analysis well: the structured analytical techniques that reduce cognitive bias, the calibration practices that produce accurate confidence assessments, the writing conventions that communicate analytical conclusions clearly, and the quality control practices that catch analytical errors before products reach decision-makers.
ANALYTICAL TRADECRAFT KB
BY TECHNIQUE:
Technique: [e.g., "Analysis of Competing Hypotheses" or "Devil's Advocacy"]
WHEN TO USE:
Best applications: [Where this technique adds value]
Warning signs it's needed: [When the analyst should reach for this technique]
HOW TO APPLY:
Step by step: [How to actually do this]
Common errors: [What goes wrong when people apply this incorrectly]
What good application looks like: [How to evaluate whether it was done well]
MY EXPERIENCE:
Where I've applied it: [Personal experience with this technique]
What I've learned: [Practical wisdom from using it]
BY COGNITIVE TRAP:
Trap: [e.g., "Mirror imaging" or "Anchoring and adjustment"]
WHAT IT IS:
Description: [The analytical failure mode]
How it manifests: [What it looks like in practice]
WHERE I'VE SEEN IT:
In my own work: [If I've caught myself doing this]
In others' work: [Examples without personalizing]
HOW TO GUARD AGAINST IT:
Active countermeasures: [What analysts can deliberately do]
When to be especially vigilant: [Conditions that make this trap more likely]
BY WRITING AND COMMUNICATION:
Element: [A finished product quality — e.g., "Conveying confidence levels"]
WHAT WORKS:
Language and structure that effectively communicate: [What I've found effective]
Audience-specific adaptations: [If different audiences need different approaches]
COMMON ERRORS:
What doesn't work: [Analytical writing failures]
Why: [What the failure mode is]
"In my own work" under cognitive traps is the professional humility field that makes this section actually useful. Intelligence analysts who document cognitive traps they've caught in their own work — where mirror imaging colored their assessment, where anchoring made them slow to update, where confirmation bias led them to underweight disconfirming collection — are developing analytical self-awareness that can protect against future instances of the same errors. The analyst who believes cognitive traps happen to others but not to themselves is particularly vulnerable to them.
Domain 4: Professional and Institutional Knowledge
Professional and institutional knowledge is the understanding of how the intelligence enterprise works: the analytical standards and requirements, the collection capabilities and their limitations, the professional relationships that facilitate collaboration, and the institutional dynamics that affect how intelligence reaches and is used by decision-makers.
PROFESSIONAL AND INSTITUTIONAL KB
BY ANALYTICAL STANDARD:
Standard: [An analytical or product standard]
REQUIREMENT:
What's required: [The standard]
Why it exists: [The professional rationale]
MY PRACTICE:
How I apply this: [How I implement this standard]
Where I find it challenging: [Personal difficulties with this standard]
What I've learned: [Practical wisdom about applying it]
BY COLLECTION CAPABILITY:
Capability: [A collection system or access]
WHAT IT CAN DO:
Access: [What intelligence it can produce]
Timeliness: [How quickly it produces it]
LIMITATIONS:
What it misses: [Collection limitations]
What distorts its reporting: [If relevant — source biases or collection artifacts]
BY PROFESSIONAL RELATIONSHIP:
Relationship: [An analytical colleague, customer, or partner]
Context: [Professional relationship type]
WHAT'S WORKED:
How to collaborate effectively: [What I've learned]
What they value: [What this person / office most benefits from in collaboration]
WHAT TO KNOW:
Their analytical perspective: [How they approach analytical questions]
Potential friction points: [Where collaboration has been difficult]
The Pre-Product Knowledge Retrieval Sequence
Before producing a finished intelligence product:
-
Collection KB: what does the collection picture show on this topic? What are the gaps? What do the gaps tell us?
-
Analytical judgments KB: what's the current best assessment? What's the confidence level? What assumptions is this judgment resting on?
-
Judgment history: have prior assessments evolved? What drove changes?
-
Tradecraft KB: what analytical techniques are appropriate for this product? What cognitive traps should I be especially watchful for?
-
Institutional KB: are there specific analytical standards or requirements for this product type?
This sequence converts accumulated analytical work into the foundation for each new product.
Key Takeaways
-
Document what collection gaps tell us, not just what collection shows. Collection silence is analytically significant; treating gaps as simply absence underuses the intelligence picture.
-
Track judgment history, not just current assessment. Prior assessments and what changed them enable professional learning and analytical accountability.
-
"What would change this" is the rigor field that distinguishes assessment from belief. Specifying in advance what evidence would shift the judgment maintains analytical openness and drives collection requirements.
-
Document cognitive traps you've personally experienced. Self-awareness about one's own analytical vulnerabilities is more valuable than abstract knowledge of traps that happen to others.
-
Separate what is collected from what is assessed. The knowledge base entry that clearly distinguishes known facts from analytical conclusions maintains the professional standards that intelligence analysis requires.
Conclusion
The intelligence analyst's knowledge base organizes four domains: collection and source intelligence ("what collection doesn't show" and "what gaps tell us" as the analytical integrity and analytical significance fields; source reliability by topic with interpretation guidance); analytical judgments and their evolution ("what would change this" as the analytical rigor field; judgment history as the professional accountability and learning field; cognitive traps actively considered); analytical tradecraft ("in my own work" under cognitive traps as the professional humility field; structured techniques with common errors and personal experience; writing and communication quality with what works and what doesn't); and professional and institutional knowledge (analytical standards with personal practice and challenges; collection capabilities and their limitations; professional relationships with what's worked and what to know). The pre-product knowledge retrieval sequence converts the accumulated analytical knowledge base into the foundation for each new finished intelligence product.
To go deeper, check out Building a Personal Knowledge Base.