Blog

Fewer Stops Don't Make a Route Easy.

A so-called nursery route can be the hardest one on the board. Label the difficult work, take the time pressure off the drivers who run it, and practice the kind of transparency that builds a professional team.

One of the things I have never understood is the lack of transparency a lot of DSPs develop. Sometimes I feel that it is because they do not know how to own up to their mistakes. Sometimes it is the heavy control Amazon has on almost everything, and they buckle. They just keep working, unhinged, inside a flawed system, a flawed culture, or flawed operations.

The Logistics Master is independent of Amazon. I am not writing this to endorse a platform. I am writing it because drivers are still paying for routes that were never as easy as the stop count made them look.

They called it a nursery route

They call some routes nursery routes because they have few stops. That label can be misleading.

If the route is residential and full of apartments, and property management has not kept the signs, door numbers, or directions up to date, the driver will spend a lot of time just trying to figure out where to go. That is when the dashboard starts collecting mishaps: delivered to the wrong address, or never received. That is not a driver problem. It is tied to how the platform connects with property management, and to how those properties are actually being managed. The driver still pays for it.

Researchers who study last-mile work inside buildings have shown why a "short" stop can still eat the day. Germán Paredes-Belmar, Guillermo Latorre-Núñez, and Andrés Bronfman modeled the time it takes to finish in-building deliveries — the walking, the elevators, the waiting, the unloading — and found that those times change with the building, the time of day, and when the driver arrives. In the instances they solved, delivery time varied by 15 to 30 percent between off-peak and peak hours, and the order of the visits changed with arrival time. A review of urban last-mile vehicle routing by Reza Jazemi and colleagues made a similar point at the route level: compared with a classic routing problem, last-mile work in a city has more uncertainty and more change during the day, tighter windows, and service time at the door that is not always treated as part of the plan.

So a full residential route of nothing but houses is often more of a true nursery route than a low-stop route with a whole string of hiccups along the way. Those are two different jobs. The stop count does not tell you which one you handed someone.

The brain needs a chance to learn the route

To top it off, drivers rarely get the same route. Repetition is how the procedural part of the brain learns the work. Every time you get a new route, new problems show up. The clock becomes a problem again, and the pressure can create even more problems for the driver.

That is not just a feeling from the van. Paul Fitts and Michael Posner described skill learning as a move from a first, conscious stage, through practice, toward a more automatic one. John Anderson later described the same shift as knowledge moving from a declarative stage — facts you have to think through — into procedural memory, where the work is embodied in how you actually do it. In a systematic review of route familiarity, Ilse Harms, Bridget Burdett, and Samuel Charlton found that a familiar route reduces the sense of task difficulty and changes how much conscious control a person has to spend on the immediate environment. I am not saying a familiar route makes a driver careless. I am saying a new route is a new puzzle, and a repeated route can become a procedure. If you keep shuffling people, you keep them in the hard stage of learning, under a clock that does not care.

The software cannot see everything

We all know that software, including AI, builds a lot of these routes. It does not account for many of the things a driver actually walks into. A driver should have a way to edit the plan, or to teach the system where it is failing.

Mechanisms for that already exist. Amazon has said that when drivers encounter mapping issues, they can report them, and that its systems process that feedback. It has also said it is trying to reduce the number of steps in the delivery app. I have used the process. It is there. It still takes too many steps. A streamlined way to teach the system is necessary, because a report that is too slow or too buried might as well not be a report.

Coin the hard routes

Difficult routes need to be coined — named, labeled, treated as what they are. Once they are coined, specific drivers with the right attributes should be placed on them, with no time pressure. You tell them: just get it done the best you can, we will pay. It is a hard route already. Plan ahead.

Instead, in my experience, people get fired constantly trying to finish routes that should not have been built that way. I am not citing a public number. I am telling you what I have seen. And where such a route does exist, a cheat sheet should be in place — the notes that tell the next driver which entrance to use, which door numbers are wrong, and where the real problems are. A lot of DSPs do not know about those cheat sheets, or they will not use them, even though they would make the work better for the driver.

These are not things I have only noticed. I got proactive about them, as if I were an owner myself, and I built systems that organize routes as difficult or easy based on facts, not on what someone assumes is a nursery route. I will not invent a scorecard or a set of metrics for those systems here. The point is the approach: label the work honestly, then staff it honestly.

Transparency is a tool, not a slogan

Transparency is a powerful tool in business and for culture. DSPs that are aware of that, and that are proactive about it, build strong, straightforward, professional teams, and a safe place to call work home.

Researchers have been saying a version of this for years. Andrew Schnackenberg and Edward Tomlinson described organizational transparency as more than a vague promise. They framed it as disclosure, clarity, and accuracy, and they argued that those qualities support the trust people place in an organization. In a DSP, that can be as practical as saying: this route is hard, here is why, here is who is running it, here is how we will pay for the time it actually takes, and here is the cheat sheet so the next person is not starting from zero.

In the end, I believe that should be the foundation of every business: a form of exchange, not just an extraction system. A friend of mine has a hard way of putting the other version. He says some of these operations feel like "slave ships," with whip crackers and no real sense of leadership or innovation. That is his line, and I credit it to him. I will not dress it up, and I will not turn it into a spectacle. What I will say is this: people get up every morning and make the work possible. Leadership and innovation are how you honor that. A whip is not a culture.

Let's do better

People sometimes say there are over 4,000 DSPs in the United States, and that they are part of our community. I wanted to check the number before I repeated it. In April 2025, Amazon wrote that the DSP program had empowered 2,600 U.S. business owners. In September 2025, it described a global network of 4,500 small-business owners. I could not find a later official figure that confirms more than 4,000 DSPs inside the United States alone. However you count them, they are part of our community. That means they could be doing so much more to make a real community possible: through transparency, through synergistic operations, and through some intentional innovation. The DSP world could be, as they say, really cool, and inspirational.

Let's do better.

The Field Guide is free through December 31, 2026. DSP owners can begin on the DSP Owners page. And if you want to compare notes with other drivers and operators, join us in the TLM Discord.

Sources

Back to the blog