How To Build A High Performance Organization That Lasts
Eleven years ago, my colleague Bill Remy wrote that a high-performance organization is easy to spot and hard to build. He was right on both counts. Walk the floor of one and you can feel it — controlled pace, people who understand the strategy and their piece of it, problems that get solved instead of re-explained every week. He gave leaders five starting points: focus on the critical few goals, plan and execute with discipline, standardize your management processes, measure and report without flinching, and build the muscle to learn and move on.
Every one of those still holds. What’s changed is the clock speed they have to operate at.
In 2015, a plant could run on periodic updates and still be considered well-managed. Today, demand shifts by the week, customer windows compress by the day, and most operators aren’t running one site — they’re running a network. The five fundamentals didn’t get replaced. They got put under pressure most management systems were never built to handle.
Three shifts separate the high-performing organizations still winning at that pace, and all three show up on the P&L, not just the shop floor.
- They treat problems as information, not confessions
Most companies say they want problems surfaced early. Then a shipment slips, and the first question in the room is “who owns this?” Scrap goes up — “who caused it?” A project stalls — “who didn’t deliver?”
People learn fast. Bad news creates attention, attention creates pressure, so problems get softened, explained, or hidden until someone has a fix. The system is training people to manage the message instead of the operation — and every day that takes, the fix gets more expensive.
High-performance organizations ask a different question: not “who caused this,” but “what is the system telling us?” A late shipment, recurring overtime, a supervisor who’s always firefighting — that’s not noise. That’s the plant talking. When leaders treat it that way, bad news starts traveling fast instead of slow, and problems get cheaper to fix because they get caught sooner.
- They use speed to expose waste, not to work faster
When executives hear “cut the cycle time in half,” they usually hear “push people harder.” That’s rarely the real opportunity. Ask an organization to compress how long something takes to deliver, and the waiting, the queues, the approvals, the handoffs, the rework — all of it becomes visible. Very little of the elapsed time in most processes is actually value-creating. Cost tells you how much a process is bleeding. Time tells you where and why.
A six-week process with three days of real work in it isn’t a labor problem. It’s a flow problem — and flow problems cross departmental lines, which is exactly why the department-level metrics on most scorecards never catch them. The right executive question isn’t “how do we make each step more efficient.” It’s “why does this take so long.” Speed doesn’t create the friction. It just makes it impossible to keep hiding.
- They manage flow, not utilization
The most persistent bad habit in operations leadership is treating high utilization as high productivity. Keep every machine and every person busy, and what you get is more work-in-process, longer queues, more expediting, more overtime — and missed customer commitments, because everyone was busy and nothing was flowing.
Activity is local. Flow is enterprise-wide. Customers don’t care whether one department hit 95% utilization. They care whether they got what they wanted, when they wanted it, at the quality and price they agreed to. So, the question changes again: not “how do we keep this resource busy,” but “what’s preventing value from reaching the customer.” Sometimes the right call is for a resource to sit idle. Sometimes it’s smaller batches. The goal was never to maximize activity. It’s to maximize the rate at which the enterprise creates value.
The Infrastructure That Turns These Three Shifts Into a Number On Your P&L
All three of these — problems as information, speed as a diagnostic, flow over utilization — run on the same input: visibility that’s current, not historical. That’s the gap a digital management system closes.
The daily visual board isn’t going away, and the discipline behind it is still the point. What digital adds is reach and speed. A signal from a line in one plant reaches the leader who needs it within the shift it happened, not the next status meeting. Escalation follows a defined path instead of waiting on a calendar. Leaders spend less time reconciling spreadsheets and more time on the one constraint actually limiting throughput this week.
Put a number on it, because that’s the question a manufacturing executive should be asking before signing off on anything: recovering less than a point of uptime in a mid-sized plant can be worth hundreds of thousands of dollars in output annually. A fraction of a point of scrap reduction protects material margin at scale, and it compounds across a multi-site network. One pharmaceutical manufacturer grew productivity 17% by redesigning the management rhythm alone — daily performance reviews, hourly problem-solving, real-time feedback, no capital investment, no headcount change. SPX Technologies built the same discipline into a lean-based continuous improvement model: daily problem-solving, leaders coaching on the floor instead of managing from the conference room, visual accountability that traveled across every site. The result wasn’t a culture initiative. It was a margin outcome that started with redesigning the system underneath the culture.
A high-performance organization was never about attitude. It’s a management system, sized to the speed the business actually has to run at — and for most multi-site operators, that now means digital.
What This is Worth, and Where to Start
You don’t need to digitize everything on day one. You need to know precisely where your current system is hiding a problem, slowing a decision, or paying people to look busy instead of produce. That’s a diagnostic question with a dollar answer, and it’s the right place to start before any technology conversation.
Digital amplifies discipline — it doesn’t create it. If the management fundamentals underneath aren’t solid yet, that’s the first engagement, not the second. But for operators who already have the fundamentals and are still losing time to slow signals and disconnected sites, the ROI case for a digital management system is one we can build with you in weeks, not quarters — using your data, not a generic benchmark.
If you want to see what that case looks like for your operation — the specific uptime, scrap, and leadership-capacity numbers a digital management system would put in play — let’s set up a working session – complete the form on the right of this page. I’ll bring the framework; you bring your numbers.
