How long should a marketing decision actually take?

Most organizations measure the quality of their decisions and ignore the speed. Latency is where the money actually leaks — and it is the one number nobody on the org chart is paid to lower.

Why this metric exists

Cost Per Decision establishes that every decision carries a cost. Decision latency is the hidden multiplier on that cost. A decision that is correct but arrives two weeks late is not a correct decision — it is a stale one, made against a signal the market has already moved past. The full argument for why this metric matters — and why it's a P&L problem, not an ops one — is in Decision Latency: The Rate-of-Learning Metric That Finally Has a Number.

In an auction-based, continuously-optimizing channel, latency compounds. Every day a budget shift, a creative kill, or a structural change waits in committee is a day the algorithm spends against the old answer. The cost is not the decision. The cost is the wait.

The benchmark table

Latency = signal availability → committed action. Ranges reflect the typical span from "the data is clear" to "the decision is approved and executing." v1 synthesis from public reporting; directional only, to be replaced with primary data.

How to read it

Find your sector and size, then locate yourself against three bands:

So: is your 14-day committee approval standard or failing? In enterprise FinTech, it is standard. In mid-market DTC, it is a structural liability. The same number is healthy or alarming depending entirely on the room you are competing in.

What drives the variance

Latency is not a personality trait of slow companies — it is an architecture. Three things drive it.

Approval layers. Each additional sign-off compounds latency rather than adding to it. A decision requiring four approvals does not take four times as long as one — it takes longer, because each layer introduces queue time, not just review time.

Data trust. Teams that do not trust their measurement re-litigate the signal before every decision. Low data trust converts directly into latency: you cannot move fast on a number you suspect is wrong. This is where broken measurement becomes a latency tax.

Committee size. Decision latency scales with the number of people who can say no. The fix is rarely "decide faster" — it is "reduce the number of nodes the decision has to pass through."

This is an org-design problem, not a productivity problem. You do not solve it with a faster tool; you solve it by redesigning the approval architecture.

The P&L translation

Convert latency to money through Cost Per Decision. If a decision is worth a 10% efficiency improvement on a $500K monthly channel, that is $50K/month — roughly $1,650/day of value. An enterprise decision that takes 21 days instead of 7 does not cost 14 extra days of patience. It costs 14 days × the daily value of the improvement you delayed.

That is the line a CFO recognizes: latency is a carrying cost on decisions you have already effectively made but have not executed. To put your own number on it, run the Decision Latency Calculator — three fields, two minutes, the dollar cost of every week your decisions sit in committee.

Methodology

The v1 figures are a directional synthesis of publicly available reporting on marketing approval cycles, decision-making cadence, and organizational structure across the named sectors. They are not primary Uncommon Move data and should be read as a starting baseline, not a measured result. Primary data collection is underway; each subsequent version of this table will be more authoritative than the last, replacing synthesized ranges with observed medians and stated sample sizes.