Practical guide
Build a dashboard that distinguishes inputs from outcomes
A dashboard should separate resources and actions from observed outcomes so activity is not mistaken for achievement.
A dashboard should separate resources and actions from observed outcomes so activity is not mistaken for achievement.
A practical procedure
-
Place preparation hours, scripts and demonstrations in an inputs-or-activity section.
-
Place verified answer coverage, reviewed accuracy and confirmed outcomes in a separate results section.
-
Add definitions and missing-data labels, then connect each result to a possible follow-up decision.
Worked example: a fictional session
A fictional dashboard shows ten prepared scripts as activity and twenty verified answers as output, without combining them into a sales figure.
Check the limits
An attractive chart does not resolve unclear metric definitions.