I want to walk one decision end to end, because the whole shape of the problem is visible in a single case.
We have been asking executives what happens to their decisions and commitments. A senior program director at a medical device manufacturer answered with a product enhancement, and it is worth reading in the order it happened.
First, the hard part went well. There was alignment on the enhancement. There was a decision process, and the process ran. Whatever getting to that decision cost in meetings and reading and argument, the organization paid it and got an answer.
Then months passed.
Then the whole thing was reopened. His account of the cost is the part to sit with: a huge amount of extra work and time to, in his words, "essentially re-litigate which had already been decided."
Nothing failed on the way to the decision. It failed on the way from it.
Walk back through it and there is no villain and no mistake. Alignment was real. The process was real. The answer was real. What was missing is the part nobody owns: something that holds the decision after the room empties, so that reopening it has to be a choice somebody makes rather than a thing that just happens.
So here is the shape.
There is one distance that matters: from a call a leader faces to work that is actually finished. It opens in two stages, and the decision is the hinge between them.
Before the hinge is the clarity gap. You cannot make the call because the understanding you need was never assembled. Walking into a meeting cold lives here. So does the cognitive load of rebuilding context that should already exist. The enemy on this side is context blindness.
After the hinge is the execution gap. The call got made and nothing carried it. Work you delegated that nobody is tracking lives here. So does priority drift, where the urgent quietly displaces what you decided mattered. The enemy on this side is decision decay, which is what happens when nobody executes a decision and nobody kills it either.
Across both sits decision amnesia. A settled question comes back and nobody can say what was decided, what was ruled out, who disagreed, or what the evidence was. That is the mechanism that makes the two stages compound each other, and it is exactly what the program director was paying for when he re-litigated a decision his organization had already made.
Most calls never make the trip from decided to done. Larry takes that whole distance apart in the second Executive Intelligence Paper, The Decision-to-Done Gap. It is free, ungated, and about a twenty-minute read.
–Clint
Zac on the architecture
Your tools do not store decisions. They store messages, and a decision is assembled out of a dozen of them. No single message holds the call, so nothing in your stack has a field for who owns it or whether it still holds.
Every tool you own holds a piece of it. The thread where it was argued. The deck. The minutes. The chat where somebody said go. Search any of them and the pieces come back. The decision does not.
So there is nobody to ask what came of it. You can pull up the conversation and rebuild the answer, which is what a room does when it starts over. That rebuild is what the program director above paid for twice.
Brief holds decisions and commitments as objects. Not documents that mention them. Not messages someone starred. Objects with state, that persist, that change, that know where they came from and who owns them. A decision here has a date, an owner, the reasoning that produced it, and a status that stays live after everyone leaves the room.
That buys two things text cannot do. Brief can notice when a decision goes quiet, because quiet is a state rather than an absence of messages. It can also tell you a settled question is being reopened while it is being reopened, instead of after you have argued it a second time.
An object you cannot check is one more thing to take on faith. The test I use on any system is a call my team made three months ago. What did it rule out, and who disagreed. Most stacks cannot say.
–Zac
Product progress
Brief has always shown you where something came from. Reaching it took two clicks.
Now hover the mark beside a commitment or a decision and the message opens right there, with the subject and the sentence that produced the item. Click and you are in the source. On a phone the mark is a plain link, so one tap takes you there.
The same hover works elsewhere. Where several messages sit behind one claim, the stack opens the whole list. In a narrow column, where a row's status shrinks to a dot, hovering tells you what the dot means.
Two places it stops short. When the record never named the message it came from, you get a subject line and a link out. A thread row keeps its plain mark, because the whole row is already a link.
One more, if your team works in Slack. Brief now reads the replies inside a thread. It used to see only the first message, so a commitment you made four replies deep never reached it.
–Zac
Which side of the hinge costs you more? Before, if the expensive part of your week is getting to a decision without the understanding you need. After, if the expensive part is what happens to a decision once you have made it. I genuinely do not know which side is worse, and nobody has asked you.