An illustrative diagnostic of TMS integration failure. When the system reflects how the organisation wished it operated—not how it actually operated—adoption collapses. The fix was alignment and governance, not technology.
This is an illustrative example scenario, based on common challenges we see in distribution and transport environments. It is not a case study from a specific client, but reflects the types of findings a diagnostic typically produces.
The regional distribution business had invested significantly in a new Transport Management System (TMS). The objective was clear: standardise route planning, improve delivery visibility, and reduce reliance on informal communication.
The implementation took eight months. Costs exceeded the original estimate. Training was delivered. The system went live.
Within weeks, it became clear that adoption was low.
Dispatchers continued planning routes in spreadsheets.
Managers relied on phone calls to track deliveries.
Drivers treated handheld confirmations as secondary to operational reality.
The immediate assumption was resistance to change.
The diagnostic approach rejected that assumption and asked a different question:
What decisions was the TMS meant to support — and did the organisation operate in a way that allowed those decisions to be captured digitally?
The TMS had been configured according to a formal requirements document. That document described:
In theory, this matched a disciplined distribution model.
In practice, the organisation operated on negotiated flexibility.
Customer delivery windows were treated internally as fixed constraints in the TMS.
In reality:
These changes were operationally normal — and commercially valuable.
The TMS had no simple mechanism for capturing this dynamic negotiation. It required formal amendment workflows that slowed dispatchers down.
The result:
Delivery completion in the TMS required a structured four-step confirmation process.
Drivers were required to:
In areas with reliable signal, this worked.
However, a significant portion of the delivery network operated in low-connectivity zones. Submissions were delayed by hours. In some cases, they failed entirely.
Dispatchers, seeing incomplete deliveries on screen, reverted to the most reliable channel available: a phone call.
The phone call answered the operational question immediately:
The TMS record was often not updated afterwards.
By end of day:
Operational truth and system truth diverged.
The system’s credibility eroded quickly.
Managers began to ask:
Because the TMS data did not align with lived experience, it lost authority.
Once trust was lost:
No formal decision was made to abandon the system. It was simply bypassed.
The diagnostic did not conclude that the TMS was poorly implemented.
It found that:
In short:
The system reflected how the organisation wished it operated, not how it actually operated.
As discrepancies grew, the cost of correcting them increased.
Dispatchers faced a choice:
Operational continuity won.
Over time:
Because the root cause was structural — not a single configuration error — no quick fix existed.
The recovery did not begin with system changes.
Leadership first addressed decision clarity:
Most importantly, the organisation separated two questions:
Only once these were clarified did technical adjustments make sense.
TMS integration failures are often framed as training issues or resistance to change.
In this case, the failure stemmed from a deeper misalignment:
When systems attempt to impose order without recognising lived operational complexity, users revert to trusted informal channels.
Technology did not fail.
Alignment did.
Restoring that alignment required acknowledging reality before attempting control.