Sam, product designer
All work

Working title for your finished case study

One sentence on the problem in plain words. Who was stuck, and on what.

Role
Lead product designer
Company
Secondmind
Timeline
Month 20XX to Month 20XX
Platform
Web app, desktop first
Team
1 designer, 1 PM, 4 engineers
Status
Shipped
Cover: the strongest final screen, at full width
XX%
reduction in time to complete the task
XX%
of target users adopted it in the first month
X
support tickets on this flow since launch

Problem

Two or three short paragraphs. Who the user is, what they were trying to do, and what was getting in the way. Then the business reason this mattered, with a number if you have one.

State the problem as one sentence you could say out loud in the interview.

Constraints

What made this hard. Be specific, because this is where Revolut’s panel looks for maturity.

  • Design system. What you had to work within, and where you extended it.
  • Technical. Data, performance or platform limits that shaped the design.
  • Domain or compliance. Rules the interface had to respect.
  • Time and team. What you could and couldn’t ship in the first release.

Exploration

Show how you got there. Early sketches, the directions you tried, what research told you.

Direction A: what you tried first
Direction A: what you tried first
Direction B: the alternative
Direction B: the alternative
One sentence on what each direction was optimising for.

Decisions and trade-offs

One block per significant decision. Lead with the evidence.

How should engineers switch between calibration profiles?

  • Option you choseChosen

    What it was good at.

  • Option you droppedDropped

    Why it lost.

We tested both with N engineers. X completed the task faster with the first option because of Z. The trade-off was Y, which we accepted because it only affected a small share of sessions.

The flow

The complete journey, from where users start to where they finish. Include navigation, empty states and confirmations.

Primary journey5 steps
  1. Screen 1: Entry point
    1Entry point from the main navigation
  2. Screen 2: Empty state
    2Empty state
  3. Screen 3: Core task
    3Core task
  4. Screen 4: Review
    4Review
  5. Screen 5: Confirmation
    5Confirmation
Key screen at full resolution. Show it large enough to judge type and spacing.
Caption explaining the one thing to notice on this screen.

Edge cases and validation

Errors, limits and unusual data. These show attention to detail more than any hero screen.

Edge cases4 steps
  1. Screen 1: Validation error
    1Validation error inline, on blur
  2. Screen 2: Conflicting values
    2Conflicting values
  3. Screen 3: No permission
    3No permission
  4. Screen 4: Loading and partial data
    4Loading and partial data

Outcomes

What shipped and what changed. Repeat the headline metrics with context: how you measured, over what period, against what baseline. Add a quote from a user or stakeholder if you have one.

Reflection

Two or three sentences. What you’d do differently, and what you’re iterating on next.