You're in a conference room at Riverside Distribution Co. Dana met you at the door and walked you in. Three people are already seated. You came to read this operation, and while you do, every person here is reading you. Listen to how they introduce themselves. Each one is telling you what they care about and what will sink your project if you miss it.
"Thank you for coming. Let me introduce the team. Tom Ruiz is our VP of Finance. He will be involved in any capital decisions. Ray from our IT department is here because I have a feeling this project is going to touch some systems and I want him in the room early. And this is Michael Collins, our facilities and maintenance lead. Michael has been in this building longer than anyone. If it moves or makes noise in this facility, Michael knows about it."
"Here is the short version of our problem. We ship for five retail clients. Apparel, housewares, and packaged food products. All outbound sorting is done manually right now. Our associates are making carrier decisions by hand at the staging area near the dock. We are running a misdirect rate of about three percent. Two of our five clients have issued chargebacks. During peak wave releases the staging area becomes a complete bottleneck. I need that to stop."
"I will be brief. If this project does not make financial sense I cannot support it regardless of the operational benefit. I will need to understand the return before we go any further. Dana can give you the operational picture. I will answer questions about the financial side when you are ready for that conversation."
"We have had equipment in here before. Twice. Neither one of them made it past the first year running the way it was supposed to. I am not against trying again. I just want to make sure somebody actually thinks about how this thing gets maintained and not just how it gets installed."
"I am honestly not sure why I am here yet but Dana said to come so I came. We run a WMS. I manage it. If you need to talk to our systems at some point I am the person you need."
Nobody has shown you the floor yet, and the meeting has already handed you the project. Tom led with money, so whatever you design has to pencil out or it never gets built. Ray isn't sure why he's in the room, which tells you the systems side has been an afterthought here. Dana used one word you should have flinched at: manually. And the maintenance lead, Michael Collins (same name as the man teaching you this course, no relation, good name), said nothing until you made eye contact, then told you two systems have already died on this floor. That's the room reading you back.
By the end of this lesson you can walk into a facility you have never seen and read it before anyone speaks: name where the labor and the pain concentrate, tell a maintained system from an abandoned one, and turn a powered-off conveyor into the one conversation worth having.
Now Dana walks you through the building, and Michael comes along without being asked. That tells you the maintenance lead doesn't trust what happened here last time. Before you ask a single question, start reading, because the operation is already talking. Look first at the manual processes and how many people each one takes. That's where the labor cost sits and where automation has the clearest case. Then look at where people cluster, where product sits idle, and where the floor is worn. A worn path is a vote. It shows you how the space is actually used, not how the drawing says it should be.
The first thing I look at is manual processes. How many people does it take to get that task done? That tells you immediately where the labor cost is concentrated and where automation has the clearest case. I talk to full-time employees whenever I can, because they live the current process every day. They know exactly where it breaks down.
Here's what the walk shows you at Riverside. You start at the dock doors on the south wall. Three doors, two with trailers backed in, one empty. The staging area in front of them is crowded with carts and loose cartons. Two associates are working it, moving fast. And there's a carton sitting in the wrong lane. Neither associate has noticed.
Two associates are moving as fast as they can, a carton is sitting in the wrong lane, and neither of them has caught it. Before you read another word, write down what that one carton tells you. Not what to do about it. What it tells you about the operation, right now, before anyone has quoted a single machine.
Keep walking. North into Zone B, ground floor, pick-to-light shelving. It's orderly. Picks come off the shelves into cartons, cartons go onto carts, and a full cart gets wheeled south toward staging. Then northwest, up the stairs to the mezzanine. Zone A is on the second floor, sixteen feet up, apparel and housewares, the same pick-to-light setup. But these carts have to come back downstairs before they can reach staging. Stand at the mezzanine edge and look down, and the shape of the problem is right there in the building.
"That mezzanine edge is going to be your challenge. Whatever comes down from up here has to land somewhere before it can go south. You have got about 40 feet of horizontal run from the mezzanine edge to where the ground floor zone ends. After that you are in the main aisle. Forklifts run that aisle all shift."
"We had two near misses last year. Carts coming down from upstairs crossing paths with a forklift in the main aisle. Nothing happened but it was close."
He looks at you.
"If you put conveyor across that aisle you need to think about how a forklift gets through."
A customer who already has automation just handed you the truest thing in the building. Start by looking, not asking. Is it running, or worked around? Clean, or wearing a hand-lettered out-of-order sign? The physical state of a machine tells you more than any interview can.
The Total Guide to Warehouse Automation makes the point plainly: more than 80 percent of warehouses are still using the same manual processes they started with. So an abandoned system isn't a lazy operation. It's a customer who tried something, got let down, and went back to doing it by hand. That's not a lost cause. That's where the real conversation starts. Before you propose anything new, you have five questions to ask about what's already there.
Then ask the one that matters most: if you were starting fresh today, would you install the same system again? That answer tells you whether you're building on a foundation the customer trusts or replacing something that left them with scars. Know which before you draw anything.
If you see a conveyor sitting powered off, then ask its story before you propose anything at all. Tradeoff: it costs you an awkward minute, standing in front of a machine nobody in the building wants to talk about. Verify: their answer tells you exactly what killed it. A compressor nobody could service, a line that stopped the whole building every time one zone jammed, a vendor who came out twice and never again. That story is the most useful thing you'll hear all day, and it's the one thing a spec sheet can never give you.
Step back from the equipment and read the building as a whole, because every warehouse has a personality and it's a design input, not a mood. A clean, well-maintained facility with trained operators is telling you the customer will maintain what you design for them. A chaotic facility is telling you the opposite: the solution you leave behind has to be simpler and more maintainable than whatever they run now, or it joins the pile of things that got installed and abandoned. Riverside is split, calm pick zones and a chaotic sort, and the chaos sits on the exact task Dana wants fixed.
You'll hear two versions of how this operation runs. The manager gives you the designed process, the way it works on a good day. The operator gives you the real one, what happens during a wave release when two zones pull at once and there's no time to scan. They rarely match, and the gap between them is usually where your project lives. New engineers hold questions back because they're afraid of looking uninformed, and the question you were too proud to ask is the one that sinks the project six months later. A customer will answer a hundred honest questions from someone who wants to understand their operation. Ask the operator directly what they think of the system, and they'll tell you the truth faster than any org chart.
You already learned to think like the package. Now add the person. Somewhere inside the system you design, at two in the morning on the worst night of the year, one associate is standing in front of a jam with a truck waiting at the dock. Can that one person clear it alone, or does your elegant design need two people and a call to a vendor who won't answer? Michael's one maintenance guy is who you're really designing for. If he can't keep it running, it doesn't matter how well it ran on paper.
Facility readout, Riverside. Here's what the operation told you before anyone quoted a machine.
Stated ask. Dana wants a system that reads a barcode and routes each carton to the right dock door. That's the sentence she gave you. It's not the whole job.
Observed problem. A manual carrier sort at the dock with no scan to back it up. You watched a carton sit in the wrong lane and nobody catch it. The three percent misdirect rate isn't a slide, it's happening in front of you.
Existing automation and its story. Two systems have already died on this floor, neither one making it past the first year, and nobody in the room defended them. Whatever goes in next is the third attempt, and everyone knows it.
Maintenance reality. The team is one. Whatever goes in has to survive a crew of one. Design for Michael, not for the brochure.
Building constraints. The building fights you at the mezzanine. Sixteen feet up, about forty feet of run to a forklift aisle that runs all shift, and two near misses there last year.
Personality and appetite. Split. Calm pick zones, chaos at the sort, which is exactly the task Dana wants fixed. The operation and the customer agree on where it hurts.
Start the facility readout page in your Riverside note. Write what this operation is telling you and what it has already told you it won't tolerate. Date it, and keep it where you can find it. Every decision you make later answers back to this page.
This is Lesson 3 of thirty-five, and it's the one that runs entirely on judgment. No calculator, no conveyor spec, no drawing. Just you, reading a building before anyone tells you what to think about it. Everything that follows takes its input from this read: get it right and the rest feels nearly obvious, because you already understand the problem you're solving. Rush it, and you spend the project retrofitting your design to a reality you never saw. The operation is always talking. Your job starts with whether you were listening before anyone spoke.