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 dashboard to review the health and trajectory of AWS, with a particular lens on developer customers who evaluate, adopt, build on, and scale cloud services. The dashboard should help leaders understand whether AWS is creating durable customer value, growing efficiently, operating reliably, and staying competitive in the cloud infrastructure market.

Your task is to define what this executive dashboard should measure, how the metrics should be structured, and how leaders should interpret them. Assume the dashboard must be useful across major AWS services and customer segments, while still surfacing actionable signals for developer experience, enterprise adoption, usage growth, reliability, and business performance.

The focus is not on designing a visual UI, but on selecting the right metrics, defining them clearly, explaining their denominators and cuts, and identifying guardrails that prevent misleading conclusions. Consider how Amazon leadership would use this dashboard to make decisions about investment, operational focus, customer experience, and competitive positioning.

The experience should consider:

- The primary executive questions the dashboard must answer about AWS growth, customer value, reliability, and developer adoption.

- Clear metric definitions, including numerator, denominator, time window, and whether each metric is leading, lagging, or diagnostic.

- How to segment metrics by customer type, service family, region, workload maturity, account size, and developer lifecycle stage.

- Instrumentation needs across console usage, API activity, billing, service utilization, support interactions, reliability events, and customer feedback.

- Guardrail metrics that prevent over-optimizing for revenue, usage, or adoption at the expense of trust, reliability, cost transparency, or customer satisfaction.

- Cohorts that distinguish new customers, expanding customers, churn-risk customers, startups, enterprises, and highly technical developer teams.

- How the dashboard should support decision-making, escalation, and trend monitoring rather than simply reporting vanity metrics.

The goal is to propose an executive-level AWS metrics dashboard that is clear, decision-useful, and balanced across customer outcomes, business performance, operational excellence, and long-term cloud platform health.