Tribal Knowledge vs. Data: The Battle of the Century

What I’m Seeing in Manufacturing Today

Lately, I’ve been noticing a pattern in conversations with manufacturers and operators.

Not a crisis or urgency, but a bit of a shift.

Many companies are still running effectively on tribal knowledge. It’s literally how they built their success. The production manager knows which jobs tend to run long. The controller knows which customers compress margin. The warehouse lead knows which SKUs always seem slightly off. That awareness is earned over decades.

It works. In SMB environments, where everyone is close enough to the ops to feel what is happening in real time. Where instinct fills the gaps and decisions happen quickly, the experience carries weight.

But alongside that, I am starting to see something different emerge.

A Subtle Shift in Mindset

A growing group of SMB leaders are thinking beyond today’s needs.

They are not reacting to failure or dissatisfied with their systems. They are recognizing that the business they are running now likely won’t look the same five years from now.

The main realization that comes from this is that there are data points that are not valuable right now but could become valuable later.

From where I’m sitting, that’s a big shift in mindset for some small business manufacturers.

In earlier growth stages, companies focus on immediate problems. Are we profitable? Are we shipping on time? Is cash flow stable? If a spreadsheet answers the question, that is often enough.

But as operations become more layered, the questions change.

• Can we see margin trends over multiple years by product family?
• How has vendor lead time variability shifted over time?
• What does scrap look like by machine across shifts?
• How has customer order frequency changed by segment?
• Most companies do not need those answers immediately. Some of those questions are not even relevant yet.

What I am observing is a mindset centered on optionality. Leaders understand they may not know which data sets will matter in the future. But they also understand that if the data is not captured now, it cannot be analyzed later.

Tribal Knowledge Is Not the Problem

I want to be super clear on this point.  Tribal knowledge is not a flaw or even evidence of a flawed system.

It is adaptive, fast, and grounded in lived experience. Loads of successful companies still operate largely on institutional memory, and they do so effectively.

The tension between tribal knowledge and structured data is evolutionary.

Tribal knowledge allows businesses to move quickly. Data infrastructure takes discipline to build. But it creates continuity.

As organizations grow, what once lived in a handful of people’s heads has to flow across a larger system. Intuition becomes harder to scale as the operation adds layers or as markets change.Shameless Plug

Since I spend most of my time these days in the ERP world, I’d be remiss not to mention where this conversation often lands.

It begins with talking about their desire (or understanding that they need to) modernize.  Which comes from knowing that, despite it working now, there are looming market or internal changes that could instantly render some tribal knowledge useless or inaccessible.

This is where Microsoft Dynamics 365 Business Central naturally enters the picture.

One of the things it does well is enforce structure. Transactions, inventory movements, production orders, purchasing activity, financial entries. It brings those into one environment instead of scattering them across spreadsheets, emails, and disconnected tools.

It’s nearly impossible to keep a growing company on the same page if everyone is reading from a different book.

Leaders thinking ahead are less concerned about what they can analyze today. They are more interested in preserving history. They want to know that if three years from now they need to evaluate margin compression, customer behavior shifts, supplier variability, or operational anomalies, the historical data will exist in a usable format.

They understand that some data sets do not reveal their value immediately but can gain meaning over time.

I’m a bit biased, but Business Central is an elite option for making sure that when the moment comes to ask a more sophisticated question, we have the clay tablet there to reference.

Parting Words

Tribal knowledge has built and continues to build businesses.  Structured data is increasingly viewed as insurance for the future and way to make sure that as teams change, markets shift, and questions become more sophisticated, the answers will exist.