Create a metric dashboard for the executive team reviewing AWS

Problem Statement Description

Product context: Amazon is a commerce, logistics, media, devices, and cloud company; its products include Marketplace, Prime, Prime Video, Alexa devices, ads, fulfillment, and AWS. AWS is Amazon's cloud platform; its products include compute, storage, databases, analytics, networking, security, machine learning, and developer tools.

Amazon’s executive team wants a concise, decision-ready dashboard to review the health and trajectory of AWS. The audience is senior leadership, so the dashboard should not be a long operational report; it should surface the most important signals about customer value, business performance, reliability, growth quality, and strategic position across AWS.

Assume AWS serves a broad set of customers, with developers and technical teams as a critical user segment. These users discover services, build applications, deploy workloads, monitor infrastructure, manage costs, and scale usage over time. Friction in any part of this workflow can affect adoption, retention, workload expansion, and trust in AWS as a platform.

Your task is to define what an executive metrics dashboard should include, how the metrics should be structured, and how leadership should use the dashboard to make decisions. Focus on metric definitions, denominators, segmentation, instrumentation needs, guardrails, and how the dashboard distinguishes healthy growth from short-term or misleading movement.

The experience should consider:

- The core executive questions the dashboard must answer, such as whether AWS is growing, retaining customers, delivering reliable infrastructure, and expanding developer usage.

- Clear definitions for primary metrics, including what counts in the numerator and denominator, and how metrics should be normalized across customer sizes, services, and regions.

- Cohorts and segments that matter, such as new vs. existing customers, startups vs. enterprises, developer-heavy accounts, service families, geography, workload maturity, and pricing model.

- Instrumentation requirements across account creation, service activation, API usage, compute/storage/network consumption, billing, support, reliability events, and customer feedback.

- Guardrail metrics that prevent over-optimizing for revenue or usage at the expense of customer trust, cost predictability, security, latency, availability, or support quality.

- Leading indicators versus lagging indicators, including which metrics help executives act early before revenue, churn, or reliability issues become visible.

- Dashboard usability for executives, including refresh cadence, trend views, alert thresholds, drill-down paths, and ownership for metric interpretation.

- Decision usefulness, including how the dashboard would support investment, pricing, reliability, regional expansion, product portfolio, and competitive response discussions.

The goal is to frame a metrics dashboard that helps Amazon leadership understand the state of AWS at a strategic level while still being grounded in measurable developer and customer behavior. The dashboard should make trade-offs visible, highlight where deeper investigation is needed, and enable confident decisions without requiring executives to inspect every underlying operational metric.