What you’re saying is that making an employee work and profiting from that work are two different things. - Eliyahu M. Goldratt

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.

We had physical constraints that helped us to focus our attention, to zoom in on the real policy constraint. That isn’t the case in the division. Over there we have excess capacity going through our ears. We have excess engineering resources that we succeed so brilliantly in wasting. I’m sure that there is no lack of markets. We simply don’t know how to put our act together to capitalize on what we have.

Bob comes into the office with a smear of grease on his white shirt over the bulge of his beer gut, and he’s talking nonstop about what’s going on with the breakdown of the automatic testing machines. “Bob,” I tell him, “forget about that for now.