Did the faster process actually save time?

A faster process saves time when the work it removes exceeds the checking, corrections and maintenance it adds. The time to produce its first output is one measurement. The time to reach a result someone can use is another.

Put the new work in the total

For an invented example, a team spends six hours each week preparing a supplier comparison. A new process assembles a draft in fifteen minutes. Someone then spends ninety minutes checking it, thirty minutes correcting missing information and another fifteen minutes maintaining the inputs.

The new weekly total is two hours and thirty minutes. It releases three hours and thirty minutes compared with the six-hour process. Calling the improvement “six hours saved” would erase the work that makes it usable. Calling it worthless because it still needs review would ignore a substantial gain.

Now include the initial setup. If the team spent fourteen hours building and learning the process, four weeks at the stated saving recover that amount of staff time. That is a simple time comparison, with the assumptions held steady. A change in volume, error rate or maintenance can change the result.

Chapter 16 of Infinite Upside applies that distinction to automation. It asks whether a recurring task is worth improving and whether the improvement survives the work of making its output dependable. The useful unit is a finished job, including the exceptions.

Compare the same finished job

The old comparison may have included delivery dates, cancellation terms and a recommendation. If the new draft includes only prices, it has removed part of the task as well as some work. Establish what the finished result must contain before declaring the new process faster.

A good baseline need not be elaborate. Follow a few ordinary runs and the last difficult one. Record what came in, who worked on it, what had to be corrected and when someone could make the decision. Distinguish elapsed time from staff time: waiting overnight for a reply is different from spending eight hours on the task.

The book’s example also recognizes a benefit beyond minutes. A better process may prevent a recurring omission and spare a manager from reopening a decision. Conversely, an occasional consequential error can create a cost the average time measure misses. Review the exception that would matter, not just the smooth demonstration.

Finishing sooner with the same staff time

Overlapping work can shorten the wait without reducing the total work. Consider a separate invented job preparing an event packet. Its five tasks use the following supplied times:

• A: verify the roster, four minutes.
• B: prepare the route diagram, six minutes.
• C: assemble the roster and diagram, two minutes, after A and B finish.
• D: check the delivery list, three minutes.
• E: check and release the packet, three minutes, after C and D finish.

A, B and D are ready to begin at minute zero. Every worker is qualified for every task. All starting materials and equipment are available, and the durations include required checks and handoffs. Each task needs one worker's full attention without interruption; splitting it between workers cannot shorten it. There are no other constraints or rework in this example.

The tasks total eighteen staff-minutes: minutes of work added across the people doing it. One person can perform A, B, C, D and E in eighteen elapsed minutes.

Two people can finish in eleven elapsed minutes. The first performs A during minutes 0–4 and D during 4–7, then E during 8–11. The second performs B during 0–6 and C during 6–8. The first person waits from minute seven to eight because E still needs C. Total staff time remains eighteen minutes.

Dividing eighteen by two gives nine. It does not produce a feasible nine-minute schedule. B needs six minutes before C can begin, then C needs two before E's three can begin. That chain alone requires eleven minutes.

A third qualified person can start D at zero alongside A and B. C still starts no earlier than minute six, and E no earlier than minute eight. The packet still finishes at minute eleven. Extra headcount alone has not shortened this required chain.

Before promising a shorter completion time, identify which work can overlap and which finished result the next task must receive. Record total staff time separately from the feasible finish.

Choose resources for the particular work

The invented supplier comparison does not require every step to use the same resource. Finding the current quotation, copying its stated price and checking an addition are different jobs from interpreting a cancellation condition that conflicts with the proposed delivery date.

If a simpler, less costly process handles the routine extraction dependably, keep the source, date and relevant wording with its result. Send the unresolved condition to a reviewer capable of examining it, with enough context to decide what changes. Escalating every lookup can add cost and delay; leaving a difficult judgment with a process that repeatedly gets it wrong can create more correction work than it saves.

Chapter 16’s choice is about the finished task. Compare the full routes, including the transfer, checking and recovery when a step fails. A lower cost for the first pass is useful only if the result still reaches the person who needs it in a form they can use.

Try the repair where the old process worked

A correction can make yesterday’s failure disappear while creating a different omission. Chapter 16 asks for a changed instruction to be tried on several cases. The useful question is what the revised process now does, including work the earlier version handled properly.

Return to the invented supplier comparison. Suppose its draft omitted a supplier’s cancellation condition, leaving the reviewer to find it in an attachment. The coordinator proposes a new rule: copy the paragraph headed “Cancellation” into every comparison. On the failed example, that produces the missing paragraph. The correction appears to work.

Now take a quotation the previous process handled well. It has no paragraph with that heading. The relevant condition sits under “Changes to a confirmed order,” where the supplier describes what happens if the buyer alters the order after preparation begins. Copying only a section called “Cancellation” would drop information that the manager still needs.

The proposed rule looks for a heading when the manager needs a condition. What must survive is the information that could change the purchase decision, wherever the supplier has placed it.

A revised process could keep the relevant supplier passage and its current source with the comparison, then identify which change, delay or cancellation it concerns. The reviewer can examine the condition in context rather than accept a blank field as evidence that no condition exists. Use that approach on both quotations before replacing the ordinary process.

Now suppose the supplier’s current quote refers to an attachment that is unavailable. An older attachment is easy to find. It does not establish the current terms. The comparison needs to identify the missing source and the decision still waiting on it, while carrying forward the other facts that can be supported. Filling the field from the older file would hide the remaining work.

Keep the cases small enough to inspect. Preserve the example that exposed the omission, an ordinary example the process previously got right and an example with a consequential input missing. Decide what each result must retain before looking at the revised output.

Choose earlier cases by what the change can affect. For this repair, keep comparisons whose result depends on selecting the right supplier terms.

Any extra recurring checking belongs in the time comparison. A more dependable process can be worth the additional review. Count that work, then follow the next ordinary comparisons to see whether the correction remains useful.

Released capacity is not automatically cash

If the team’s pay and hours remain the same, saving three and a half hours does not immediately remove those hours from payroll. It creates capacity. The team can use it to serve customers, finish delayed work, learn something useful or reduce an unsustainable workload.

That capacity can be valuable before any expense falls. It may also delay a hire if the team can handle additional work. A cash saving needs an actual change in spending. Keep those outcomes distinct so the improvement can be judged on what it does accomplish.

Chapter 3 shows an earlier version of the same concern: when preparation is incomplete, employees compensate while customers wait. A fast handoff that leaves the receiver to rediscover the facts has moved the work rather than finished it.

Choose a recurring review date and compare the same task again. Is someone using the result? Are the corrections becoming smaller? Does another person know how to keep the process working? What useful work has the released time made possible?

Those answers help choose the next improvement. If checking dominates, make the inputs or evidence easier to inspect. If nobody uses the output, reconsider the task.