Why Most Reporting Fails at the Last Mile
Reporting rarely fails because the data is wrong. It fails when insight doesn’t translate into decisions. The last mile, from dashboard to action, is where most reporting quietly breaks down.
Read →Systems Outlive People
Every system carries the imprint of the people who built it.
Walk into any organisation and open one of its systems.
What you’re looking at isn’t just software.
It’s history.
Every field, every workflow, every report is a record of decisions made by people who may no longer even work there. The system becomes a kind of organisational fossil record — preserving assumptions, priorities, and compromises long after the people who made them have moved on.
And unlike people, systems tend to stick around.
The Fossil Record of Decisions
Most systems are not designed all at once. They evolve.
A field gets added because someone needed it for a report.
A workflow changes because a process was updated.
A workaround becomes permanent because the “temporary fix” never got revisited.
Over time these layers accumulate. The system grows not as a clean design, but as a collection of responses to real problems faced at specific moments in the organisation’s life.
Five years later, someone opens the system and asks a simple question:
“Why is it built like this?”
The honest answer is often:
“No one really knows.”
The System Knows More Than the Organisation
One of the strange realities of systems work is that the system often knows more about the organisation than the organisation knows about itself.
Hidden in the database are traces of:
- processes that no longer exist
- teams that have been restructured
- priorities that changed years ago
- decisions made under constraints nobody remembers
You can sometimes reconstruct the story of an organisation just by looking at how its systems are shaped.
Where there are duplicate fields, there was once disagreement.
Where there are workarounds, there was once urgency.
Where there are complex rules, there was once risk.
Systems are not just tools. They are archives.
The Archaeology of Systems
Working with systems often feels less like engineering and more like archaeology.
Before you can change anything, you have to understand what you’re looking at.
Why does this field exist?
Why does this report matter?
Why does this process have three approvals instead of one?
Sometimes there is a clear answer. Often there isn’t.
And that’s when the real work begins — not just improving the system, but rediscovering the logic that shaped it.
The Responsibility of Today’s Builders
Because systems last longer than people, every change we make carries a quiet responsibility.
The field you add today may still exist in ten years.
The process you automate may shape how people work long after you’ve left.
The report you build may influence decisions you’ll never see.
In that sense, building systems is an act of stewardship.
You’re not just solving today’s problem — you’re shaping part of the environment future teams will inherit.
Leave the System Better Than You Found It
No system will ever be perfect. Organisations change too quickly for that.
But we can aim for something simpler and more realistic:
Leave the system better than you found it.
Clearer.
More understandable.
More aligned with how the organisation actually works.
Because long after we’ve moved on, the system will still be there — quietly carrying the history of the decisions we made.
And someone, somewhere, will open it and wonder why.
Every system carries the imprint of the people who built it.
Related posts
Systems Need Owners, Not Just Users
Systems degrade when everyone uses them but no one owns them. Without clear accountability, definitions drift, exceptions multiply, and trust quietly erodes.
Read →Automation Doesn’t Start With Tools
Automation fails when it begins with procurement instead of process clarity. Before software, there must be visibility, ownership, and agreement on what should - and shouldn’t - be automated.
Read →