How do you measure management latency?
Take ten recent material changes and record four timestamps for each: when it changed, when a person able to act knew, when the decision was made, and when the action shipped. The median gap from changed to acted is your management latency. The widest of the three internal gaps tells you which problem you actually have.
Why it works this way
The measurement is deliberately crude, because a crude number that exists beats a precise one that does not. Ten incidents and a median is enough to act on. Companies that try to instrument this properly before measuring it once generally never produce the first number.
The reason the four timestamps matter more than the total is that each gap has a different fix, and treating the total as one problem sends the effort to the wrong place. Changed to known is a noticing problem — nothing in the system was watching. Known to decided is a cadence and ownership problem — someone knew and the next forum was Friday, or nobody was sure whose call it was. Decided to acted is an execution problem. A company with a five-day known-to-decided gap will get nothing from better monitoring.
Review cadence sets a hard floor that no amount of data freshness lowers. If a class of decision is only made in a weekly meeting, its latency cannot go below roughly seven days no matter how current the warehouse is. That floor is usually the finding, and it is usually a surprise, because the company has been investing in freshness.
The comparison worth making is internal and over time. There is no credible industry benchmark for this and anyone quoting one is guessing. Measure it once, change one thing, measure it again in a quarter.
The measurement, step by step
- 1. Pick ten recent material changes — Choose things that actually mattered in the last quarter — a deal slipping, a churn signal, a margin move, a spike in support volume. Avoid crises: they get abnormal attention and will flatter the number.
- 2. Record when it changed — The timestamp in the source system where the change actually happened, not when it appeared in a report. This is usually the hardest of the four to recover, and how hard it is is itself a finding.
- 3. Record when a person able to act knew — Not when it was technically visible somewhere. When a specific person with authority over the response became aware. Slack messages and calendar entries usually settle this.
- 4. Record when the decision was made, and when the action shipped — The decision timestamp is when the call was actually made, which is often later than the meeting it was discussed in. The action timestamp is when something changed in the world.
- 5. Compute the median and find the widest gap — The median changed-to-acted figure is your management latency. Then look at which of the three internal gaps is widest across the ten — that is the class of problem to fix first, and it is frequently not the one the company assumed.
- 6. Re-measure after one change — Change one thing — a monitoring rule, a decision owner, a review cadence — and measure the same way a quarter later. Against your own prior number, not a benchmark.
What it looks like
The deal slips on Tuesday. It surfaces in the forecast call on Friday. The response is agreed the following Monday and ships Wednesday. Management latency: eight days. The same company pages an engineer at three in the morning for four hundred milliseconds of API latency.
What this establishes, and what it does not
- What this establishes — The four-timestamp method is straightforward and reproducible, and companies running it generally can produce the first three numbers with effort and find the fourth easy. The finding that review cadence sets a floor is arithmetic rather than a claim.
- What it does not — Whether reducing management latency improves outcomes, or whether it mostly produces faster wrong decisions in companies that lack the evidence to decide well. The plausible reading is that latency reduction helps only where the decision quality is already adequate, which would make evidence the prior constraint and speed the second one.
- What would show it is wrong — If a company halves its management latency across a year and its rate of avoidable surprises and its decision reversal rate are unchanged, then latency was not the binding constraint for that company. Reversal rate is the useful control: speed that produces more reversals is not an improvement, and a measurement programme that does not track it can show progress while making things worse.
The words this answer uses
- Management latency (https://www.themeetpatel.com/glossary/management-latency) — The elapsed time between something changing in a business and the person able to act on it knowing about it. Most companies measure system uptime to the second and leave management latency unmeasured.
- Organizational attention (https://www.themeetpatel.com/glossary/organizational-attention) — The finite capacity of a company to notice, prioritise and act on what is actually happening inside it. Storage buys none of it, and most tools spend it.
- Decision infrastructure (https://www.themeetpatel.com/glossary/decision-infrastructure) — The systems, ownership and thresholds that determine how a company moves from information to a decision. Dashboards sit one layer below it, as reporting infrastructure.
Related questions
- Why do the CRM and the finance system disagree about revenue? (https://www.themeetpatel.com/answers/why-crm-and-finance-disagree-about-revenue) — Almost always because they are answering different questions correctly. The CRM holds what was sold, dated when it was signed. Finance holds what was recognised, dated when it was delivered. Add mid-term changes, credits and currency, and two accurate systems produce two different numbers. The disagreement is a definition problem, not a data-quality problem.
- Decision intelligence vs business intelligence: what is the difference? (https://www.themeetpatel.com/answers/decision-intelligence-vs-business-intelligence) — Business intelligence is responsible for the view: it establishes what happened and presents it when asked. Decision intelligence is responsible for the decision: it notices what deserves attention without being asked, reconciles the systems that disagree, and carries a recommendation with its evidence attached. BI produces a chart. Decision intelligence produces a call someone can defend.
Frequently asked questions
How do you measure management latency?
Take ten recent material changes and record four timestamps for each: when it changed, when a person able to act knew, when the decision was made, and when the action shipped. The median gap from changed to acted is your management latency. The widest of the three internal gaps tells you which problem you actually have.
What is management latency?
The elapsed time between something changing in a business and the person able to act on it knowing about it. Most companies measure system uptime to the second and leave management latency unmeasured.
What is a good management latency?
There is no benchmark worth quoting and anyone offering one is guessing. The only useful comparison is against your own prior number. Most companies find their first measurement is in days for things they had assumed took hours, and that finding alone is usually worth the afternoon it costs.
Is management latency the same as data freshness?
No. The warehouse can be current to the minute while the person able to act finds out on Friday. Freshness is a property of the pipeline; management latency is a property of the organisation. Companies routinely buy the first while measuring nothing about the second.
How many incidents do I need to measure?
Ten is enough for a median that will change behaviour. The precision you lose is smaller than the precision you lose by never running the measurement, which is what happens to teams that decide to instrument it properly first.