kindly
A UX case study focused on preventing dangerous allergic reactions in restaurants. 'Kindly' is a mobile tool designed to gives staff an easy-to-use filtering system to quickly identify safe menu options for customers with allergies.
(This is a concise overview. You can read the full, in-depth case study here.)

Overview
In the high-stakes restaurant industry, a single food allergy mistake can devastate a business. This project, initially inspired by my part-time work to create a staff training app, pivoted after in-depth interviews revealed a more critical issue. The true problem wasn't a lack of training, but the pervasive fear of accidentally serving a guest with a food allergy.
This insight shifted my focus entirely. I designed Kindly, a "Single Source of Truth" mobile app built to solve this specific problem. Instead of a general training tool, Kindly empowers employees to handle all allergy and dietary inquiries with speed and certainty. Its core feature, the "Safe Menu Filter," instantly identifies safe options, transforming staff anxiety into confidence and ensuring a secure experience for every guest.

"A single food allergy mistake is devastating. It puts a diner's health in serious danger and can ruin our restaurant's reputation overnight."
— Jimmy Chu, Restaurant Owner
"I saw an ambulance called for a peanut allergy at my last job. Now, every time a guest asks, that's all I can think about. I'm terrified of being the one to make that mistake."
— Tony Simson, Server

Information Architecture
User Flows and the Path to a Solution
To ensure our design addresses real user needs, I created user flows to visualize the journey through the most critical scenarios. I chose to highlight two key paths that demonstrate how the application solves the core problem for our primary personas: Tony, the server, and Jenny, the kitchen staff.
Flow 1: Handling a Severe Allergy Request
Scenario: A customer informs Tony they have a severe nut allergy and need a safe meal.
Impact: This flow eliminates the chaotic and time-consuming step of running back and forth to the kitchen. Tony uses the 'Filter Tool' to instantly filter and present safe menu options directly at the table. This process builds guest trust and empowers Tony to perform his job with complete confidence.
Flow 2: Ensuring Kitchen Accuracy and Safety
Scenario: Jenny receives a ticket for Pad Thai with a handwritten note: "Severe fish allergy, check sauce."
Impact: This flow shows how the app acts as the kitchen's "Single Source of Truth." Instead of guessing, yelling to the chef, or checking a binder, Jenny uses the app to look up "Pad Thai." She instantly taps the "Allergy Info" tab and verifies the standard sauce contains fish. She then taps the "Substitutions" tab, which gives her the clear, approved instruction to use the "vegetarian sauce base." This process removes all guesswork, ensures the dish is 100% safe, and stops a critical error before it ever leaves the kitchen.
Wireframing from Sketches to Structure
After defining the user flows, I translated the concepts into tangible layouts. I began with low-fidelity paper sketches to quickly brainstorm and validate core structures, focusing specifically on the complex 'Dish Detail' page and the critical 'Allergy Filtering' system. Once the basic layout was confirmed, I transitioned to digital mid-fidelity wireframes. This crucial step allowed me to refine the app's structure, establish a clear information hierarchy, and add all necessary components.












Early Usability Testing and Key Findings
Before the final visual design, I conducted an early round of usability testing on the mid-fidelity wireframes. This step was crucial for validating the app's structure and revealed several critical usability issues. Users confirmed that buttons were too small for a fast-paced environment, the core "Filter Tool" was not easily discoverable, and the path to finding specific "Allergy Info" was not intuitive. This valuable feedback directly informed my design iterations, and all of these key improvements were implemented in the final high-fidelity prototype to ensure the end product was genuinely easy to use in a real-world context.
Branding and Visual Identity
The brand identity for Kindly was designed to instantly communicate safety, trustworthiness, and warmth.
The logo itself reflects this mission by combining symbols of a 'wheat sheaf' and a 'peanut' to directly represent the common allergens the app helps manage.
The color palette builds on this trust, a primary Cool Green connects to health and safety, while a secondary Warm Orange represents food and friendliness, with a neutral Gray for readable text.
Finally, the General Sans typeface was chosen for its clear, approachable, yet professional feel. All these elements work in harmony to create a brand identity that users can immediately and wholeheartedly trust.

Design system
To ensure "Kindly" has long-term consistency and scalability, I built a comprehensive Design System. This system establishes all core visual foundations like Colors, Typography, and Iconography, and includes a full component library I designed, covering everything from Buttons and Cards to Navigation and Search. This system acts as a shared language for designers, developers, and stakeholders. It streamlines collaboration and speeds up future development, ensuring the product can evolve efficiently with a high-quality, cohesive user experience.















AI-Powered Solutions
While usability testing confirmed the app was highly useful, it also revealed two critical workflow problems.
First, owners called the initial manual input of every menu detail a "massive burden" and a barrier to adoption. To solve this, I designed AI-Powered Recipe Onboarding. Since every restaurant already has SOP files, managers can simply upload their PDF. The AI then parses the file, extracting all key data like allergy info, ingredients, substitution ,and cooking steps, which a human user verifies before the data goes live, turning hours of setup into minutes of review.
Second, testing showed the manual filtering process was too slow (18s). To fix this, I designed a Natural Language Query, allowing staff to speak a request like "no peanuts or dairy" and get a list of safe items in under 5 seconds, directly solving the speed issue.


RESTAURANTS
Manage menus
Get visibility
Pay subscription

DINERS
Search safe restaurant
Book table
Free+Paid
Learnings & Next Steps
Thank you for reviewing this work. I welcome questions and discussion.


















