CASE STUDY · 2026 · LEADERSHIP
The case that proves UX leadership is restraint, not addition. 27 metrics down to 5. Decision velocity nearly doubled.
Metric Overload &
Executive Blindness
A short case on UX leadership under constraints — when restraint becomes the design skill.
DOMAIN
Leadership / Governance
ROLE
UX Lead
YEAR
2026
STATUS
Shipped
Context
A product leadership team responsible for a complex, data-heavy platform. Mature analytics infrastructure, dozens of KPIs, regular executive dashboards.
On paper, decision-making was data-driven. In practice, it lacked direction.
TL;DR
- Problem:Leadership wasn't missing information. They were overexposed to it.
- Solution:Forced metric scarcity + ownership framework + direction over precision.
- Key insight:Good UX doesn't add insight. It removes distraction.
Process
TIMELINE — Compact engagement — leadership-only audience
STAKEHOLDERS
- — Executive sponsor — drove the reduction call
- — Head of analytics (initial pushback)
- — End user from product leadership
- — Senior PMs across squads (action item owners)
- — Data engineering — backend pipeline
- — BI / dashboard admin — implementation
DECISION POINTS — 3 CRITICAL
- Forced metric scarcity (27 → 5 KPIs) — remove most of the executive view
- Metric ownership triplet — Owner + Decision + Action — three-question test
- Direction over precision — trend tier instead of decimal accuracy
The Real Problem
Product leadership wasn't missing information. They were overexposed to it.
"When everything is visible, nothing becomes decisive."
Dashboards surfaced growth, engagement, performance, and operational metrics simultaneously — all competing for attention. The negotiation that followed wasn't a clean swap from 27 to 5; it was weeks of fights about which fears were real.
Decisions
ADOPTED
- Forced metric scarcity — single decision per dashboard view
- Metric ownership triplet (Owner × Decision × Action)
- Trend tier visualization (small / medium / large change)
- Backend pipeline preserved — data team's work intact
- Reduction framed as a governance change, not a "data hide"
REJECTED
- Better grouping + collapse — still 27 metrics, just hidden
- Drill-down + custom views — more interaction, less decision
- Decimal precision UI improvements — precision ≠ decisiveness
- Removing metrics from backend pipeline — loses option value
- Hiding the persistent fear ("if we hide metrics, we hide problems") — mitigated by audit instead
Visual Journey
Before vs after — and what changed in between. Four key surfaces of the executive review.
Before — Executive Dashboard
27 KPIs in a 7-column grid. Visual chaos by design — feel the cognitive load.
Metric Ownership Triplet
Each KPI tested: Owner × Decision × Action. Most fail the test.
After — Single-Decision View
5 KPIs. Trend tier instead of decimals. Each metric reads as a recommendation.
Action Item Tracker (90-day)
Decisions to outcomes. The system measures itself.
Voices from the negotiation
“My fear wasn't losing data. It was looking like I don't trust data. We had to design the cover, not just the dashboard.”
“If we hide metrics, we hide problems. That fear didn't go away — we mitigated it with the audit, not by ignoring it.”
“We don't read 27 charts. We act on 1. The metrics we lost? We rebuilt squad-level dashboards for them — better than they were before.”
Impact
Rough estimates from review meetings — figures are approximate.
My Role
DISCOVERY
Leadership meeting shadows and metric usage interviews.
DEFINITION
Decision-to-metric mapping, ownership triplet framework.
DESIGN
Single-decision dashboard pattern, trend tier visualization.
DELIVERY
Sponsor presentation, hi-fi feedback rounds, BI integration.
POST-LAUNCH
Measurement window, monthly review cadence locked.
Reflection
What I'd do differently
We shipped "Forced Metric Scarcity" in a single move — 27 to 5 in one go. The sponsor opened it for debate, but mid-level PMs felt deprived in the first week. In hindsight, we should have staged the rollout — 27 → 12, listen and measure, then 12 → 5. The resistance would have been smaller for the same outcome. The lesson: the larger the change, the smaller the rhythm has to be.
Bigger picture
Good UX doesn't add insight. It removes distraction. In executive contexts, restraint is a design skill — and the biggest win isn't clarity. It is decisiveness.