Manufacturing Leadership Is More Than Checking the Box

Manufacturing organizations are exceptionally good at checking boxes, especially when it comes to shop-floor data collection. The pattern is familiar:

Pick the vendor. Check!

Install the system. Check!

Train the users. Check!

Fire up the displays. Check!

Run the reports. Check!

Each step gets completed, each milestone gets checked off, and then everyone waits for performance gains that somehow never materialize.

Somewhere along the way, implementing shop-floor data became synonymous with improving performance — as if visibility alone creates productivity, or collecting data automatically translates into better manufacturing leadership. It doesn’t.

Data systems can provide clarity, but they cannot create alignment, urgency, accountability, or operational discipline on their own. Those are manufacturing leadership functions, and when they’re missing, even the most sophisticated platform becomes little more than an expensive observer.

Manufacturing Leadership Drives Results — Not Dashboards

In plants that consistently hit performance targets, the differentiator is rarely better dashboards or more KPIs. It’s manufacturing leadership teams that know how to use the data to focus attention, align teams, and convert recurring issues into shared priorities.

That capability is becoming rarer. Many organizations have invested heavily in shop-floor data systems but never developed the manufacturing leadership skills needed to extract real value from them. Supervisors remain buried in daily firefighting, the same issues reappear shift after shift, and although problems surface faster, they still don’t get solved. The gap between expectations and execution stays exactly where it was.

Sometimes data use even backfires. Instead of creating clarity, it fuels defensiveness. Instead of supporting problem-solving, it becomes a tool for explaining variances after the fact. Having visibility through data often creates the expectation that “somebody” will do “something” to address the issues impacting performance. When that does not happen, trust erodes quickly, and once trust is damaged, more data rarely fixes it.

This isn’t a technology failure. It’s a manufacturing leadership capability gap.

Visibility Creates Opportunity — Manufacturing Leadership Creates Value

Most shop-floor systems don’t fail because the technology is flawed. They fall short because organizations mistake visibility for capability. Data can highlight opportunities, but manufacturing leadership is what turns those insights into action.

Using data well means asking better questions rather than demanding better numbers. It means helping people understand the story behind the metrics so they see why performance matters, creating a shared source of truth instead of competing narratives, and focusing attention on the few drivers that genuinely improve outcomes. Those are practical manufacturing leadership skills, not technical ones, and they don’t emerge automatically when a system goes live.

If productivity improvement is the goal, the question can’t simply be, “Do we have the data?” It has to be, “How is this data changing how we lead?” Installing systems is relatively straightforward. Training users is necessary. Changing how manufacturing leadership teams think, decide, and act is harder — but that’s where the real gains come from.

Until organizations close that gap, “checking the box” will remain one of the most expensive habits in manufacturing. That manufacturing leadership gap sits squarely at the heart of They Just Don’t Get It.

Connected Workforce Manufacturing Needs Structure, Not Noise

Over the last few years, connected workforce has become a popular promise in manufacturing software. The idea is straightforward: give operators a way to message, post photos, and share updates in real time, and collaboration will improve. Problems will surface faster. Decisions will happen sooner.

That’s the theory.

What often happens on the shop floor looks different.

More communication doesn’t automatically improve execution. In many plants, it creates a new layer of noise—activity without direction, visibility without ownership. Messages increase, but clarity doesn’t. People stay busy, but the same issues keep coming back.

Most connected workforce tools are built on a social model. Open posts. Free-form comments. Constant interaction. That model works when the goal is conversation. Manufacturing doesn’t run on conversation. It runs on priorities, constraints, and follow-through.

When communication isn’t structured, a few predictable things happen. Important signals get buried in volume. Problems get reported faster, but they don’t land with clear responsibility. Supervisors spend more time sorting messages than fixing problems. Leaders inherit more information, but less certainty about what actually needs to change.

The organization feels more “connected,” but execution gets harder.

From a Lean perspective, this is a problem. Lean depends on standard work and disciplined problem-solving. Ad-hoc communication cuts around those systems. Instead of reinforcing process, it bypasses it. Instead of helping teams learn, it creates running commentary. Root causes get replaced with opinions. Priorities blur. Attention scatters.

That isn’t improvement. It’s entropy.

None of this means operator input isn’t valuable. It is. Operators see things long before dashboards do. The mistake is assuming that giving people more ways to talk automatically turns insight into action.

It doesn’t.

When voice isn’t tied to a system, the burden shifts downstream. Supervisors chase context. Managers interpret intent. Leaders absorb noise. What looks like empowerment often becomes another form of waste—one more thing that relies on heroic effort to manage.

This is why we take a different position at Flex. We believe the most important connection, and the one that ultimately unifies an operation, is the connection between people and process. Communication should support execution, not compete with it. Operator input should function as operational signal—structured, contextual, and actionable—not as conversation.

When voice is handled this way, it does real work. It clarifies priorities. It reinforces discipline. It creates follow-through instead of accumulation.

That’s the difference in focus. Connected workforce platforms optimize for more communication. Flex optimizes for better execution. Where others increase volume, we work to increase signal. Where others surface issues, we work to ensure ownership. Where others create activity, we focus on building capability.

