A recurring management question that takes two weeks to answer costs money. It does not appear on any account, which is exactly why it persists.
The visible cost, and the larger one
The visible cost is analyst time. Illustratively: three analysts, four days each, twelve times a year. At a fully loaded rate of $95 an hour that is roughly $110,000 a year of effort to answer one recurring question.
That number is real, and it is the smaller one.
The larger cost is what happens while the organization waits.
- The decision the question was meant to inform is deferred, and the business continues moving in the meantime
- Leadership meets twice, because the first meeting cannot resolve which number is right
- When the answer arrives it describes a situation that has already changed
- Because the answer took two weeks, the question gets asked less often than it should — so the organization operates on a longer feedback loop than it needs to
That last effect is the one that compounds. An organization that can answer a question in two days will ask it monthly. One that needs two weeks will ask it quarterly, and will make three months of decisions without it.
How to size it without a study
You do not need a formal exercise. Ask four questions about one recurring question:
- How long does it take to answer, start to finish?
- Who gets pulled in, and what stops while they do it?
- What decision waits on the answer, and what does a month of delay on that decision cost?
- How often is the answer disputed, and what happens then?
Question three is the one people skip and the one that carries the money. A staffing decision deferred a month in a 400-person firm is not a rounding error.
Why this matters before choosing what to build
Most analytics investment is justified on capability — we will be able to see more. That is hard to price and easy to defer.
Decision latency is a cost that already exists, is already being paid, and can be described in terms a CFO recognizes. It reframes the conversation from what could we build to what are we currently paying for not having it.
It also produces a better ordering. The questions worth solving first are not the interesting ones. They are the ones where the current answer is slow, expensive, disputed, and attached to a decision that matters.
An illustrative ordering
Four recurring questions at a mid-sized firm, scored on the four criteria above:
| Question | Time to answer | Disputed? | Decision it holds up |
|---|---|---|---|
| Why did delivery margin move? | 2 weeks | Frequently | Staffing and portfolio mix |
| What is pipeline coverage? | 1 day | Rarely | Sales focus |
| Which clients are actually profitable? | 3 weeks | Always | Account strategy, pricing |
| What is headcount versus plan? | Hours | Never | Recruiting pace |
The first and third are worth solving. The second and fourth are already working and should be left alone, however easy they might be to improve.
That ordering is not obvious from the outside, and it is frequently the opposite of what a technology-led assessment would recommend — because the questions that are slowest to answer are usually the ones spanning the most systems, which look the least attractive to start with.
The reframe that matters
Most analytics investment is justified on capability: we will be able to see more. That is difficult to price and easy to postpone for another year.
Decision latency is a cost that already exists and is already being paid. Naming it changes the conversation from what could we build to what are we currently paying for not having built it — and the second question is much harder to defer.
Identifying and ordering those questions is what the 360° Enterprise Intelligence Blueprint produces.