A dashboard is not a collection of charts. It is a decision interface. Before I design a SaaS dashboard, I write a decision contract: 1. Who is looking? Founders, operators, finance teams, and customers should not inherit the same view. 2. What decision should change? If a metric cannot change a priority, allocation, approval, or next action, it may be reporting noise. 3. How fresh must the data be? Some decisions need seconds. Others need a reliable daily snapshot. 4. What happens when data is incomplete? Show stale sources, missing records, and assumptions instead of presenting false certainty. 5. What can the user do next? A useful dashboard usually ends with an action: investigate, assign, approve, export, contact, or change a rule. The strongest dashboards become simpler after the decisions are defined first: fewer charts, clearer permissions, better actions. What is one metric your team keeps showing even though it rarely changes a decision?