The Case for Boring Manufacturing Software

Manufacturing tech is often sold through a carefully choreographed demo. There’s the dashboard with perfectly arranged KPIs. The colorful production schedule. The command center showing everything happening across the facility.

But some of the most valuable manufacturing software may be far less impressive in a demo.

• It’s the screen an operator opens and immediately knows what to do next.

• It’s the information that appears automatically instead of requiring someone to go find it.

• It’s the production status that a manager can trust without asking three people whether it’s current.

• It’s the integration that quietly eliminates a spreadsheet nobody particularly liked maintaining anyway.

In other words, good manufacturing software doesn’t necessarily give people more technology to use. It gives them fewer things to think about.

And that’s a very different way to evaluate a software investment.

Manufacturing Has a Cognitive Load Problem

Consider how much information a typical manufacturing operation asks people to keep track of:

• What’s running?

• What’s late?

• What changed?

• Is material available?

• Which revision are we using?

• What needs attention?

• Did someone enter that into the ERP? Is that spreadsheet current?

• Who knows what happened on second shift?

None of those questions is particularly unusual; the problem is the amount of human effort required to answer them.

When systems don't reflect how work actually happens, people become the integration layer:

• Someone remembers that a certain field in the ERP isn't reliable, someone else knows which spreadsheet contains the real schedule.

• A supervisor knows to call a particular person before trusting a status.

• An operator has learned three extra steps that aren't documented anywhere.

• A planner exports information from one system, manipulates it, and enters it somewhere else.

Eventually, the operation develops an invisible layer of human knowledge holding everything together. Production continues to move, and it’s easy to assume the system is working, because technically, it is.

The question is how hard your people are working to make it work.

Stop Counting Features. Start Counting Friction.

Manufacturing software evaluations often begin with functionality.

• Does it support scheduling?

• Can it track work orders?

• Does it have dashboards?

• Can it integrate with our ERP?

• Does it have AI?

Those questions matter, but they don't necessarily tell you whether the software will actually improve your operation.

Try asking different questions instead:

• How many places does someone have to look before making a decision?

• How many times is the same information entered?

• How often does someone leave a system to finish a task?

• How many production questions require asking another person?

• How much institutional knowledge is required to interpret what the system says?

• How many workarounds have become so normal that nobody calls them workarounds anymore?

Those questions reveal something a feature comparison can't: operational friction.

And reducing that friction can be one of the highest-value jobs software performs.

Your Workarounds Are Requirements in Disguise

There's an interesting moment in almost every manufacturing software project.

You ask someone how a process works. → They explain the official process. → Then you watch them actually do it.

But the official process and what goes into actually executing it can be two very different things.

There might be a spreadsheet downloaded every morning, or a whiteboard used because it's faster than updating the system. A handwritten note attached to a traveler. A group chat where schedule changes actually get communicated.

It can be tempting to look at those behaviors as problems to eliminate. But first, they're worth studying.

A workaround exists because someone encountered a gap between what the system expects and what the operation requires.

That doesn't mean every workaround should become a software feature. Some are symptoms of bad processes that should disappear entirely. But taken together, they provide an unusually honest map of where your current systems aren't supporting the business.

Before writing requirements for a new manufacturing system, we should probably spend more time documenting everything employees do outside the existing one.That's often where the most useful requirements are hiding.

The Goal Isn't to Put the Entire Factory on a Screen

Q: If you can collect 200 data points, why not display 200 data points?

A: Because someone still has to decide what matters.

There is another trap in manufacturing technology: assuming more visibility is always better.

• A production manager doesn't necessarily need more data. They might need to know which three jobs require attention.

• An operator doesn't need an enterprise-wide dashboard. They might need to know what to run next and whether anything has changed.

• Leadership doesn't necessarily need another report. They might need confidence that the number they're looking at means the same thing across every department.

The purpose of visibility isn't to make everything visible, it's to make the right things obvious. That distinction should influence everything from dashboards to alerts to production workflows.

Sometimes Custom Software Should Be Surprisingly Small

“Custom manufacturing software” can sound like a proposal to replace half of your technology stack, but it doesn't have to be.

Sometimes the highest-value solution is a relatively small piece of software sitting between systems that are already doing their jobs reasonably well.

• Maybe the ERP should remain the system of record.

• Maybe the machines don't need to change.

• Maybe the existing scheduling process is fundamentally sound.

The question shouldn't be: “Could we replace this system?”

It should be: “Where would software remove the most friction?”

Those answers can lead to very different investments.

Good Software Should Eventually Become Boring

There's a tendency to judge technology by how impressive it looks immediately after implementation, but the real test is how helpful it is in 6 months, 1 year, 2 years, etc.

• Do people trust it?

• Has the emergency spreadsheet disappeared?

• Are people still maintaining parallel processes “just in case”?

• Can a new employee understand the workflow without learning a collection of undocumented tricks?

• When something changes in production, does the right person know?

• Can people answer routine questions without hunting for information?

