I’m Draya.
This is why I care.

The ramp was accelerated.
The learning was real.

My dispatch story includes a fast ramp, revolving staffing doors, demanding routes, and a team trying to keep the work moving. It includes insurance claims and workers’ compensation coordination, attendance, completion pressure, driver conflict, and the constant need to protect motivation.

It also includes building. I have developed training, area references, attendance and loadout automation work, quality tracking, dispute workflows, route-feasibility analysis, and peak support planning. They grew out of practical questions: what are we missing, who needs help, and how do we make this easier to follow?

“If we are talking about treating them better and listening to their concerns, we must pay attention.”

The part I carry with me.

I love my drivers. I feel the frustration of seeing an obstacle coming and not always having the power to remove it. The stress and anxiety are real, but so are the happiness, humor, and pride in helping people learn. I want those parts of the work to have a place here too.

Writing letters, gathering evidence, and asking for context to be considered are part of that care. This site shares what those efforts teach me while keeping private case records and personal details out of the conversation.

Saint Louis deserves local attention.

I worked on a similar Saint Louis rollout before our current city-area work. Central West End, North City, medical campuses, apartments, and grouped stops have reinforced the same lesson: understand the place and listen to the driver before deciding what a number means.

And some of it became a book.

I wrote Smile! You’re on Camera (...and probably fired). The book and this site make room for the people, pressure, and humor of delivery. Meet the book →

The victories I can stand behind.

I have created a four-week trainer structure, ride-along and progress review materials, references for difficult delivery areas, and workflows that connect quality events to follow-up. I have worked to bring route context into conversations about performance. A system being built is not a guarantee that every process is fully solved; refinement is part of the work.

Why this space exists.

Owners need useful tools. Dispatchers need people who understand their day. Drivers need clear expectations and support. Amazon management needs to hear what is happening beneath the metrics. This is a place for those conversations to meet.

I am also studying digital marketing, so I care about communicating the work as clearly as I care about organizing it. I want this site to make a useful lesson easy to find, a good question easy to ask, and a better next step possible.