Three weeks after the quarterly review, the VP of Engineering pulled me aside. “I thought we decided to sunset that service,” she said. This was in the early 2000s.
I thought we did too. The team thought we were evaluating it. The PM thought we were continuing it with modifications.
Four people. Four versions of the same decision. One conversation.
Nobody was lying. Nobody had missed the meeting. The problem wasn’t clarity. The problem was that the decision transferred, and the reasoning didn’t.
The Gap Is Not Friction
Most leaders treat the gap between decision and outcome as noise. Something to minimize, monitor, or trace back to whoever dropped the ball. A decision gets made; the output doesn’t match; someone misunderstood, or didn’t read the memo, or didn’t take it seriously.
That frame is wrong. The gap isn’t failure. It’s where the organization lives.
A decision is a point-in-time artifact. It captures what a set of people in a room understood at a particular moment. The execution of that decision happens across time, across people who weren’t in the room, across a hundred small choices nobody tracked. Every one of those choices is a micro-decision made without the original criteria.
Think of it as signal loss. The decision is the transmission: clear, intentional, directional. What the execution layer receives is downstream of every interpretation, assumption, and context gap in between. Something was broadcast. Something arrived. The difference is your execution gap. Every organization has one. Most are just not measuring it.
The Decision vs. The Brief
Here’s what actually transfers when a decision gets made: the conclusion.
“We’re sunsetting the service.” “We’re investing in the mobile product.” “We’re shifting to a federated model.” These are conclusions. They’re what goes in the notes, the follow-up email, the all-hands slide. They’re what the people who weren’t in the room receive.
What doesn’t transfer: the criteria. The tradeoffs you considered and rejected. The boundaries of the decision: what’s in scope, what’s explicitly not. The edge cases you resolved, even implicitly, while talking. The conditions under which the decision would change.
When criteria don’t transfer, every ambiguity downstream gets resolved without them. The engineer picks the implementation that makes technical sense, not the one that serves the business constraint you were weighing. The PM prioritizes features that match her read, not the outcome you were optimizing for. Nobody’s wrong. They’re executing on the brief they received. The brief was incomplete.
I’ve seen teams spend six weeks building the technically correct solution to the wrong problem, not because they were incompetent, but because nobody told them what the real constraint was. They were optimizing for a tradeoff the room had already rejected. They just didn’t know.
The decision isn’t done when someone says “agreed.” It’s done when someone who wasn’t in the room can reconstruct why you decided what you decided, and use that to navigate the edge cases.
Nobody Owns the Floor
The second failure point is simpler and harder to fix: ownership doesn’t transfer with decisions.
“The product team will handle the migration.” “Engineering owns the rollout.” “Marketing will coordinate.” These feel like assignments. They’re not. They’re categories. Categories don’t surface problems. They don’t catch drift. They don’t notice when the execution is heading somewhere the decision didn’t intend.
Ownership of a decision’s execution requires a person: not a team, not a function, not a verb in the meeting notes. One person who can tell you, on any given day, where the execution is relative to the original intent. One person who knows the decision criteria well enough to catch when the implementation is drifting from them.
When that person doesn’t exist, status updates get generated and drift doesn’t get caught. Everyone’s working. The status is green. And ninety days later the output doesn’t match what was decided. By then you’re too far in for a cheap correction.
The ownership gap is the most expensive one because it compounds silently. The decision gap shows up eventually. The ownership gap often doesn’t surface until delivery.
What Closes It
Before you leave any meeting where a decision gets made, do two things.
Name one person who owns the execution chain. Not the team. Not the function. The person. They should be able to tell you, without pulling up slides, what you decided and why.
Then ask them to play back the criteria. Not the conclusion. The criteria. What tradeoffs did we make? What would change this decision? What’s out of scope? If they can’t answer those, the brief isn’t complete. Spend five more minutes on it. It’s cheaper than the alternative.
I’ve done this in rooms where it added eight minutes and saved three months. The extra time is always worth it. The version where you skip it always costs more.
That’s the whole practice. No new tool. No new meeting. Just a decision that stays open two minutes longer, and a person who leaves the room owning it, criteria and all.
Name one decision you made in the last month that you’ve actually followed through the full execution chain. Not whether it shipped. Whether what shipped is what you decided.
If you can’t answer that, you know where the gap is.
This arc maps what happens to decisions going down. The prior arc closed with a field manual for everything going up: What I Know After 25+ Years in Technical Leadership.
ZenOne also produces trance music. The mixing arc behind his productions is at zenonemusic.substack.com.
Resources & Further Reading
The Knowing-Doing Gap by Jeffrey Pfeffer & Robert Sutton (Harvard Business School Press, 2000) — The foundational research on why organizations know what to do and fail to do it. The decision/execution distinction runs through it.
Good Strategy Bad Strategy by Richard Rumelt (Crown Business, 2011) — The “kernel” framework: why most strategies are goals dressed up as strategy, and why the execution gap starts in how decisions are framed, not how they’re communicated.
Implementation Intentions: Strong Effects of Simple Plans by Peter Gollwitzer, American Psychologist, 1999 — Research on why stating a goal produces far less action than specifying when, where, and how. The criteria problem has a 25-year research base.