CI-201c · Module 2

Translating Intel for Executives

4 min read

Executive audiences process intelligence differently from operational teams. An operational manager needs to know what happened and what to do about it. An executive needs to know what it means for the business strategy and whether the current direction is still correct. The same intelligence, reframed for these different cognitive modes, produces different outputs.

Translation requires three shifts. Shift from events to implications: the executive does not need to know that a competitor hired fifteen engineers — they need to know that a competitor is building capability that threatens the company's core differentiation. Shift from data to narrative: executives process stories, not spreadsheets. The narrative arc is situation (where we are), complication (what changed), and resolution (what we do). Shift from comprehensive to selective: an operational brief presents all relevant findings. An executive brief presents only the findings that affect strategic decisions. Everything else is noise at this altitude.

Do This

  • Lead with strategic implications: "Our pricing advantage in mid-market is at risk" not "Competitor X hired a Pricing Director"
  • Use narrative structure: situation → complication → resolution creates a cognitive path the executive can follow
  • Quantify impact in terms executives care about: revenue at risk, market share shift, competitive positioning change

Avoid This

  • Present raw intelligence findings and expect the executive to draw their own strategic conclusions
  • Use intelligence jargon — "OSINT," "corroboration," "source tiers" — that creates distance instead of understanding
  • Include every finding for completeness — at executive altitude, completeness is clutter; relevance is the filter