Case study04 / 04
ClientSATIS.AI
Years2022 — 2023
RoleSenior Product Designer · Design lead
DomainOperational intelligence · Multi-tenant SaaS

Quality Score,
made legible.

— Thesis

How do you turn a constant stream of AI signal into a single number — one that a regional manager, a franchise owner and a corporate exec can each act on, at three different latencies?

Two laptops showing brand-level Quality Score dashboards with comparison charts.
— Product

Quality Score — brand audits at your fingertips.

A real-time, AI-powered scorecard that compares back-of-house performance across an entire restaurant estate — without anyone having to visit a single kitchen.

Instantly view and compare how each back-of-house is performing, with unparalleled, authentic AI-powered data and insights.

SurfacesGlobal · Brand · Store dashboards
AudiencesRegional Manager · Franchise Owner · Corporate
LatencyDay · Week · Quarter
UnderlyingCV inference per station, rolled up
— 01 / Context
Why a score, not a feed

The kitchen never stops talking. The operator needs one thing to look at.

A streaming signal is only as good as what it lets a manager do.

By 2022 the SATIS.AI camera and inference stack was producing tens of millions of events a week across multiple kitchens. The Packing Order Accuracy work (case study 01) made that signal useful to the crew on the line.

This case study is about the other direction: rolling that signal up. Turning hours of streaming inference into a single Quality Score per store, comparable across a network of franchises — readable in three seconds.

Fig. 02  ·  The opening view Compare back-of-house, across the estate
Three pillars stitched into one product
Quality Score & Insight overview — a laptop showing a comparison dashboard across kitchen sites.
— 02 / Audiences
Three personas, three time-scales

Same number, three completely different jobs to be done.

The hardest design move was not the dashboard. It was deciding which version of reality each role got to see.
↳ Interviewed three of each across UK & US operators.

Quality Score had to serve three audiences who almost never see the same screen in real life. A regional manager living in a day, a franchise owner living in a week, a corporate exec living in a quarter. Each of them wanted “the score” — and each of them meant something completely different by that.

Persona 01

Regional Manager

Lives in a day. Manages 4–8 stores in close proximity. Wants to know what to fix this shift.

Latency: Hours · Action: corrective
Persona 02

Franchise Owner

1–3 stores, eyes on margin. Wants to know how each store is trending and where the gap is.

Latency: Days · Action: investigative
Persona 03

Corporate

Group-wide. Wants to know whether the system is working — and which brands and regions are pulling their weight.

Latency: Weeks · Action: strategic
Fig. 03  ·  Audience model from research Original from the brief
Target audience card row: Regional Manager, Franchise Owner, Corporate — with the questions each one needs answered.
— 03 / Pillars
How a score gets made

Capture, compute, decide.

The pillars are the contract between the CV team and the user. They're also the place trust can break the most quietly.

Three pillars hold the product up: AI-powered data capture (the camera and inference stack), Quality Score calculation (the rollup logic) and Decision Making (the surface that turns the score back into a decision a person can sign off on).

The hardest design problem sits in the middle pillar — it's where probabilistic events become a deterministic-looking number. Every design decision in this case study lives in that translation.

Fig. 04  ·  Three pillars AI capture · Score calculation · Decision making
From the working architecture
Three numbered circles: 01 AI-Powered Data Capture, 02 Quality Score Calculation, 03 Decision Making — each with their underlying inputs.
— 04 / Goals
Support · Visibility · Action

Three legs of the same stool.

Each goal is the one the others fall over without. None of them is enough on its own.

The product goal split into three: support the day-to-day of an efficient kitchen, give franchise owners visibility into what's happening across their stores, and make sure that visibility translates into action — not just dashboards.

Fig. 05  ·  Goals & Objectives From the project kickoff
A three-step linked diagram: Support → Visibility → Action, with one line of explanation for each.
Fig. 06  ·  KPI · Risks · How might we The team contract
A three-column strategy board: KPI (number of unique visits, length of stay), Risks (too many analytics platforms, insights not translating into action), HMW (overall performance of audience, collect management, store level insights).
— 05 / System
A modest visual contract

The palette and the voice.

A small, calm system — chosen because the product was about to ship a lot of numbers.
↳ Headline · Public Sans · Semibold. Body type adopted from the SATIS.AI core system.

