A sales director at an industrial gases manufacturer told us about a fix his operations team owed him.
Operations owed me a process improvement for delivering product to a specific customer. They provided a solution but never executed. It has been ongoing
The last four words are the ones to sit with. It has been ongoing. Not stalled, not cancelled, not disputed. Ongoing.
Notice what did not go wrong. The commitment got made. The work got done. Somebody took the problem seriously, designed a process improvement, and handed it over. Audit this from the outside and you find a real deliverable with a real author, and you mark the item closed.
The customer is still getting product the old way.
A solution is the easiest thing in the world to mistake for an outcome. It has a name on it, it arrives on a date, and it can be attached to a ticket. Execution has none of those properties until the moment it finishes, which means the stretch where this work actually died is invisible to every system that tracked it being born.
That stretch has a name. It is the execution gap, and it is where the work you delegated goes quiet: not refused, not reversed, just never switched on, with nothing in the stack watching for it.
–Clint
What's on Larry's mind
The sales director put both halves in one sentence. They provided a solution, and they never executed. Read it twice and notice that those two clauses don't contradict each other.
Handing something over and changing how a customer gets product are two different events, and most companies never say which of them closes the commitment. Leave that unsaid and a handoff can be reported as finished work without anybody lying about anything. The person who asked keeps waiting, the person who delivered has a real artifact with their name on it, and neither of them is being careless.
That is what makes this kind of failure so hard to kill. It needs nobody to behave badly. It needs nobody to disagree out loud. It needs only the closing condition to go unstated on the day the work gets assigned, which is the ordinary case, and after that the item can sit for months while everyone involved behaves exactly as you would want them to.
Set the closing condition at the moment you make the commitment, and put it on the far side of the handoff, where the person who asked can see whether anything changed. That is what we're building into Brief, so a commitment stays open until the change lands and not until somebody files a deliverable. Done belongs to the person who asked for the work.
–Larry
Product progress
You've been able to ask Brief things from inside Claude or ChatGPT via the Brief MCP server for a while. Brief now goes the other direction too. It can call out to the tools you already run.
Meeting notes are the clearest case. The AI notepad you keep open all day publishes an MCP server on its paid tiers. Connect it to Brief and those notes stop being a separate place you have to go. Ask what you promised the ops team on Tuesday and Brief answers from what you actually said in the room, not just from what turned up in email afterwards.
Same for the rest of them. Linear, Notion, GitHub, the internal MCP server your team stood up a year ago. Setup lives in Settings, under Connections, in the group called Agent tools. Paste the server's address into the MCP servers card and sign in once. Switch on the tools you want Brief to have, and they turn up in Brief Chat next to Brief's own.
What it changes is where an answer ends. Ask what you owe people this week and you get a list. It's right, and you still have to go somewhere else to act on it. Now the sentence keeps going. "File the top three as Linear issues on the platform team, with the dates I agreed to." Brief knows the dates. It read the mail where you agreed to them.
We kept it tight on purpose. A server you've just connected can't do anything until you authorize a tool, one at a time.
–Zac
The execution gap is one half of what Larry takes apart in the second Executive Intelligence Paper, The Decision-to-Done Gap. It is free, ungated, and about a twenty-minute read.
Somewhere in your company, or in a company you work with, there is a person who would have caught this one. They are the one who comes back three weeks later and asks whether the thing everybody agreed to is actually running yet. Often they are a chief of staff or a head of operations, and often the job appears nowhere in their title.