Why every briefing ends with the things we couldn't figure out
The most useful section of a briefing is sometimes the list of questions you should ask in person — not the answers we pretended to have.
Every Clickbrief briefing ends with a section called Honest gaps. It’s a short list of the things we tried to find out and couldn’t. Sometimes that’s “we couldn’t confirm who reports to whom in their procurement org.” Sometimes it’s “we couldn’t find public pricing on the product you’re probably going to be discussing.” Sometimes it’s “the LinkedIn profile of the person you’re meeting hasn’t been updated in four years; treat the role description as approximate.”
This section exists because the easiest way to ruin a briefing is to fill it with confident-sounding sentences that aren’t actually backed by anything. A language model is happy to do this. It will tell you the procurement team has 12 people if you don’t stop it, even though that number doesn’t appear in any source. It will assign a job title to the person you’re meeting that they had two years ago and have since moved on from. It will infer the tech stack from one mention in a job posting and present it as gospel.
This is, fundamentally, a craft problem more than a model problem. The fix is to teach the model — through prompting and through filtering — to mark its uncertainty rather than smooth it over. Easier said than done, but the “honest gaps” section is where we make the uncertainty visible to the reader instead of pretending it isn’t there.
The dual benefit
First benefit: the reader doesn’t walk into the meeting thinking they know something they don’t. They walk in with a list of two or three questions to actually ask.
Second benefit: the gaps section becomes the trust ladder. If we’re willing to write “we couldn’t find this,” the reader trusts the things we did write down a little more. The alternative — a confident briefing with no gaps section — reads like marketing material. Marketing material is not what you want to walk into a meeting holding.
The discipline of saying “we don’t know”
In an era of language models that are eager to please, saying “we don’t know” is a competitive advantage. Every tool around us — search engines, chat assistants, enrichment APIs — is racing to give us an answer to every question we ask, even when the honest answer is silence. Reverting to silence, when silence is the honest answer, turns out to feel almost luxurious.
That is what the honest gaps section is, in the end. A small piece of silence at the bottom of an otherwise confident page. We think of it as the most important thing on it.