The Difference Between Data and Evidence

We have more data than we’ve ever had.

Especially in transportation.

Arrival times.
Departure times.
Inspection records.
Safety events.
Maintenance records.
Miles driven.
Loads completed.
Service failures.
Customer complaints.
Driver turnover.

Nearly everything creates a data point.

And yet, somehow, we still struggle to answer a much simpler question:

Who should I trust?

I think part of the problem is that we’ve started treating data and evidence as though they’re the same thing.

They’re not.

A data point tells you something happened.

Evidence helps you understand what that something means.

Imagine a driver arrives two hours late to a delivery.

The data says:

Late.

That may be completely accurate.

But what if the driver spent four hours waiting at the previous receiver?

What if an interstate was closed because of an accident?

What if weather forced traffic to stop?

What if the appointment time was changed after the driver was already dispatched?

None of those things make the original data point false.

They make it incomplete.

And incomplete information can become misleading remarkably quickly when we turn it into a judgment about someone.

Context Changes the Signal

Transportation is filled with situations like this.

A broker sees a late delivery.

A carrier sees a service failure.

A shipper sees detention.

A driver sees an equipment problem.

Each party may possess an accurate piece of information.

But no single piece necessarily tells the whole story.

That's why I've become increasingly interested in the distinction between recording events and building evidence.

Evidence requires more than accumulation.

It requires context.

It requires provenance—where did the information come from?

It requires repetition—is this an isolated event or part of a pattern?

And, when possible, it requires corroboration—does other information support the same conclusion?

Those things transform isolated data points into something much more useful:

a signal.

Patterns Matter More Than Moments

Suppose that same driver has completed 1,200 loads.

The record shows consistent communication.

Regular equipment inspections.

Strong safety performance.

Very few service failures.

And hundreds of examples of doing exactly what was expected.

Then comes one late delivery.

Which tells us more about that driver?

The one failure?

Or the 1,199 other pieces of evidence?

Obviously, the failure still matters.

But now we know how much weight to give it.

That's what history does.

History gives individual events proportion.

Without history, every new event can become disproportionately important.

With history, we can begin distinguishing an exception from a pattern.

And that distinction matters enormously when people's livelihoods, businesses, and reputations are affected by the conclusions we draw.

More Data Isn't Necessarily More Truth

This is where I think something interesting is happening across transportation.

We're getting extraordinarily good at collecting information.

But collecting more information doesn't automatically create better decisions.

In some cases, it may actually create more opportunities to misunderstand people.

A thousand disconnected data points are still disconnected data points.

What matters is whether we can determine:

Who created the information?

When did it happen?

What was happening around it?

Can it be independently supported?

Has this happened repeatedly?

How does it compare with the person's broader history?

Those questions move us from data collection toward evidence.

And evidence moves us closer to trust.

Reputation Should Be Built Like a Case

Think about how we make important judgments in almost every other part of life.

We rarely trust one observation.

We look for patterns.

Consistency.

Independent confirmation.

History.

Context.

The stronger the decision, the stronger we generally expect the evidence behind it to be.

Yet professional reputation is still surprisingly vulnerable to isolated moments.

One bad load.

One complaint.

One disagreement.

One rating.

One checkbox in somebody else's system.

Sometimes those events reveal something important.

Sometimes they don't.

The problem isn't that negative information exists.

The problem is when we don't have enough surrounding evidence to know what it means.

What If Work Created Its Own Evidence?

This is the idea I keep coming back to.

What if the everyday work people already perform gradually created a verifiable history?

Not another résumé.

Not another star rating.

Not another place where people simply tell us they're trustworthy.

Actual evidence created through work.

Inspections completed.

Commitments kept.

Problems communicated.

Maintenance documented.

Loads delivered.

Issues resolved.

Professional behavior repeated over time.

No individual event would need to define someone.

Instead, thousands of small actions could slowly reveal something much harder to manufacture:

a pattern.

And patterns are where trust begins.

Transportation doesn't have a shortage of data.

It may have the opposite problem.

What we need is a better way to determine which information deserves weight, how much weight it deserves, and what the broader history tells us.

Because ultimately:

A data point tells us what happened.

Context tells us why.

Patterns tell us what to believe.

And evidence gives us a reason to trust.

That's a distinction worth building around.