For new DSPs · UPDATED 2026-10-15

What I wish someone had told me about the DSP world.

Start with the real work, give people support, and build a plan that can survive a difficult day.

If you are new to operating a DSP, I want you to have more than a list of metrics to hit. I want you to understand the work behind them. An accelerated ramp and revolving staffing doors make it easy to spend every day recovering from the last one. The time to build a few clear routines is before that rhythm becomes normal.

Learn a route before judging its pace Ask what the stop count leaves out. How many delivery locations are grouped together? How far is the route from the station? Where is parking difficult? Which buildings require a receiving process, a locker, or a walk beyond the entrance?

In Saint Louis, the Central West End, North City, medical campuses, and apartment-heavy areas need local context. Do not turn one driver’s experience into a blanket claim about a neighborhood. Learn the actual work and the actual constraint.

Put a person in charge of the learning A new hire should know who their trainer is and when somebody will check their progress. My training structure uses involvement across the first four weeks rather than treating the first ride-along as the whole process.

Make the basics clear too: attendance, scheduling, timekeeping, call-off procedures, conduct, and safety. A person cannot reliably follow an expectation they were never shown. Protect some time for the trainer to teach; a reference sheet cannot do the whole job alone.

Available is not always ready A name on a roster does not tell you the whole staffing picture. A parked van does not tell you the charging picture. A route assignment does not tell you whether the driver has the information they need.

Bring those checks together before departure. Record the gap, the person responsible for the next action, and when it will be checked again. That simple ownership matters when the desk gets loud.

Give quality events a follow-through A row in a spreadsheet is not the end of a quality process. Keep the event, its context, the supporting evidence, and the next action connected. Distinguish a coaching opportunity from a supported dispute. Missing evidence should be visible, rather than treated as proof that nothing happened.

Do not promise every dispute will be overturned or every automation will catch everything. Review what actually came in, what did not match, and what still needs a human decision.

Support needs a purpose Plan coaching and on-road support early. Tell drivers what help is being arranged and what you need them to report. Make a rescue a clear operational instruction, not a public judgment of somebody’s worth.

Recognize preparation, safe decisions, useful communication, and improvement. Motivation has a better chance when people understand the plan and see that their effort is noticed.

Leave the next dispatcher an answer At the end of a shift, write down the unresolved issue, the current status, and the next action. Give the next person enough information to continue the work without rebuilding the whole story from messages.

These are public starting principles, not my full operating playbook. If you want somewhere practical to begin, use the free peak checklist and time worksheet on this site. Build one routine your team can actually follow, then improve it with what the next day teaches you.