design exercise

Designing loyalty for owners with zero time.

COMPANY
COMPANY

Confidential · Selection exercise

Confidential · Selection exercise

ROLE
ROLE

Product Designer

Product Designer

Product Designer

EXPERTISE
EXPERTISE

UX · Product thinking

UX · Product thinking

YEAR
YEAR

2026

2026

Project description

Project description

The brief

A take-home exercise for a Product Designer selection. Design "Fidelity": a new section of an existing SaaS dashboard that lets independent restaurant owners build and run loyalty programs for their customers. No specs, no internal benchmarks. Just the product context and a reasoning process from scratch.

The product

A SaaS suite for independent restaurants, already covering social, advertising, CRM, menu, website, newsletters and reservations. Its users are owners and managers, often not tech-savvy, looking for simple tools to grow. Fidelity is the missing piece.

My approach

The brief was deliberately open, so the first real job was framing the problem before designing anything. With three and a half days for the whole exercise, working in the order the brief asked for, research first and visual artifacts last, was also a way to spend the time where it mattered most. Reasoning over pixels.

Deliverables

Value Proposition Canvas for two profiles, a pain/win synthesis, four solution cards designed as one system, the full UX flow for the chosen feature, and low-fidelity wireframes of its key screens.

Process

Process

The brief made the priority explicit: reasoning first, artifacts second. So the process moves from understanding two very different users, to choosing which pains to attack, to designing a system rather than a pile of features.

01 - research
Two sides of the same table

Loyalty only works if it serves two people at once: the owner who runs the program, and the diner who lives it. I mapped a Value Proposition Canvas for both, because a feature that delights one and annoys the other fails quietly. The owner is the primary platform user; the diner never touches it, but feels every decision made inside it.

Loyalty only works if it serves two people at once: the owner who runs the program, and the diner who lives it. I mapped a Value Proposition Canvas for both, because a feature that delights one and annoys the other fails quietly. The owner is the primary platform user; the diner never touches it, but feels every decision made inside it.

Value Proposition Canvas

Owner + diner

Jobs · Pains · Gains

02 - pain & win
Three pains, chosen from different angles

From the canvas I picked three owner pains on purpose, each from a distinct axis: identity, time, knowledge. Choosing across axes (instead of three flavors of the same complaint) keeps the solution from solving one thing three times. For each pain, a win point defines the transformation Fidelity has to unlock.

From the canvas I picked three owner pains on purpose, each from a distinct axis: identity, time, knowledge. Choosing across axes (instead of three flavors of the same complaint) keeps the solution from solving one thing three times. For each pain, a win point defines the transformation Fidelity has to unlock.

Identity

Time

Knowledge

03 - system
A system, not a menu of features

The four solution cards aren't independent. Customer View feeds the VIP Circle by suggesting candidates. Loyalty Programs are how the Circle gets activated without configuration. Impact measures everything else and keeps the owner engaged. Designing the connections mattered more than designing the boxes

The four solution cards aren't independent. Customer View feeds the VIP Circle by suggesting candidates. Loyalty Programs are how the Circle gets activated without configuration. Impact measures everything else and keeps the owner engaged. Designing the connections mattered more than designing the boxes

Solution cards

System thinking

How might we

04 - flow & wireframes
The VIP Circle, end to end

I took the most distinctive feature to its full flow, from dashboard to sent invitations, then sketched the key screens low-fidelity. The whole flow is built around one constraint: the owner's zero time. Every step has to earn its place; if it doesn't, it's cut.

I took the most distinctive feature to its full flow, from dashboard to sent invitations, then sketched the key screens low-fidelity. The whole flow is built around one constraint: the owner's zero time. Every step has to earn its place; if it doesn't, it's cut.

User flow

Block diagram

Wireframes

The three pains, and what fixes them.

The three pains, and what fixes them.

Pain 1 • Identity

Afraid of looking pushy or promotional

Afraid of looking pushy or promotional

Today

The owner avoids "doing marketing" because discounts feel like they cheapen the place. Result: no communication, and the customer forgets.

Win point

