Why Reroutes Stall Before They Start
Layla Shaikley [ Head of Product & Cofounder, Wise Systems ]
The cross-functional alignment problem that kills route optimization projects before the model ever runs
Most route optimization projects don’t fail at the model. They fail at the meeting.
Not because the technology isn’t ready, and not because the data doesn’t exist. They fail because the right people aren’t in the room — and the people who are don’t have what they need to move forward.
It’s a pattern we see consistently: one operations manager, no cost data, no sales buy-in. A motivated individual with a genuine problem, trying to drive a cross-functional initiative with only a fraction of the required inputs. The reroute gets started, stalls, and eventually gets shelved — not because it wasn’t worth doing, but because it was never set up to succeed.
Why this keeps happening
Rerouting feels like an operations problem. Routes live in the ERP. Operations runs the fleet. So operations takes the lead.
But a real reroute touches far more than operations. Delivery days change, which means customer relationships change — and that’s a sales conversation. Cost modeling requires profitability data by account, by stop, by route — and that lives in finance. System updates require IT. And the whole initiative needs leadership alignment to survive contact with competing priorities.
When those stakeholders aren’t engaged from the start, the project moves forward on incomplete information. Route models get built without cost visibility, so there’s no way to evaluate tradeoff decisions. Sales hears about account changes after the fact and pushes back. Leadership, never fully briefed, fails to prioritize the activation work. The model sits in a spreadsheet and waits.
The data problem no one talks about
There’s a specific version of this that comes up often: the ops manager who has route data but no cost data.
You can optimize for drive time, stop density, and driver hours — and produce a model that looks strong on paper. But without knowing what each stop actually costs to serve, you can’t make the call on which inefficiencies to fix first, or whether a route restructure pencils out financially. The model is technically sound and practically incomplete.
Cost data tends to live with finance, and finance isn’t always a natural partner in routing conversations. Getting them involved early — framing the project as a margin initiative, not just a map exercise — changes what the model can actually tell you.
What alignment actually looks like
Successful reroutes aren’t built by one person working across departments. They’re built by a defined project team that includes operations, sales, finance, IT, and a sponsor in leadership who can break ties and protect the timeline.
That team needs to be formed before the modeling starts, not after. Because the decisions that shape a route model — which accounts are priority, what service frequency is non-negotiable, what cost thresholds define an inefficient stop — require input from people who aren’t looking at a routing screen.
When that team is in place early, the modeling process runs faster and the results are more defensible. Every assumption has been pressure-tested by the person who knows it best. Every tradeoff has a business case behind it. And when the plan is ready to activate, there are no surprises — because the people responsible for each workstream helped build it.
The model should be the easy part
Route optimization software can do a lot. It can ingest your stop data, apply real-world constraints, and surface a more efficient network in a fraction of the time it used to take. But no software replaces the organizational alignment that makes a new plan executable.
The distributors who get reroutes done aren’t necessarily the ones with the best data or the most sophisticated tools. They’re the ones who treat the project as a cross-functional initiative from day one — and build the internal coalition to see it through.
If your last reroute stalled, it’s worth asking: who wasn’t in the room?
Want to see how Wise Systems supports the full reroute process — from data aggregation to activation? Come to our next webinar.
