Tell me how you measure me, and I will tell you how I will behave. - 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.

When a proto-type — a new initiative — doesn't work, we face two alternatives: one is to bitch about reality and the other is to harvest the gift it just gave us, the knowledge of what has to be corrected.

"While they go get the others, I figure out the details. The system I’ve set up is intended to "process’’ matches. It does this by moving a quantity of match sticks out of their box, and through each of the bowls in succession. The dice determine how many matches can be moved from one bowl to the next. The dice represent the capacity of each resource, each bowl; the set of bowls are my dependent events, my stages of production. Each has exactly the same capacity as the others, but its actual yield will fluctuate somewhat.