← All projects
Case Study 2026

CookUnity
Chef Portal

Giving chefs a clearer way to manage their dishes — one source of truth to see what's live, what needs attention, and how every dish is performing.

UX Research Product Design Design System SaaS Dashboard
A chef holding a tablet showing the CookUnity Chef Portal Portfolio dashboard in a professional kitchen

Overview

CookUnity chefs did not have a centralized place to understand which dishes were live, inactive, or underperforming.

Each chef managed their own tracking through spreadsheets, notes, and internal conversations. The information existed, but it was scattered and difficult to act on.

“I never really knew which of my dishes were trending or why certain ones were being taken off the menu.”

From a chef interview
A chef reviewing the My Portfolio dashboard on a tablet at a kitchen pass

Chef Portal · Portfolio in context

The challenge

Design a clear and scalable experience where chefs could quickly understand:

  • What was live
  • What needed attention
  • How each dish was performing
  • What action to take next

The goal was not to show more data, but to make the existing information easier to understand and use.

The hypothesis

If chefs had a single source of truth for their dishes, they could manage their portfolio more proactively, reduce manual tracking, and depend less on internal teams.

A Sweet Chili Chicken dish with an in-app card showing Live Menu status, average rating and today's performance

01 — Status

See what's live
at a glance

Every dish carries a clear state — Live Menu, Active, On Hold or Archived — so chefs instantly know what customers can order right now, without cross-checking a spreadsheet.

A Steak Chimichurri dish with a Top Rated card showing a 4.8 rating and a top 10% performance score

02 — Performance

Understand how
each dish performs

Lifetime rating, recent trend and percentile sit right on the dish — surfacing the top performers and the ones slipping, so chefs know where to focus.

Research and testing

We interviewed chefs and internal stakeholders to understand how they were tracking their dishes and where the main friction points were.

We then tested the first design concepts with users to validate the structure, dish states, labels, and information hierarchy. The feedback helped us simplify the experience and make status, performance, and actions easier to understand.

A chef talking through her portfolio during a research session
A chef reviewing his dishes and Playbook status on a tablet

Concept testing with chefs across cuisines

The solution

We created a centralized Portfolio section inside the Chef Portal where chefs could:

  • View all their dishes
  • Understand their current status
  • Review key performance information
  • Identify what needed attention
  • Access relevant actions
COOKUNITY Portfolio Last sync · today
Total SKUs
40
Live Menu
35
Active
15
On Hold
02
Archived
13
Subscription
07

The at-a-glance portfolio header

The outcome

This validated the initial hypothesis: chefs needed a clear and actionable way to understand and manage their dishes. The initiative increased visibility and autonomy for chefs while creating a stronger foundation for future performance and growth features.

Portfolio became one of the most visited sections in the Chef Portal.

CookUnity · Chef Portal

Let's turn your idea
into something real.

Start a Project