Intelligence Direction is the crucial first phase of the intelligence cycle. It involves identifying the information needs of decision-makers and translating them into specific intelligence requirements.
This involves understanding what information decision-makers need to make informed choices. It's about asking the right questions and defining the scope of the intelligence effort.
Requirements gathering is where intelligence work begins—not with satellites or encrypted communications, but with a simple yet profound question: "What do you need to know?" This seemingly straightforward inquiry is actually the most complex part of the intelligence cycle. It's the difference between providing decision-makers with what they think they want versus what they actually need to make informed choices.
Effective requirements gathering starts with understanding your audience. A military commander planning an operation needs different intelligence than a diplomat negotiating a treaty or a business executive entering a new market. Each operates in different timeframes, faces different risks, and makes different types of decisions.
The skilled intelligence professional becomes a translator between two worlds: the world of available information and the world of decision-making needs. This requires developing what we call "customer empathy"—the ability to see through the decision-maker's eyes and understand their pressure points, deadlines, and constraints.
Good intelligence requirements follow the SMART principle:
Requirements gathering is an investigative process. Initial requests are often just the tip of the iceberg. A request for "economic data on Country Y" might actually stem from concerns about supply chain vulnerabilities, trade negotiations, or investment decisions. The analyst must probe deeper:
The best requirements are collaborative products. They emerge from dialogue between intelligence professionals and decision-makers. This conversation should establish:
Every requirement should be documented clearly. This serves multiple purposes: it ensures all parties have the same understanding, provides a reference point for analysts, and creates accountability for both the requester and the intelligence organization.
Requirements gathering is both an art and a science. It requires technical knowledge of intelligence capabilities, interpersonal skills to build relationships with customers, and the analytical thinking to translate complex needs into actionable intelligence tasks. Master this skill, and you'll set the foundation for intelligence success.
"Intelligence requirements are like teenagers asking for money—they're rarely specific about what they actually need it for, they want it immediately, and they get frustrated when you ask follow-up questions. The difference is that teenagers usually just want pizza money, while intelligence customers might be planning to invade something."
Fun fact: The most common intelligence requirement in history is probably "What are they up to?" closely followed by "Are they going to attack us?" and "Can we trust them?" These three questions have likely launched a thousand intelligence operations and kept analysts busy since the dawn of civilization.
Not all intelligence requirements are equally important. This step involves ranking requirements based on urgency, impact, and feasibility, ensuring resources are allocated effectively.
In an ideal world, intelligence organizations would have unlimited resources to answer every question that comes their way. In the real world, intelligence professionals face a harsh reality: everyone wants to know everything, and they want it yesterday. This is where prioritization becomes not just important—it becomes survival.
Prioritization in intelligence is like triage in an emergency room. You must quickly assess what's most critical, what can wait, and what might be interesting but isn't essential. The stakes are often just as high: poor prioritization can mean the difference between preventing a crisis and merely documenting it after the fact.
Effective prioritization requires a systematic approach. The classic framework evaluates requirements across multiple dimensions:
Not all customers are equal in the intelligence world. Understanding your organization's stakeholder hierarchy is crucial for effective prioritization:
Intelligence prioritization isn't a one-time event—it's a continuous process. Requirements that were low priority yesterday might become critical today due to changing circumstances. Effective intelligence organizations build flexibility into their prioritization systems:
Remember that behind every intelligence requirement is a human being facing a difficult decision. Prioritization decisions can have profound impacts on these individuals and their organizations. This adds an emotional dimension to what might otherwise be a purely analytical process.
Effective prioritization requires:
"Prioritizing intelligence requirements is like being a restaurant server on Mother's Day—everyone thinks their order is the most important, they all want it immediately, and somehow you're supposed to keep everyone happy while the kitchen is on fire."
The intelligence prioritization drinking game: Take a sip every time someone says their requirement is "urgent and critical." Take two sips if they claim it's for "national security." Finish your drink if they say "the President needs this by tomorrow" for something they've known about for six months. (Note: Please don't actually play this game—you'd be unconscious by lunch.)
Once requirements are prioritized, resources (personnel, technology, budget) are assigned to the intelligence tasks. This ensures that the necessary tools and expertise are available for collection and analysis.
Effective resource allocation in intelligence is about matching the right capabilities to the most critical requirements. It's not just about having resources—it's about deploying them where they'll have the greatest impact.
"Resource allocation in intelligence is like playing Tetris with your budget—just when you think you've got everything fitting perfectly, someone drops a new 'urgent' requirement shaped like a giant 'L' that ruins your whole plan."
The three laws of intelligence resource allocation: 1) There's never enough, 2) Everyone wants more, 3) The most important requirements always emerge after you've allocated everything.
The intelligence improvement loop that transforms experience into wisdom, problems into opportunities, and intelligence direction from a static plan into a dynamic system.
Intelligence direction isn't a "set it and forget it" process—it's a living, breathing system that must constantly evolve. Think of it as tending a garden: you don't just plant seeds and walk away. You water, prune, fertilize, and adjust based on what you observe.
This phase recognizes a fundamental truth: our initial understanding of what intelligence is needed is almost always incomplete. As we learn more about a situation, new questions emerge. As circumstances change, priorities shift. As we discover the limits of our capabilities, we must adjust our expectations.
Effective feedback in intelligence comes from multiple sources:
Gathering feedback requires more than just asking "How did we do?" It requires:
"Intelligence feedback and refinement is like marriage counseling for your organization—it requires honest communication, willingness to change, and the maturity to admit when you're wrong. The good news is that unlike marriage counseling, you don't have to split custody of the office coffee machine if things don't work out."
The Five Stages of Intelligence Feedback: 1) Denial ("Our process is fine!"), 2) Anger ("Who are they to criticize us?"), 3) Bargaining ("Maybe we could just tweak this one little thing..."), 4) Depression ("We're terrible at everything"), 5) Acceptance ("Okay, let's figure out how to improve"). The secret is that professional intelligence organizations skip straight to stage 5, unless it's Monday morning and the coffee hasn't kicked in yet.
