The floor doesn’t fail. The system does.

Early in my career, I worked as a Business Unit Manager for a Fortune 100 company overseeing both internal proprietary molding and external injection molding suppliers. That role gave me access to a wide range of facilities — small job shops, large structured operations, plants running efficiently and plants in visible distress.

Most shared the same structure on paper. Supervisors, process technicians, team leaders, quality managers, operators. First shift fully staffed. Second and third shifts running leaner versions of the same.

What stood out, across nearly every facility, was what didn’t exist beneath that structure. There was very little consistent standard work for how the shift was actually managed. Supervisors were promoted based on availability, tenure, or attendance — not operational capability. Once promoted, they were expected to perform without any framework for what shift leadership actually required.

In practice, a parallel system quietly filled the void. Process technicians ended up making most of the critical decisions around quality and process stability — not by design, but because they were the only ones with enough technical depth to respond in real time.

The result was predictable. Customer returns. Higher-than-expected scrap. Less reliable deliveries. Constant variability between shifts. And a consistent misreading of the cause: the supervisors were not the problem. They were doing their best inside a system that gave them nothing to operate from.

What became undeniable, over time, was a single insight: supervisors influence the majority of day-to-day culture on the floor. Roughly 80% of operational behavior is shaped at the supervisory level.

Which means: if supervisor behavior does not change, floor culture does not change — regardless of what else is invested.

That realization made the direction clear. Not another training program. Not broader leadership education. Not a quarterly classroom session followed by a return to the same floor conditions.

What was needed was an operational system that supports supervisors directly — on the floor, in real time, during the actual shift. A foundational design decision was made early and held throughout:

The intent was not wide coverage of topics. It was deep operational change in one specific place — the supervisory layer, where floor behavior is actually shaped.

The Shift™ was built inside live production environments. Second shift. Third shift. During handoffs. During breakdowns. During the real conditions where operations either stabilize or deteriorate.

What emerged quickly was a pattern that appeared in almost every facility: shift handoffs were almost entirely verbal. Critical information — unstable presses, tooling concerns, scrap trends, process drift — was shared in conversation and lost within hours. There was no written record, no consistent format, no confirmation that the incoming supervisor started the shift informed.

Each shift began from a lower base of knowledge than the last one left. Information decay between shifts was the norm, not the exception.

As observation expanded, another insight emerged:

Operators and supervisors were observing conditions. They simply had no shared framework for determining what those conditions meant — and no written record confirming the observation had occurred.

One more discovery reshaped the design. Early on, the tools were called forms. That created immediate resistance, because forms imply paperwork and compliance. That wasn’t what was being built. These tools were shaping decisions in real time, influencing behavior during the shift.

So the language changed. They became artifacts — operational tools that create visible evidence of how work is being managed. That distinction is not semantic. It changes how supervisors engage with them.

By the final phase of implementation in early sites, something happened that confirmed the design was right. Supervisors started reinforcing the system themselves. They corrected each other. They ran standups without facilitation. The system no longer depended on external enforcement.

That was the shift.

Returning to the agricultural component example — at the start of the program, the scrap problem was understood as a performance issue. The question being asked was: why can’t the operator keep up?

By Week 12, the question had changed entirely. The supervisor was conducting time studies, analyzing work cell layout, reviewing material flow, restructuring task sequencing. The focus had moved from the person to the system.

That shift in perspective — from reaction to analysis, from blame to diagnosis — is what The Shift™ is designed to produce. It doesn’t happen because supervisors are told to think differently. It happens because the artifacts they’ve been using for twelve weeks have built a different relationship with the data.

By Week 12, they’re not reacting to the floor. They’re reading it.

This is for the plant leader who already senses something is off — even when the metrics haven’t fully broken. The operations director who sees supervisors reacting more than leading. The owner who keeps investing in equipment, lean initiatives, and standard work — and still sees inconsistency at the supervisory level.

It’s for the plant where these patterns have become normalized:

If any of that is familiar, the problem is not the supervisors.

The problem is the absence of an operating structure at the supervisory level — a gap so consistent across the industry that most organizations have stopped noticing it.

The Shift™ is a 12-week field-based program built by JAYCE Consulting that installs that structure. Not through classroom training. Through artifacts — operational tools that supervisors use on the floor, every shift, that turn judgment into consistent execution.

By Week 12, the floor runs the same way regardless of who is on shift. The system holds when you’re not watching.