(this is at a campus Dunkies where there's no drive-through, and I have a hard deadline to start my lecture. If there's no line at the register, and I've got five minutes before class starts in a room down the hall, it shouldn't take a logistical genius to get me a regular coffee in time for class)
Interesting to think about. Local coffee shop baristas are more transparent about what's brewed and enjoy taking the opportunity to recommend a certain roast or origin if I'm not picky. However, their systems fall down when they're unexpectedly busy.
My local cafe that does both coffee and sandwiches (dine-in, to go and catering) is possibly the worst, not taking orders until they feel caught up on the sandwiches. You can end up waiting 10+ minutes just to get a cup of coffee. From a queueing/distribution perspective, they should be taking those orders constantly and letting them pile up so they have more information about what they need to make and they can reduce the mean wait time. On the other hand, their baffling system is charming and the people placing large orders love the attention and spend way more money than I do. :)
Realistically this is your personal crusade and while you want Starbucks to change themselves for you, I doubt it would really move the needle at all on the sales slump they're having.
The queue management models that work for banks, grocery stores, and warehouses do not fit the highly interdependent plant operations of a coffee shop--Poisson doesn't cut it.
At any given time, there's a good deal of work contained in the "head cache" of the workers (lack of transparency) and orders are (largely) interdependent due to the limited throughput and cornucopia of wait-states of the components that process them.
For a better analog, look at the classic French "brigade de cuisine" system developed by Escoffier and watch videos of high-end restaurants during service.
Pay particular attention to the expediter and notice how there's specialization, redundancy in labor, and semaphoring to manage exceptions, wait-states, and accommodate the entirety of the workload.
Neither of those strategies can be utilized (at-scale) in a coffee-shop due to vastly different expectations of workload processing timeline, quality, variance, available labor, expected margin, and physical plant size.
A large fast-food restaurant is middle-ground between these extremes.
Is this true in a Starbucks? Every order goes into the computer before it's made, whether via the app or at the register. Or are you referring to something else more specific, like performing and recording the individual steps in making a speciality coffee?
axus•1h ago
Should probably add that in-store customers are third-class citizens; drive-through orders without customization get priority.