Most businesses do not wake up one morning with broken insight. They arrive there slowly, through a series of sensible decisions made over time.
A report is created to answer a question. A workaround is introduced to meet a deadline. A new tool is added to support a growing team. Each step feels justified. Each solution works well enough in the moment. None of it looks like a mistake.
Until one day, decisions start to feel harder than they should.
Numbers no longer align. Dashboards contradict each other. Meetings spend more time debating which figures are correct than deciding what to do next. Confidence quietly erodes.
This is not a sudden failure. It is the result of legacy insight building up without ever being brought back into alignment.
This is not about broken tools
When organisations first notice conflicting insight, the instinct is often to blame the tools.
Excel feels too manual. Dashboards feel out of date. The CRM feels incomplete. The analytics platform feels confusing or slow. Technology becomes the visible suspect.
But tools are rarely the root cause.
In most cases, the real issue is that insight has grown faster than it has been consolidated. Logic has been duplicated, adapted and reinterpreted across teams without ever being reconciled. Over time, different versions of the truth quietly emerge.
This is a form of data decay.
In our earlier article, Data Decay: When Your Data Stops Keeping Up With Your Business, we explored how data gradually loses relevance, reliability and usefulness as organisations evolve. One of the most common and damaging ways this decay shows up is through conflicting insight.
When teams trust different numbers.
When reports tell slightly different stories.
When decisions based on “the data” point in opposing directions.
How legacy insight quietly builds up
The process usually starts innocently:
A single report answers a single question.
That report is copied to answer a similar one.
Another team builds their own version using slightly different assumptions.
Someone tweaks the logic to suit a new context or audience.
Each step feels reasonable. Each version works well enough. Nothing appears obviously wrong.
But as these parallel versions accumulate, they begin to drift. Definitions change subtly. Timeframes shift. Filters are applied differently. Calculations are updated in one place but not another.
Eventually, there is no longer a shared understanding of what the numbers actually represent.
At this point, insight still exists, but coherence is lost.
The Excel example, properly understood
Excel is often blamed because it is familiar and visible.
It is also genuinely excellent. Flexible, powerful, and accessible. For a long time, it works extremely well. That is precisely why organisations rely on it for so long.
The problem is not Excel itself. The problem is when Excel quietly becomes the backbone of an organisation’s data infrastructure.
The progression is almost always the same:
One spreadsheet becomes twelve.
Twelve become forty.
Forty become a shared folder full of files that no one fully understands.
At that stage, the challenge is no longer efficiency. It is trust.
Which file is the latest.
Which version reflects reality.
Which logic should be used in a leadership meeting.
Excel works best as an interface, a way to explore and interact with data. It struggles when it becomes the central source of truth.
When decisions start to disagree
Conflicting insight rarely shows up as obviously wrong data.
Instead, it shows up as disagreement:
Sales and finance debate revenue numbers.
Marketing and product disagree on performance.
Operations plan for one outcome while leadership expects another.
Each team can justify their figures. Each dataset makes sense in isolation. The issue is not accuracy. It is alignment.
This is what infrastructure debt looks like in practice. Not missing data. Competing realities.
Over time, teams begin to trust their own numbers more than shared ones. Local optimisation replaces collective direction. The organisation continues to move, but no longer in the same direction.
Why this happens as organisations grow
Legacy insight is rarely the result of poor decisions.
More often, it is the outcome of good decisions made under different constraints:
Someone needed speed.
Someone needed autonomy.
Someone needed answers quickly.
As organisations scale, systems are introduced to solve immediate problems. New tools are layered on top of existing ones. Teams move faster than governance can keep up. Assumptions that once held true slowly stop applying.
The business evolves, but the logic behind its insight often does not. Without deliberate intervention, fragmentation becomes inevitable.
When insight becomes historical rather than operational
Another clear sign of this problem is when insight becomes backward looking by default.
Reports explain what happened, but rarely guide what should happen next. Teams spend more time interpreting numbers than acting on them. Decisions are justified after the fact rather than informed in advance.
This is not because the data is wrong. It is because the system producing it was never designed to support alignment at scale.
Insight becomes descriptive rather than decisive.
Why replacing tools rarely fixes the problem
At this point, many organisations attempt a reset:
They invest in a new dashboard.
They roll out a new platform.
They centralise reporting.
These steps can help, but only if the underlying logic is addressed.
If definitions remain unclear, ownership is absent, and assumptions are left unchallenged, new tools simply recreate old problems in a different interface. Technology amplifies what already exists. It does not resolve misalignment on its own.
What actually helps organisations realign
Fixing conflicting insight requires a shift in mindset. Insight is not a collection of reports. It is infrastructure.
A few principles matter more than any specific tool:
Centralising the truth matters more than perfecting presentation. One shared source, even an imperfect one, is better than multiple polished reports that disagree.
Clear ownership matters more than access. If everyone owns the data, no one does. Accountability is what keeps definitions consistent as systems evolve.
Automation should focus on flow, not firefighting. Manual exports and copy paste workflows introduce drift. Direct system connections reduce interpretation at the wrong layer.
And finally, clarity comes from restraint. Measuring fewer things, more deliberately, often leads to better decisions than tracking everything.
Excel still has a role. Just not at the centre of the system.
How this connects back to data decay
Conflicting insight is one of the most damaging forms of data decay because it undermines trust.
When teams no longer trust shared numbers, decision making slows. Conversations shift from action to reconciliation. Performance suffers, not because insight is missing, but because it cannot be agreed upon.
This is why data decay is not just a technical problem. It is a strategic one.
A final thought
Legacy processes do not break businesses overnight.
They slow them down quietly. They introduce friction where there should be flow. They turn insight into something that must be defended rather than trusted.
The solution is not to throw everything away. It is to understand how you arrived here, decide what still serves you, and redesign the rest with intention.
Because the most dangerous moment for any organisation is not when it lacks data. It is when it has plenty, and none of it agrees.