A Case Study by Elizabeth Kupchella

Roles: UX Design | UX Research | Graphic Design

Resources: Figma | Canva | In-Field Ethnographic Research

The Obstacle

the

The existing cocktail recipe resource from my hospitality group was slow and inefficient, taking 17–20 seconds to access a single recipe, which is far too long for use during busy service.

Its structure also made it difficult to quickly scan or search, slowing down workflows behind the bar.

Opportunity

the

I couldn't help but wonder if there wasn't a faster, more intuitive tool tailored to working bartenders.

Like generations before me, I asked myself that one little question every woman in her mid-twenties must face:

How might we design a recipe index that reduces load time and supports fast, in-the-moment decision-making during service?

The Approach

the

I prioritized speed and usability in developing bartender-friendly information architecture like this:

1.5 oz X

0.75 oz Y

.25 oz Z

I focused on rapid prototyping, user testing with industry peers, and iterative improvements based on performance benchmarks.

PROCESS

the

To structure my case study, I used the Hasso-Plattner Design Thinking Framework, which breaks down the design process into five steps:

#1

#2

#3

EMPATHIZE

DEFINE

IDEATE

#4

#5

PROTOTYPE

TEST

Empathize

While Shake+Strain was inspired by my personal bartending experience, I intentionally stepped outside my own perspective by onboarding a first-time bartender at my day job –– an opportunity that served as an extended empathy interview and informal ethnographic study.

Watching someone navigate back-of-house systems for the first time helped me reset assumptions and refocus the design from 'what would I need to do this job more efficiently?' to 'what would anyone need to do this job efficiently?'

Define

With primary research in hand, I prioritized solving key user pain points:

Replacing long recipe narratives with bartender-friendly information architecture as mentioned in my initial approach
A progressive enhancement style design that gave users the option to explore information like cocktail history deeper if they want to, but displayed key info first.

Sample user persona

User Persona: Jason Charles

Name: Jason Charles
Age: 28
Race: Black
Education Level: High School Diploma (with professional certifications in Hospitality)
Languages Spoken: English
Family Status: In a long-term relationship
Occupation: Bartender at a high-end cocktail bar

"I need an app that’s as quick and efficient as I am behind the bar. The last thing I want is to waste time fiddling with an app while the orders pile up."

GOALS

Fast Access to Recipes:

Jason wants an app that allows him to quickly search and access verified recipes, especially when he's under pressure and working at high speed.

Customization for Professional Use:

Inventory changes all the time. Jason wants to be easily able to submit a spec change within the beverage index to be approved by his beverage director.

FRUSTRATIONS

Slow or Unresponsive Apps:

During peak hours, Jason needs quick access to a recipe. Slow or laggy apps waste valuable time and make him lose focus on his customers.

Inaccurate or Outdated Recipes:

He dislikes apps with recipes that don’t always match up with standard measurements, ingredients, or techniques used at his bar.

Jason is detail-oriented and highly focused when it comes to his craft. He thrives in high-pressure environments and loves the fast-paced nature of bartending. He's all about delivering perfection quickly and efficiently, and values tools that help him maintain that level of service.

Ideation

wireframe snapshot

Drawing from user themes and personas, I brainstormed key features for a mobile beverage index, including:

Replacing long recipe narratives with clear, concise overviews
A quick-search bar for time-sensitive recipe needs
Progressive information architecture that offers depth without overwhelm
Customization for specific hospitality teams, allowing easy updates and feedback tied to inventory

Design System Selections

Prototype Snapshot

In the prototype phase, I explored Figma DevMode to enhance the accessibility of the app. For example, I added alt text as an annotation for icons and images like this one.

Testing

that's
2.5× faster!

In comparative usability testing, SHAKE+STRAIN both reduced cognitive load and streamlined the search experience.

Participants were able to locate a Black Manhattan recipe in an average of 7.5 seconds, compared to 18.5 seconds using a mobile web search.

That's a 59.5% improvement in task efficiency, indicating a significantly more intuitive and purpose-built experience for users seeking cocktail information.

Demos

In addition to usability testing, I demoed the app directly to stakeholders across my hospitality company: service directors, the Director of Information Technology, Senior Executive beverage leadership, and eventually one of two co-founders of the multi-million dollar hospitality group.

These sessions provided valuable, real-time feedback that shaped feature prioritization and helped validate the app’s relevance and potential impact across departments,

Takeaways

#1

Accessibility isn’t a test; it’s a mindset.

I initially built the design without checking color contrast, which led to unnecessary rework. It was a valuable reminder that accessibility must be prioritized from the start to ensure the product works for all users.

#2

Subject matter expertise is a bonus, not a bypass

When I wrote this case study in fall 2024, I prioritized speed and aesthetics, assuming my own use of such a tool each day at my bartending job served as adequate UXR.

Revisiting this case study in August 2025, I nearly scrapped it out of embarrassment until I realized I'd much rather be the colleague who can name, own, and grow from their mistakes than the one who pretends they never make them.

That's why, moving forward, I'm committed to treating subject matter expertise as a bonus, not a shortcut.

I might've learned it in a cringe-worthy way that I know (and hope) my future colleagues will call me out for –– but I learned it.

What would you do differently?

I'm constantly trying to be a better UX Designer than I was yesterday.

Whether or not you're a professional UX Designer, I want this case study to make sense to you. Any insights or feedback you have to help get me there are always welcome at elizabeth@kupchelladesign.com.