The Ledger Is Not the Past

I keep returning to the same research question: How do we get the best work from the best people and how do we do that ethically?

The answer cannot be found by only looking at individual employees. I also like to examine the structures of work and the microcultures of the workplace: what gets rewarded, what gets overlooked, who carries the hidden labor, and what the organization has decided counts as productivity.

That is partly why I find financial reports, dashboards, and performance reports so fascinating. They appear to tell us what happened. But they also reveal the limits of what an organization knows how to see.

A financial ledger looks authoritative. Its columns are orderly. Its figures are exact. Each amount has a place, and every transaction appears to tell a clear story.

But the ledger is not the past. It's a record made from the past.

Before anything enters a spreadsheet, someone has already made a series of decisions. What should be counted? How should it be categorized? Which details matter? What belongs together, and what should be separate? Those choices shape the story the numbers eventually tell.

Accounting is often treated as a technical language, but it is also a cultural practice. It reflects assumptions about value, responsibility, time, ownership, and risk.

An experienced auditor already knows this. The numbers can reveal, or conceal, part of a story about the behavior of a business and, by extension, the people doing, managing, and recording its work.

A financial report may show that a program cost more this year than it did last year. It cannot explain on its own whether that increase represents waste, growth, delayed investment, or an unexpected need.

It does not tell us that Carole retired and an entire department experienced a crisis, followed by an awkward but ultimately productive reinvention of itself.

It does not tell us that a toxic actor stirred up some Class A drama that consumed weeks of attention, emotional energy, and otherwise productive time.

Those things happened. They affected the work. But where do they appear in the report?

The numbers require context. That does not make them unreliable. It makes interpretation necessary. Still, it is easy to begin treating the record itself as the truth rather than as one lens onto the reality it represents. A neat table can make the past look equally neat. But lived experience rarely arrives in clean categories.

Projects overlap. People contribute in ways that are never recorded. Decisions are made under pressure. Some costs appear in dollars, while others are absorbed through time, stress, lost opportunities, delayed work, or strained relationships.

Reports capture what entered the system. It may not capture what was required to make the system work. This distinction matters far beyond accounting. We increasingly rely on dashboards, databases, reports, and digital archives to tell us what happened. Once we believe we understand the past, we use those records to project farther into the future and drive decisions toward more desirable outcomes. But projections depend on the assumption that the future will resemble the past closely enough for the old data to remain useful.

Sometimes it does. Sometimes Carole retires. Sometimes a department restructures, a pandemic arrives, a technology changes the work, a leader leaves, or a conflict reorganizes the social life of an institution.

An extreme event exposes something the old data could never fully know: the conditions that produced the numbers were never guaranteed to continue.

Data is not memory without interpretation.

Prediction is not certainty simply because it has been placed inside an "objective model."

A responsible reader asks not only what various reports contain, but what conditions produced it. Who created the categories? What kinds of value fit inside them? What disappeared because it could not be easily counted? What labor was essential but never assigned a line item? Who had the authority to document what happened, and who was too busy holding everything together to write it down? How do leaders negotiate the costs transferred into someone’s time, patience, health, or relationships?

When we look at a period of strong performance, I wonder if we are we seeing a healthy system or a small number of people quietly compensating for a fragile one? When productivity declines, are employees working less effectively, or has the organization lost one of the people whose invisible labor once made the numbers possible? And when a model predicts what should happen next, does it understand the human conditions behind the earlier outcome--or only the outcome itself? The ledger does not always share what happened.

Perhaps it tells us what the system was capable of recognizing about what happened.

That is still valuable. Records help us notice patterns, establish accountability, allocate resources, and make better decisions.

For me, ethical productivity requires me to look beyond the record. My curiosity asks to examine the structures and microcultures that produce The Numbers and to ask whether the people creating the organization’s best results are being supported by the system or quietly consumed by it.

Reports may help us find the story, but they should never be mistaken for the whole of it.