Key Intelligence Topics (KITs)
Updated July 18, 2026
The prioritized list of questions or issues that a CI program answers, established during the planning phase.
Also known as: KITs
KITs give a competitive intelligence function its agenda. Instead of monitoring everything competitors do and hoping something proves useful, the CI team works with executives and other decision-makers to identify the handful of strategic topics where intelligence would actually change a decision: a rival's likely response to a product launch, the risk of a new entrant, consolidation moves in the market. Those topics become the program's charter: they determine what gets collected, which analyses get produced, and whose needs get served first.
The concept was formalized by Jan Herring, a former CIA intelligence officer who later built the corporate intelligence function at Motorola and described the KIT process in a 1999 article in Competitive Intelligence Review. Herring's core argument was that intelligence programs fail most often not because of weak analysis but because they work on questions nobody with decision-making authority ever asked. The KIT process inverts the flow: management defines its intelligence needs first, through structured dialogue, and collection follows from there.
In practice, KITs anchor the planning-and-direction phase of the intelligence cycle, and everything downstream inherits their priorities. A program without explicit KITs tends to drift into producing news clippings; a program with well-defined KITs produces intelligence that a named stakeholder is waiting to use.
Herring's three categories of KITs
Herring grouped intelligence needs into three types. Strategic decision and issue KITs support a specific upcoming decision: entering a market, acquiring a company, responding to a competitor's pricing move. Early-warning KITs cover threats and opportunities management does not want to be surprised by: a rival's potential platform launch, a substitute technology maturing, a partner turning into a competitor. Key-player KITs call for ongoing profiles of the actors who shape the environment: competitors above all, but also customers, suppliers, regulators, and potential partners.
The categories matter because each demands a different operating rhythm. Decision KITs are project-shaped with a deadline, early-warning KITs require continuous monitoring for weak signals, and key-player KITs need periodically refreshed profiles rather than daily coverage.
How KITs are developed
KITs are established through direct conversations with decision-makers, not by the CI team guessing at what leadership wants. The intelligence lead interviews executives about the decisions they face over the coming quarters, the developments that would genuinely surprise them, and the players they feel they understand least. Those raw needs are then consolidated (different executives often express the same underlying topic in different words) and prioritized against the program's real capacity.
The final step is explicit agreement: each KIT gets a sponsor who confirms the topic matters and will consume what the program produces. That sign-off is what turns a wish list into a mandate, and it gives the CI team standing to decline low-value requests that fall outside the agreed topics.
KITs vs. Key Intelligence Questions (KIQs)
The two terms travel together and are easy to conflate. A KIT names a broad topic of concern; a KIQ is a specific, answerable question derived from it that collection can actually pursue. From the KIT 'Competitor X's enterprise strategy', a team might derive KIQs such as: is Competitor X building a dedicated enterprise sales team? Which security certifications are they pursuing? What discount levels are they offering on multi-year contracts?
The decomposition is where planning becomes operational. A topic cannot be assigned to an analyst or matched to a source, but a question can: each KIQ points to concrete signals, whether job postings, pricing-page changes, or win/loss interviews. KIQs have their own glossary entry covering how to write them well.
A worked example from SaaS
Imagine a mid-market SaaS vendor whose leadership fears its main rival is moving upmarket. The KIT might read: 'Competitor X's move into the enterprise segment and its implications for our mid-market position.' The early-warning framing tells the team what to watch: enterprise-flavored job postings (sales engineers, compliance leads), the appearance of SSO and audit-log features in the changelog, a new 'Contact sales' tier replacing published pricing, enterprise logos surfacing in case studies, and sponsorships of enterprise-oriented events.
Each signal on its own is ambiguous; the KIT is what makes them cumulative. When several fire within a quarter, the CI team can brief leadership with a confident assessment rather than a stray observation, and the sponsor who requested the KIT knows exactly why the briefing matters.
Common mistakes
The most frequent failure is having too many KITs. A list of twenty topics spreads a small team so thin that nothing gets real depth; a short, ruthlessly prioritized list outperforms a comprehensive one. A second mistake is writing KITs in isolation: topics the CI team finds interesting but no executive ever endorsed, which guarantees the output lands in unread inboxes.
Teams also treat KITs as permanent. Topics should be revisited on a regular planning rhythm and whenever the landscape shifts materially: a rival's acquisition or a new entrant can make last quarter's priorities obsolete overnight. Finally, a KIT is not a competitor list: 'Track Competitor X' names a subject, not an intelligence need. The topic should say what about Competitor X matters and to whom.
Stop looking terms up. Start tracking them.
meertrack watches your competitors' websites, pricing, and hiring, then alerts you when something meaningful changes.
Frequently Asked Questions
What are the three types of Key Intelligence Topics?
Jan Herring's framework defines three categories: strategic decisions and issues, which support a specific upcoming decision; early-warning topics, which monitor threats and opportunities management must not be surprised by; and key players, which call for ongoing profiles of competitors, customers, suppliers, regulators, and other actors shaping the market.
What is the difference between KITs and KIQs?
A KIT is a broad topic of management concern, such as a competitor's enterprise strategy. A KIQ (Key Intelligence Question) is a specific, answerable question derived from that topic: for example, whether the competitor is hiring enterprise sales engineers. KITs set direction; KIQs make collection and analysis operational.
How many KITs should a CI program have?
Few enough that each one gets genuine analytical depth. Many practitioners keep the active list to a handful (often between three and ten depending on team size) because a long list spreads resources thin and turns the program back into general news monitoring. Prioritization is the point of the exercise.
Who should define the KITs in an organization?
The decision-makers who will use the intelligence (typically executives and senior leaders) with the CI team acting as facilitator. The intelligence lead interviews stakeholders about upcoming decisions and potential surprises, consolidates the answers into candidate topics, and secures a sponsor for each KIT before committing resources.
How often should KITs be reviewed or updated?
Most programs revisit KITs on their regular planning rhythm, commonly annually or quarterly, and immediately after major market events such as a competitor acquisition, a disruptive product launch, or a significant new entrant. Decision-driven KITs also retire naturally once the decision they supported has been made.
Related terms
Specific, answerable questions derived from KITs that guide the collection and analysis effort, e.g., "Will Competitor X enter the European market in the next 12 months?"
Intelligence CycleThe repeating process framework for CI: (1) planning/direction, (2) collection, (3) processing/analysis, (4) dissemination, (5) feedback. Adapted from military/government intelligence doctrine.
Competitive Intelligence (CI)The systematic process of collecting, analyzing, and distributing actionable information about competitors, market trends, and the external business environment to support strategic decision-making. Relies exclusively on legal, ethical, publicly available sources.
CI ProgramA formally resourced initiative dedicated to gathering and distributing competitive insights across the organization.
Early Warning SystemA CI mechanism that detects and flags emerging competitive threats or market disruptions before they materialize, giving decision-makers time to respond proactively.
Strategic Early Warning (SEW)A methodology for detecting weak signals that indicate emerging competitive threats or market shifts before they become obvious. The proactive, forward-looking edge of CI.
Actionable IntelligenceInformation processed, analyzed, and contextualized to the point where it can directly inform a specific business decision, as opposed to raw data or general awareness.
Market & Competitive Intelligence (M&CI)Combined framework integrating both market-wide awareness and competitor-specific monitoring for comprehensive strategic insight.