Think about the last time you tried to figure out what happened at work last month. Not what the report says happened — what actually happened. Who was waiting on whom. Which thing sat untouched for weeks. When the deal really went quiet, as opposed to when someone finally wrote “lost” in the system.

You almost never find that in the official record. You find it in the leftovers. The email that went unanswered. The calendar that suddenly emptied. The same document saved again and again under different dates. The chat thread that just… stopped.

That stuff has a name. People who work with data call it data exhaust — everything a system gives off while it’s running, that nobody sat down and decided to keep. It sounds like a byproduct, because it is one. But it’s also, very often, the only true story you have.

The photograph and the film

Here is the simplest way I know to say it.

Your official records are photographs. The customer file, the account balance, the status column that says “In Progress.” A photograph is honest about one instant and silent about everything else. It cannot tell you how long the person has been standing there.

The exhaust is the film. Every time someone opened the file, every time the balance changed, every day the status didn’t change — that’s a frame, and stacked up, the frames are a movie of the thing being used. Nobody directed this movie. Nobody framed the shots. That’s exactly why it doesn’t lie.

A record tells you what something is. The trail tells you what it’s been through.

The difference matters more than it used to, and the reason is AI.

What AI actually needs from you

There’s a lot of noise about what AI can do. Underneath the noise, the machines are pretty simple about one thing: they can only reason about what you show them.

Show an AI the photograph — the customer file — and it can describe your customer the way a stranger reading a form would. Show it the film, and something changes. It can see the customer over time: when they first showed up, when they got busy, when they went quiet, how quiet is normal for them and how quiet is a warning. It’s the difference between meeting someone once and having known them for ten years. Ten years of knowing someone isn’t a bigger form. It’s the trail.

A friend and I have been calling this predator vision — the movie version, not the heat-map. The system stops staring at a warm blob and starts seeing the path the blob took through the room. That’s the only thing that lets you guess where it’s going. And it works in reverse, too: once you know the shape of a normal week, you can see the shape of the week that’s missing — the silence with an outline around it. Nothing happening, on its own, tells you nothing. Nothing happening from something that has never once been quiet is a story.

Half the elephant

Now the uncomfortable part, which is about people rather than machines.

To get any of this to work you have to understand two things at once: what your data actually is, and what the AI actually does with what it’s shown. Almost everyone I meet has one of the two.

The data people know their business inside out — where the numbers come from, which fields are trustworthy, why the March total looks weird — and they treat the AI as a magic box that answers questions. The AI people can get a beautiful paragraph out of anything and have never once asked what the model could see when it wrote it. Each one has a hand on the elephant. One says “snake,” the other says “wall,” and neither is wrong about the part they’re touching.

The skill that’s actually scarce right now isn’t prompting, and it isn’t spreadsheets. It’s holding enough of your own data in your head that you know which film to hand the machine, at what level of detail, with the dates still on it — and knowing, when the answer comes back, whether it read something or made something up. That’s a data skill wearing an AI costume. Which is why, for those of us who always liked the plumbing — pulling data from here, cleaning it up, putting it where someone can use it — this moment doesn’t feel like a break with the old work. It feels like the old work finally got a reader who can do something with it.

What to do on Monday

You don’t need a project for this. You need a habit and one decision.

  • Stop deleting the trail. Old versions, old logs, the notes from the meeting that went nowhere. Storage is close to free. What you’re really keeping is time.
  • Keep the last look next to the current one. The single most useful thing I’ve built this year is a file that says “here’s what I saw yesterday” sitting beside “here’s what I see today.” Almost every real insight is in the gap between them.
  • Ask about change, not state. “What’s the status?” gets you a photograph. “What’s different from last week, and how long has it been that way?” gets you the film.
  • Distill it before it rots. A trail nobody ever summarizes is just a bigger photograph. Write the one line — “this goes quiet every August” — while you still remember why it mattered.

And be honest about the limits. Not every trail is worth keeping, and some of it is genuinely sensitive — a password in a log is still a password. Keep it where it fell, keep it locked, and think before you share any of it. But don’t throw it out because nobody asked for it. Nobody ever asks for the film. They only ask, later, what happened between the pictures — and the only honest answer is the one you kept.

This is the plain-language half of a pair. The technical half, with the actual mechanism, is The Negative.