What you should be able to do
- Ask efficient discovery questions.
- Prioritize order accuracy during rush periods.
- Use repeat-back and modifier confirmation.
- Handle complaints as structured recovery events.
Discover without interrogating
Useful questions are short: hot or iced, milk or black, sweet or not, strong or gentle, familiar or adventurous. Ask only what changes the recommendation.
Repeat-back discipline
Repeat size, temperature, milk, sweetness, extra shots and any critical modifier. A ten-second confirmation can prevent a remake and protect allergy-sensitive orders.
Rush-hour prioritization
Use clear roles, ticket sequencing, batching only where quality is protected, and visual station organization. Speed comes from removing wasted motion and rework—not skipping quality controls.
Handoff and identification
Use a consistent handoff method so drinks go to the correct guest. In busy environments, ambiguous calls create service errors even when the beverage itself is perfect.
Complaint recovery
Listen, clarify the issue, acknowledge the experience, remake or resolve within policy, and capture recurring issues. The goal is not to win an argument; it is to restore service while learning from the failure.
Inclusive recommendations
Avoid assumptions based on age, appearance or background. Recommend from stated preferences and product facts. Be clear about caffeine, allergens and ingredients without making medical claims.
Apply the lesson
Run a five-minute rush simulation with ten mixed tickets. Track order accuracy, remake count and average completion time. Identify one layout or communication change that would improve throughput without lowering quality.
Open Coffee Lab ↗Test your understanding
Pass at 70% or higher, then mark the module complete. You can retry as many times as needed.
Progress is stored locally in this browser. Completing a module does not issue a formal certification.