October 13, 2026 — In private equity, delayed operating information is often treated as an inconvenience of reporting. I view it differently. It is a compounding economic cost: it shortens the time available to make a good decision, increases the price of correcting a bad one, and gradually teaches an organization to manage explanations rather than conditions. The issue is not whether a company can produce a monthly packet. It is whether the people closest to an operating deviation can recognize it, interpret it, and change course while the outcome is still open.
Information has a decay rate
A business can be profitable, well staffed, and competently led while still operating with stale facts. The symptoms are familiar: a margin shortfall becomes visible after the selling period has closed; customer-service deterioration is explained after renewal conversations have occurred; inventory imbalances are discovered only after expedited freight has become necessary; labor overruns are understood after the schedule can no longer be repaired.
None of these failures begins with a spreadsheet. They begin with a gap between an event and the moment a responsible operator can act on a reliable interpretation of that event.
I think of that gap as decision latency. It is not simply the age of a report. It includes the time required to capture a transaction, reconcile conflicting records, establish what the metric means, assign responsibility, decide on a response, and see whether the response worked. A company may have an attractively formatted dashboard and still have excessive decision latency if its measures are disputed, its exceptions are not routed to an owner, or its managers lack authority to act.
The economic cost is usually hidden because it does not appear as a discrete expense. It emerges in smaller forms: an additional discount granted to save a customer, excess overtime used to recover a production schedule, a purchase made at an unfavorable price, a supervisor assigned to reconcile data rather than improve the process, or a manager who becomes reluctant to make a call without another meeting. Over time, these costs can become embedded in the company’s normal performance. What begins as a reporting weakness becomes an operating habit.
Accuracy is necessary, but timeliness changes the economics
It is tempting to frame the problem as one of data accuracy. Accuracy matters, but it is incomplete. A number can be correct and still be economically unhelpful if it arrives after the relevant decision has become irreversible.
ISO’s information-quality framework is useful in this respect. It treats quality as more than format or correctness, encompassing whether information has the meaning and practical usefulness required for its intended use. It also emphasizes measurement and reporting of quality through the information life cycle. (iso.org) For an owner, that is a more demanding standard than asking whether a report ties to the general ledger.
The appropriate question is: useful for which decision, made by whom, before what deadline?
Consider a service business with labor as its principal variable cost. A month-end labor report may be accurate and valuable for financial control, but it may be too late to influence the staffing choices that created the overage. The relevant operating information may instead be daily scheduled-versus-worked hours by location, the volume assumptions behind the schedule, and a clear threshold for intervention. The monthly report confirms the result. The daily signal creates the possibility of changing it.
This distinction matters because operating decisions have different clocks. Pricing can sometimes be corrected in weeks. Staffing can require days. A missed service commitment may need attention within hours. A quality failure may demand an immediate production hold. The faster the business can incur an irreversible cost, the less acceptable delayed information becomes.
The value of an operating fact is not fixed at the moment it is recorded; it declines as the available choices narrow.
That judgment does not imply that every measure should be real-time. Real-time reporting can create noise, distraction, and false precision. The right cadence depends on the operating cycle and the reversibility of the decision. A weekly procurement measure may be appropriate in one business and dangerously slow in another. The discipline is to make the cadence explicit rather than inherited.
Delay changes behavior before it changes results
The most serious effect of delayed information is behavioral. When people repeatedly receive facts after the moment for intervention, they adapt. They become skilled at reconstructing what happened. They become less practiced at preventing it.
This is an important distinction. Retrospective explanation has value; it can reveal root causes and improve future process design. But an organization that mainly receives retrospective information will naturally allocate more energy to variance narratives, attribution, and negotiation over the past. The operating conversation shifts from “What should we change today?” to “Why did last month differ from plan?” Both questions matter. Only one preserves immediate choice.
Research on management practice supports the broader principle that measurement and follow-through are connected. In a field experiment involving airline captains, performance monitoring and target setting were among the practices associated with improved performance on the targeted fuel-saving measures. (nber.org) That evidence should not be stretched into a universal prescription for every company. It does, however, reinforce a practical point: measurement produces value when it is tied to a specific behavior, a defined objective, and a timely feedback loop.
The same logic applies beyond frontline operations. A commercial leader cannot improve pipeline quality from a late-quarter summary if stage definitions are inconsistent and aging opportunities are not reviewed while they can still be qualified, advanced, or removed. A procurement leader cannot protect availability merely by explaining purchase-price variance after substitutions and emergency orders have occurred. A plant manager cannot preserve throughput with a report that identifies a recurring constraint only after the production week is complete.
In each case, delayed information does more than slow a decision. It changes what management believes its job to be.
The hidden cost is lost optionality
I would not measure the cost of information delay solely by the number of hours needed to prepare a report. The larger cost is the loss of lower-cost options.
Early in a deviation, management often has several reasonable responses. It can rebalance workload, revise a schedule, contact a customer, change a replenishment order, inspect a process step, or redirect capacity. As time passes, those choices disappear. The remaining actions tend to be more expensive and more disruptive: overtime, expedited freight, concessions, rework, rush purchasing, broad price cuts, or a senior escalation.
This is why two businesses with similar reported results can carry different underlying risk. One may be encountering problems early and resolving them through normal operating routines. The other may be achieving the same reported result through repeated recovery efforts. The latter can look stable until an additional disruption removes the room for recovery.
Thomas Hubbard’s study of onboard computers in trucking offers a useful historical illustration. Its central insight was not that information technology, by itself, creates economic value. It was that better information and communication can improve the allocation of scarce capacity when dispatchers can bring that information to bear on actual operating decisions. (nber.org) The enduring lesson is organizational rather than technical: information must arrive in a form, and at a moment, that permits a different allocation of resources.
I therefore regard operating latency as a form of contingent liability. It may not affect every day’s results. But it raises the expected cost of disruption because the business enters a problem later, with fewer choices and less confidence about where to intervene.
Measure the path from event to action
The remedy is not a larger reporting package. It is a more deliberate map of the information path for a limited set of consequential decisions.
For each critical operating measure, I would want the company to define six moments:
- Event time: When did the underlying condition occur?
- Capture time: When was it recorded in a usable system?
- Verification time: When did the company have sufficient confidence in the measure?
- Decision time: When did an accountable person review it and choose a response?
- Action time: When did the response change the operation?
- Learning time: When did the company determine whether the response worked?
This sequence makes hidden delays visible. A finance team may close quickly, while the underlying operational measure remains unverifiable for two weeks. A daily report may be available, while no one reviews it until a weekly meeting. A manager may identify the problem promptly, while the person with authority to change the schedule is unavailable. Each is a different failure. Treating them all as “a data issue” obscures the remedy.
The objective is not to monitor everything. It is to identify the small number of measures where lateness is especially costly: conversion at a constrained sales stage, backlog aging, service failures, yield loss, unplanned downtime, labor deployment, cash collection, or another variable specific to the business model.
For each measure, there should be a named owner, a plain-language definition, a tolerance range, and a predetermined escalation path. Most importantly, there should be a stated action associated with a breach. A metric without a decision rule easily becomes theater. It can create the appearance of control while leaving the operating response discretionary, delayed, or undefined.
Build reliability without creating bureaucracy
Speed without trust is not an improvement. If managers learn that early information is frequently wrong, they will wait for a later and more credible number. That response may be rational, but it recreates the latency problem.
The solution is not to insist that all preliminary data be treated as final. It is to distinguish clearly between provisional operating signals and confirmed financial results. An early measure can be useful if its directionality, known limitations, and owner are understood. A company does not need perfect certainty to investigate a rising exception rate, deteriorating schedule adherence, or unusual order pattern. It does need honesty about the confidence level of the signal.
A 2026 Federal Reserve Bank of San Francisco working paper found that firms’ larger revisions to forecasts of their own sales and employment were associated with greater perceived uncertainty, with recent revisions exerting particular influence. (frbsf.org) I take a narrow lesson from that work: unstable information can shape judgment as well as planning. The answer is not to suppress early signals. It is to maintain disciplined definitions, record changes in assumptions, and separate what is observed from what is inferred.
In practice, this means keeping an exception log that is short enough to use. It should record the deviation, the first observed date, the owner, the working hypothesis, the action taken, and the result. Over time, this log can reveal whether a company’s primary issue is slow detection, slow decision-making, weak execution, or weak learning. Those are not interchangeable problems, and they should not receive interchangeable solutions.
An owner’s standard
I believe an owner should ask more of operating information than a quarterly explanation of performance. The standard should be whether management can show that it knows which facts arrive too late, why they arrive late, and what decisions become more costly as a result.
That inquiry is constructive when it remains specific. It should not become a demand for universal surveillance or another layer of approval. The goal is to give capable operators enough reliable time to exercise judgment before choices narrow.
The best reporting systems do not make a business feel busier. They make it less surprised. They reduce the distance between condition and response, preserve lower-cost options, and create a record from which the organization can learn. That is the hidden cost of delayed operating information: not merely that management learns late, but that the company has already paid more for the right to act.
Sources reviewed
- ISO 8000-8:2015 — Data quality: Information and data quality: Concepts and measuringInternational Organization for Standardization
- The Impact of Management Practices on Employee Productivity: A Field Experiment with Airline CaptainsNational Bureau of Economic Research
- Information, Decisions, and Productivity: On-Board Computers and Capacity Utilization in TruckingNational Bureau of Economic Research
- Recency Effects in Perceived UncertaintyFederal Reserve Bank of San Francisco