Key Intelligence Topics are the big-picture strategic issues that intelligence has to address. They represent the needs of management for planned decisions or pending action — broad themes broken down into sub-categories as necessary.
Key Intelligence Questions are specific, bite-sized questions that, when answered, provide the insight required to support each KIT. They guide the collection effort and define precisely what the CI team needs to find out.
Together, KITs and KIQs express what a company needs to know. They're the starting point for the entire CI process — the first step in the cycle we published in Nature Biotechnology: Intelligence Requirements → Collection Plan → Secondary Collection → Human Collection → Processing & Analyzing → Final Analysis → CI Review → Strategy. KITs and KIQs are the "Intelligence Requirements" that start the cycle, and the CI Review that ends it loops back to reassess and refine them.
Information needs get organized into a hierarchical structure: KIT → Sub-KIT → KIQ. That structure facilitates collection tasking, communication, analysis, and reporting.
A well-constructed KIT is a prioritized summary of the topics of greatest significance to the brand that provide direction for CI operations. A well-constructed KIQ is a specific, prioritized question identified within the context of a KIT — the basis for the intelligence research that will follow.
This matters more than most people think:
A KIQ like "What's happening with the competitor?" fails on every criterion. A KIQ like "What primary and secondary endpoints are competitors using in their Phase III trial for indication X, and how do they differ from our design?" is specific, measurable, actionable, relevant, and time-bound.
When you ask only general questions, you get general answers that are not conducive to decision-making. The quality of your KIQs directly determines the quality of intelligence your program produces.
KITs and KIQs help surface the difference between what the intelligence consumer says they need and what they actually need. This distinction is critical. A stakeholder who asks "What did the competitor announce at the conference?" may actually need to know "How does the competitor's conference data change our positioning for launch?"
The CI professional's job is to anticipate and explore decision-making needs, not transcribe the initial request. That requires understanding the stakeholder's decision context, their planning cycle, and the assumptions underlying their current strategy.
a senior strategy executive at a top-10 pharma company puts it well: "I want AI to do the data gathering so I can spend time on strategic thinking — framing those strategic choices, scenarios, implications." The point applies equally to how KIQs get defined. The best KIQs don't just ask for data — they ask for the intelligence that frames strategic choices. The CI professional who can anticipate those choices, and define KIQs that surface the relevant intelligence before the executive asks for it, is the one who earns the seat at the table.
The successful CI professionals are the ones who can anticipate stakeholder requirements and define those requirements in detail. KIQ definition is a proactive, expertise-driven activity — not a passive brief-taking exercise.
KITs and KIQs provide the structural foundation for everything:
Without this foundation, collection becomes unfocused, analysis lacks direction, and deliverables miss the mark — regardless of how well-produced they are.
KITs and KIQs connect CI activities to specific business decisions and specific decision makers. This creates accountability in both directions: the CI team is accountable for answering the defined questions, and stakeholders are accountable for providing the strategic context that makes those questions meaningful.
The process takes approximately two weeks when done properly.
Engagement is essential throughout. But there's a cardinal rule:
Don't mention the KIT.
When speaking with internal customers, talk about what's important to them. Use their vocabulary. Position material from their frame of reference. What words are common to both of you, and what sounds like jargon? Dump the jargon. Decision makers don't think in terms of "KITs" and "KIQs." They think in terms of decisions, risks, and opportunities.
The planning meeting with internal customers should cover: alignment with the budget cycle, decision points where CI can influence outcomes, key competitive events, planning processes that need support, upcoming industry meetings, monitoring cadence, and preparation for unplanned CI needs.
Properly defining requirements demands effective client interaction and an experienced CI team. The CI professional takes responsibility for anticipating decision-making needs, defining timelines and deliverable requirements, anticipating intelligence needed to support analysis, anticipating changes to KITs as the landscape evolves, and responding to the customer's real needs — not being reactive to their immediate questions.
This distinction matters in practice. A stakeholder who asks "Did the competitor get FDA approval?" may actually need to know "How does the competitor's regulatory timeline affect our launch window, and what should we do about it in the next 90 days?" The CI professional's job is to surface the real intelligence need beneath the tactical question.
Not all KIQs are equal. Prioritization uses a three-tier system:
Each KIT should be aligned to a business objective with a clear expected action. Only if the information will impact strategy or inform a specific business decision should it be prioritized.
KIT difficulty depends on four variables: time, talent, sensitivity, and availability of sources. Some questions are inherently harder to answer — they require rare expertise, access to sensitive information, or extended collection periods. The prioritization process has to account for these constraints.
Prioritization requires honest conversations about what's achievable. Variables to consider: impact on strategy, likelihood of accuracy, ease of collection, who's asking, and whether the answer can arrive before the decision window closes.
Push back gently when expectations exceed what's feasible. Escalate if necessary. And be prepared for new priorities — the competitive landscape doesn't wait for your planning cycle.
Before collection begins, define how the intelligence will be delivered:
Nothing destroys CI credibility faster than an analytically rigorous report that arrives too late, in the wrong format, or at the wrong level of detail.
How CI Evolves From Drug Discovery to Commercial Launch
The collection plan bridges KIQs and actual intelligence gathering. It determines who will gather what, when, where, and how.
In the CI process flow we published — Intelligence Requirements → Collection Plan → Secondary Collection → Human Collection → Processing & Analyzing → Final Analysis → CI Review → Strategy — the collection plan is step two. But it's directly governed by step one. Every element of the plan traces back to specific KIQs.
A robust plan considers the appropriate mix of secondary (public) and primary (human) sources for each KIQ, redundancy for critical questions to validate and triangulate, and cueing strategies — using findings from one source to guide questions for another.
The relationship between KIQs and collection is hierarchical. High-priority KIQs drive dedicated primary research — interviews with KOLs, competitors, industry experts. Medium-priority KIQs are tracked through secondary sources — clinical trial databases, regulatory filings, financial reports, conference proceedings. Low-priority KIQs are captured when relevant information surfaces.
Each collection cycle produces lessons about which sources are most productive, which approaches yield actionable intelligence, and where gaps persist. Those lessons feed forward into the next cycle. The collection plan should build on past experience and ensure efficiency and standardization.
KITs and KIQs are not a one-time exercise. The competitive landscape changes, new competitors emerge, clinical data shifts priorities, strategic decisions reshape what the organization needs to know.
The review cadence:
Calibrating to the client's leadership style matters too. Know your customer. Some stakeholders want data and analysis. Others want recommendations. Some prefer brief alerts. Others want comprehensive decks. Some engage deeply in the KIQ process. Others delegate and expect results. The CI professional has to adapt without compromising the rigor of the requirements process.
Theory without examples is hollow. These come from actual pharmaceutical CI programs — not textbook generalities but operational specifics that inform daily decisions.
Early Development: "What is the mechanism of action of competitor products, and how does it differ from our approach?" / "Which drug delivery technologies can we make proprietary?"
Clinical Development: "What phase are competitors' ongoing clinical studies in?" / "What primary and secondary endpoints are competitors using?" / "What's the known safety profile of competitor products versus ours?"
IP/Legal: "What known intellectual property exists for competitor products within the class?" / "What freedom to operate do we have?"
Market Access: "What's the pricing strategy of competitor products in each market?" / "What HEOR evidence are competitors generating?"
Loss of Exclusivity: "What's the status of competitors' API sourcing for generic versions?" / "What regulatory strategy are generic competitors pursuing?"
The full inventory — 156 strategic questions organized by development phase plus 102 questions organized by cross-functional decision point — reflects the complexity of the decisions that CI has to inform. The depth is not accidental.
How CI Evolves From Drug Discovery to Commercial Launch
In a well-designed CI function, six core deliverables flow from the KIT/KIQ foundation:
The connection is direct. KIQs determine what goes into every deliverable. Alerts answer specific KIQs. Landscapes map KIQ themes. Deep dives resolve complex KIQs. Quarterly reviews assess progress against the KIQ portfolio.
This holds across the entire product lifecycle. During Phase II/III, when the deliverables are competitive pipelines, clinical trial trackers, and product profile comparisons, the KIQs driving those deliverables focus on mechanisms of action, trial design, and enrollment progress. During pre-launch and launch, when the deliverables expand to include early warning systems, war games, and competitive threat assessments, the KIQs shift to competitor positioning, messaging, field force structure, and market access strategy. During loss of exclusivity, when the focus turns to Gx/biosimilar tracking, the KIQs address manufacturing capacity, regulatory routes, and first-to-market timing.
Without KIQs, deliverables become generic data dumps — comprehensive but unfocused. With KIQs, every deliverable answers a specific decision maker's question. That's the difference between CI that earns its seat at the table and CI that sits on a shelf.
After two decades of designing CI programs, certain failure patterns keep recurring.
1. Skipping requirements entirely. The majority of all CI failures originate at the requirements stage. Teams that jump to collection without defining what they need to know produce impressive volumes of data that don't answer anyone's questions.
2. Asking the wrong questions. CI professionals must respond to the customer's real needs, not react to their immediate questions. Decision makers often frame intelligence needs as tactical queries when strategic questions are what's needed. Surface the strategic question beneath the tactical request.
3. Not making KIQs SMART. Vague, immeasurable, untimed KIQs lead to unfocused collection. "Tell me about the competitor" is not a KIQ.
4. Using CI jargon with stakeholders. Don't mention the KIT when talking with decision makers. Ask: "What decisions are you making in the next six months that competitive information could inform?" That gets you further than asking an executive to "define their KITs."
5. Setting and forgetting. KIQs set 12 months ago may have been answered, may have become irrelevant, or may need fundamental revision. The competitive landscape moves. Your KIQs have to move with it.
6. Not managing expectations. Failing to calibrate accuracy, timelines, and format leads to disappointment regardless of quality. An accurate finding delivered in the wrong format will be ignored.
7. Overloading with too many KIQs. Without prioritization, everything is urgent and nothing is adequately covered. The priority system exists for a reason.
8. Asking general questions. When you ask only general questions, you get general answers that are not conducive to decision-making. Compare: "What's the competitor's partnership strategy?" versus "What's the revenue split model between the competitor and their co-promotion partner? What are the incentives for both companies?" The second question generates intelligence you can act on. The first generates a summary nobody reads.
KITs and KIQs are not relics of the pre-digital era. In AI-powered CI systems, they've become the configuration layer that determines what automated systems surface, how they categorize information, and when they alert.
The way I think about it: in traditional CI, KITs and KIQs guide human analysts in deciding what to look for, what to prioritize, and how to structure collection. In AI-driven CI, those same KITs and KIQs serve an additional function — they tell the technology what to do.
The human tells the technology: these are my priorities, these are my key intelligence requirements, these are the companies I'm interested in. The technology then goes out, does the crawling, pulls the information, processes it, and provides something that is already usable.
This isn't a metaphor. In modern CI platforms, KITs and KIQs are literally defined once and used by AI agents to decide what to surface, how to categorize it, and when to alert.
I'll give you a practical example. For an oncology franchise:
These are defined once in the system. The monitoring agents then use them continuously to filter thousands of daily inputs down to the handful that matter for this specific team.
The logic applies equally to how AI is used for strategic thinking, not just monitoring. Chintan The strategy executive describes building what his team at a top-10 pharma company calls the "a centralized intelligence system" — uploading all their intellectual property into a centralized AI knowledge system. The logic: "Your best shot is your first shot." When strategists approach a new problem with the organization's full accumulated knowledge behind them, the first recommendations are dramatically stronger.
But the quality of what the system produces depends entirely on the quality of the questions you feed it. An AI system configured with vague KITs will surface vague intelligence. A system configured with precise, SMART KIQs will surface intelligence you can act on. The principle hasn't changed from the pre-AI era — it's just that the consequences of getting it wrong (or right) are amplified by scale.
This is the real connection between traditional CI methodology and AI. The CI professionals who know how to define sharp intelligence requirements — who can anticipate what a decision maker needs before they ask — are the ones who can configure AI systems that produce genuinely strategic outputs rather than noise.
In an automated monitoring pipeline, KITs and KIQs define the alert criteria at the processing stage. The pipeline works in four stages:
The "check alert criteria" step in stage 3 is where KITs and KIQs do their work. Each incoming piece of intelligence is scored against defined KITs with confidence scores. An LLM reasoning log might show: "Quarterly Earnings Calls for Competitors = 1.0 confidence; Phase 3 Trial Update = 0.9; Planned Adcom and Results = 0.0." That creates the same audit trail manual CI has always provided — matching intelligence to defined requirements — but at machine scale.
When KIQs drive automated systems, the stakes of getting them right go up. Poorly defined questions produce systemic noise — every vague KIQ generates a stream of irrelevant alerts that trains stakeholders to ignore the system. Well-defined KIQs produce targeted, high-signal alerts that build trust and drive action.
Natural-language interfaces are changing who can participate in defining KIQs. Brand managers, MSLs, and executives can specify their intelligence needs directly, not just through CI professionals. This broadens the input base for KIQ development — but it also increases the need for CI professionals to curate and prioritize. The system has to serve strategic needs, not just curiosity.
A KIT is a big-picture strategic issue — a broad theme like "Competitor Clinical Development" or "Market Access Dynamics." A KIQ is a specific, answerable question beneath a KIT, like "What primary and secondary endpoints are competitors using in their Phase III trial?" KITs define the territory. KIQs define exactly what you need to find out within that territory.
There's no fixed number. The priority system provides the constraint. High-priority KIQs get dedicated primary research. Medium gets secondary tracking. Low gets captured opportunistically. The practical limit is the CI team's capacity for primary research on high-priority questions — typically 15–25 active high-priority KIQs per brand.
KITs every 6 months with senior leadership. KIQs quarterly with the operational team. Ongoing review of findings should continuously generate follow-up questions. Ad-hoc reviews after major competitive events or conferences.
It's SMART: Specific, Measurable, Action-Oriented, Relevant, Time-limited. Precise enough to drive focused collection and specific enough to produce actionable answers. "What's happening with the competitor?" fails every criterion. "What's the field force structure and size of the competitor, and how are different indications being prioritized?" passes.
Decision makers, franchise heads, and cross-functional teams. The CI professional facilitates but doesn't define KIQs in isolation. Stakeholder engagement captures the real intelligence needs and creates buy-in. The CI professional's unique contribution is anticipating requirements that stakeholders haven't yet articulated.
KIQs drive the collection plan. The plan determines who will gather what, when, where, and how — and every element traces back to specific KIQs. High-priority KIQs get primary research resources. Medium-priority KIQs get secondary source tracking.
Real-world examples from pharma CI programs: "What's the field force structure and size?" / "What's the product's messaging and positioning? Any changes versus previous year?" / "Any innovative commercial models with payers — risk-sharing, outcomes-based?" / "What's the promotional grid? Which products and indications are being prioritized?" / "How are sales incentives being calculated?" / "What's the revenue split model between co-promotion partners?" These are the kinds of specific, SMART questions that produce intelligence you can act on.
KIQs configure AI agents to surface, categorize, and alert. They're defined once and used continuously by monitoring agents to filter incoming intelligence. Each item is scored against KITs with confidence scores, creating a transparent audit trail between what was defined as important and what gets flagged. The principle is identical to manual CI — matching intelligence to defined requirements — but at machine scale and speed. The quality of your KIQs determines the quality of what the system produces.