Comment

Comment by hackermailman

Mailman and software developer here. Of course all these problems can be fixed with a simple db that tells the delivery agent upon scanning any customer specifics like no safe dropping, go to rear door, ect. Weird individual access problems like gates or hidden doors could also be entered by agents to keep an up to date personalized delivery schedule. Right now the process is a bunch of cards that get lost and are outdated and take a lot of time to check for every delivery.

Agents should be able to see a complete overview of delivery that day, in order of route, and consistent metrics taken to better the service over time. Staffing could get weekly info of inbound parcels for each route and determine staff levels needed as compared to now which is just fly by seat of your pants. Of course CanPost who I work for don't do any of this, don't talk to any employees and make all these decisions far away from the people who have to implement them. The routes they design are ridiculous and nobody follows the official version. It seems trivial to solve since it's just a plaintext database and updates, plus talking to the agents to average time values and build efficient routes but for whatever reasons they don't even try. The DbaaS startup I work for remotely is constantly asking me ways they can improve, nobody at CPC has ever done so.

I was surprised when Amazon delivery appeared on the streets and they were run just as poorly as us, assumed they would 'disrupt' delivery instead of carbon copying an already bad service with UPS/Post/DHL ect.

parent hackermailman 10 years ago

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton