A Single Source of Truth for Executive Decisions
Role
Product Design, Research, Prototyping, Design System, Developer Handoff
Team
Sai Dheeraj, Akhil Ram
Industry
Healthtech
Healthcare executives were pulling reports from different business units, and every team measured things its own way. One team's "active patients" wasn't another team's "active patients." Getting a real read on the business meant opening five spreadsheets side by side and manually reconciling numbers that used different definitions to begin with — a process that could eat half a morning before anyone got to an actual decision.
The goal is to build one dashboard, built on one set of definitions, that gave a straight answer in seconds.
How did the project start?
No PRD. No user stories. No existing workflow to reference.
Just one 30-minute meeting with executives.
Most projects start with a feature request. This one didn't. Leadership asked for an "Executive Dashboard" and left it at that. No brief, no requirements doc, nothing to reverse-engineer from. So the first job wasn't design. It was figuring out what they actually meant.
Discovery
Requirement Discovery
30-min executive meeting
Stakeholder discussions
Data Understanding
Excel reports
KPI definitions
Business terminology
Information Design
Affinity mapping
KPI categorization
Information architecture
Dashboard Design
Wireframes
UI exploration
Validation
We sat down with operational teams across different healthcare functions to see how they actually put together reports for leadership. Every conversation surfaced new KPIs, different formats, different terminology, Each one shaping the dashboard a little more.
Artifact Analysis
Every team had its own way of reporting. Before we touched the design, we had to figure out what each metric meant — and which ones executives actually looked at.
Affinity Mapping
Client Filters
Overview
Procedures
Office Visits
Quality
Operational Alerts
We pulled together everything we'd learned. Patterns from operational teams, Stakeholder conversations, Old Excel reports and organized it into six dashboard modules an executive could scan in under five seconds.
Information Architecture
Rather than dump every operational metric onto the screen, we grouped things into modules that matched how leadership actually reviewed performance.
Challenges
No PRD or Defined Requirements
The project started as a request from Senior leadership. No PRD, no user stories, nothing predefined. Before we could design anything, we had to figure out the business problem ourselves and decide what an executive dashboard should even include.
Disconnected Reporting Across Teams
Every operational unit kept its own Excel reports, each with different KPIs, terminology, and formats. We had to find the patterns underneath it all and stitch the fragments into something consistent.
Limited Executive Access
We got one 30-minute conversation with executives and that was it. So most decisions leaned on operational teams, whatever data we had, and industry research instead of direct stakeholder feedback.
Information Prioritization
Executives needed to read performance at a glance, but every team wanted their metrics front and center. The real challenge was deciding whose numbers went first without it turning into a turf war.
Evolving Requirements
New KPIs kept coming up during reviews, even after we thought scope was set. Instead of locking the layout, we designed modules that could take on new metrics without redoing the whole page.
Disconnected Reporting Across Teams
Every operational unit kept its own Excel reports, each with different KPIs, terminology, and formats. We had to find the patterns underneath it all and stitch the fragments into something consistent.
We sat down with operational teams across different healthcare functions to see how they actually put together reports for leadership. Every conversation surfaced new KPIs, different formats, different terminology, Each one shaping the dashboard a little more.
Key Design Decisions
Overview
Executives don't read reports — they don't have time. So the dashboard opens with business health, SLA status, client score, and the KPIs that actually matter, all visible before you've even started scrolling.
Show completion and automation together
Completion percentage alone didn't say much. A team could hit 90% by automating most of the work, or by grinding through it manually — the number looked the same either way. Pairing it with automation coverage and pending work made the difference visible at a glance.
Prioritize exceptions over successful automation
Instead of only showing automation percentages, the table highlights partially automated workflows and exceptions so leaders know exactly where manual effort is concentrated.
Surface issues before they become escalations
Executives shouldn't have to dig through reports to find what's wrong. Operational Alerts catch SLA risks, authorization expirations, and automation drops on their own, and surface them before anyone has to go looking.
Quality Trends Over Point-in-Time Metrics
A single score rarely tells the full story. We introduced weekly and monthly trend views so leaders could quickly understand whether quality was improving, stable, or declining before diving into detailed audits.
One dashboard, multiple business units
Global filters allow executives to move between clients, providers, specialties and business units without changing dashboards, keeping the experience consistent across operations.
Remove mental calculations
Instead of comparing KPIs against targets manually, every metric communicates its performance through contextual badges like "2% above target" or "1% below last week", making trends instantly understandable.
More screens
What did i learn
This project taught me that slowing down at the beginning saves far more time later. Investing in information architecture and content hierarchy early made every design decision clearer, collaboration faster, and the final experience much easier for people to understand.
A Single Source of Truth for Executive Decisions
Role
Product Design, Research, Prototyping, Design System, Developer Handoff
Team
Sai Dheeraj, Shashwita
Industry
Healthtech
Healthcare executives were pulling reports from different business units, and every team measured things its own way. One team's "active patients" wasn't another team's "active patients." Getting a real read on the business meant opening five spreadsheets side by side and manually reconciling numbers that used different definitions to begin with — a process that could eat half a morning before anyone got to an actual decision.
The goal is to build one dashboard, built on one set of definitions, that gave a straight answer in seconds.
How did the project start?
No PRD. No user stories. No existing workflow to reference.
Just one 30-minute meeting with executives.
Most projects start with a feature request. This one didn't. Leadership asked for an "Executive Dashboard" and left it at that. No brief, no requirements doc, nothing to reverse-engineer from. So the first job wasn't design. It was figuring out what they actually meant.
Discovery
Requirement Discovery
30-min executive meeting
Stakeholder discussions
Data Understanding
Excel reports
KPI definitions
Business terminology
Information Design
Affinity mapping
KPI categorization
Information architecture
Dashboard Design
Wireframes
UI exploration
Validation
We sat down with operational teams across different healthcare functions to see how they actually put together reports for leadership. Every conversation surfaced new KPIs, different formats, different terminology, Each one shaping the dashboard a little more.
Artifact Analysis
Every team had its own way of reporting. Before we touched the design, we had to figure out what each metric meant — and which ones executives actually looked at.
Affinity Mapping
Client Filters
Overview
Procedures
Office Visits
Quality
Operational Alerts
We pulled together everything we'd learned. Patterns from operational teams, Stakeholder conversations, Old Excel reports and organized it into six dashboard modules an executive could scan in under five seconds.
Information Architecture
Rather than dump every operational metric onto the screen, we grouped things into modules that matched how leadership actually reviewed performance.
Challenges
No PRD or Defined Requirements
The project started as a request from Senior leadership. No PRD, no user stories, nothing predefined. Before we could design anything, we had to figure out the business problem ourselves and decide what an executive dashboard should even include.
Disconnected Reporting Across Teams
Every operational unit kept its own Excel reports, each with different KPIs, terminology, and formats. We had to find the patterns underneath it all and stitch the fragments into something consistent.
Limited Executive Access
We got one 30-minute conversation with executives and that was it. So most decisions leaned on operational teams, whatever data we had, and industry research instead of direct stakeholder feedback.
Information Prioritization
Executives needed to read performance at a glance, but every team wanted their metrics front and center. The real challenge was deciding whose numbers went first without it turning into a turf war.
Evolving Requirements
New KPIs kept coming up during reviews, even after we thought scope was set. Instead of locking the layout, we designed modules that could take on new metrics without redoing the whole page.
Disconnected Reporting Across Teams
Every operational unit kept its own Excel reports, each with different KPIs, terminology, and formats. We had to find the patterns underneath it all and stitch the fragments into something consistent.
We sat down with operational teams across different healthcare functions to see how they actually put together reports for leadership. Every conversation surfaced new KPIs, different formats, different terminology, Each one shaping the dashboard a little more.
Key Design Decisions
Overview
Executives don't read reports — they don't have time. So the dashboard opens with business health, SLA status, client score, and the KPIs that actually matter, all visible before you've even started scrolling.
Show completion and automation together
Completion percentage alone didn't say much. A team could hit 90% by automating most of the work, or by grinding through it manually — the number looked the same either way. Pairing it with automation coverage and pending work made the difference visible at a glance.
Prioritize exceptions over successful automation
Instead of only showing automation percentages, the table highlights partially automated workflows and exceptions so leaders know exactly where manual effort is concentrated.
Surface issues before they become escalations
Executives shouldn't have to dig through reports to find what's wrong. Operational Alerts catch SLA risks, authorization expirations, and automation drops on their own, and surface them before anyone has to go looking.
Quality Trends Over Point-in-Time Metrics
A single score rarely tells the full story. We introduced weekly and monthly trend views so leaders could quickly understand whether quality was improving, stable, or declining before diving into detailed audits.
One dashboard, multiple business units
Global filters allow executives to move between clients, providers, specialties and business units without changing dashboards, keeping the experience consistent across operations.
Remove mental calculations
Instead of comparing KPIs against targets manually, every metric communicates its performance through contextual badges like "2% above target" or "1% below last week", making trends instantly understandable.
More screens
What did i learn
This project taught me that slowing down at the beginning saves far more time later. Investing in information architecture and content hierarchy early made every design decision clearer, collaboration faster, and the final experience much easier for people to understand.
A Single Source of Truth for Executive Decisions
Role
Product Design, Research, Prototyping, Design System, Developer Handoff
Team
Sai Dheeraj, Akhil Ram
Industry
Healthtech
Healthcare executives were pulling reports from different business units, and every team measured things its own way. One team's "active patients" wasn't another team's "active patients." Getting a real read on the business meant opening five spreadsheets side by side and manually reconciling numbers that used different definitions to begin with — a process that could eat half a morning before anyone got to an actual decision.
The goal is to build one dashboard, built on one set of definitions, that gave a straight answer in seconds.
How did the project start?
No PRD. No user stories. No existing workflow to reference.
Just one 30-minute meeting with executives.
Most projects start with a feature request. This one didn't. Leadership asked for an "Executive Dashboard" and left it at that. No brief, no requirements doc, nothing to reverse-engineer from. So the first job wasn't design. It was figuring out what they actually meant.
Discovery
Requirement Discovery
30-min executive meeting
Stakeholder discussions
Data Understanding
Excel reports
KPI definitions
Business terminology
Information Design
Affinity mapping
KPI categorization
Information architecture
Dashboard Design
Wireframes
UI exploration
Validation
We sat down with operational teams across different healthcare functions to see how they actually put together reports for leadership. Every conversation surfaced new KPIs, different formats, different terminology, Each one shaping the dashboard a little more.
Artifact Analysis
Every team had its own way of reporting. Before we touched the design, we had to figure out what each metric meant — and which ones executives actually looked at.
Affinity Mapping
Client Filters
Overview
Procedures
Office Visits
Quality
Operational Alerts
We pulled together everything we'd learned. Patterns from operational teams, Stakeholder conversations, Old Excel reports and organized it into six dashboard modules an executive could scan in under five seconds.
Information Architecture
Rather than dump every operational metric onto the screen, we grouped things into modules that matched how leadership actually reviewed performance.
Challenges
No PRD or Defined Requirements
The project started as a request from Senior leadership. No PRD, no user stories, nothing predefined. Before we could design anything, we had to figure out the business problem ourselves and decide what an executive dashboard should even include.
Disconnected Reporting Across Teams
Every operational unit kept its own Excel reports, each with different KPIs, terminology, and formats. We had to find the patterns underneath it all and stitch the fragments into something consistent.
Limited Executive Access
We got one 30-minute conversation with executives and that was it. So most decisions leaned on operational teams, whatever data we had, and industry research instead of direct stakeholder feedback.
Information Prioritization
Executives needed to read performance at a glance, but every team wanted their metrics front and center. The real challenge was deciding whose numbers went first without it turning into a turf war.
Evolving Requirements
New KPIs kept coming up during reviews, even after we thought scope was set. Instead of locking the layout, we designed modules that could take on new metrics without redoing the whole page.
Disconnected Reporting Across Teams
Every operational unit kept its own Excel reports, each with different KPIs, terminology, and formats. We had to find the patterns underneath it all and stitch the fragments into something consistent.
We sat down with operational teams across different healthcare functions to see how they actually put together reports for leadership. Every conversation surfaced new KPIs, different formats, different terminology, Each one shaping the dashboard a little more.
Key Design Decisions
Overview
Executives don't read reports — they don't have time. So the dashboard opens with business health, SLA status, client score, and the KPIs that actually matter, all visible before you've even started scrolling.
Show completion and automation together
Completion percentage alone didn't say much. A team could hit 90% by automating most of the work, or by grinding through it manually — the number looked the same either way. Pairing it with automation coverage and pending work made the difference visible at a glance.
Prioritize exceptions over successful automation
Instead of only showing automation percentages, the table highlights partially automated workflows and exceptions so leaders know exactly where manual effort is concentrated.
Surface issues before they become escalations
Executives shouldn't have to dig through reports to find what's wrong. Operational Alerts catch SLA risks, authorization expirations, and automation drops on their own, and surface them before anyone has to go looking.
Quality Trends Over Point-in-Time Metrics
A single score rarely tells the full story. We introduced weekly and monthly trend views so leaders could quickly understand whether quality was improving, stable, or declining before diving into detailed audits.
One dashboard, multiple business units
Global filters allow executives to move between clients, providers, specialties and business units without changing dashboards, keeping the experience consistent across operations.
Remove mental calculations
Instead of comparing KPIs against targets manually, every metric communicates its performance through contextual badges like "2% above target" or "1% below last week", making trends instantly understandable.
More screens
What did i learn
This project taught me that slowing down at the beginning saves far more time later. Investing in information architecture and content hierarchy early made every design decision clearer, collaboration faster, and the final experience much easier for people to understand.
More works
Think of all the cool stuff, We could accomplish together
All rights reserved.
Created by Sai Dheeraj
Think of all the cool stuff, We could accomplish together
All rights reserved.
Created by Sai Dheeraj
Think of all the cool stuff, We could accomplish together
All rights reserved.
Created by Sai Dheeraj