The problem usually isn’t the dashboard itself.
It’s that nobody knows:
Why it matters
What decision it supports
Where to start
What they’re supposed to do next
Before you send your next dashboard, write a three-line introduction:
This dashboard helps you: [make a specific decision]
Start by checking: [one specific view or metric]
If you see: [specific problem], then [recommended action]
That small amount of context can make the difference between a dashboard being ignored and becoming part of someone’s regular workflow.
Your job isn’t just to build the report.
Your job is to help people use it.
--Andy Kriebel
No comments:
Post a Comment