Part III. Lesson 8. Flow Before Equipment.
Sit a new engineer down with a floor plan and a project brief and watch what happens. They see a dock door and think induction belt. They see open floor and start drawing conveyor runs. They see the pack stations and route a takeaway toward them. Piece by piece the drawing fills in. By the time they're done they've got a layout.
What they don't have is a design.
Equipment arranged on a floor plan. It accounts for the machines that came to mind and fits them into whatever space is open. It starts from the hardware.
The controlled, logical movement of material through a building, worked out before any machine gets a name. It starts from the flow.
Same building, same products, two completely different starting points, and the starting point decides everything after it.
Equipment-first thinking produces a design that runs fine while the building is calm. But systems get stressed. Waves release, volume surges, a downstream station slows and the queue backs up behind it.
A design built around the flow handles stress because the flow accounted for it. A layout built around equipment handles the equipment, and discovers the stress after go-live.
If the flow is wrong, so is every layout built on top of it, and no equipment corrects a flow problem after the fact.
Each block is a process step or a functional area. Each arrow is a movement of material. Where the flow splits, the diagram branches. Where it combines, it merges. Where a decision gets made, you mark a decision point.
The test for whether it's finished is plain: can you read it out loud, start to finish, as a coherent story with no gaps? A transition you can't explain is a gap that becomes a problem in the layout.
Cases to the dock. The flow everyone draws first.
Bulk to pick face. Leave it off and its volume never gets evaluated.
Volume, rate, and package condition understood and drawn before any decision.
A defined path to a staffed station, and a defined path back into the flow.
Draw each independently first. Combine later only if it earns its place. Undoing a flow you combined before you understood it costs far more.
Treating replenishment and returns as footnotes to the outbound flow. It feels efficient. Everything's moving the same direction anyway. But each one has its own volume, its own timing, its own package condition, and when they share the outbound path without being designed for it, they create conflicts you can't resolve without a redesign. Draw them separately from the start. Combine later, if it earns its place.
A safe assumption is one where being wrong is easy and cheap to fix. An unsafe assumption is one where being wrong forces a redesign. Peak volume projections are unsafe. Product dimensions handed over by the customer are unsafe.
Label every assumption by type, right on the diagram, the moment it appears. Then verify the unsafe ones in writing with the customer before the design goes any further.
"You are not a cart. You are a carton. You just got picked on the second floor. You are in a corrugated box. You weigh 12 pounds. You are 13 inches long, 9 inches wide, and 3 inches tall. How do you get from the second floor pick shelf to Dock Door 1 on the south wall?"
Trace that journey. Every transition, every wait, every direction change, before you draw a single line. Then produce the Layer 1 process flow diagram: both zones as separate starts, the merge, the sort decision, three doors. Blocks and arrows only.
Next, Lesson 9: How does a flow diagram grow into the design map?