Set thresholds for lead volume, response time, pipeline movement, retention signals, and data completeness. Note expected seasonality.
Investigate first
Check tracking, source mix, ownership, and process changes before assigning a business cause. Record evidence and confidence.
Close the action
Assign an owner, question, due date, and smallest confirming check. Functional owners decide corrective action.
Define a useful exception
Compare current values with a stable baseline and annotate seasonality, launches, outages, and tracking changes. Fewer leads after a form edit requires a tracking check before a demand conclusion.
Move from signal to test
Write observation, suspected causes, evidence checked, confidence, owner, and confirming check. Close only when the check has an outcome. Keep mixed evidence visible. Use a growth dashboard exception review to trace one unusual metric back to its source rows and definition. Write down the expected range, affected segment, freshness check, and operational decision that the exception could change.
If the number is a data defect, assign the source-system fix and preserve the original snapshot. If it is a real shift, give the business owner a focused follow-up question rather than rewriting the dashboard to hide volatility.
