Training Staff at a Brewery or Taproom: Style Knowledge Without Snobbery
Hey Team!
A guest walks up to your tap wall on a Saturday afternoon. Fourteen handles. They squint at the chalkboard and say, "What's good?" Your bartender says, "Well, the Mosaic IPA has an IBU of 65 and an original gravity of 1.062." The guest nods politely, orders a Bud Light from the bottle cooler, and you've lost the upsell before it started.
That's the training failure I see over and over in brewery taprooms. Staff who know the technical facts cold but can't translate them into something a regular human being finds useful. IBUs are a brewing measurement. They are not a guest experience. And the difference between those two things is the whole ballgame.
I spent a good chunk of time last year working through this with a team at several locations. Their situation was a little different, wine and food focused, but the same core problem showed up. Staff were memorizing spec sheets instead of learning how to describe what's actually in the glass. And guests were tuning out. The fix wasn't more information. It was better translation.
Here's the part that trips people up with beer specifically. The craft beer world has developed its own vocabulary, and a lot of people working in taprooms learned that vocabulary first. IBUs, SRM, ABV, original gravity, terminal gravity, mash temperature. That's the language of brewing. It's genuinely interesting if you're the one making the beer. But your guest on a Tuesday afternoon who wants to know if something is bitter or sweet? They don't speak that language and they shouldn't have to.
What actually works is descriptor drilling. Not memorization of numbers. Drilling on words that match what a guest is physically experiencing when they take a sip.
Take a West Coast IPA. Instead of "65 IBUs, dry-hopped with Citra and Simcoe," your staff should be able to say, "It's dry, kind of resinous, you'll get pine and a little grapefruit peel on the finish, and the bitterness lingers." That's the same beer. One version is a spec sheet. The other one is a conversation starter. And the second version is trainable with the right drills.
What I mean by descriptor drills is simple. You sit your team down with a flight. Four or five beers, styles spread out. You don't hand them a fact sheet first. You ask them to drink it and write down three words. Just three. What does it smell like, what does it taste like, how does it finish. Then you compare. You build a shared vocabulary. You correct when someone uses a brewing term instead of a sensory term and you push them toward the guest-facing language. Over a few sessions, your whole team is speaking the same dialect, and it's a dialect your guests actually understand.
At Fat Tommy's we did something similar when we expanded the draft program a couple years back. We went from six taps to twelve and I needed the bar staff to be able to walk somebody through the new additions without sounding like they were reading a menu. So we ran tasting sessions before service. Not lectures. Just beer, a notepad, and the question: "What would you tell your mom this tastes like?" That last part sounds silly but it works. It forces people out of their heads and into plain language fast.
Now, I'm not saying your staff shouldn't know the numbers at all. If a guest asks the ABV, they need that answer. If someone mentions they're sensitive to gluten, your team better know which beers are filtered and which aren't. Allergen and sensitivity knowledge is non-negotiable and it needs to be accurate every single time. But that's table stakes. That's the floor. Descriptor fluency is what separates good beer service from great beer service.
The other piece of this that doesn't get enough attention is style context. Guests who are new to craft beer don't just need descriptors, they need a reference point. "This is similar to what you'd find in a lot of New England IPAs, hazy, soft, tropical" does more work than a technically accurate style classification. You're meeting them where they are. You're giving them a map. And your staff can only do that if they've been trained to think in comparisons, not categories.
The training challenge is that style knowledge lives in people's heads unevenly. One bartender grew up homebrewing and knows everything. Another one came from a cocktail bar and is still learning the difference between a saison and a farmhouse ale. A third one is brand new. You can't run one training session and assume it landed for all three the same way. You need a way to test retention and find the gaps, and you need staff to be able to revisit the material when they need a refresh before a shift.
This is exactly what we built ShiftTrained around, getting the right questions in front of the right people on their phones without anyone having to chase them down with a printed sheet. But whatever system you use, the point stands: knowledge gaps in a taproom are expensive, not just in lost sales but in guest trust, and style knowledge is one of the most patchwork, inconsistently held skills in the building.
The goal isn't a team that sounds like a BJCP judge. The goal is a team that can make a first-time craft beer drinker feel smart for choosing the right pint. That's the training outcome worth chasing. Descriptors do it. IBUs don't.
Have a great day! — Terry
Your AI Restaurant Guy