Why Multiple Sources of Truth in Manufacturing Means Zero Accountability

Prefer listening? Catch this week’s episode of the Everyday Business Problems podcast wherever you listen, or watch it on YouTube.

Nearly every manufacturer I walk into has the same problem hiding in plain sight. They are running at least two systems that both claim to be the source of truth. And depending on where you sit in the organization, you rely on one, ignore the other, and assume everyone else sees the world the same way you do.

They don’t.

I was working with a print manufacturer a while back. They had a management information system for production, an accounting tool for financials, and paper job tickets that traveled with every order through the shop. Three places where information about a single order could live. Three places where that information could be different.

And it was different. Constantly.

The operations leader relied on the MIS. The production floor relied on what was physically written on the job ticket. Accounting relied on whatever they could piece together from both, plus their own system, just trying to get invoices out the door.

Nobody was wrong, and that’s the whole point. When leadership has never declared which system is the master, everyone builds their own version of the truth. Then your customers and your team pays for it every single day.

The Most Expensive Question in Your Organization

Think about the last time someone in your company questioned a number. A report came across someone’s desk and the first reaction was not “what does this tell us” but “where did this come from?” That question, “which number do we use,” is probably the most expensive question being asked throughout your organization.

Here is what it triggers: instead of acting on the information, everyone stops to backtrack. They have to retell the story of what happened on that order, that production run, that customer transaction. Every person who touched it gets pulled in. The accounting team, who should be processing invoices and managing cash flow, is now running a forensic investigation on a single order.

Multiply that across every order where the systems disagree. In the print manufacturer I was working with, the accounting team had become the unofficial reconciliation department. Two people were spending more of their week cleaning up data mismatches than doing actual accounting work. They were comparing what the MIS said to what the paper ticket said to what the accounting system said, order by order, line by line.

Here is where it gets expensive; An overrun that was handwritten on a job ticket but never entered into the MIS? It either gets missed on the invoice, which means you are leaving money on the table. Or it gets caught by accounting after the invoice is already out the door, which means the customer disputes it. Now you are crediting invoices, reissuing them, and chasing the same dollar twice.

I have watched this pattern in company after company. Material ordered for jobs that changed or never happened. Labor hours burned chasing data that should have been right the first time. Revenue sitting uncollected because invoices do not match what was delivered. When you start adding it all up, reprints from bad specs, unbillable reconciliation labor, disputed invoices, uncollected receivables, wasted materials, it is easily a six-figure problem annually. That is why I built our Cost of Chaos Calculator, so leaders can see what this is costing them using their own numbers instead of taking my word for it.

The People Who Pay the Price

The financial cost is significant. But the human cost is what actually kills the business over time.

When multiple sources of truth compete and nobody reconciles them, the people in the middle pay for it. Not the ones causing the chaos and not the ones in leadership who could fix it. The people who show up every day, do the work correctly, and watch nothing change.

I have seen this play out two ways, and both of them cost you.

The first type gets smaller. They keep doing excellent work despite never being recognized for it. Sometimes they complain and get louder and louder. Other times they just get quieter and quieter. They shrink into the background, doing the work of three people, holding the whole system together with duct tape and institutional knowledge. They are the person who knows which system to check for what, who remembers the workarounds, who can reconcile the mess because they have been doing it so long.

The second type cycles through quickly. They come in, see that nothing is going to change, get frustrated, and leave. Usually fast.

Both types cost you, just on different timelines. The one who leaves takes their skills and energy to a competitor. The one who stays and shrinks? When they finally leave, and they eventually do, everything they were holding together falls apart. All the tribal knowledge, the personal relationships with vendors and customers, the sheer workload they were absorbing. Gone.

And then leadership does the most ironic thing possible. They try to save them with money. A raise, a bonus, a counter-offer. By then it is way too late. You cannot pay someone enough to stay in chaos they have been screaming about for years. The money just confirms they were never being heard.

It Is Not a Technology Problem

I want to be direct about this because I hear the wrong diagnosis constantly. Leaders look at the competing systems and conclude they have a technology problem. They need a better ERP. They need to consolidate platforms. They need to rip out the old system and start fresh.

That is not the problem. The problem is that nobody in leadership ever made the decision about which system is the master. The tools did not create the chaos. The absence of a decision did.

