Opening the book…
The same system view matters when a team proposes a change. A local improvement makes one task or department perform better according to a selected measure. It may benefit the larger system, but that needs evaluation. An unintended consequence is an effect that was not the intended purpose of the change. Faster or cheaper work can create delays, extra work, or new risks elsewhere.
Imagine that the enzyme company asks purchasing to lower material costs. Purchasing selects larger containers because their price per unit is lower. Production uses only a small amount each week. Repeated opening increases handling, storage becomes crowded, and unused material reaches its expiration date. The purchase price improves while total waste may rise. This is a hypothetical example; the team would need actual records to determine the result.
A bottleneck is a step whose limited capacity restricts the flow of work. If production increases output while QC capacity stays the same, more samples may wait for testing. Production can report success even as customers wait longer. The system benefits only when the increased activity supports usable output at the pace the whole process can handle.
Consider a laboratory that starts with no backlog. It receives 28 samples but completes only 20 reports each working day. Assume each sample needs one report, with no retesting or cancellations. Eight samples remain unfinished each day, so the backlog grows to 40 after five working days. Receiving more samples has increased waiting work without increasing completed reports.
Before approving a change, examine the connected processes. Ask who will receive more work, whether information or material needs will change, and whether the change affects storage, training, review, or customer commitments. In a controlled process, use the applicable change procedure and obtain required approvals before implementation.
Select measures that reveal the broader result. End-to-end performance describes how well work meets its purpose across a stated path. For the enzyme company, useful measures may include order-to-delivery time, complete and correct orders, avoidable repeat work, waste, and shipment-linked complaints. Define the population and boundary for each measure; a narrower testing turnaround measure answers a different question from order-to-delivery time.
Compare performance before and after a change using the same definitions and a suitable observation period. Check whether workload, product mix, or other conditions also changed. A short improvement in one number does not by itself show that the change caused better system performance. Include feedback from employees and customers who experience the effects.
This page titled 5.8: Recognizing unintended consequences of local improvements was last modified on Fri, 06 Nov 2026 11:48:10 GMT and is shared under a CC BY-SA 4.0 license and was authored, remixed, and/or curated by Emalee MacKenzie.
The book could not be loaded just now.