Decision Churn: The Quiet Way Companies Miss the Quarter
- Eric Becker
- Feb 12
- 3 min read
“Alignment” is often just indecision with better branding.
If decisions don’t hold, execution can’t compound.
What kills initiatives isn’t debate — it’s re-debate.
Decision Churn
Most initiatives don’t miss because the team made a bad decision.
They miss because the organization keeps quietly re-deciding the same things — until the calendar makes the outcome inevitable.
That’s decision churn:
decisions that don’t stick
decisions that get reopened without new information
decisions that “move forward” but never actually settle
Everyone stays busy. The plan still looks clean, and the quarter still gets hit.
What decision churn looks like (operator version)
You’ll recognize it quickly:
The team “decides,” but work doesn’t change the next day.
The same topic returns next week with a new slide.
“One more pass” becomes the go-to move.
Teams keep building options instead of building the thing.
Progress requires an executive in the room to keep work from stalling.
If your operating cadence is dominated by “alignment” forums, you’re not running execution. You’re running decision support.
The financial punch isn’t the meeting hours. It’s the value you push to the right.
Back-of-the-envelope model (order of magnitude):
Deferred value ≈ (Annual value at stake ÷ 12) × Months of churn delay × Realization factor (0.3–1.0) Example: a $50M/year initiative, 4–6 weeks of churn (1.0–1.5 months), and a 0.6 realization factor ≈ (50 ÷ 12) × (1.0–1.5) × 0.6 = $2.5M–$3.75M deferred. If realization is closer to 1.0 (immediate value), it’s $4M–$6M.
The point isn’t precision — it’s that one extra decision cycle routinely moves mid-seven figures in material initiatives.
The cost stack (what churn actually creates)
When a decision won’t hold, the org pays in predictable ways:
Rework: build → revise → rebuild
Decision latency: work waits on moving answers.
Escalation churn: “Can you jump on for 15 minutes?” becomes the operating model.
Scope creep: teams optimize for the latest comment, not the outcome
Throughput collapse: fewer finished outputs per week
Churn rarely appears as “failure.” It shows up as slippage, rework, and margin erosion.
The 4 root causes (what’s really underneath it)
Decision churn is usually a system problem, not a talent problem.
1) Decision rights aren’t real
People don’t know who can lock it — or the “decider” won’t decide without consensus.
Tell: the decision bounces between forums, with no finality.
2) Trade-offs aren’t declared
If you won’t say what you’re not doing, everything remains negotiable.
Tell: “We can do both” language. Everything remains “important.”
3) Risk ownership is missing
Nobody wants their name associated with the downside, so the org keeps asking for more analysis.
Tell: “Let’s pressure-test” becomes a loop rather than a step.
4) Pressure reopens everything
As timelines tighten, leaders reopen settled calls because the consequences become real.
Tell: decisions that were “locked” become “up for discussion.”
Fast diagnosis: Are you deciding or auditioning?
For any “decision,” ask three questions:
Did downstream work change within 24 hours?
Can one person name the decider on the spot?
Is there a reopen rule — or can anyone reopen at any time?
If you can’t answer all three, you don’t have a decision. You have a conversation instead.
One operator move that reduces churn in 7 days - No workshop. No new process.
Run a “Decision Lock” on your top 5 initiatives
For each initiative, write this in a shared doc (5 lines, no narrative):
Decision: one sentence
Decider: one name
Inputs: max 3 names
Deadline: date + time
Reopen criteria: only reopened with new information in categories A/B/C
Then enforce the rule that changes behavior: If someone wants to reopen, they must bring new information — not new preferences, new politics, or new anxiety.
This doesn’t reduce debate. It reduces re-debate.
Quarter-end shouldn’t be when you start diagnosing what happened — whether good or bad.
If decisions don’t hold, you don’t have an execution problem. You have a decision system that can’t commit under pressure.
And here’s the uncomfortable truth: Every extra decision cycle is a quiet way of choosing to miss the quarter while staying busy.
Which function creates the most churn in your experience: Product, Sales, Finance, or the executive layer?
