The Executive Illusion: Boardroom vs. Shop Floor

(Part 4 of 5 of the series “The Human Code of ERP”)

There’s a whiplash unique to this job. If you have been involved in an ERP implementation, you know exactly what I mean: the feeling of moving between two completely different dimensions on the exact same day.

It is 9:00 AM, and you are sitting in a quiet, spotless boardroom. The CEO and CFO are leaning over a shiny conference table, throwing around “digital transformation” and “seamless automation” like confetti. They have just committed a huge part of their budget to this project, and you can see the hopeful relief in their eyes. To them, this system is a promise: flawless operations, instant speed, infinite profit. Starting Monday.

In the afternoon, you walk down to the warehouse. It is loud. The Wi-Fi probably drops every ten meters. A tired operator in heavy work gloves stares at the barcode scanner you just handed him. He doesn’t speak for a moment. Then: “Five clicks to move one pallet? Tell the trucks to take their sweet time. This shipment will be ready when hell freezes over.”

Welcome to the Executive Illusion.

The Two Realities

The biggest trap in our job is forgetting that an ERP project is essentially two different projects happening at the same time.

The Executive Board bought a vision. They bought control, visibility, and data. They want to know exactly how much a specific production order costs down to the last cent. To get that data, they often design processes that require operators to report every single micro-activity into the system.

The Shop Floor, on the other hand, deals with physics. They deal with delayed suppliers, broken machines, and the pressure of getting things out the door before the shift ends. For those working in the warehouse, the ERP often feels like an endless obstacle course. It acts as a massive daily hurdle, an extra screen and a heavy layer of digital friction added to an already exhausting shift.

Listen only to the board, and you’ll design an elegant disaster. A system so complex that operators will hate it, boycott it, or feed it with fake data just to bypass the controls. Listen only to the shop floor, and you’ll build a fast system that gives the executives exactly nothing of what they paid for.

As a Business consultant, you are caught right in the middle. Funny, eh?

The Art of the Pushback

Most consultants take the easy way out. When a manager asks for a highly complex reporting step, the consultant just nods, configures the system, and forces it upon the workers. Then, when the workers complain, the consultant hides behind the classic excuse: “Management requested it.”

This approach breeds resentment. It poisons every single Go-Live.

A good consultant has the courage to challenge the Executive Illusion. When a director asks for a process that will paralyze the shop floor, you need to step up. You must find a way to politely say: “I get why you need this data. But asking a driver to take off his gloves and type 12 digits on a tablet creates a bottleneck. Let’s find a smarter way.”

You have to protect the people doing the heavy lifting, while still delivering the value the business needs.

Surviving the Crossfire

Bridging this gap without losing your mind, or the client’s trust, requires a different playbook entirely.

Master the Two-Way Translation. Stop handing out instructions. Start sharing context. An operator doesn’t need another barcode to scan. They need to know that barcode shuts up the sales team calling them every hour to ask where the order is. Tell them exactly that: “I know this scan is annoying, but it automatically updates the sales team so they stop ringing you.” Suddenly, the extra click has a personal benefit. It stops being an obstacle and starts being a shield.

But it goes both ways. You must also translate the shop floor’s physical struggles back to management so they understand why a certain procedure needs to be simplified. If the executive only sees a clean dashboard, they will never understand the sweat behind each data point.

Design for the Friday Afternoon Shift. Stop designing for the person in the vendor brochure, the one smiling at a screen with a fresh latte. That person does not exist. Design for the operator on a Friday afternoon, two hours into overtime, a machine screaming behind them and a supervisor screaming in front of them. Keep the interface clean. Keep the clicks minimal. If a process demands perfect focus to work, it fails in the real world.

Force a Reality Check. Sometimes, you need more than words. If there is a massive disconnect between a managerial request and the physical reality, invite the manager to walk the floor with you. Have them stand next to the operator who is actually performing the task.

I have done this multiple times in my career, and it works every single time. When a manager watches a real person sweat, balancing a heavy box with one arm while clicking through a dropdown they designed from a comfortable chair, the data gets a face. The theoretical perfection crumbles. And the Executive Illusion melts.

My Final Take

The most elegant architecture means nothing if the people on the front lines refuse to use it.

At the end of the day, Humans are the engines that generate your data. Make their lives miserable with overly academic processes, and they will find workarounds. They will scan the wrong barcode on purpose. They will copy yesterday’s values into today’s report. And the beautiful executive dashboards will be filled with garbage that no one can trace back to its source.

Your job is to balance the dreams of the boardroom with the reality of the shop floor. Listen to the managers, but always design for the tired operator. When you make the software work for the people, the business results will naturally follow.

Next up: We have designed the system, we have aligned the teams, and now it is time to turn the switch on. We will dive into The Go-Live Hangover

Written by Andrea Guaccio 

May21, 2026