If the answer to these questions is yes, the software may no longer feel particularly innovative. Instead, it has simply become part of how the operation works. And that's probably a compliment!

Maybe the Best Software Strategy Starts Without Software

Before deciding what to build, integrate, replace, automate, or buy, spend some time looking for friction.

• Follow a work order through the facility.

• Ask where information gets re-entered.

• Find the spreadsheets that aren't supposed to be important but somehow are.

• Notice where people have to remember things the system doesn't.

• Ask supervisors which questions take surprisingly long to answer.

• Look for places where employees have created their own tools.

Then ask: “What would have to change to make this easier?”

Sometimes the answer will be custom software; sometimes it will be an integration, a better use of something you already own, a process change, an off-the-shelf product, or no technology at all. But remember, that's the point.

Manufacturing doesn't need more software for software's sake. It needs systems that quietly remove obstacles between what needs to happen and the people trying to make it happen.

And if we've done that particularly well, eventually nobody will be talking about the software.

They'll just notice that the work got easier.

The Most Important Software in Your Factory Might Be the Stuff IT Didn’t Buy

Walk through almost any manufacturing company and you’ll eventually find it.

A spreadsheet. And not just any spreadsheet - The spreadsheet.

You know, the one that has been around for years. The one with 14 tabs, mysterious formulas, and color coding that only three people fully understand.

Maybe it tracks production, maybe it schedules jobs, Maybe it calculates quotes, manages inventory, tracks quality issues, or tells the morning meeting what actually happened yesterday.

🚫 It probably wasn't part of a digital transformation roadmap.

🚫 Nobody issued an RFP for it.

🤷‍♂️ Someone just needed to solve a problem, so they built something.

⚠ And then the company started depending on it.

Every factory has an unofficial technology stack

Manufacturers usually have an official list of systems: ERP. Accounting. Quality. Maintenance. Scheduling. Maybe an MES. Then there's the unofficial list:

• Spreadsheets.

• Access databases.

• Shared folders.

• Whiteboards.

• Paper travelers.

• Email chains.

And, occasionally, the employee who somehow knows how everything connects.

These tools are easy to dismiss as technical debt. But they tell you something important.

They show you where the official systems stopped matching the reality of the operation.

Someone created that production spreadsheet because they couldn't get what they needed from somewhere else.

Someone built that scheduling board because the ERP screen didn't give supervisors the visibility they needed.

Someone created a manual quality log because the existing process was too cumbersome on the floor.

These aren't just workarounds.

🔎They're clues.🔎

Don't delete the spreadsheet. Investigate it.

When companies begin modernization projects, there's often an understandable urge to clean everything up; Ditto when Mr. Manager reads an article like this one. To be clear, the long-term goal can be to:

• Get rid of spreadsheets.

• Eliminate paper.

• Standardize systems.

• Automate everything.

But before eliminating a workaround, it's worth understanding why it exists.

• Find the person who created it.

• Ask what problem they were trying to solve.

• Ask who uses it.

• Ask what would happen tomorrow if it disappeared.

That last question is especially useful.

If the answer is: "Production would have a serious problem.” You've probably found something worth studying.

Your best process analysts might already be on the floor

Another interesting thing happens when you investigate these unofficial systems: You find people who understand the operation extraordinarily well:

• The production planner who built a complicated scheduling workbook.

• The quality manager who created a better way to track defects.

• The supervisor who redesigned a paper form because operators kept missing information.

They may not call what they're doing "systems design,” but that's essentially what it is. They understand the inputs. They understand the exceptions. They understand what information matters.

And most importantly, they understand what happens when the process meets reality. That knowledge is incredibly valuable when deciding what to automate or modernize.

The goal isn't to eliminate scrappy solutions immediately

The goal is to learn from them. A spreadsheet that has survived for eight years is telling you something.

So is the whiteboard everyone checks before the ERP, and the employee who receives five emails every morning and manually combines them into one report.

Those things mark the places where people have adapted technology to fit the operation.

And those places are often exactly where the next technology project should begin.

So the next time you walk through a manufacturing facility, don't just ask what software the company uses.

Ask a different question:

"What do you use that you're pretty sure you're not supposed to be using?"

The answer might teach you more about the operation than the official system diagram ever will.

What We Learned Touring Manufacturing Facilities Across New England

Over the past couple of years, we made a conscious decision to spend less time selling and more time learning.

Instead of chasing every opportunity, we visited manufacturing facilities across New England, attended industry events, and sat down with leaders at every level, from executives and plant managers to engineers and production teams.

We weren't looking for projects. We were looking for perspective.

While every manufacturer is different, we found that many of them are working through remarkably similar challenges.

Every Manufacturer Is Unique, But the Challenges Are Familiar

The products change.

The equipment changes.

The regulations change.

The people don't.

Whether it was a precision machine shop, shipbuilder, or industrial fabricator, we consistently heard the same themes.

Visibility Is Harder Than It Should Be

Many organizations have the data they need, but not the visibility.

