Lesson 8 is where the program stops teaching parts and starts teaching design. Everything before it was preparation. Here the student learns the one discipline the rest of the program leans on: flow before equipment. The single outcome every student must leave with is the reflex to describe how material moves through a building, in plain language, before they name a single machine. If a student can define a flow diagram but reaches for equipment the moment you hand them a floor plan, the lesson hasn't landed. Don't lecture the process flow diagram off a slide. Put a floor plan in front of the room and make them draw the flow before anyone says the word conveyor.
| Segment | Min | What happens |
|---|---|---|
| The engineer with a floor plan | 5 | Read the hook aloud. Put two words on the board: layout and design. Ask the room what separates them, and steer to the answer. A layout is equipment arranged on a floor. A design is material movement worked out before any machine gets named. |
| Why equipment-first fails | 8 | Walk the failure modes: it plans for the machine, optimizes for open space, skips where material waits, and runs fine only while the building is calm. Land the law on the board: flow before equipment. The structured stress test is Lesson 10; today you only establish that stress is where an equipment-first design breaks. |
| Blocks and arrows | 8 | Blocks are process steps, arrows are material moves, no equipment. Read a sample flow out loud as a story. Walk the checklist: entries, exits, decisions, splits, merges, wait points, replenishment and returns as their own flows. Have the room guess the Three W's before you reveal the card. |
| Draw the flow from the floor plan | 15 | Key teaching moment, below. This is the center of the lesson. Don't cut it to save time. |
| Separate the flows | 8 | Outbound, replenishment, returns, exceptions, each its own path. Use the Common Mistake as a discussion prompt: what breaks when replenishment rides the outbound path unplanned? Mark wait points; don't size them, that's Lesson 9. |
| Safe and unsafe assumptions | 6 | A safe assumption is cheap to correct; an unsafe one forces a redesign. Have them label two or three assumptions from the floor-plan exercise by type, then say which one they'd confirm with the customer first and why. |
| Riverside and close | 10 | Run the classification debate below. Read the you-are-a-carton walk aloud. Collect each student's Layer 1 flow call and their justification. Grade the reasoning, not the drawing. |
| Total | 60 | Baseline session. Expand with the stretch options below if you have 90 minutes. |
Hand the room a building floor plan with the dock doors, the pick zones, and a staging area marked. Give them the throughput requirement and the product, nothing else. Then set one rule: produce a flow diagram before you touch any drawing tool. Blocks and arrows only, no equipment. Give them the quiet minutes to do it.
Then put the diagrams up side by side and compare them across the room. They won't match. One student merged the two pick zones early, another kept them separate all the way to the dock. One drew a returns path, another forgot returns entirely. Those differences are the whole point. Walk each one and ask what engineering consequence follows from it: how different people read the same operation differently, and what each reading costs downstream. A student who has drawn the flow, defended it, and watched a peer's version expose a gap in their own will never again open a drawing tool first.
The failure mode this lesson exists to prevent is the student who walks in with equipment already pictured and whose instinct is to place it. Stop it early. Require the flow diagram before any equipment gets discussed, every time. Signs:
A student who restates the definition of a flow diagram has memorized it. A student who can take a floor plan they've never seen and narrate the material path through it has internalized it. Test for the second, not the first. Two tells matter here: they draw equipment when you ask for flow, and they can't narrate the package's journey out loud.
When you see either one, don't repeat the content. Change the scenario. Give them a different building, a different product, a returns flow they have to place, and watch whether they reason through it or reach for the answer they memorized. Surface learners apply the memorized answer. Real learners slow down, think it through, and find where it doesn't fit.
Michael has watched two systems fail in this building. The first was a pneumatic accumulation system that lost air pressure at peak and became a maintenance problem nobody was trained for. The second stopped the whole line every time anything downstream slowed. Put both on the board and run a debate: was each one a flow problem or an equipment problem? Push them on the second. A line that halts whenever a downstream station slows has no buffering where material needs to wait, and that's a flow design gap, not a hardware defect. New equipment on the same flow fails the same way.
Then run the flow story. Read the you-are-a-carton walk aloud and have each student produce Riverside's Layer 1 diagram: both pick zones as separate starts, the merge, the sort decision, three dock doors. Have them narrate it out loud. The drawing isn't the grade. The justification is. A student who can defend why the flows merge where they merge understands it. A student with a tidy diagram and no reasoning behind it doesn't.
This Layer 1 diagram is the artifact Lessons 9 and 10 build directly on top of. Make sure every student keeps theirs in the running Riverside project note they started in Part I, dated and organized. Frame it as simply what engineers do, and keep reinforcing the habit every time Riverside comes up.
Don't tell them where it leads. Lesson 9 hands this same diagram back and starts layering volume, delays, and the three data questions onto it. The students who kept a clean Layer 1 without being told why will have a far easier time then. Your only job now is to make keeping it feel normal.