Field Note · Independent analysisProduct teardown

The Logistics Visibility Gap

Everything is tracked. Very little is actually visible.

Modern logistics generates an enormous amount of tracking data and very little visibility. The shipper sees one system, the carrier another, the customer a status page that updates when someone remembers to scan. Nobody can confidently answer the only question anyone asks (where is it, and when will it arrive?), and so a large share of customer service is people asking that question by hand. This is the domain I work in day to day, which is why the gap is so visible to me: the data exists; the product that would make it useful mostly does not.

Where visibility breaks

Manual updates, so information arrives hours after the event. Silos: each party has its own truth and no one has the whole picture. No prediction: delays are discovered, not anticipated, even when the signals were there. No shared channel, so a problem becomes a chain of phone calls. The last mile, which matters most to the recipient, is the least instrumented stretch of the whole journey. Exceptions with no owner and no path. And multi-carrier shipments, where the hand-offs are exactly where the tracking goes dark.

What I would build

A real-time layer: vehicle and package telemetry feeding automatic status without a human scan, unified across carriers behind one interface. A predictive layer: models that flag a likely delay before it is late, continuously refined ETAs, route adjustments, and anomaly detection that raises the exception instead of waiting for a complaint. One communication surface: a shared dashboard where shipper, carrier and recipient see the same shipment; proactive notifications that fire on events people care about and stay quiet otherwise; self-service for the questions that do not need a person. Visibility layers on the shipment itself: live location and ETA, milestones, condition monitoring for sensitive goods, and proof of delivery. And exception management with automatic detection, clear resolution paths, escalation when a path stalls, and root-cause review so the same failure does not recur.

Design principles

Transparency over obscurity. Proactive over reactive. One system and one truth for many stakeholders. Automated over manual wherever a human is only relaying a fact. And contextual: the right information at the right moment, which for a recipient is usually 'it is late, here is why, here is the new time'.

What I would measure

Share of support contacts that are 'where is my order': the metric that should go to near zero. Median time between a shipment event and the status reflecting it. ETA accuracy, and the share of delays flagged before they occurred. Exception resolution time. And satisfaction on delayed shipments specifically, because a late delivery that was communicated well is a different experience from one that was not.

The learning

Visibility is what turns logistics from a black box into something that can be managed. Telemetry and prediction are necessary; the product that puts them in front of the right person at the right moment is what actually closes the gap, and it has to be designed across the whole stakeholder set, not just for whoever pays for it.

Next field noteLinear vs JiraTwo tools for the same job, built on opposite beliefs about what a team is.