As we continue developing the Voice of the Operator, we’re being intentional about how it works—not just what it captures. The goal isn’t to make it easier to talk. It’s to make it easier to provide useful context, and harder to create noise. Because the way people are asked to communicate shapes how they think, how leaders respond, and whether insight actually turns into improvement.

Why Manufacturing Data Analytics Initiatives Fail

My professional career has exposed me to a wide range of data-driven initiatives.

Prior to graduating from college, I had the pleasure of working as an engineering co-op student. I spent a summer working at the Naval Research Center in Bethesda, Maryland collecting sonar data on nuclear submarine runs.

This was the summer that Tom Clancy’s “Hunt for Red October” mega-best seller came out. I was thrilled to spend time on the USS Dallas, the submarine in the story that was showcased in the movie with Sean Connery as her captain.

My co-op job was working with a team of engineers to collect sonar data that allowed the Navy to ping the ocean and utilize advanced algorithms to identify sea vessels in the surrounding water based on their unique data “signature.”

The US Department of Defense paid significant amounts of money for teams of engineers and technicians to collect reams of data to create the visibility needed to accurately detect and respond to a range of potential threats at sea.

My first job after college was working as a fiber optics engineer. One project was to collect data from a strain gauge within a rotating shaft via optical transmission. There was valuable mechanical stress data that our customer needed for their product design team to leverage for higher reliability.

Magnetic Bearings Inc. (MBI) was perhaps the most advanced technology company I worked for during my career as an engineer. MBI developed electromagnetic bearings to levitate high-speed (15,000 RPM) rotors in turbines for applications such as pumps for natural gas pipelines.

There was a tremendous amount of detailed vibrational data collected at MBI through microcontrollers. This data was used to “tune” the bearing dynamically using algorithms that enabled machines to reach higher speeds than traditional oil bearings. Without a reliable feedback loop of highly accurate data collection, the magnetic bearing system would fail – sometimes catastrophically.

Close-up of a Flex-Metrics Direct Machine Interface (DMI) module with wired sensor connections for real-time manufacturing data collection and machine monitoring.

I have now spent the past 20+ years collecting data within manufacturing plants using a Direct Machine Interface [DMI] technology, like a Fitbit that attaches to manufacturing equipment. I’ve been deeply involved in developing data collection systems for production equipment ranging from printing presses to bottle fill lines to automotive assembly robots.

As a result of these career experiences, I can’t help but notice automated data collection systems that appear to be spreading at an exponential pace. For example, I was recently at a fast-food restaurant and noticed they had invested in a real-time data collection system for their drive-through lane to count cars and highlight current and average wait times at the window.

Even fast food has data automation and KPIs

Why do businesses spend various degrees of money on these types of data collection systems? As usual, it depends on what they seek to achieve, such as:

• Real-time Visibility: Typically, stand-alone monitoring solutions. Provide a better “line of sight” to build a culture of ownership and accountability. Minimal change-management skills are required.

• Process Improvements: These data systems require organizational change agents and sophisticated data users to generate a payback. Data-driven changes are typically focused on the process, product designs, or capital equipment. Requires highly trained decision-makers and disciplined internal processes to implement and sustain changes. A wide range of potential changes in human behavior may be required to realize a positive return on investment.

• Automated Process Optimization: Historically, such data collection systems are coupled with advanced technology and capital equipment. Improved accuracy and timeliness of feedback loops drive optimization algorithms. Ideally self-optimizing systems based upon well-tuned feedback loops have minimal dependency on human behavior. Examples include automated count control and speed optimization algorithms.

  
  

Given the spectrum of complexity that follows these different levels of manufacturing data analytics systems, it is not surprising that many organizations tend to over-shoot when they realize they have fallen behind the competition when it comes to building a culture of data-driven decisions

Fast-food drive-through monitoring screen displaying real-time service time metrics and operational performance data.

Like the display at the fast-food drive-through, it’s hard to go wrong with a simple, real-time visibility solution. High performers like to keep score. Presenting accurate, real-time data in an intuitive format makes it easier for everyone to “stay in the game”. Real-time visibility enables practically anyone to be more productive immediately when there’s a line of sight on current performance results.

Flex-Metrics Shift Score Card from the Equipment Portal. **queue oohs and ahs**

Collecting data to make design changes to a product or process requires an entirely different level of data users’ skills over a longer time frame. This is the classic example of engineering, which is to apply math and science to make changes to create a Future State that is tangibly better than the Current State.

In the business of software development, there is a concept called a Maturity Model that explains how some software firms reach a Level 4 Maturity by following a proven process to release high-quality code that just works. Unfortunately, there are far more software businesses stuck at Level 0 “Ad-hoc” Maturity that brute force results every day. A key concept in the Maturity Model is that it’s impossible to jump levels.

I’ve seen the same concept play out with manufacturing sites that want to go from no data collection to full-blown Kaizen black belts in a single initiative. Instead, I would strongly advise starting slow and simple, then moving fast based upon “quick wins”. Walk before you run!

If your manufacturing site is not currently utilizing real-time visual factory displays on the shop floor, that is one of the easiest ways to start on the journey toward a data-driven culture of Operational Excellence. Once a team gets a taste of trustworthy data that makes it easier to win, with less stress, going to the next level of data maturity comes much more naturally.