Essays on customer programs, operator judgment, and agentic AI in production. Written by someone who ran the function at the highest level, then rebuilt it with AI. Proof, not hype.
Counting briefings held does not survive a budget review, and AI makes the old counts worse. One metric that cannot be gamed in either direction, the six-part rubric behind it, and how it ladders up to revenue.
Most briefing programs are built to send a story one way. The best customer intelligence a company hears all month is said in that room, and almost none of it reaches anyone who could act on it. Why that is changing.
"Bespoke at scale" means nothing until you can say what, exactly, gets customized. The five dimensions every executive briefing is composed of, and the one most programs skip.
Most AI plans for customer programs fail on scope: the full picture gets approved, then stalls because nothing in it is small enough to finish. How to start with one workflow, and why you write down the kill signal first.
The "Executive Briefing Center" label is consolidating into customer programs at AI-native companies. The work is getting more valuable, not less. An operator's read on where the function is going, and what it means for the people who run it.
Briefing prep has always been waterfall: plan, build, lock, hope nothing changes. When a finished-grade pack can be rebuilt in minutes, late intel stops being a problem and becomes the best input of the week.
Deep for a few or wide for many was the oldest tradeoff in executive engagement. Agentic AI makes a bespoke briefing cost about what a generic one used to. What that changes, and the three legs that keep it from being a slogan.
One rule I will not bend when AI touches an executive briefing: a named person certifies the facts before anything reaches an executive. How to build that gate so it scales instead of becoming the new bottleneck.
Most people use AI to write the thing. I use it to find the one place the thing falls apart. Why your own review has a blind spot, and a four-step way to find the weak point before the room does.
The fastest way to kill an AI rollout on a briefing team is to let it sound like an automation play. What each role sheds and picks up, and the three design choices that make adoption structural instead of motivational.
Ask anyone to make something excellent and you get a feature list. The move that works: name the failure modes of a mediocre version, then design every feature as a defense. The four ways AI pilots die.
Handing a briefing team a powerful AI tool is not a strategy. Specialists run workflows, not prompts. The eight layers of an agentic system for an executive briefing team, and the two the team ever sees.
I inherited an executive briefing program that ran like a coin flip. The instinct was to rebuild it. The fix was to move it, twice. Why recategorizing beats rebuilding, and why the same error is all over AI right now.
Ask ten companies what their briefing center is for and you will hear about showcasing innovation and hosting customers well. None of that is the job. The job is decision compression, and the framing decides everything downstream.
Most executive briefing agendas open with a welcome and a company overview, and reach the customer's problem after lunch. I build mine in the opposite order. The sequence, and the timing rules I don't trade away.
Get Operator Notes by email. New essays land on this page first and go out to the list the same week. No noise between issues.
Subscribe