PRODUCT DESIGN · ENTERPRISE TRANSFORMATION · WEB PLATFORM

Track360: designing for the three minutes a CFO has before the board meeting. 🖌️

$590M across 100+ transformation initiatives, tracked across scattered PowerPoint decks, Excel trackers and status meetings that rebuilt the same picture every week. I led the end to end design of an executive command centre that let a global beauty company's C-suite move from reporting to deciding, in a single view.

MY CONTRIBUTION

Requirement synthesis → information architecture → user flows → wireframing → high-fidelity UI → prototyping → stakeholder reviews → engineering handoff

ROLE
Product Designer
DURATION
3-week proof of concept
PLATFORM
Web · React
USERS
C-suite executives
011

Outcome: from status meetings to a single decision-ready view.

$590M
Portfolio value made visible in a single view
100+
Transformation initiatives consolidated
4
Additional client engagements won directly off this proof of concept
✓ My ownership
  • Led the UX process from discovery through high-fidelity design
  • Structured a fragmented data ecosystem into one IA
  • Directed AI-accelerated concept exploration
  • Delivered React-ready specs in 3 weeks
🗂️ File📌 Ownership🕐 12:00 PM
✓ Deliverables
  • User flows for executive drill-down
  • Component specs and engineering handoff docs
  • Interactive prototype for stakeholder walkthroughs
  • Information Architecture
🗂️ File📌 Delivery🕐 12:00 PM
02

The problem was not missing data. It was missing shape.

The client did not need more information. They already had all of it. What they did not have was one place to look, and one shared definition of what "on track" meant.

⚠️ DANGER: Which file has answers?!
  • Fragmented → updates spread across PowerPoint decks, Excel trackers and recurring status meetings, with no single source of truth
  • Manual → every status meeting rebuilt the same picture from scratch, by hand
  • Duplicated → the same numbers were reformatted and re-presented for different audiences, again and again
  • Invisible → with $590M and 100+ initiatives in flight, no single view showed where the real risk was sitting
THE UX QUESTION
"If a CFO has three minutes before a board meeting, what is the one number they need, and how fast can they get from that number to the initiative actually driving it?"
How to navigate?!
What's off track Why Where in the portfolio Whats Next
✏️
03

Research here meant structuring, not discovering.

The client came in with a defined vision and complete data. They told us plainly: "We have all the data you need, we just don't want it to look like another dashboard." That changed what research had to do.

Requirement synthesis·Secondary research·Stakeholder alignment·Rapid IA structuring·AI-accelerated concept exploration

STATUS IS NOT INSIGHT

Executive dashboards are scanned for deviation first, detail second. Leadership needed to see what was off before they needed to know why.

ONE METRIC, FOUR DEFINITIONS

Inconsistent KPI definitions across departments were quietly eroding trust in the numbers themselves, not just the reporting process.

THE REPORT WAS ALWAYS LATE

Manually assembled updates meant leadership was always looking at where the portfolio used to be, not where it actually stood.

Evidence
Insight
Design response
Updates lived across PowerPoint decks, Excel trackers and recurring status meetings, with no shared source of truth
Leadership needed one place to look, not more reports to reconcile
Build a single command center that replaces the reporting ritual, instead of adding to it
KPI definitions varied by department, so "on track" did not mean the same thing twice
Consistency of definition matters as much as accuracy of data
Standardise portfolio health indicators so a status colour means the same thing in every view
Executives had minutes, not hours, to review portfolio status before a decision
The interface needed to answer "what needs my attention" before "here is everything"
Lead with three drill-down entry points instead of one flat data table
Research note: there were no exploratory interviews on this project. The client already knew exactly what they wanted to see and handed over complete, ready-to-use data, so the three-week timeline went into synthesis, structuring and secondary research on executive reporting patterns, not discovery. I have been upfront about that distinction rather than dressing it up as user research.
04

The core experience: three lenses on one portfolio.

Instead of one dense table trying to serve every executive, Track360 gives each of them their own way into the same $590M.

Command Center
Portfolio health at a glance, $590M in one view
→
Choose a lens
Value Drivers, Project Phase or Domain
→
Drill into a project
Full context on that specific initiative
→
See the risk
Dependencies and blockers surfaced directly
→
Decide
What to escalate, fund or unblock
Track360 information architecture tree
Why three lenses instead of one fixed hierarchy — A CFO scans for value, a COO scans for phase, a department head scans for their own domain. Forcing all three into one hierarchy would have optimised for none of them, so each got its own entry point into the same underlying data.

Why drill-down stops at two levels — With $590M and 100+ initiatives in flight, anything past two clicks risked recreating the exact problem this was meant to fix. Overview to project detail had to feel immediate, not like another report to dig through.
05

The final interface turns $590M into something you can read in seconds.

There was no room in three weeks for a formal V1 to V2 pass on screens. The real iteration happened earlier, in deciding what kind of product this would even be.

V1 · Early directions → Explored
  • Multiple concept passes explored fast using Figma Make, Framer and Lovable
  • Several read as familiar BI dashboards: dense tables, generic bar charts
  • Fast to produce, but risked looking like every reporting tool the client already had
→
V2 · What we built → Shipped
  • A visual, story-driven command centre built around three entry points, not one dense table
  • Ranked value-driver sliders and a domain map replaced generic charts
  • Direction confirmed with the client before locking high-fidelity work in Figma

Value Drivers ranks what matters most. The domain map and project phase level shows where the portfolio actually lives, further drill down to project level details

Track360 final dashboard interface
06

What Track360 says about how I work.

The strongest part of this project is not the visual polish. It is what happened when the timeline and the research budget both disappeared.

MOVE FAST WITHOUT LOSING RIGOUR

Three weeks, no interviews, complete client data. I still built the structure through evidence, not guesswork, just compressed.

DESIGN THE DECISION, NOT THE DATA

Every screen exists to answer one question: what does this person need to decide right now.

USE AI AS LEVERAGE, NOT A SHORTCUT

Figma Make, Framer and Lovable helped explore directions fast. The judgment on which direction to ship stayed mine.

CLIENT FEEDBACK

"This is something that doesn't exist anywhere in our company. It's truly one of a kind."

DIRECT IMPACT

"Additional 4 client engagements"

Scope note: Track360 was delivered as a three-week proof of concept for one client, working from a defined brief and complete data rather than exploratory user research.

Enterprise data does not need to look like enterprise data.
high-speed product problems: find the shape inside the complexity, design around the decision the user actually needs to make, and hold the line on rigour even when the clock is short.

Track360 • Product Clock Case Study • Madura Sankar
VIEW OTHER CASE STUDY BACK