The Free Productivity You Walk Past Every Day

Show Notes

Not every productivity gain needs a capital request. In this episode of Handled It, Joe Perkins and Brent Hillabrand sit down with Dan Grupp and Ashley Watkins to talk about the low-hanging fruit, the low-cost, low-drama changes that can move output right away, before anyone signs off on another hire, a new system, or a robot. If your instinct when the numbers slip is to add people or add technology, this conversation makes the case that you should walk your floor first.

The group gets practical fast: shortening default Outlook and Teams meetings, cutting unnecessary standups, reducing wasted walking, relocating supplies, and re-slotting SKUs that clearly aren't where they belong. A dusty box sitting in a prime pick zone might look insignificant, but it can be a signal that your slotting strategy hasn't been questioned in years. From there, the conversation gets into a bigger problem: leaders often confuse "busy" with productive, become blind to waste that's hiding in plain sight, and fail to reanalyze processes that operators already know are broken. Dan and Ashley explain why the people closest to the work often have the best ideas, why incentive structures can keep them from speaking up, and how simple disciplines like Gemba walks and repeatedly asking "why" can uncover improvements without spending a dollar on automation.

In this episode, you will learn:

- Why your cheapest productivity gains may already be hiding on the warehouse floor

- How meetings, standups, walking paths, and supply placement quietly eat into output

- Why dust on a box can tell you your slotting strategy needs another look

- How leaders become "waste blind" and start confusing activity with productivity

- Why operators often see the problem first — and what keeps them from speaking up

- How morale, absenteeism, turnover, lighting, and temperature affect measurable performance

- Why Gemba walks and root-cause thinking should come before expensive automation

Before you buy another machine or post another job opening, look at the work that's already happening. The biggest productivity gains may come from removing the friction, wasted motion, and outdated habits your team has learned to work around every day.

Timestamps

00:00 Why Do Warehouse Leaders Walk Past Free Productivity Gains?

01:40 What's the Cheapest Productivity Win in a Warehouse?

03:53 Why Is Slotting the Most Underdone Fix in a Facility?

07:57 Does Employee Morale Really Affect Warehouse Productivity?

13:40 What's the Difference Between a Low-Cost Fix and a Costly Shortcut?

16:42 How Do You Find the Root Cause of a Warehouse Problem?

23:24 What Is a Gemba Walk and How Does It Improve Productivity?

26:47 Do You Need Automation, or Just a Line Rebalance? (Case Study)

30:32 How Much Does Heat Reduce Warehouse Productivity?

34:36 Hot Takes: Slotting, Morale, and Busywork vs. Real Productivity 

Transcript

Many warehouse leaders look for more headcount or new equipment when throughput falls short. Yet recoverable productivity may already be sitting in the operation: an inefficient pick path, a poorly placed printer, an overlong meeting or a bottleneck that has become routine.

In this episode of Handled It, Carolina Handling COO Joe Perkins and CEO Brent Hillabrand speak with Ashley and solutions architect Dan Grupp about finding those opportunities. Their starting point is simple: observe the work, listen to the people doing it and understand the problem before choosing a solution.

Busy Does Not Always Mean Productive

An associate crossing the warehouse all day looks busy. An operator waiting briefly for a part from a vertical lift module may look idle. But the automated part can arrive faster than the associate would have retrieved it on foot. Movement is visible; useful output is what matters.

The same distinction applies to daily routines. A stand-up meeting can help a team coordinate work, but it can also repeat the same discussion several times per shift without producing a decision. Shortening a meeting or reducing its frequency gives time back when the content no longer justifies it. Leaders should ask what is discussed, whether the data is accurate and whether the people in the room can act on it.

Slotting Can Reveal a Low-Cost Win

Slotting is an example of a fix that can be missed while a facility considers a larger investment. Fast-moving products should be positioned to reduce travel. When boxes near the front of a warehouse are covered in dust, that valuable space may be occupied by inventory that rarely moves.

