Back Cadence · Case Study
Kartik Harish

Teaching a dashboard to do something about the problems it finds.

This started as a brief for an AI-powered team management app. Somewhere in the process it became something more: a real attempt at designing a product that solves an actual problem, not just one that satisfies a spec.

Role Solo product designer  ·  Timeframe 2 days  ·  Tools Figma, coded prototype

The AI Recommended Action card, proposing a workload reassignment from Rohan to Priya
2
days, the brief start to prototype
2
screens, fully interactive, as scoped
1
feature, designed to solve a real problem

This was a timed design-round assignment, not a shipped product. So instead of making up usage numbers nobody measured, here's what actually got built and why.

From brief to product

I designed the full system to meet the brief. Once it worked, I kept going, because meeting a brief and solving someone's actual problem aren't always the same thing.

Designed to the brief AI Daily Digest card
Meets the brief
Designed as a product AI Recommended Action card
Solves the problem

The screens

Home and Analytics as designed to the brief, then Home again with the AI Recommended Action added.

Cadence Home dashboard, designed to the brief, with the AI Daily Digest
Home, designed to the brief
Cadence Analytics and Reports screen with velocity trend, task status breakdown, and risk forecast
Analytics & Reports, designed to the brief
Cadence Home dashboard extended with the AI Recommended Action card
Home, extended into a product

How it came together

01
Who is this for?

Team leads at fast-moving startups, managing anywhere from 5 to 15 people across several projects, expected to catch problems before they turn into fire drills.

02
What was stopping them?

Status lived everywhere except the dashboard, scattered across standups and Slack messages. Every tool could tell you what had already gone wrong. None of them could tell you what was about to.

03
Why did it matter?

A missed risk signal meant a late launch, a quietly burnt-out teammate, or a lead spending their week chasing updates instead of unblocking anyone.

04
Where do you come in?

I was given two days, full creative freedom, and one hard requirement: merge familiar dashboard UI with a real AI feature, not a chatbot bolted onto the side.

05
What did you do?

I mapped the user and their pain points first, then designed the brief's Home and Analytics screens, including an AI Daily Digest that turned scattered status into one clear read every morning.

06
What changed the direction?

The brief was done. But finishing an assignment isn't the same as finishing the thinking, so I kept asking questions. The Digest was fast to read, sure, but was it fast to act on? Someone still had to notice the problem, decide what to do, and go make the change by hand.

07
What did you make?

So I designed one step further than what was asked: an AI Recommended Action card that closes that gap. It names the exact problem, proposes one specific fix with the numbers already worked out, and asks before acting. There's a genuine "do something else" option too, so it's never forced on the user.

08
What improved?

Between the brief and the iteration, the dashboard went from reporting status to actually reducing the work of acting on it. Every card and transition is fully prototyped, with hover, press, and animated states, so it reads like a working product instead of a static comp.

09
What did you learn?

Finishing the brief is easy to mistake for finishing the thinking. The habit worth keeping is asking "what's still causing friction?" even after the assignment is technically done. That's where this feature came from.