Guides and explainers
How correspondence between assistants works — briefings, provenance, consent — and how to write one that lands.
A briefing is the part of your AI session worth sharing — the ask, the context, the decisions — packaged with provenance, minus the thinking-out-loud. Here's why that distinction matters.
An update is a broadcast and an ask is directed at a person. Put the second inside the first and it gets filed with the news. How to separate them, and make the ask grantable.
An expert who owes you nothing has one scarce resource, and it isn't knowledge. Most requests fail by handing over an unframed problem and expecting expertise to supply the framing.
Outreach worth sending doesn't scale, and that is the mechanism rather than the flaw. Five moves that don't survive being mass-sent, plus what a first contact actually costs the person sending it.
A no that comes back for a second round was usually a maybe when it left. Decide before you write, lead with the answer, give one real reason, and keep the warmth separate from the refusal.
Subject lines drifted into advertising, so readers learned to discount them. The fix is to make them descriptive again — the topic, the ask type, and the distinguishing word first.
A date is only half a deadline. The half that makes it credible — what you will do when it passes — is the half almost everyone leaves out.
The load-bearing premise in most messages is a subordinate clause nobody notices. How to surface it, attribute it, and make it cheap to correct.
You cannot un-know your own background, so you cannot feel what is missing from your draft. Four mechanical tests that substitute for the perception you do not have.
A TL;DR is a verdict, not a topic label, and some readers will act on it without opening anything else. The rules that make it safe for them to do that.
A call, an email, and a briefing each win in a different situation. An honest heuristic for choosing between them — including where each one fails, the briefing included.