In this essay
  1. What I have and what I do not
  2. What you lose
  3. What you gain
  4. Information becomes the work
  5. What I would watch for
  6. Coordination, not just instruction

On the ramp you can see a problem with your own eyes.

From a distance, you often have to understand it through the information you receive.

That is the biggest difference between the two ways I have worked in last mile. In 2025, as a Team Leader and then as an Area Manager, I was in the operation: on the ramp, at the loading, next to the dispatchers, with the KPIs every day. Since 1 January 2026 I have worked part-time as a Last Mile Dispatcher, remotely, from home. The role covers the operational coordination of 80+ vehicles and 100+ drivers: tours, drivers, delays and problems during delivery.

The same problems. A completely different position in front of them.

What I have and what I do not

I will not write the names of applications or systems, the exact way we communicate, or the shift times. Some of these I do not know precisely, and I do not publish internal work details. Nor will I say exactly what the system shows, live location, stops or ETA, because I am not sure.

I do not have a documented incident from this role that I can describe with certainty from start to resolution. I have documented cases from my earlier work in last mile, with vehicles and with delays, but I will not present them as cases solved from a distance.

So this essay is not a success story. It is a comparison of two ways of working, from someone who has been in both. And it is my analysis, not a measured result.

What you lose

You lose the chance to observe every situation yourself.

In Gemba I wrote that the report shows the result and the floor shows how that result is made. From a distance, the floor is not there. What is left is the information that comes from it.

And information reported from a distance is not always the same as what you could observe yourself. When you are on the ramp, the problem appears in front of you. When you are remote, the problem only reaches you if someone sees it, understands it and reports it. Any one of those three steps can be missing.

What you gain

But distance is not only a loss.

On the ramp you see well what is in front of you. From a distance, if the information and the tools support it, you can see the coordination of many tours as one operation. Not one van, but all of them together. Not one delay, but whether delays are gathering somewhere.

That does not happen by itself. It only happens if the information you receive is sufficient and reliable.

Information becomes the work

From a distance, three things become even more important than on the ramp: the quality of the information you receive, the communication, and the clarity of responsibilities.

When you cannot see the vehicle, you need a reliable way to understand what is happening with it.

On the ramp, you can make up for unclear information by going to look. From a distance, you cannot. Unclear information stays unclear, and the decision you take on it stays just as uncertain.

On communication, I have no documented rules that I set myself: when I call, when I write, when I escalate. But as a principle I believe good communication should be short, clear, and say which action is needed. A message that needs three follow-up questions to be understood has lost the time it was supposed to save.

What I would watch for

I do not know of a documented personal method I use to spot problems before they happen. But today I would pay attention to three things.

Deviations that repeat. One delay is an event. The same delay, in the same place, several days in a row, is a pattern.

Problems left unsolved. From a distance it is easy for a problem to be reported and then left hanging, because nobody sees it any more.

Information that arrives late. When information arrives late, the lateness itself is a signal. The problem has had time to grow before you learn about it.

Coordination, not just instruction

Remote coordination is not just giving drivers instructions. It is building a way of communicating in which problems become visible, responsibilities are clear and decisions are taken in time.

This links to this whole series. An improvement holds when it does not depend on someone being there. In remote coordination, being there does not exist at all. All that is left is the system: who sees the problem, how they say it, who takes it on, when it is closed.

You can fill in the sheet below for a problem you cannot see and copy it. Last-Mile CX Control Tower gathers the cases, actions and causes of many tours in one view, so the operation can be seen as one, not as a hundred phone calls.

On the ramp, the problem appears in front of you. From a distance, either you go looking for it, or you have built a way for it to come to you.

A problem you cannot see

0/5

A guide to how I would do it today. It is not a documented method from my current role.