FFCS Intelligence All articles
Executive Intelligence

Name the Decision First: The Scoping Discipline That Rescues Intelligence Programs From Themselves

FFCS Intelligence
Name the Decision First: The Scoping Discipline That Rescues Intelligence Programs From Themselves

Photo: executive writing a one-page decision brief at a desk with laptop, business planning documents, via veblendirectors.com

We have spent a decade buying better instruments and almost no time deciding what we are trying to measure. Ask an intelligence team what it is working on and the answer is usually a subject: the competitive landscape, the regulatory environment, the customer's evolving priorities. Ask which decision that work will change, and the room gets quiet. That silence is where most programs quietly fail.

The failure does not look like failure. Collection proceeds. Reports are produced. Stakeholders express general satisfaction. And yet nothing in the operating plan moves, because nothing was ever designed to move it.

The Collection Reflex

The reflex is understandable. Data is abundant, requests arrive faster than they can be triaged, and a team that says yes to everything appears responsive. But responsiveness and usefulness are different currencies, and only one of them compounds. A briefing that answers a question nobody was going to act on is not neutral. It consumes the scarcest resource in the function — analyst attention — and it trains the organization to expect output rather than advantage.

The remedy is not more rigor at the end of the pipeline. Reviewing a finished briefing for relevance is quality control applied too late, at a point where the alternative to publication is an awkward conversation. The discipline has to sit at the front. Before collection begins, someone must be able to state, in a sentence, which decision the work will inform.

Three Fields Nobody Fills In

Most intelligence requests arrive missing three pieces of information, and their absence is the root cause of downstream disappointment.

The decision. Not the topic. The specific choice the recipient will make differently depending on the answer. Enter a new segment or defer it. Match a competitor's pricing move or hold. Extend a supplier contract or open a second source. If no such choice exists, the request is research, not intelligence, and should be labeled and resourced accordingly.

The deadline. The date by which the recipient must act. This is not the date the report is due; it is the date the decision can no longer be deferred. Working backward from it sets the cadence and, crucially, allows the team to declare when the evidence is sufficient rather than complete.

The threshold. The level of evidence, or the specific finding, that would trigger action. Without a threshold, every briefing invites another round of analysis. With one, the intelligence function inherits a defensible stopping rule and the executive inherits a reason to decide.

A Template That Fits on a Postcard

We recommend a four-line scoping note, completed jointly by the requester and the analyst, before any collection begins.

Decision: Which specific choice will this inform? Decision date: When must it be made? Threshold: What finding would change the current course? Cost of being wrong: What happens if we answer this and the answer is mistaken?

The fourth line is the one most teams skip and the one that most improves outcomes. It forces a conversation about stakes, and stakes determine how much rigor is proportionate. A low-cost reversible decision does not require a six-week research cycle. A high-cost irreversible one does, and the conversation about which is which is often more valuable than the briefing that follows.

A Worked Example

A commercial leader asks for a competitive assessment of a rival's new pricing structure. Undisciplined, the request becomes an eight-week project covering packaging, discounting, and channel incentives.

Scoped, it becomes something narrower. The decision is whether to match a proposed discount in the enterprise segment. The date is the pricing committee meeting in five weeks. The threshold is evidence that more than a handful of shared accounts have already been offered the new terms. The cost of being wrong is a margin concession across a book of business that may not have been under pressure at all.

Same subject. Entirely different work. The scoped version can be answered in nine days, and its conclusion is a recommendation rather than a survey of the field.

What Changes After the Discipline Sets In

Three effects tend to appear within two quarters.

Request volume falls, and its quality rises. Teams that must name a decision self-select out of the speculative ones.

The kill rate increases, and that is healthy. Programs that never terminate a line of inquiry are not thorough; they are undirected. A culture in which an analyst can say the threshold has been met, or will not be met in time, without career risk is the mark of a functioning function.

Vendors adapt or leave. Suppliers asked to serve a stated decision produce sharper work than suppliers asked to cover a landscape. Those that cannot scope to a decision are usually selling content by volume.

The Objection Worth Taking Seriously

Executives will say they do not yet know what decision they face, and they are often telling the truth. The correct response is not to abandon the discipline but to apply it earlier. The scoping conversation is frequently the first moment a vague concern becomes a named choice, and that conversion is a service in its own right.

The instrument was never the constraint. Enterprises have more data, more platforms, and more analytical capacity than at any point in the last twenty years. What they lack is a habit of beginning with the decision. Adopt that habit and the same budget produces markedly different work — not because the analysis improved, but because it finally had somewhere to go.

All Articles

Related Articles

Lead Times Don't Lie: Building a Supplier-Signal Pipeline With Your CPO

Lead Times Don't Lie: Building a Supplier-Signal Pipeline With Your CPO

Hallway Signals: The Unstructured Intelligence Your Platforms Were Never Built to Catch

Hallway Signals: The Unstructured Intelligence Your Platforms Were Never Built to Catch

The Briefing That Changed Nothing: A Case Against Intelligence Theater in the Boardroom

The Briefing That Changed Nothing: A Case Against Intelligence Theater in the Boardroom