Yes, there is. We’ve just been talking - Eliyahu M. Goldratt

Deciding that the company is wasting too much money on duplicated efforts and thus moving to a more centralized mode. Ten years later, we want to encourage entrepreneurship and we move back to decentralization.

With the bottlenecks more productive now, our throughput has gone up and our backlog is declining. But making the bottlenecks more productive has put more demand on the other work centers. If the demand on another work center has gone above one hundred percent, then we’ve created a new bottleneck.

STEP 1. Identify the system’s bottlenecks. (After all it wasn’t too difficult to identify the oven and the NCX10 as the bottlenecks of the plant.)
STEP 2. Decide how to exploit the bottlenecks. (That was fun. Realizing that those machines should not take a lunch break, etc.)
STEP 3. Subordinate everything else to the above decision. (Making sure that everything marches to the tune of the constraints. The red and green tags.)
STEP 4. Elevate the system’s bottlenecks. (Bringing back the old Zmegma, switching back to old, less “effective” routings. . . .)
STEP 5. If, in a previous step, a bottleneck has been broken go back to step 1.