The tolerated pain
A spreadsheet takes time to open, switching applications stalls a task, and a restart interrupts work that was already under way. Each delay looks too small to justify attention. Keeping the device feels economical because replacement has a visible price while waiting is scattered through the working day. This argument only holds if the existing setup still supports the work at an acceptable total cost.
Operational consequence
Separate device delay from slow network access, application response and an unusually demanding task. A faster laptop will not necessarily fix a remote service bottleneck. Record the task, duration, frequency and whether the employee could do useful alternative work. Repeated restarts can also create recovery work: reopening files, checking saved changes and reconstructing the point at which the task stopped.
Financial consequence
For a measured period, estimate blocked capacity cost as the sum, across affected employees, of genuinely blocked minutes divided by 60 and multiplied by each employee’s loaded hourly employment cost. Add separately recorded support and recovery hours at the appropriate rates. Do not count the same minute as both waiting and recovery. Use actual payroll inputs and observations; there is no universal cost per slow computer.
What the estimate does and does not mean
This is a valuation of capacity consumed, not an automatic reduction in payroll available from buying equipment. Cash savings require a real change such as avoided overtime or an otherwise necessary hire. If delays affect a constrained customer process, record missed commitments separately and establish attribution before assigning lost contribution. Multiplying every pause by gross sales would exaggerate the effect.
Commercial urgency
A useful trigger is a repeated, measured delay in a task that gates other work, especially when support visits keep treating the same symptom. Compare the observed avoidable burden over a consistent planning period with the full intervention cost: diagnosis, repair or replacement, configuration, migration and disruption. Do not assume every measured minute will be recovered or that the most expensive device is the right answer.
Resolution
Start with a representative task on the affected setup and a suitable comparison setup. Identify whether the constraint is local hardware, configuration, connectivity or the application. Trial the smallest supported correction, preserve the employee’s files and test the task again. Agree acceptance criteria with the person doing the work. Track both blocked time and support demand after the change, including any new migration or compatibility issues.
The economic meaning
Device life should be judged against productive use and support burden as well as purchase price. A working machine can still consume scarce capacity; a replacement earns its place when evidence shows that it removes the actual constraint.
Sources and method
This is a diagnostic cost model, not a client case study or an industry benchmark. It uses the operating condition described above and requires your own time, transaction and cost records. No numerical loss or saving is asserted. The related Mellorca article supplies context; the model does not rely on current product features or external statistics.