Before selecting charts, identify the decisions the dashboard must support and the people responsible for making them.
Write the decision first
What will the user decide after reading the report? Allocation, investigation, escalation, and forecasting each require different evidence. One report can support more than one decision, but each section should have a clear purpose.
Agree on the definitions
Write down what each important metric counts, where it comes from, and what it excludes. State the reporting period and whether that period is complete. A polished chart cannot repair a disagreement about the meaning of its numbers.
Expose the limitation
Freshness, missing records, and unresolved reconciliation should be visible. Show what is known and what still needs checking. A useful dashboard supports confidence in a decision without pretending that the underlying evidence is perfect.
Connect observation to action
An exception should lead to a next step: an owner, a question to investigate, or an agreed response. Review whether the dashboard actually changed the decision. If the same figures are copied into another document before anyone acts, the operating design may still be incomplete.
Clarity → sequence → system → compounding.
Explore how this thinking becomes a named YERID output, or start with the Growth System Diagnostic.
