Dashboard design is the screen-level problem. Audience design is the operating problem: who needs which view, at what grain, to make which decision?
A VP of Engineering and an engineering team lead may look at the same system. They should see different things.
The VP wants to know: are we winning? What bets are at risk? What needs my attention?
The team lead wants to know: what's broken? Who's blocked? What are we shipping next?
Same underlying data. Completely different questions. A dashboard that tries to serve both serves neither.
The Team View: Exception and Action
Team dashboards answer different questions:
- What's failing? A team dashboard without an exception view is not doing its job. Teams need to see what broke, who's blocked, and what needs attention now.
- What's our delivery status? Sprint progress, upcoming deadlines, dependency risks.
- What's our quality signal? Bug rates, incident frequency, test coverage. The numbers that tell the team whether they're building well.
The team doesn't need the big picture presented at the same resolution as leadership. They need precision about their own domain.
What Each Level Actually Needs
| Level | Primary question | Time horizon | Grain | Typical action |
|---|---|---|---|---|
| Executive | Are we winning? | Monthly/quarterly | Directional | Reallocate capital, change priority, escalate risk |
| Director/VP | What bets are at risk? | Weekly/monthly | Category | Remove dependency, adjust plan, intervene |
| Team lead | What's broken? What ships next? | Daily/weekly | Functional | Assign work, unblock people, change sequence |
| Individual contributor | What do I do today? | Daily | Task-level | Execute, flag risk, fix defect |
The same metric can appear at every level, but not with the same job. "Activation is down" means strategic risk to an executive, roadmap pressure to a VP, flow debugging to a team lead, and task work to an IC. If the view does not match the action, the dashboard will either be ignored or misused.
