Lesson 1 taught the job. This lesson teaches the thing the job acts on: the operation. The one outcome every student must leave with is the ability to look at a real building and see flow instead of equipment. If they can recite the five tasks but can't place them in an actual facility, the lesson hasn't landed. Don't lecture the five tasks off a slide. Build a warehouse on the board with the room and make them put a real product through it.
| Segment | Min | What happens |
|---|---|---|
| Open at the dock door | 5 | Read the hook aloud. Put the one idea on the board: a warehouse is a machine for managing the gap between goods in and goods out. Ask the room why those two flows never line up. Let them get to vendor schedule versus customer schedule on their own. |
| The five tasks | 9 | Draw them out: receipt, internal transport, storage, order prep and consolidation, dispatch. Show the flow diagram. Stress the information line running back underneath, and that systems like a WMS live there but do not get taught until Part V. Today you name them, you don't design them. |
| Draw the warehouse | 12 | Key teaching moment, below. Build a real facility on the whiteboard from the class's own calls. This is the center of the lesson. Do not skip it to save time. |
| Flow types and the 3W | 12 | Simple, medium, complex, with a real example of each. Then run the Three W's guessing game on flow classification before you reveal the card. Land the rule: name the flow before you name any equipment. |
| ABC rotation | 7 | A, B, C by how often product moves. Work the 80/20 case: top 20 SKUs at 80 percent of picks. Ask what that changes about the site walk. This is the Pro Tip made concrete. |
| Verticals and environments | 5 | Same five tasks, different worlds. Vertical sets the order profile; environment sets the physical constraints. Keep it light. Environments get their real treatment in Lesson 17. Today they just learn to notice and flag food, freezer, and washdown. |
| Riverside and close | 10 | Read Dana's operational picture. Run the classification debate below. Collect each student's flow call and the justification. Grade the reasoning, not the label. |
| Total | 60 | Baseline session. Expand with the stretch options below if you have 90 minutes. |
Go to the whiteboard with nothing drawn. Ask the room to name a warehouse they've all seen: a grocery distribution center, a parcel hub, an auto parts depot. Pick one. Then build it on the board entirely from their calls. Where does the truck back in? Draw the dock. Where does product go first? Where does it wait? Where do orders get put together? Where does it leave? You are the pen. They are the operation.
As the drawing fills in, label each piece with one of the five tasks. The goal is for the room to watch an abstract list become a real building in front of them. When it's done, put one product on the board, a single carton, and walk it through the whole thing out loud with the class. That walk is the lesson. A student who has drawn one warehouse and pushed one carton through it will never again see the five tasks as a list to memorize.
The failure mode this lesson is built to prevent is a student who memorizes the five tasks as vocabulary and never maps them to a real floor. Watch for it and drive them back to the board. Signs:
Before you show the 3W card, put the concept on the board by itself: classifying an operation's flow type. Ask the room to guess the three W's for it. Why does naming the flow type matter? When does an engineer do it? Where does it sit in the workflow relative to picking equipment?
Take every answer, right and wrong, and write them up. Only then reveal the card. The reveal lands hardest on a mind that has already committed to a guess. The one you're steering toward is the NOT WHEN: don't classify from the org chart, classify from the material path. If a student guessed that flow type follows from company size, you have the perfect live example to correct, and that correction is worth more than the card.
Read Dana's operational picture aloud, then give the room a few quiet minutes to classify Riverside's flow: simple, medium, or complex. Have them commit to one and write two sentences of justification before anyone speaks. Then open the floor.
Expect a split, and that is the point. There is a strong case for medium: two pick zones, pick-to-light, cartons assembled into orders and consolidated at staging. There is also a defensible case for leaning complex, given two separated zones on two floors, multiple client rulesets, and manual carrier sortation at the dock. Do not settle it for them. A student who says medium and justifies it from the picking-and-consolidation path is right. A student who says complex and justifies it from the multi-zone, multi-client reality is also right. A student who picks either one because Riverside is a 3PL and 3PLs sound complicated has not done the work. The label is not the grade. The justification is the grade. Make that explicit before they hand anything in.
Keep reinforcing the project-note habit from Lesson 1. The Riverside strip asks each student to write their flow call and justification into the same running Riverside note they started last session. Every time Riverside comes up, remind them to date the entry and keep it organized. Frame it as simply what professional engineers do.
Don't explain where the habit leads. The payoff is theirs to find later, and it lands hardest for the students who kept their notes without being told why. Your only job is to make the habit feel normal from the second lesson on.