A better location for a product, tool or workstation can remove repeated steps from every shift. Joe recalls moving a label printer from the opposite side of a pick route to where associates finished their work. The change reduced travel without adding equipment.

Finding the time to study slotting is difficult when a team is focused on getting orders out the door. A brief pause to analyze the flow, however, can expose work the facility has been paying for every day. The issue can also begin upstream with planning or ordering, so moving a SKU should follow an understanding of why it is in the wrong place.

Ask the People Who Do the Work

Supervisors may expect associates to report inefficient routines. Associates may simply adapt and keep working, particularly when time away from picking affects a productivity measure or their pay. A picker walking an extra 30 feet may never describe that walk as a problem unless someone asks.

The people executing a process often understand its constraints best. Leaders can ask what frustrates them, what takes too long and what makes the job harder than it needs to be. They also need to make room for those answers and give teams a way to help test changes.

Dan describes a customer who requested another conveyor on an automated line. After observing the process and speaking with the operator in Spanish, he found that her station had lost one of its two packing machines while the incoming pace remained the same. Rebalancing the line addressed the bottleneck more directly than adding another conveyor.

The example shows why the first request is not always the real problem. Asking why a customer prefers a particular control system, for instance, may reveal that the underlying concern is the team's ability to support it. A useful solution begins with the cause, not the most visible symptom.

Design Around the Actual Operator

An efficient layout on paper may be inefficient or unsafe for the people using it. Ashley describes pick locations that seemed accessible to a six-foot designer but required shorter associates to use a grabber repeatedly. A supposed high-value pick zone was not functioning that way for the team working there.

Different heights, languages and experiences reveal details that a single viewpoint can miss. Bring the operators into layout and process decisions, and observe how the work is actually performed before setting a standard.

Morale Has Operational Consequences

Morale can sound intangible until it appears in turnover, absenteeism and a lack of engagement. Replacing and training associates consumes time and money; understaffed shifts affect output. When people repeatedly say they do not have what they need to complete the work, they may be describing a flow problem as well as frustration.

The physical environment matters, too. Heat, lighting and access to water can affect how associates experience a shift. Moving drinking water closer to the work, for example, can reduce unnecessary travel while making it easier for people to stay hydrated. Those conditions deserve attention alongside labor and equipment metrics.

The discussion also considers how heat may affect attention, accuracy and safety. Rather than assume a particular percentage of loss in every facility, leaders can examine their own temperature, error and output patterns and put a value on the changes they observe.

A Cheap Fix Must Solve the Right Problem

The lowest upfront cost is not always the lowest long-term cost. Dan notes that a new building designed without adequate insulation may be expensive to improve later. Joe offers a similar lesson from technician bays beneath a crane path: when the space became hot, adding overhead fans was not straightforward.

Other fixes merely move the constraint. Adding headcount to one step might push the backlog into the next team. A local cost reduction can hide a larger cost elsewhere. Evaluate the entire flow and ask whether a change increases useful output or only shifts where the delay appears.

Make Floor Observation a Habit

Ashley recommends a gemba walk: go to the place where the work happens and follow the flow of product and people. Look for repeated travel, waiting, awkward reaches, extra handoffs and tasks that interrupt the main job. If the problem is not visible, ask associates what consumes time each day.

One walk will not finish the job. Product lines, customer requirements and technology change. A process that worked well years ago may now create waste, so leaders need to revisit it and give people a continuing way to suggest improvements.

Small wins also need to be measured and shared. Moving one item to a better location can be a useful starting experiment. Track the travel or time it saves, then use that evidence to decide what to change next. Celebrating these gains helps leadership see the value of work that does not arrive with a large capital request.

Final Takeaway

Before buying a machine or adding a shift, spend time where the work is done. Follow the product, question repeated steps and listen to the associates who live with the process every day.

The best productivity opportunity may be a better slot, a shorter meeting, a rebalanced line or an easier way to do the job. Identify the constraint, measure the effect of the change and keep looking as the operation evolves.