How a drink gets made
If we watch this video and break down what Mr. Boudreau does, we get a number of steps.
- Hear The Order
- Set Up a Mixing Glass
- Measure Whiskey
- Pour Whiskey
- Measure Vermouth
- Measure Amaro
- Pour Combo into Mixing Glass
- Add Ice
- Pour into Serving Glass
- Add Foam
- Add Bitters
Once we know what steps are involved in how a drink is made, we can represent them in a “waterfall” and see how steps play out over time.
The waterfall will immediately show us several things:
Some actions might be nested (Adding spirits is made up of other actions)
Some things might together or at the same time (Two spirits are added at the same time)
Some actions might block others (You can’t stir the drink until you add the ice)
Tracking the individual ingredients is a great step at monitoring how the drink is made, but what if we wanted to compare this waterfall to the waterfall of other drinks? We need to find a way to standardize our measurements even if the bartender does different things with different ingredients.
To track this process, we can use milestones.
- Drink Started: Gives patron feedback that order is started
- Spirits Complete: Are the bottles easy to find?
- Drink Index: Bartender says you could technically drink it
- Drink Complete: Bartender's job is done
- Drink Delivered: Is the drink hard to deliver to a table?
Once we have all this mapped out, what does it tell us? The more ingredients you have, in both number and volume, the longer it takes to finish.
How does this relate to web performance?
The standard way to represent how a website loads is with a waterfall. Here is an example of a waterfall generated by www.webpagetest.org.