Operational chaos: measure its real cost

Choose a specific workflow

“Chaos is expensive” is not a measurement. Start with an observable journey: processing an enquiry, preparing an invoice or approving a delivery. Define where it starts and ends, and which teams are involved.

Over a representative period, record how many cases pass through that workflow. This gives you a denominator for comparison instead of a general impression.

Record visible losses

Identify repeated data entry, searches for information, corrections and cases sent back to an earlier step. For each occurrence, note its frequency and the time actually spent resolving it. Activity logs and team discussions can help establish the facts.

Separate active work from waiting. A case held up for two days does not automatically mean two days of labour were lost; it may, however, delay a response or an invoice.

Estimate without inflating the figures

For an initial estimate, multiply the observed rework time by a consistent internal hourly cost, then add documented direct expenses: credit notes, repeated services or penalties actually incurred. Always state the period and assumptions.

Do not count the same incident twice, for example as lost time and then as a “cost of delay” without separate evidence. Lost sales opportunities can be tracked separately, but they are not guaranteed revenue.

Find the cause

Classify recurring incidents by origin: missing instructions, inaccessible data, late approval or an unsuitable tool. The most visible symptom is not always the main cause.

Check the diagnosis with the people doing the work. Automation will not resolve a contradictory decision rule; it may only repeat it faster.

Test a correction

Choose a limited intervention: clarify a required field, remove duplicate entry or move an approval to the right point. Name the person responsible for the test and the cases it covers.

Keep the previous process available during the trial if the risk of disruption is real. A local improvement should not make another team's work harder.

Compare before and after

Repeat the same measures over a comparable period. Look at rework time, error counts and the quality of the outcome. If case volume or complexity has changed, say so before drawing a conclusion.

• Define a workflow and baseline period.
• Document frequency, active time and direct expenses.
• Separate observed facts from financial assumptions.
• Test a correction, then measure again.