The waste isn't in your lanes it's between them.

A lane has a start and an end. A truck doesn't. That gap between how freight is usually managed and how it actually works is where most of the waste in the industry lives.

Here's what I mean. We manage freight in lanes. We price lanes, bid lanes, contract lanes, report on lanes. Each one is a tidy line from A to B with a rate attached. It's a sensible way to organize an overwhelming amount of activity, and it's how nearly every system, contract and team in freight is built. Nothing wrong with it, as far as it goes.

1: What happens after B

But the truck doesn't stop existing when the load lands at B. It's sitting there now, and what it does next - find a load home or run back empty, depends on the whole web of moves around it. The load is delivered and done. The truck's day and duty cycle continue. And that next move, the one no lane accounts for, is where the cost quietly piles up.

2: Lane thinking, network thinking

Lane thinking looks at each line from A to B on its own and asks whether it's priced right. Network thinking looks at all the lines at once and asks how they connect, because in freight the value and the waste both live in the connections, not the individual lanes.

3: The empty backhaul

On paper, A to B was profitable. But the truck had nothing to carry back, so it ran 400 miles empty - a cost that belonged to no lane in particular, evaporating into the gap between two moves nobody looked at together. Multiply that across a fleet, and you've found where a stunning amount of freight spend actually goes. Not the lanes themselves, but the empty space between them, which no single lane has to answer for.

4: A seeing problem

Here's the part that's easy to miss. Most freight waste isn't a pricing problem, and it isn't a bad-lane problem. It's a seeing problem. When you look at one lane at a time, the empty miles between them are invisible - nobody's line item, nobody's KPI, nobody's job to notice. Network thinking makes them visible. And the moment they're visible, a lot of them turn out to be fixable: a load on the way back, a round trip that two separate teams never spotted because each was looking only at their own lane.

5: Why lane thinking stuck

I want to be fair about why lane thinking dominates. It isn't laziness. Contracts are written per lane. Systems store data per lane. Teams are organized by lane. It's a completely reasonable way to manage staggering complexity, and asking people to hold an entire network in their head at once isn't realistic. The problem is simply that the math of efficiency lives at the network level, and lane thinking, by design, can't see it.

The way forward

Which is why the shift from lane thinking to network thinking might be the single biggest unlock in freight efficiency. And it starts as a change in how you see the problem, long before it becomes a change in what you buy to solve it.

‍