Lessons from the Floor: Change Is Hard. Most Leaders Make It Harder.

A warehouse floor never sits still. Volume shifts, seasons turn, demand spikes, and people get moved to where the work is — sometimes daily, sometimes by the hour. The layout you set in the morning isn't the layout you're running by two o'clock. That's not a sign something's broken. That's the job.

But most employees dread the change anyway. Not because they can't adapt — floor people adapt constantly, it's half of what makes them good — but because change usually arrives as a command. Move here. Do this now. No reason given. The associate gets pulled off a pick lane they'd settled into, dropped somewhere new, and told to make rate by the end of the hour. Nobody explained why. Nobody's going to.

That's where leaders lose them. Not in the move itself — in the way the move landed.

Here's what forty years on the floor teaches you: people don't resist change nearly as much as they resist being changed at. The exact same move they'd fight when it's barked across the floor, they'll run toward when they understand it. The reassignment doesn't change. What changes is whether the person doing it feels like a chess piece or a teammate.

Three things make the difference, and none of them are complicated. None of them cost money. None of them slow the operation down — they speed it up, because a team that understands the play runs it faster than a team that's just following orders.

The first is the why — the real one. Not the corporate why. Not "we're optimizing labor allocation." The real one. The order that has to ship tonight. The truck backed into the dock with the driver's clock running. The customer on the other end who's waiting on something they already paid for. Operators live in a world of concrete things — cartons, pallets, cutoff times — and the reason for a move has to be just as concrete. Give them the abstract version and they'll nod and move slow. Give them the truck that's waiting and they'll move like it's theirs.

The second is listening. When someone pushes back on a change, the instinct is to hear resistance. Usually it's not. Usually it's information. The fear is specific — "I've never run this line and I don't want to tank the numbers," or "the last time we did this, replenishment couldn't keep up and we all got blamed." That's not someone refusing to adapt. That's someone telling you exactly where the plan is going to break, if you stop long enough to hear it. The best operators I've worked with treated pushback as a free diagnostic. It told them what to fix before it cost them a shift.

The third is bringing them into it. People defend what they help build. Hand a crew a finished plan and they'll comply with it. Hand them the problem — "here's the gridlock, here's the cutoff, how do we get there" — and something changes. Now it's theirs. Now they're not resisting your solution, because it stopped being your solution the moment they had a hand in it. The move you were going to mandate anyway gets executed better, because the people running it own it.

Change on a warehouse floor is constant. It's not the enemy. The enemy is change delivered as a decree — no reason, no ear, no ownership. Strip those three failures out and the same disruptive move becomes something a team will carry themselves.

The floor was always going to change. The only question is whether the people on it are changing with you or being changed at.