01 FastBites OMS
I hate that I have to use so many different apps to manage my restaurants, I wish there were a more reliable app.
FastBite's order management system serves three connected touchpoints, a customer-facing ordering site, a staff operations dashboard, and an owner-level records and analytics platform.
All three had gone largely untouched for over a decade. FastBite brought us in to redesign the full system, with the goal of improving usability, operational efficiency, and the end-to-end experience for every user type.
Role
Lead UXUI Research
Duration
2 months
Client
FastBite
Team
StackBlue
Software Used
This was the largest project I took on at StackBlue, three distinct products under one system, each with its own user base and workflow. Scoping the work properly was just as important as the design itself. I leaned heavily on project management to keep the research organized, prioritize the right problems across all three platforms, and make sure nothing slipped through the cracks.
Customer Ordering Platform:
I used the ordering site as the entry point into the larger system; it was the most straightforward of the three, which made it a good place to establish design patterns and build momentum. The focus was on simplifying the information hierarchy so customers could move through the ordering flow with less friction. I also reworked the order history and account sections to cut redundancy and make past orders easier to find and reference.
I looked at six platforms across two categories to understand the landscape. On the customer-facing side, I analyzed Uber Eats, DoorDash, and Grubhub; these set the bar for how users expect to browse menus, place orders, and track delivery status.
On the operations side, I studied Foaps, MarginEdge, and UpMenu to see how restaurant staff and owners manage incoming orders, inventory, and multi-location reporting.
The goal wasn't to replicate any single competitor but to identify patterns that worked well across both sides of the experience and find gaps where FastBite could differentiate; particularly around giving restaurant operators more control without adding complexity.
Staff OMS:
The staff-facing dashboard needed to support fast decision-making in a high-pressure environment. Knowing that many kitchens rely on tablets and large mounted screens, I designed around glanceability; color-coded status indicators on each order so staff could read the state of things without stopping what they're doing. When a deeper look was needed, the order detail view used oversized tap targets and large content cards to keep interactions fast and low-effort. I also built in analytics views for shift leads and managers to track performance at the restaurant level.
Owner RMS:
The owner platform gives multi-location operators a single view into analytics and order data across all their restaurants. In my audit of the existing system, I found a lot of redundant pages and bloated menu structures housing long, unsorted lists. I simplified the navigation and consolidated views so owners could monitor individual locations or compare across their portfolio without digging through unnecessary layers.
Project Takeaways:
Two months wasn't enough time to fully address every issue across three platforms.
Given more time, I would have conducted foundational user interviews and tested against the existing system before designing, then run usability testing after the redesign to validate decisions.
That said, the constraint pushed me to prioritize ruthlessly and focus on the changes that would have the most immediate impact.
Please Scroll
