Case Study
Anheuser-Busch
Building a unified design system for one of the world's largest beverage companies, creating consistency across 500+ brands while preserving each brand's distinct identity.
The Problem
The MyCooler app — Anheuser-Busch's loyalty MVP already live on iOS and web — didn't represent the brand accurately or well. Built quickly as a beta, it had limited functionality, clunky interactions, and subpar readability and consistency. The core concept was genuinely compelling: loyal customers could scan purchase receipts to earn points, redeemable across physical touchpoints like bars, sporting events, and in-venue QR codes. But the application experience didn't match the ambition of the idea.
The challenge was compounded by brand complexity. Anheuser-Busch's portfolio spans Michelob Ultra, Budweiser, Stella Artois, and hundreds of sub-brands — each with distinct color systems, messaging tone, and content types. A design system that could accommodate all of them without becoming overwhelming or inconsistent required a clear architectural decision from the start.
When I joined, there was no documentation to work from — no brand guidelines, no asset library, no specification for how the MVP had been built. I was the lead and only designer on the project. I had to dive in and discover everything.
Current State Analysis
With no assets or documentation provided by the client, the first priority was a ground-up audit of everything the existing MVP contained.
Full App Walkthrough
I walked the entire application from create account and login all the way through answering onboarding questions and building a profile — mapping every screen, interaction pattern, and layout decision as I went. The visual audit revealed approximately 17 different colors in use, with around 8 navy variants alone. There was no consistent grid, no typography scale, and no token structure underlying any of it.
Information Architecture Mapping
Simultaneously with the visual audit, I mapped out the current information architecture and user experience flows — understanding how the navigation was structured, where friction lived, and how the app's sections related to each other. This ran alongside the visual work because the structural problems and the design problems were inseparable.
Accessibility Review
I reviewed contrast ratios across the app's existing color combinations. My hypothesis on the customer demographic — loyal Anheuser-Busch buyers, likely 35–60 — made accessibility a critical design priority, not a compliance checkbox. Ensuring readability and scanability for this demographic on mobile needed to be baked into every decision from the start.
The Core Finding
The app had been built without a structural foundation. No design system, no grid, no typographic scale, no token system. Every screen had been assembled ad hoc. Before any visual improvements could land, the underlying architecture had to be rebuilt from scratch.
Design Process
The work moved through a deliberate sequence: grid → typography → color → components → hi-fidelity prototype. Each layer had to be resolved before the next one could be built on top of it.
Grid System
I built a new grid structure from scratch, referencing standard breakpoints across mobile, tablet, and desktop. Containers were the priority — having a solid structural framework meant that every page and component could be assembled in a modular, adaptable way. This alone was an elevation over how the application had been functioning.
Typography
I selected a type system and worked through the atomic relationships — how the sizes fit together, what spacing existed between them, how white space could serve readability for the target demographic. The goal was a scale that a developer could build from precisely, not a loose collection of sizes applied by feel.
Color
I reduced the existing palette from 17 colors down to 9. Saturated, high-contrast primaries were chosen to both resonate with the Anheuser-Busch brand and visually distinguish the app as its own sub-brand — with an eye toward intriguing a younger demographic. The original brand colors were retained as accents, keeping the palette familiar to existing customers while giving the product a cleaner, more intentional visual presence.
Components in Sketch
This work was done in Sketch — Figma hadn't yet established its current reputation. That meant individually mapping every margin, column, padding, and spacing value by hand. The documentation was thorough enough that the Director pushed back at one point, saying I was spending too long on button states. My position was that leaving things open to interpretation during a build creates confusion; the detail was there so engineers could build with minimal oversight. He reluctantly agreed. The quality of what got handed off validated that call.
High-Fidelity Prototype: Referral Flow
The Director initially said not to build high-fidelity screens — we needed to deliver the system, not full comps. My view was that the client needed to see the components working together holistically to understand the direction and trust the decisions being made. I proposed spending a couple of hours putting together a referral flow — a specific flow the client had identified as important — to show how all the pieces came together. If the client didn't respond well, I'd drop it. The Director reluctantly agreed.
The following day, I walked the client through the documentation and the screens. The reaction was immediate — they said they could now see the direction clearly, understand how the colors were being applied, and read the design decisions holistically. Afterward, in the debrief, the Director told me it was a good call. Taking that initiative, going slightly beyond scope to build confidence and alignment with the client, was one of the more meaningful moments of the project.
The Solution
A complete design system built from the ground up: grid, typography, color, components, documentation, and templates — all specified with enough detail that engineering could build with minimal oversight.
Design System & Component Library
Ten major components delivered with full state coverage: default, hover, active, focused, disabled. Checkboxes, buttons, sign-up forms, dialog boxes, dropdowns — each documented with margins, spacing, color values, and usage notes for both mobile and desktop breakpoints. Every decision was annotated so there was no room for interpretation at handoff.
Design Tenets & Guidelines
A set of design tenets and system guidelines giving the client a framework for how to apply the system going forward — not just what was built, but the principles behind the decisions, so future designers and developers could extend the system without breaking it.
Information Architecture & Templates
Improved information architecture reflected in sign-up and onboarding templates — moving the app from its ad hoc structure to a deliberate, navigable flow. Pattern UI components and hi-fidelity wireframes provided a full reference set for building any area of the application.
Validation
High-Fidelity Prototype
The referral flow prototype served as the primary validation mechanism — taking the design system out of documentation and showing it applied to a real, client-identified user flow. The client's positive reaction confirmed that the color choices, component decisions, and overall direction were reading as both distinctly AB InBev and visually fresh. It aligned the team on what was being built before build decisions locked in.
Client Alignment Sessions
Regular client calls throughout the engagement — with the Director of UX at Wunderman Thompson, the client directly, and a second designer later brought onto the team — provided ongoing validation checkpoints. Having another designer ask questions during client calls filled in gaps that deep documentation work can create when you're too close to the details.
Retrospective
In hindsight, the project would have benefited from stepping back earlier to validate the core MyCooler concept itself — not just the design system. A one-week interview guide, one week of customer interviews, and one week of prototype testing around the receipt-scanning mechanic and physical touchpoint ideas (scanning a QR at a bar, a receipt at a stadium) could have surfaced whether the concept was valid before committing to the full build. The design system was elevated, but the more impactful question — whether customers would use it — was left unanswered.
Impact
The design system elevated the MyCooler product significantly — and the most tangible evidence of its durability came years later, not immediately after delivery.
The Budweiser app that emerged over subsequent years reflected the guidelines directly: the color choices, button types, input fields, form fields, and layout structure all followed what had been designed for MyCooler. Seeing those decisions carry through into a shipped, public product — without my involvement in the eventual build — was confirmation that the system was coherent and buildable enough to translate across teams and time.
- 17 colors reduced to 9 — a disciplined palette that balanced brand familiarity with visual clarity
- 10+ major components delivered with full state coverage and individual documentation for both mobile and desktop
- Structural foundation built from zero — grid, typography, color, and component systems where none had existed
- Client confidence established through high-fidelity prototype work that made the system legible before build decisions locked in
What I Learned
The detail matters — but knowing when to show the vision matters just as much. Delivering meticulous documentation builds engineering confidence. But taking the initiative to assemble those components into a real screen, over the Director's objection and with a clear read on what the client needed to see, was what actually moved the project forward. The two things together — rigorous craft and strategic communication — are what design leadership looks like.
Get in Touch
Like what
you see?
Let's talk about your next project.