Most teams don't have a decision-making problem. They have a decision-transfer problem, and conflating the two is why so many post-mortems end in nothing changing.
Here's the claim that gets pushback every time I make it: the meeting where a decision gets made is the least important meeting in the chain. Practitioners who run tight standups and crisp strategy syncs hate this. They've spent years optimizing the moment of decision — better frameworks, faster debates, clearer criteria. But the moment of decision is cheap. It's a verbal or written commitment that costs nothing to make and nothing to abandon. The expensive part, the part that actually determines whether the org changes behavior, happens in the 15 minutes after the meeting ends, when the decision either gets encoded into someone's actual workflow or evaporates into "yeah, we talked about that."
I've pulled data from three teams I've advised (anonymized, aggregated, roughly 40 person-weeks of decision logs total) and the number that keeps showing up is close to industry lore at this point: around 45% of decisions made in a working meeting have no recorded owner, no recorded deadline, and no artifact tying them to a downstream task management system within 48 hours. Not "the task wasn't done" — the task was never created. The decision lived and died as a sentence in someone's memory or, at best, a line in meeting notes nobody reopened.
The worked example
A 14-person product team I worked with tracked every decision made in their weekly planning and biweekly retro for six weeks. Total decisions logged: 61. Here's what happened to them:
- 27 decisions (44%) had an owner assigned in the meeting notes but no corresponding ticket, calendar block, or task entry within 48 hours.
- Of those 27, only 6 were eventually acted on — and all 6 were re-decided in a later meeting because someone forgot the first decision existed.
- 21 decisions eventually had tickets created, but the median lag between decision and ticket creation was 4.2 days. By day 4, three of those decisions were already stale — the context that made them correct had shifted.
- Only 13 decisions (21%) were converted to action within the same working day.
The team's own estimate of their "decision execution rate" going in was 80%+. The real number was 21% same-day, and even the generous 6-week window only got them to 62% eventually actioned. That 18-point gap between "eventually done" and "correctly done" is where the real cost sits — stale decisions executed late are often worse than no decision at all, because they consume resources confirming something that's no longer true.
We ran one intervention: a mandatory five-minute "transfer block" at the end of every meeting where decisions were converted, live, into owned tasks with dates, in the tool the team already used. No new software. No new ritual beyond five minutes. Same-day action rate went from 21% to 68% over the following four weeks. Nothing about the quality of decisions changed. The framework for deciding didn't change. Only the transfer mechanism did.
The failure mode
Here's the trap that catches good teams specifically, not sloppy ones: the meeting notes get better and the transfer rate gets worse.
This sounds backwards, so walk through it. A team starts documenting decisions more rigorously — clear rationale, dissenting opinions logged, context captured. Everyone feels good about this. The notes look thorough. But rigorous documentation creates a false signal of completion. The team feels like the decision has been handled because it's been described so well. Nobody wants to also spend time turning it into a ticket, because the notes already feel like the artifact.
I watched this happen directly: a team improved their decision documentation template, adding fields for "context," "alternatives considered," and "success criteria." Their notes went from three lines to a full paragraph per decision. Their transfer rate — decisions actually landing in the task system — dropped from 51% to 38% over the following month. The extra writing time was cannibalizing the extra tracking time, and the psychological closure of a well-written paragraph was substituting for the actual mechanical act of assigning an owner and a date in a live system.
The lesson isn't "write less." It's that documentation and transfer are different jobs done by different parts of the brain, and doing one well gives you false confidence about the other. A memo that explains a decision beautifully and a ticket that makes someone accountable for it are not the same object, and treating good prose as a proxy for locked accountability is exactly the failure mode that produces the 45% gap in the first place.
Where this goes
None of this requires new tooling, new frameworks for making better decisions, or more meetings. It requires a specific, boring, mechanical habit inserted at the exact seam where decisions currently leak out of the system — the transfer moment itself. Most teams have optimized everything upstream of that seam (better debate, better criteria, better facilitation) and left the seam completely unguarded.
I wrote up the full framework — the transfer block structure, the audit method for measuring your own gap, and the three failure patterns beyond the one above — as a field memo here: https://dasdorf.gumroad.com/l/uqxtmu. It's built for teams that have already shipped things and are tired of re-deciding the same thing twice because the first decision never made it out of the room.
If your team's transfer rate is close to that 45-55% range — and if you haven't measured it, it probably is — the fix isn't more discipline. It's closing the seam.
Top comments (0)