Key Intelligence Questions (KIQs)

From KITs to KIQs: the decomposition

The standard path to a KIQ starts with a key intelligence topic: a broad area of stakeholder concern such as a rival's expansion plans or the threat of a new entrant. The KIT process was formalized by Jan Herring, who built one of the earliest corporate intelligence functions at Motorola after a career in US government intelligence, and it deliberately stops at the level of topics. Topics are too broad to collect against directly, so analysts break each one into questions narrow enough to answer with identifiable sources. A KIT like 'Competitor X's enterprise ambitions' might decompose into whether X is hiring enterprise sales reps, whether SSO and audit-log features have appeared on its roadmap, and whether its pricing page has sprouted a contact-sales tier. Each question implies its own sources, indicators, and deadline.

What makes a question collectible

A useful KIQ has four properties. It is specific: it names one competitor, one behavior, and one market rather than gesturing at strategy in general. It is answerable: there are observable indicators (filings, job posts, website changes, partner announcements) that would move the answer, and the team can realistically access them. It is time-bound: a phrase like 'in the next twelve months' turns an open-ended worry into a question that can eventually be closed. And it is decision-linked: someone has said what they would do differently depending on the answer. A quick test is to ask what evidence would settle the question; if no realistic evidence could, the question is a topic in disguise and belongs back at the KIT level, waiting to be decomposed further.

How KIQs drive the collection plan

KIQs do their real work in the planning and direction phase of the intelligence cycle, where they are converted into a collection plan. Each question gets mapped to the sources most likely to answer it: a question about market entry might route to job boards in the target region, local press, and partnership pages, while a question about pricing strategy routes to the competitor's pricing page and packaging announcements. This mapping is what makes automated monitoring effective rather than noisy: website change detection, job-posting alerts, and news tracking are configured around the questions instead of around a generic list of competitors. When a monitored signal fires, it arrives already attached to the question it informs, which shortens analysis and makes the resulting intelligence easier to act on.

Common mistakes with KIQs

The most common failure is writing questions that are really topics: 'What is Competitor Y's AI strategy?' cannot be closed with evidence, so it lingers on the list forever. The opposite failure is trivia: questions so narrow that answering them changes nothing, which usually means the decision link was never established. Programs also let KIQ lists rot: questions written during annual planning stop matching reality within a couple of quarters, so a standing review (retiring answered or irrelevant questions and adding new ones as the landscape shifts) matters as much as the initial drafting. Finally, some teams treat KIQs as an analyst-only artifact. They work best when stakeholders help write them, because the stakeholder is the only person who knows which answers would actually change a decision.

Frequently Asked Questions

Related terms