I've read a fair amount of what people think should be done (theory) but haven't found a ton of content from people who actually have done it (practice)
I've read a fair amount of what people think should be done (theory) but haven't found a ton of content from people who actually have done it (practice)
4 comments
- Guy owns a wholesale bakery that delivers to restaurants
- They do one delivery a day in the morning to each of their customers
- The options were to hire their own drivers or outsource to a delivery service.
The bakery owner points out that while it's cheaper to use the delivery service, there are a couple downsides:
1. He doesn't "control" the customer experience around the delivery b/c it's a 3rd party
2. If a customer has feedback on a delivery, it's less likely to get back to the baker owner b/c the service driver isn't incentivized to pass that back up the chain
I say all of this as someone who LOVES automating things btw. Engineers can be too focused on automation though and that can lead to worse overall customer experiences even if there are short term wins.
0 - https://www.youtube.com/watch?v=eKGNctKpx8w
I would recommend decomposing and prioritizing:
If you can eliminate small task and in return larger delivery process gets automated, then it might be more beneficiall then fighting on automating large complex process