Case 02 · Product Design · 2024

Cadence

Rethinking how teams plan their week — turning a cluttered scheduler into something people actually wanted to open on Monday morning.

Role: [Your role]
Timeline: [e.g. 6 months]
Team: [e.g. 1 designer, 3 engineers, 1 PM]
Platform: [Web]

Overview

A short summary of what Cadence was and why it mattered.

Frame the product in a few plain sentences. What did it do, who used it, and what was the brief you were handed? Save the detail for the sections below — this is the elevator version.

[Replace with the one-breath story: the state it was in, the change you drove, the result.]

Figure — the redesigned week view

Caption: what this screen shows and why it leads the story.

The Problem

What was broken, and who was feeling it.

Describe the specific friction users lived with — the steps that took too long, the states that confused them, the moment they gave up and went back to a spreadsheet. Make the pain concrete and human.

[Add the cost of the problem so the stakes are clear.]

Approach

How you worked the problem.

Take the reader through your thinking: the research or signals you leaned on, the concepts you tried and killed, the key decision that unlocked the rest. Show the judgment behind the pixels.

Figure — exploration

Figure — refined

Caption: from early exploration to the direction you committed to.

Outcome

What changed once it shipped.

Land the impact honestly — usage, retention, task time, a metric that moved, or how the team's confidence shifted. Numbers if you have them, qualitative truth if you don't.

[Close with a short reflection on what you learned.]