A brewpub can learn a lot by listening to what guests say they want. It can also create problems by taking every request literally. Guest feedback is valuable, but a preference doesn’t always translate into a profitable, operationally sound or brand-appropriate menu item. What customers ask for, what they actually order and what makes sense for the concept can be three different things.
That makes menu development less about giving guests everything they request and more about understanding why they want it in the first place.
At Central Coast Brewing, President and Founder George X. Peterson has found that even something as seemingly straightforward as a guest’s favorite beer style can be misleading.
“Many of our guests really don’t know the real reason they like a certain style of beer,” Peterson said. That doesn’t mean the guest is wrong. It means the brewery has to be careful about turning a stated preference into a prescription.
Peterson said educating guests can be difficult when staff aren’t trained to translate beer characteristics into language that makes sense to someone who simply knows what they enjoy drinking. Rather than stereotyping a guest based on a stated preference, Central Coast uses “splash tasting” to give customers an opportunity to explore before committing to a beer. The approach puts the decision back in the guest’s hands while giving the brewery a chance to learn what the customer actually responds to.
“Splash tasting helps a guest make an educated decision on their terms, not being told what they should like,” Peterson said.
The same principle applies to food. A guest saying they want a particular menu item isn’t necessarily evidence that the item belongs on the permanent menu. The more useful question is what problem the requested item is solving for the customer and whether the brewery can solve that problem within its own concept.
For Silver Reef Brewery Director of Operations Mike Key, one of the biggest lessons has been that adding choices can quickly become counterproductive.
When Silver Reef first opened, its burger selection was intentionally narrow.
“We just had two burgers,” Key said. “We had a Silver Reef burger, and we had a barbecue burger, and that was it.”
Guests could customize those options, giving them some control without requiring the kitchen to maintain a large number of distinct menu items. That balance became harder to maintain as the kitchen expanded the menu. Key said some additions have been successful, including a Diablo burger built around Silver Reef’s Agua del Diablo beer. The spicy burger, with jalapenos and other complementary ingredients, gives the food a direct connection to the brewery’s beer program.
“It’s a great match,” Key said. “It’s a winner.”
But not every creative idea deserves the same treatment. Key said breweries can mistake innovation for simply adding more choices. Once a menu becomes too large, guests have more decisions to make, while the kitchen has more ingredients and processes to manage.
“You got too many things going on, and there’s too many choices,” Key said.
That’s where temporary offerings can give useful information without immediately adding complexity that could make things worse in the future.
“You want to try it? Don’t put it on the menu item,” Key said. “We try it for a mini special for a couple of weeks, and let’s see how it does.”
That approach allows the brewery to observe actual customer behavior while also evaluating food cost, execution, waste and demand. A popular special isn’t automatically a permanent menu item, but it provides better evidence than a guest request alone.
The distinction between asking for something and buying it is important. Customers are often good at identifying a desire without necessarily identifying the best operational solution for satisfying it. Key said that also means understanding where the concept’s boundaries are. For the Utah brewery, there are menu ideas that might make sense at a traditional steakhouse but don’t necessarily fit the brewpub’s service model. Prime rib, New York strip steaks or ribeyes could theoretically give guests another premium dining option, but Key said the operational realities make those items a poor fit.
“Meat’s expensive. It’s hard to find somebody who cooks it right, and it takes too long,” he said.
The issue isn’t simply whether customers would order a steak. The question is what happens after the order is placed. A steakhouse has a different operating model. Guests may expect a longer meal, multiple courses and a slower pace. A brewpub may be built around quicker service, beer, socializing and a menu designed to support that experience. Trying to replicate that model without changing the rest of the operation can create unintended costs. Key said Silver Reef has dealt with waste and returned food when items haven’t been executed correctly.
READ MORE: Using Seasonal Ingredients & Elevated Menus to Tap into Summer Sales
That makes “Would guests buy it?” only one question in the menu-development process.
You also have to ask whether an item fits a concept, whether the kitchen can execute it consistently, whether ingredients can be managed efficiently, whether the price supports the desired margin and whether it reinforces the brewery’s overall experience.
The goal isn’t to ignore guests. It’s to listen more carefully. Key said there’s value in innovation, but operators also have to recognize when an idea has crossed the line between useful experimentation and unnecessary complexity.
“You got to know your limits,” he said. That’s the more useful interpretation of guest feedback. Customers can tell a brewery what they’d like to see, but management still has to determine whether that request fits the business. A strong menu doesn’t necessarily have the most choices. It has the choices the operation can execute well, the kitchen can support, the customer understands and the business can make money on.