A section that lets you reward instead of promote. Experiences, recognition, exclusive access, not generic discounts. A tone built on care, not on sales.

Pain 2 • Time

Zero time, loyalty always goes to the back of the queue

Zero time, loyalty always goes to the back of the queue

Today

Between service, suppliers, staff and shifts, anything non-urgent gets postponed. Loyalty matters but is never the priority, so it never happens.

Win point

A section usable at a glance, with pre-configured programs activating in a few clicks and automations running in the background. Value appears without requiring learning.

Pain 3 • Knowledge

Doesn't know who's loyal and who's slipping away

Doesn't know who's loyal and who's slipping away

Today

Finds out a customer is gone only when they stop coming. No visibility into the health of the relationship with the customer base.

Win point

A customer view segmented automatically (regulars, occasional, at-risk, new) from data already in the platform. The owner sees the situation and acts before it's too late.

Four features that switch each other on.

Four features that switch each other on.

01 • Customer View

Know your customers without analyzing data

Know your customers without analyzing data

How might we help the owner understand who their customers are, without asking them to analyze data?

The section opens on a customer list already populated from platform data, split into dynamic segments (New, Regular, VIP, At-risk, Lost) computed automatically from frequency and recency. One click reveals who's in a segment and launches a targeted action. No setup required.

The section opens on a customer list already populated from platform data, split into dynamic segments (New, Regular, VIP, At-risk, Lost) computed automatically from frequency and recency. One click reveals who's in a segment and launches a targeted action. No setup required.

Solves

Pain 3 (knowledge) and Pain 2 (zero configuration).

02 • Loyalty Programs

Launch a loyalty program in five minutes

Launch a loyalty program in five minutes

How might we let an owner launch a loyalty program in five minutes, without having to understand what a loyalty program is?

A library of ready-to-use programs, each with a recognizable name and clear use case: Welcome Back, Regulars Card, Birthday, VIP Circle. The owner picks one, sees a preview, edits 2-3 parameters at most, and activates. It runs on its own, triggered by reservation and order data.

A library of ready-to-use programs, each with a recognizable name and clear use case: Welcome Back, Regulars Card, Birthday, VIP Circle. The owner picks one, sees a preview, edits 2-3 parameters at most, and activates. It runs on its own, triggered by reservation and order data.

Solves

Pain 2 (time) and Pain 1 (curated, non-promotional templates).

03 • VIP Circle

Reward top customers with access, not discounts

Reward top customers with access, not discounts

How might we let the owner cultivate their most loyal customers with exclusive experiences, instead of discounts?

A way to recognize the best customers with experiences: tastings, menu previews, reserved tables on busy weekends, closed-door events. The system suggests candidates from the VIP segment; members get a personal invitation. No discounts, only access.

A way to recognize the best customers with experiences: tastings, menu previews, reserved tables on busy weekends, closed-door events. The system suggests candidates from the VIP segment; members get a personal invitation. No discounts, only access.

Solves

Pain 1 (reward over discount) and Pain 3 (targeted action on top customers).

04 • Impact

Answer "is it working?" without reading a report

How might we show the owner whether their time invested in loyalty is paying off, without making them read a report?

A mini-dashboard pinned to the top of the section with three indicators: repeat visits generated, average spend of members vs non-members, return rate of at-risk customers after an action. Each compared to the previous period. Plain language, no analyst terminology.

A mini-dashboard pinned to the top of the section with three indicators: repeat visits generated, average spend of members vs non-members, return rate of at-risk customers after an action. Each compared to the previous period. Plain language, no analyst terminology.

Solves

Cross-cutting: justifies the time invested (Pain 2), gives substance to actions (Pain 1 and 3).

The chosen flow: VIP Circle.

The chosen flow: VIP Circle.

I chose the VIP Circle for the main flow: it's the identity core of the product, it best embodies "reward instead of promote", and it touches every interesting state. Target: from opening the dashboard to sending invitations, under 5-7 minutes the first time, under 2 minutes after. Reference user: Marco, owner of a neighborhood trattoria, already in the platform for reservations.

