Why Numr
Arrow
Why NumrNumr vs RestPredictive Experience Intelligence
How It Works
Arrow
How Numr WorksFor Cio's and it teams
Industries
Arrow
All IndustriesBankingInsuranceAutomotiveAirlinesRetail
Resources
Arrow
case studiesBlogKnowledge Center
Company
Arrow
about numrPress & MediaPrivacy Policy
book a demo
book a demo
Knowledge Center
Visualization
How to Plan for a Dashboard?

How to plan for a dashboard?

This is some text inside of a div block.
Example H2

Steps for building a dashboard

1. Build the customer journey (or refer to the journey created at project kick-off)
    a. Understand non-journey listening posts
2. Understand users types - write down objectives for each user type
3. Map out every dashboard for each user type

Building the customer journey

1. Hand-draw the journey map. Identify where listening posts are in place and which ones are missing.
2. Is there a way we can create a customer journey score?

Understand non-journey listening posts.

1. Is there an RNPS or CNPS survey?
2. Is there social media input?

When an RNPS and CNPS survey is in place, those should be used as the primary KPI. Therefore, we need to plan for these dashboards before coming up with the journey NPS dashboard.

Map Users & Roles for each dashboard

Create a table like this

User Type Job Role Primary KPI Secondary KPI(s) What is his expected action on looking at the data
CX Team Improving the customer experience at every interaction point Churn Rate NPS Should be able to understand:
  1. If we are improving
  2. Where to put in the investments e.g.
    • a. Areas that need improvement
    • b. Which customer groups?
    • c. Which geographic locations
    • d. etc.

There can be many different types of users

- C-Suite  
- CX Team
- Process owners
- Group owners
- Regional leads
- Account managers (for b2b)
- Customer support rep
- Delivery/installation agents
- et.

There should be a different dashboard that we create for each lead.

Map every user to a dashboard

Build a dashboard view for each user type in the system and map access. Then map which user would have access to which view.

Executive Summary Process View Agent View
C-Suite X X
Process Owner X X
Delivery/installation agents X

The view should be focused on the primary user who will be logging into that particular view most often. The picture will aim to answer the question of the process owner.

Conclusion

Building a dashboard needs to be thought through in a lot of detail. Then, methodically go through all your requirements, and a pattern will emerge.

Remember to review the requirements on an ongoing basis. Talk with the users and ensure that new evolving needs are incorporated over time into the dashboard design.

‍

Author

Amitayu Basu
CEO
Client

Tired of this cycle? See how Numr breaks it

Book A Demo
Book A Demo
Talk to Our Team
Talk to Our Team
ClientClientClientStarStar
Let’s Fix CX Before It Hurts Revenue
No long forms. No sales push. Just a walkthrough of how Numr works.
Platform
How It WorksFor CIOs & IT TeamsWhat You Can DoCompare Us vs Traditional CX
Resources
Case StudiesBlogKnowledge CenterAPI Docs
Industries We Serve
BankingInsuranceAutomotiveAirlines
Company
About UsPress & MediaPartners
Legal & Security
Privacy PolicyCookie PolicyTerms of ServiceAcceptabel User Policy
Numr is an AI-powered customer experience platform that detects drop-offs, explains churn,
and drives real-time action — before revenue walks out. No dashboards. Just outcomes.
Predict behavior
Find root causes
Trigger action automatically
See It in Action
See It in Action
Request a Demo
Request a Demo
Based in Canada. Operating globally.
sales@email.numrcxm.com
© 2025 Numr Inc. | Built to move numbers — not just track them.
Icon
Linkedin
Icon