Information lives across ERPs, spreadsheets, whiteboards, emails, and the knowledge of experienced employees. Decisions often require pulling information from multiple places before anyone can act.

The issue isn't a lack of data, but instead a lack of connected information.

Technology Isn't the Biggest Problem

We expected to hear manufacturers asking for AI.

Instead, they talked about scheduling, communication, staffing, quality, and process consistency.

Many organizations already own capable software, yet still rely on manual workarounds to keep operations moving.

Technology wasn't failing them.

Their processes simply weren't designed around how people actually work.

The Best Manufacturers Never Stop Improving

One thing stood out across nearly every facility we visited.

The best manufacturers weren't satisfied with the status quo.

They continuously asked questions like:

• How can we eliminate waste?

• How can we make better decisions?

• How can we improve communication?

• How can we reduce variation?

• How can we support our workforce more effectively?

Continuous improvement wasn't a project, it was part of the culture.

Relationships Matter

Manufacturing is built on trust.

The strongest organizations weren't looking for vendors to sell them software.

They were looking for partners who understood their business, listened before recommending solutions, and were willing to work alongside them to solve problems.

That reinforced something we already believed:

Good consulting starts with understanding, not prescribing.

Technology Has a Role, But It's Not the Starting Point

AI, automation, analytics, and custom software all have tremendous potential.

But the manufacturers seeing the greatest success weren't implementing technology simply because it was available.

They were solving operational problems first and technology became the accelerator, not the strategy.

Why It Changed Us

Those conversations shaped the future of Big Room.

They influenced our services, our messaging, and ultimately our decision to rebrand as a manufacturing-focused advisory and engineering firm.

We realized manufacturers didn't need another software company.

They needed a partner who could understand their operation first, then recommend the right combination of process improvements, technology, and engineering expertise.

That's the company we set out to become.

Looking Ahead

Manufacturing is entering a period of tremendous change. AI, automation, workforce challenges, reshoring, and digital transformation are creating new opportunities and adding new complexity.

The manufacturers that succeed won't necessarily be the ones with the newest technology. They'll be the ones that understand their operations well enough to invest in the right improvements at the right time.

We're grateful to every manufacturer who welcomed us into their facilities, shared their challenges, and helped shape our perspective. Those conversations continue to influence how we work, and they reinforce our belief that the best solutions always begin by understanding the operation before recommending the technology.

The Difference Between Digitizing and Transforming Operations

Technology has never been more accessible to manufacturers. AI, automation, dashboards, ERP systems, and digital work instructions all promise greater efficiency and visibility. Yet many organizations invest heavily in new technology without seeing meaningful improvements in their operations.

Why?

Because digitizing operations and transforming operations are not the same thing.

Digitizing Means Doing the Same Things—Digitally

Digitization is the process of replacing manual tools with digital ones.

Examples include:

• Replacing paper forms with tablets

• Moving spreadsheets into a database

• Implementing electronic work instructions

• Purchasing a new ERP or MES

• Creating dashboards from existing data

These initiatives can absolutely create value. They often improve accessibility, reduce manual effort, and make information easier to share.

But they don't necessarily improve the underlying process.

If a process is inefficient today, putting it into software simply creates a faster inefficient process.

Transformation Starts with the Operation

Operational transformation asks a different question:

"How should this process work?"

Instead of focusing on technology first, it focuses on understanding:

• How work actually flows through the organization

• Where decisions are made

• Where pain points occur

• Why employees rely on workarounds

• Which information people actually need

Only after those questions are answered does technology become part of the solution.

Sometimes that solution involves new software.

Sometimes it doesn't.

Technology Is an Enabler, Not the Strategy

One of the biggest misconceptions in manufacturing is that digital transformation means buying new software.

In reality, software should support a well-designed operation—not define it.

We've seen manufacturers with:

• Modern ERP systems managed through spreadsheets

• Sophisticated dashboards no one uses

• Automated workflows that simply automate unnecessary steps

• AI initiatives built on inconsistent or incomplete data

None of these are technology problems, they're operational problems.

Transformation Creates Lasting Value

When operations improve first, technology investments become far more effective.

Organizations often experience:

• Better visibility across production

• Faster decision-making

• Less manual coordination

• Improved scheduling

• Stronger data quality

• Greater adoption of new systems

• Higher return on technology investments

Technology becomes an accelerator instead of a bandage.

The Right Question Isn't "What Software Should We Buy?"

A better question is:

"What is preventing our operation from performing at its full potential?"

The answer might be process design, communication, data quality, scheduling, accountability or, yes, technology.

The key is understanding the operation before prescribing the solution.

Our Philosophy

At Big Room, we believe manufacturers deserve more than software recommendations. They deserve a partner who understands how their business operates.

That's why every engagement begins with understanding the operation, not just a software sales pitch. Whether the right answer is process improvement, AI, system integration, or custom software, our goal is always the same: help manufacturers build smarter, more connected operations that create lasting business value.

Digital transformation isn't about becoming more digital. It's about becoming more effective. Technology simply helps you get there, and Big Room is here to help.