I am not saying you need one system. That is an important distinction. It is perfectly fine to have multiple tools. A CRM for customer relationships. An ERP or MIS for production. An accounting platform for financials. A spreadsheet for specific analysis. Most successful manufacturers I work with have all of these.

The problem is when none of them is designated as the master and the others are not reconciled to it. When your customer database lives in both your ERP and your CRM and nobody knows which one is current. When your financial planning lives in Excel and the numbers do not match what is in your accounting system. When nobody can answer the question “which one do we follow” without it turning into a debate.

You need one master source of truth. The others can exist, but they have to be subordinate. They sync to the master. When there is a discrepancy, the master wins. That is a leadership decision, not a technology decision.

The Convenient Number Trap

Here is a pattern I see that makes this even harder to solve. When multiple systems exist and no master is declared, people do not just randomly pick which system to trust. They gravitate toward whichever system gives them the answer they want in the moment.

In the print shop I mentioned, overages that were handwritten on a job ticket but not in the MIS created a no-win scenario. If accounting followed the MIS and billed based on what was in the system, leadership would have a problem because the ticket showed additional charges. If accounting followed the paper ticket, leadership would have a problem because the MIS did not reflect it. There was no way to win because there was no declared standard.

I have also seen this play out with financial reporting. A company running a macro-enabled Excel workbook alongside their ERP. Leadership reviews the financial reports and questions the accuracy because the numbers cannot be reconciled back to the accounting system. The person who built the spreadsheet trusts it because they built it. The CFO trusts the accounting system because that is what the auditors see. Neither of them is wrong, which also means neither of them can be held accountable.

That is the real damage. When there is no single source of truth, consistency, and accountability becomes impossible. Every conversation about performance, about a mistake, about a missed number starts with “which number” instead of “why is this number what it is.” You cannot hold anyone accountable to a standard that does not exist.

The Acquisition Multiplier

Everything I have described so far gets compounded when a company grows through acquisition. Now you do not just have multiple sources of truth within one organization. You have multiple sources of truth across multiple organizations, with multiple leadership teams navigating the dynamics.

The most common mistake I see in these scenarios is the rush to consolidate. ERPs carrying five or six figures in annual maintenance costs look like easy targets on a spreadsheet. Leadership wants to capture cost savings quickly, so they push to get everyone on one system as fast as possible.

The problem is that if you kill the wrong system or consolidate too fast, you break the workflows people are actually using to deliver value. The cost savings you projected evaporate when nobody can invoice correctly, when production cannot track orders, when customer service loses visibility. Whether the acquisition is about capturing market share or creating cross-selling opportunities, the complexity multiplies because you are now making source-of-truth decisions that affect people who did not ask for the change and may not trust the leadership team making it.

What to Actually Do About It

If you are reading this and recognizing your company in every paragraph, here is the temptation: pick a system tomorrow morning and declare it the winner. Do not do that.

The crawl step is the audit, not the decision.

Before you pick a source of truth, you need ultimate clarity on what data lives where and how it connects. Look at it through the lens of Planning, People, Process, Technology. What systems are in play? Who relies on each one and for what? What are the actual workflows, end to end, that deliver value to your customers? Where are the handoffs? Where do things break?

The worst thing you can do is pick a source of truth without fully understanding the end-to-end picture. If you pick wrong because you did not map the landscape first, you have just created a new mess on top of the old one.

Once you have that clarity:

1. Designate one master. Not one system. One master. The others subordinate to it.
2. Define the reconciliation cadence. How often do the subordinate systems sync to the master? What triggers a reconciliation? Who owns it?
3. Enforce it through Clarity, Consistency, and Accountability. Make the decision clear. Communicate it consistently. And then hold people accountable to it. In that order. If you skip to accountability before clarity and consistency are in place, you will create frustration, not performance.
4. Accept that it will be imperfect. You can change your mind given new information. But you cannot change it every other day on a whim. Pick one, commit, improve through your cycle of improvement, and adjust as needed.

This is not a technology initiative. It is a leadership decision. The tools are fine. The people are doing their best with what they have been given. What is missing is someone willing to make the call, communicate it clearly, and hold the line long enough for it to stick.

Because when nobody picks, the business picks for itself. And the business always picks chaos.

That’s it for today.

See you all again next week!

Dave