The visual system stayed restrained on purpose. A primary SATIS green for affirmative state and a small secondary palette of category colours for state/severity. Public Sans for type, set tight at headline weights, looser at data densities.

Numbers had to do most of the talking. Anywhere a colour appeared, it had to mean something.

Primary#18A256
Ink#18181B
Paper#FFFFFF
Lift#B6E7C9
Alert#E0563D
Insight#2B58D3
Caution#F2B82E
Wash#F2EAD3
Fig. 07  ·  Style guide Colour, type, secondary palette
The Quality Score style guide showing primary and secondary palettes, Public Sans typography sample.
— 06 / The solution
One number, three views

The same score, drilled three ways.

Drill-down was more important than discoverability. Each persona had to be able to start where they needed to start.
↳ Global → Brand → Store, with the score visible at every level.

Quality Score lives at three resolutions. The Global view rolls every brand and every store into a comparable trend. The Brand view drops one level — comparing stores within a brand on the same axes. The Store view drops the final level — what happened on the line today, why the score is what it is, and what to fix.

Every view shows the same score in the same place — so people who travel between roles never lose their footing.

— Level 01 / Global Global Audience: Corporate

An overview of every business at a glance. Average quality score across each brand — one place that holds the operation in your head.

The Global level of Quality Score showing every brand and aggregate trends.
— Level 02 / Brand Brand Audience: Franchise Owner

Diving into one brand-level overview — comparing different aspects of quality score, mapping it possible for the regional manager or the business owner to see where they're falling.

The Brand level: two laptops showing brand-level quality score breakdowns and trends.
— Level 03 / Store Store Audience: Regional Manager

The deepest insight: a particular store. Kitchen managers, franchise owners and business owners can get a comprehensive understanding of that specific location, with an in-depth review and insight of cases and operations, even to the tiniest ingredient in the kitchen.

The Store-level view: a focused single-site Quality Score readout with operations breakdown.
— 07 / Patterns
Inside the surface

Six small moves that did most of the work.

— Pattern 01

One score, always visible.

The same number sits in the same place at every level. Drill-down never disorients — the headline doesn't move.

— Pattern 02

Time is the x-axis, always.

Every chart, every view, every report. Comparison happens on time first, and on category second.

— Pattern 03

Cohort, not leaderboard.

Stores compare to their cohort, not to global. A small franchise isn't graded against a flagship.

— Pattern 04

Why, in one click.

Every score is one click away from the events that produced it. No black-box scoring.

— Pattern 05

Quiet greens, loud reds.

Good is calm. Bad is colourful. The dashboard is almost monochrome on a healthy day.

— Pattern 06

Action at the bottom.

Every insight surface ends with one specific next move. Visibility without action is what we were replacing.

— 08 / Outcome
What happened when it landed

A single number that three roles could agree on.

The win wasn't the dashboard. It was the conversations the dashboard replaced.
↳ Numbers approximate, anonymised, representative of platform signal at exit.

By 2023 Quality Score had been adopted across multiple operators in both UK and US, and was being used in pre-shift meetings, franchise QBRs and corporate board decks — the same number, in three different rooms.

The product became the spine of the SATIS.AI commercial story — not because of the model, but because a corporate exec could finally see what a regional manager had been telling them for years.

— Time-to-decision
38%
Regional managers, from first signal to first action, post-rollout.
— Estate visibility
3 levels
Global · Brand · Store — one product, one number.
— Brand audits
site visits
Estate audits became dashboard reviews — not plane tickets.
— Roles served
3 audiences
Regional manager · Franchise owner · Corporate — one screen.
— 09 / What this taught me
About designing AI for management

What it taught me about decision design.

— Lesson 01

A single number is a UI surface, not a calculation.

Most of the work was deciding what the score looks like, not how it's computed. The model was the easy part. The score was the hard one.

— Lesson 02

Drill-down beats discoverability.

For a multi-role product, never make people search for the right level. Start every persona at their level — and let drill replace navigation.

— Lesson 03

“Real-time” is the wrong frame. “Right-time” is.

A daily score is real-time for a regional manager. A weekly score is real-time for a corporate. Designing latency is more important than designing the chart.

— Lesson 04

Insight without action is a tax.

Every dashboard surface ends with one explicit next move. Otherwise you've built a thing people scroll, not a thing people use.

— 10 / Continue ↳ Next in series