I chose the VIP Circle for the main flow: it's the identity core of the product, it best embodies "reward instead of promote", and it touches every interesting state. Target: from opening the dashboard to sending invitations, under 5-7 minutes the first time, under 2 minutes after. Reference user: Marco, owner of a neighborhood trattoria, already in the platform for reservations.

01 • Entering Fidelity

The section opens with a one-line onboarding, the Customer View already populated with segments, and the program library below. No full-screen welcome, no guided tour: he sees his real data immediately. Value is shown, not promised.

02 • Choosing the program

He clicks the "VIP Circle" card. A preview explains it in a few lines, shows the email customers will get, and notes that N candidates were already identified (e.g. 12 from the VIP segment). Two CTAs: Personalize, or Activate with suggested candidates. Showing the count up front lowers anxiety and builds anticipation.

03 • Reviewing candidates

The candidate list opens: name, visits in the last 12 months, last visit. He can deselect anyone who doesn't fit and add suggestions from nearby segments. This isn't about data, it's about the sense of control. The owner knows his customers better than the algorithm; without this step, he wouldn't trust the system.

04 • Personalizing the invitation

The invite template is already written, curated and non-promotional. He can edit it or leave it, with a live preview of how it looks to the customer. Smart default, optional edit, never a blank page.

05 • Configuring benefits

He picks what to offer from pre-configured checkboxes (ad-hoc evenings, menu previews, reserved table, birthday gift), plus a free-text custom option. He doesn't have to invent the program; he picks from a set that's part of the Circle's DNA.

06 • Confirm and activate

A summary screen, then one CTA: Activate the VIP Circle. The point of no return is clear and isolated. No upsell, no extra questions. He should feel he completed something.

07 • Post-activation

Back to the Fidelity home. The Circle shows as active with a small widget: member count, invites accepted in real time, next suggested action. The flow ends not with "you did it" but with "here's what you can do next".

Key screens, low-fidelity.

Key screens, low-fidelity.

Low-fidelity on purpose: the brief asked for the logic of space and the priority of information, not polished UI. Two screens carry the flow, the program preview with the candidate count up front, and the candidate review with visits, recency, and a suggestions rail.

Low-fidelity on purpose: the brief asked for the logic of space and the priority of information, not polished UI. Two screens carry the flow, the program preview with the candidate count up front, and the candidate review with visits, recency, and a suggestions rail.

Reflection

Reflection

A system, not screens

The strongest outcome wasn't a feature, it was four features designed to switch each other on, so the section grows coherently instead of as a pile of options.

Built around one constraint

Every flow decision traces back to the owner's zero time. The fast path, the saved state, the smart defaults: constraints turned into design principles.

Honest about the unknowns

The exercise rewarded designing the solution. The harder discipline, and the one I'd carry into a real role, is staying clear about what still needs validating.

A system, not screens

The strongest outcome wasn't a feature, it was four features designed to switch each other on, so the section grows coherently instead of as a pile of options.

Honest about the unknowns

The exercise rewarded designing the solution. The harder discipline, and the one I'd carry into a real role, is staying clear about what still needs validating.

Built around one constraint

Every flow decision traces back to the owner's zero time. The fast path, the saved state, the smart defaults: constraints turned into design principles.

What I'd validate before building
Validate the "reward over discount" bet

The identity pain is my central assumption. I'd run quick interviews with owners to confirm experiences motivate more than discount mechanics, rather than assuming it.

Pressure-test "zero config" on messy data

Automatic segmentation is elegant on clean data. I'd check what the Customer View looks like for a restaurant with sparse or inconsistent history, where segments could mislead.

Bring the diner back into the loop

The exercise let me lean toward the owner. The next iteration would design the diner's side of the VIP invitation with the same care, since the program's success depends on their response.

Want the complete reasoning, the four solution cards in full, and every flow decision? The whole exercise is in one document

Want the complete reasoning, the four solution cards in full, and every flow decision? The whole exercise is in one document

Next project

Next project

Blend+ - Mobile App

Create a free website with Framer, the website builder loved by startups, designers and agencies.