I’ve seen hundreds of “executive dashboards” in Salesforce. Most of them get built in a panic the week before a board meeting, used twice, and then quietly forgotten while everyone goes back to spreadsheets.
The dashboards that stick share three traits: they answer a small number of questions clearly, they’re honest about what the data does and doesn’t show, and they get reviewed in a meeting. None of those are about the dashboard tool itself — they’re about how you design and operate it.
Start with the questions, not the charts
Before you build anything, get the executive (or executive team) to tell you the four or five questions they want answered every Monday morning. Not metrics — questions.
“Are we on track for the quarter?” is a question. “Quarter-to-date bookings” is a metric. The dashboard’s job is to answer the question, and the metric is one piece of how it does that. If you build straight from the metric, you’ll skip the context the executive needs to interpret it.
Layout: one screen, five or fewer tiles
If your executives have to scroll, you’ve already lost. Five tiles on one screen, organized roughly like the diagram above:
- Top left: The biggest leading indicator (pipeline, bookings, MRR — whatever drives the business).
- Top right: Progress toward the period goal, with explicit time remaining.
- Middle row: Three or four key metrics as big numbers — closed won, win rate, at-risk revenue. Don’t make executives interpret a chart to read a number.
- Bottom row: One trend chart that gives context. Is the trajectory good, bad, or flat? Eight to twelve weeks back is usually right.
Be honest about the data
If your pipeline number depends on stage hygiene, and stage hygiene is bad, the dashboard is lying. Either fix the underlying data or add a small caveat tile: “Pipeline assumes all opportunities have current Close Date. 12% of opportunities are past close date — see hygiene report.”
Executives lose faith in dashboards when the numbers don’t match their intuition and nobody can explain why. A small honesty footer beats a dashboard that quietly overstates the business.
Make the dashboard part of a meeting
The single biggest predictor of whether a dashboard gets used: is it on the screen during a recurring meeting? “We open this dashboard at the start of every Monday pipeline review” makes the dashboard a real artifact. Without that, even the best layout becomes shelfware.
Schedule that meeting. Subscribe the attendees to the dashboard so it lands in their inbox each Monday morning. Then it’s ready when they walk into the room.
Iterate ruthlessly in the first 30 days
Watch how it gets used. The tile that gets stared at the longest is probably the most valuable; the one nobody looks at is probably noise. Cut it. Add what people keep asking about that’s missing. By month two the dashboard should be settling into something the team trusts.
If you’re not iterating, you built a report — not a dashboard.
MotionDog 
Leave a comment