Charles Augello

HomeCase studiesDecision-support dashboard

Designing a decision-support dashboard for enterprise leaders

Senior leaders had the data but not the view. I designed a dashboard that turned dense tables into clear signals so leaders could act on delivery risk while it still mattered.

Role
UX Lead & Interaction Designer (embedded)
Timebox
15 business days
Environment
Large, regulated enterprise operating across multiple Agile teams and programs
Tools
Figma, system-based components
Outputs
Decision-ready dashboard prototype, scalable visualization patterns, documented design guidance
Minutesto identify delivery risks, instead of hours
35%fewer follow-up clarification requests
72 hrsto a prioritized set of leadership indicators

The decision to enable

Senior leaders lacked a clear, shared view of Agile health and delivery performance. Data existed, but it lived in dense tables and disconnected reports, making it hard to answer critical questions:

  • Where are teams struggling right now?
  • Which issues require immediate intervention?
  • Where should leadership focus attention this sprint?

Key decision: How can leaders move from raw data to actionable insight fast enough to influence outcomes?

Rapid insight generation

Rather than starting with exhaustive requirements, I worked directly with executive stakeholders to identify the top decisions they needed to make. I analyzed existing data sources, including Agile metrics, operational reports, and stakeholder workflows, to determine which signals truly mattered.

Within the first 72 hours, I distilled needs into a prioritized set of indicators aligned to leadership questions, not system outputs.

Dashboard prototyping at speed

Using Figma and system-based components, I delivered:

  • Days 2–3: Low-fidelity concepts exploring multiple visualization approaches
  • Days 4–5: Medium-fidelity interactive prototype with drill-down behavior
  • Days 6–7: Decision-grade prototype refined through leadership feedback

The dashboard translated complex tabular data into clear visual signals, allowing users to scan, compare, and investigate trends within minutes.

Accessibility and systems by default

Accessibility and scalability were built in from the start:

  • Color-safe palettes and non-color indicators for status
  • Clear labeling and hierarchy for screen-reader compatibility
  • Reusable visualization patterns aligned to enterprise standards

Design documentation ensured the dashboard could be extended or scaled without rework.

Test, learn, adapt

Rapid feedback sessions with executives and product leaders revealed opportunities to simplify views and surface exceptions more clearly. Iterations focused on:

  • Reducing cognitive load
  • Highlighting outliers and trends
  • Improving drill-down clarity

Each iteration tightened the connection between what leaders saw and what actions they needed to take.

Outcomes and impact

  • Enabled leaders to identify delivery risks in minutes instead of hours
  • Improved focus on high-impact issues during sprint and portfolio reviews
  • Reduced follow-up clarification requests by 35%, indicating clearer shared understanding
  • Accelerated leadership response to emerging team-level issues

Scale readiness

To support broader adoption, I delivered:

  • Modular dashboard components
  • Interaction and visualization guidelines
  • Clear mapping between metrics and decisions

These assets allowed additional teams to extend the dashboard without redesigning from scratch.

Reflection: AI-first evolution

Today, I would further accelerate this work by:

  • Using AI to surface anomalies and trends automatically
  • Generating dynamic summaries for leadership review
  • Enabling natural-language exploration of the underlying data

The principle remains consistent: design dashboards to support decisions, not just display data.

Need leaders to see risk sooner?

Email me