Most intelligence leaders struggle with requirements conversations because they begin by asking, "What intelligence do you need?" That question is too broad. Most consumers do not think in terms of intelligence; they think in terms of decisions, risks, deadlines, and uncertainty.

The intelligence leader's job is to translate business, mission, or operational concerns into clear intelligence requirements. A better approach is to guide the conversation through a deliberate progression.

1. Start with the Decision, Not the Intelligence Product

The first objective is to understand what the consumer is trying to decide, influence, prevent, or prepare for. This shifts the discussion away from "send me reports" and toward decision support.

  • What decisions are you responsible for making in the next 30, 60, or 90 days?
  • What could happen that would force you to change your current plan?
  • Where do you feel you have the least visibility right now?
  • What keeps you from acting faster or with more confidence?
  • What would you like to know earlier than you know it today?

2. Define the Operational Problem

Once the decision space is clear, narrow it into a specific problem statement. This helps distinguish general awareness from a true requirement.

  • What specific threat, risk, or uncertainty are you worried about?
  • Is this a strategic, operational, or tactical concern?
  • Is the issue persistent, emerging, or event-driven?
  • Who or what could affect your mission, business process, or environment?
  • What would success look like if intelligence helped you here?

3. Identify the Trigger for Action

Requirements are strongest when they are tied to a threshold or trigger. Intelligence is most useful when it changes behavior. This is where intelligence leaders begin converting vague concerns into warning thresholds and collection priorities.

  • What would cause you to escalate, delay, redirect, or intervene?
  • What indicators would make you say, "We need to act now"?
  • What would be an early warning sign that this problem is becoming real?
  • What would you need to see to justify additional resources or leadership attention?
  • What information would change your current level of confidence?

4. Clarify the Object of Interest

Consumers often describe symptoms rather than targets. The intelligence leader must pin down the true subject. This prevents requirements from becoming so broad that collection and analysis lose focus.

  • Who are you most concerned about?
  • Which actors, organizations, systems, geographies, or issues matter most?
  • Are we focused on adversary intent, capability, opportunity, or impact?
  • Are there specific vendors, technologies, partners, regions, or business units involved?
  • What is out of scope?

5. Understand Time, Tempo, and Cadence

A requirement without a time context is rarely actionable. The answers here clarify whether the requirement belongs in warning, decision support, baseline analysis, or environmental monitoring.

  • When do you need this intelligence to be useful?
  • How often do you need updates?
  • Is this a standing requirement or tied to a specific event?
  • Do you need immediate alerting, periodic summaries, or deep analysis?
  • What is the cost of learning this too late?

6. Establish Priority and Consequence

Not every question merits the same level of effort. Requirements must be ranked. This forces prioritization and guards against "everything is important."

  • If this requirement is not answered, what is the consequence?
  • Which issue has the highest business, mission, or operational impact?
  • Where is the organization most exposed?
  • If we could only answer three questions this quarter, which should they be?

7. Determine How the Consumer Will Use the Answer

The intelligence leader needs to understand what action the consumer will take with the output. This is essential. If the answer will not influence action, it may not be a real requirement.

  • What will you do differently if we answer this?
  • Who else needs this intelligence?
  • Will this support a decision, a brief, a budget request, a policy change, an operational action, or a risk acceptance decision?
  • What format works best for you: alert, dashboard, brief, estimate, or deeper assessment?
  • What level of confidence do you need to act?

8. Convert the Discussion into Requirement Language

Once the discussion is complete, the intelligence leader should restate the requirement in a disciplined form. A good requirement usually has five parts:

  1. The decision or outcome being supported
  2. The object of interest
  3. The intelligence question
  4. The timeframe
  5. The trigger or expected use

For example: "Provide early warning on ransomware activity targeting third-party healthcare vendors that support patient operations, in order to inform business continuity decisions and vendor risk escalation over the next 90 days." That is far better than "Watch ransomware."

9. Use Layered Question Types During the Conversation

A practical way to run the meeting is to use question categories in sequence.

Discovery Questions

Used to surface the concern: What are you worried about? Where do you lack clarity? What decisions are hardest right now?

Diagnostic Questions

Used to unpack the issue: Why is this important now? What changed? What makes this difficult to assess today?

Prioritization Questions

Used to rank needs: Which of these matters most? Which carries the greatest consequence? Which requires the fastest response?

Action Questions

Used to connect intelligence to behavior: What would you do if this were confirmed? What would make you act sooner? What would change your plan?

Constraint Questions

Used to define scope: What is out of scope? What assumptions are we making? Are there legal, policy, or resource constraints?

Validation Questions

Used to ensure shared understanding: Let me restate this requirement to you. Is the key issue early warning, trend understanding, or decision support? Have I captured the real question, or just the symptom?

10. Drive the Conversation Like an Interviewer, Not a Note Taker

The intelligence leader should not passively record requests; they should actively shape them. Two questions alone can dramatically improve requirement quality: "Help me understand what decision this supports." And: "If we answered that perfectly, what would you do with it?"

  • Challenge vague terms like "threats," "risks," "bad actors," or "keep me updated"
  • Ask for concrete examples
  • Force tradeoffs
  • Separate standing requirements from one-time questions
  • Distinguish curiosity from decision need
  • Restate and refine in plain language

11. A Simple Meeting Structure

Open the session with: "I want to understand what decisions you need to make, what uncertainty is getting in the way, and what intelligence would materially improve your confidence." Then work through: what decisions matter most, what risks affect those decisions, what would need to be known earlier, what would trigger action, and what should be monitored continuously versus answered once.

Close by summarizing: the top requirements heard, how you would prioritize them, the reporting cadence you recommend, and what you can answer now versus what requires collection development.

12. Common Mistakes Intelligence Leaders Make

  • Asking consumers to write the requirements themselves. Most consumers cannot.
  • Accepting vague requirements like "keep me informed," "watch this actor," or "give me strategic intel"
  • Failing to ask what action the intelligence will support
  • Confusing information interests with intelligence requirements
  • Not defining triggers, timelines, or scope
  • Leaving the meeting without restating the requirement in a structured way

13. A Practical Template for Translating the Conversation

After the meeting, capture each requirement using a structured form: Requirement Title (a short, decision-focused label), Consumer (who owns the decision), Decision Supported (what decision or action this informs), Core Intelligence Question (what needs to be understood), Object of Interest (actor, issue, geography, technology, vendor, campaign), Why It Matters (operational or business consequence), Time Horizon (immediate, near-term, long-term, standing), Indicators / Triggers (what signs would prompt action), Priority (high, medium, low), and Dissemination Format (alert, brief, dashboard, estimate, weekly summary).

This gives the leader a repeatable method instead of an informal chat.

14. The Mindset Shift

The intelligence leader is not there to ask, "What do you want us to report on?" They are there to diagnose: What must the consumer decide? What uncertainty is blocking that decision? What intelligence would reduce that uncertainty? What signs should trigger action?

Key Principle

Approaching the conversation as a diagnostic exercise, not a request-taking exercise, is what separates intelligence programs that consistently deliver decision advantage from those that produce reports no one reads.