Designing Effective Customer Dashboards
The source calls the customer dashboard a trust surface, not a sales surface, because it shows the customer what the system is doing.
Picturing the Dashboard Before Reading On
When people hear the word dashboard in a product setting, many picture a screen built to win business. Its charts make the product look impressive, its highlights nudge a buyer toward a purchase, and its prompts invite an upgrade. This picture treats the dashboard as a sales surface, a place where the goal is to move a customer toward a decision.
The source sets out to correct this belief. Before you read the correction, commit to an answer of your own.
What do you think happens?
According to the source, is a customer dashboard primarily a sales surface or a trust surface?
Reveal answer
A trust surface, because it shows the customer what the system is doing.
The source places the dashboard in the trust category. It is an artifact the customer consults to understand activity, not a page whose main job is to close a sale.
Why the Label Changes the Question
The distinction matters because the two labels imply different questions. A sales surface asks what the customer should do next. A trust surface asks whether the customer can see what the system has been doing and feel reassured by it. The source places the customer dashboard in the second category.
Once you ask the trust question, the design of the dashboard makes more sense. The screen is judged by whether it lets the customer understand activity, not by whether it persuades. A dashboard that succeeds as a trust surface builds confidence in the system. A dashboard read as a sales tool misreads its purpose and undermines the confidence it is meant to build.
| Aspect | Sales surface | Trust surface (the source's category) |
|---|---|---|
| Question it asks | What should the customer do next? | Can the customer see what the system has been doing and feel reassured? |
| Main job | Move the customer toward a decision | Let the customer consult activity and understand it |
| Typical content, as the belief pictures it | Impressive charts, purchase highlights, upgrade prompts | This week's activity compared with last week, presented in the customer's language |
| Effect on confidence | Can read as pressure | Meant to build confidence in the system |
The same screen judged by two different purposes
Reading This Week Against Last Week
According to the source, the dashboard shows the customer what the system is doing this week and how that compares to last week. The comparison is the important part. A single snapshot tells a customer what is happening now. A comparison with the previous week gives them a sense of direction and consistency. The dashboard frames activity against a recent baseline, so the customer sees change rather than a standalone number.
Reading a hypothetical weekly panel
A hypothetical dashboard panel says: this week's activity compared with last week's. Work out what the customer can learn from it, using only the framing the source gives.
- 1Identify the two snapshots
The panel shows this week and last week. Last week acts as the recent baseline.
- 2Look for the comparison, not just the number
A standalone figure would show only what is happening now. The comparison shows whether activity moved relative to the prior week, which gives direction.
- 3Check the language
The source says the information is presented in the customer's own language, so the panel should be readable without knowing how the system was built.
- 4Judge the purpose
The panel helps the customer see what the system has been doing. It does not need to ask for a purchase to be doing its job.
The customer learns how this week's activity relates to last week's, in plain language. That is the trust function the source describes.
The Weekly Loop the Customer Sees
The source describes a per-week loop, and it is the loop the customer sees. The loop is the underlying rhythm of what the system does, measured in weeks. The dashboard is the artifact through which the customer meets that rhythm. The customer experiences the loop through the dashboard, and the dashboard reports it week by week against the previous week.
The source does not describe the internal steps of the loop. The diagram below therefore shows only the reporting path the source does describe: each week's activity is compared with the previous week and shown to the customer in their own language, and then the cycle repeats.
Mistakes in Reading a Dashboard
Common mistake Treating the dashboard as a sales surface
What it looks likeJudging a weekly panel by asking whether it makes the product look impressive or whether it prompts an upgrade.
Why it failsThe source places the dashboard in the trust category. Its purpose is to show the customer what the system is doing, so a sales reading misses that function.
Do this insteadAsk whether the customer can see what the system has been doing and feel reassured by it.
Common mistake Reading a single snapshot as the whole story
What it looks likeLooking only at this week's activity and ignoring that the panel also shows last week.
Why it failsA standalone number tells the customer what is happening now but not whether it is changing. The comparison is what gives direction and consistency.
Do this insteadRead this week's activity against last week's baseline.
Common mistake Assuming the source lists the exact metrics
What it looks likeStating that a particular measurement must appear on every customer dashboard.
Why it failsThe source does not list which specific measurements appear, so such a claim is not grounded in it.
Do this insteadDescribe the framing: current week, prior week, and customer-readable presentation.
Common mistake Confusing the loop with the dashboard: the loop is the rhythm of the system, and the dashboard is where the customer meets it
Classifying a Dashboard Panel
A hypothetical customer dashboard shows this week's activity beside last week's, in plain language. Decide whether the panel is doing a trust job or a sales job, and explain your answer using the question each surface asks.
Hints
- Ask which question the panel answers: what should the customer do next, or can the customer see what the system has been doing?
- Check whether the panel gives a comparison with a recent baseline or only a standalone figure.
- Remember the source places the customer dashboard in the trust category.
Putting the Trust Lens to Work
- 1The source calls the customer dashboard a trust surface, not a sales surface, because it shows the customer what the system is doing.
- 2The dashboard presents this week's activity compared with last week's, in language the customer understands.
- 3The per-week loop is the loop the customer sees, and the dashboard is the artifact through which the customer meets it.
- 4Reading a dashboard as a sales tool misreads its purpose and undermines the confidence it is meant to build.
Key Takeaways
- The source calls the customer dashboard a trust surface because it shows the customer what the system is doing.
- A sales surface asks what the customer should do next; a trust surface asks whether the customer can see activity and feel reassured.
- The dashboard compares this week's activity with last week's, so the customer sees change against a baseline.
- The per-week loop is what the customer sees, and the dashboard is where the customer meets it week by week.