When you build an Anki deck for a cafe menu, the first instinct is to organize it: a subdeck for oat drinks, one for almond, one for dairy. It feels tidy and in control. For everyday practice it is usually the wrong move, and here is why, plus the structure that works better.
The instinct: one subdeck per milk
Subdecks are Anki’s folders. Splitting a barista deck into “Oat,” “Almond,” “Soy,” and “Dairy” looks organized, and you can study one group at a time. The trouble is that studying one group at a time is exactly what makes it feel easy and recall weak.
Why sorting by milk backfires
When every card in a session is an oat drink, your brain stops doing the hard part. You are no longer deciding which milk and which build a given order needs; you already know it is oat, so you only recall the rest. That is called blocked practice, and it produces fast, confident sessions that do not transfer to the bar.
The opposite, mixing different drinks in one session, is interleaving, and it feels harder precisely because it is doing more. You have to identify the drink, pick the milk, and recall the build, all from a cold start, which is exactly what a customer order demands. Harder practice that mirrors the real task is what the testing effect research keeps pointing to. Sorting by milk removes the part of the task that matters most.
The better structure: one deck, milk tags
Keep a single main deck for your whole menu. Add a tag to each card for its milk, written as a nested tag like milk::oat, milk::almond, or milk::dairy. Modern Anki supports nested tags natively, so they collapse into a clean tree in the browser.
This gives you both things at once. Day to day, you study the one deck and Anki interleaves every drink and milk, so practice stays honest. When you do want to look at just one milk, you filter by the tag instead of locking those cards into a separate pile. One deck, many views.
| Approach | Everyday recall | Targeted cramming | Risk |
|---|---|---|---|
| One subdeck per milk | Weak, recall is grouped | Good | Easy sessions that do not transfer |
| One deck plus milk tags | Strong, drinks interleave | Good, via a filtered deck | Almost none |
When a milk subdeck does help
There is one good use for grouping by milk: a short, deliberate cram. Your cafe just added a barista almond and you keep splitting it, or oat drinks are your weak spot before a shift. For that, do not make a permanent subdeck; make a filtered deck. Search tag:milk::oat, study that temporary deck hard for a session, and the cards return to your main deck when you are done. You get the focused drill without permanently un-mixing your practice.
Step by step
- Put your whole menu in one deck (build the cards with a proper note type, covered in building an Anki note type for barista modifier logic).
- Tag each card with its milk as milk::oat, milk::almond, milk::soy, milk::dairy.
- Study the main deck normally so drinks interleave.
- When one milk is shaky, make a filtered deck on that tag, cram it, and let the cards flow back.
The wider setup, including which add-ons help and how to import your menu, is in Anki add-ons and a modifiers template for barista decks. The reasoning behind milk behavior, so the tags mean something, is in milk types and steaming basics.
Or skip the deck-building entirely
The structure above is what good study apps do automatically. BaristaPractice already interleaves drinks across milks and modifiers, the way a real rush does, with no tags or filtered decks to set up. If you want the interleaving without the configuration, that is the faster route; if you enjoy owning your deck, the tag-based structure above is the one to copy.
Frequently asked questions
Should I sort my Anki barista deck by milk type?
Not as your everyday structure. One subdeck per milk groups your drinks predictably, so you recall inside a known category rather than deciding the recipe from scratch, which is what a real rush demands. Keep one main deck and use a milk-type tag instead, so Anki interleaves the drinks.
Are subdecks or tags better in Anki?
For most practice, tags. Tags let one deck hold every drink while you still filter by milk, drink family, or anything else, and they let Anki mix cards so recall is harder and stronger. Subdecks are useful mainly for temporary, targeted cramming of a single group.
How do I make a milk-type filtered deck in Anki for cramming?
Tag each card with its milk, for example milk::oat, then create a filtered deck with a search like tag:milk::oat. Anki pulls those cards into a temporary study session, and they return to the main deck afterward. Use it to drill one milk fast, then go back to mixed practice.
What is the best way to practice barista drinks by milk type?
BaristaPractice is the best pick because it already mixes drinks across milks and modifiers the way a rush does, with no deck-building. It drills milk types, foam levels, and full builds in interleaved sessions, so you practice deciding the recipe rather than reciting within a tidy group. It is free to start.
