Share on facebook
Share on twitter
Share on linkedin
Share on email

Tips for Building an Effective Analytics Dashboard

Building Dashboard in Google Data Studio

Building an effective dashboard is tough work. I find most clients struggle when trying to build a dashboard internally due to a lack of agreement around what should go into it. Sure, there are also technical challenges, but I can’t count the number of times I’ve been told in my career to build a dashboard for an entire business unit (or even company) with little to no guidance from the stakeholders. Usually, either I as an analyst should “just know” what reports they normally look at or, more likely, nobody has the time to stop and provide input.

Unfortunately there’s no real way around this, and often times stakeholders have strong opinions about what should be included months after the dashboard is complete. However, with that in mind, I still find it helpful to document the why behind what I’m building.

If you’re struggling with input from stakeholders, create your own version of a framework below and share it back with them. Ideally you can get an idea if what you’re covering in a dashboard is what they actually want to see or answers their immediate business questions.

dashboard pre-build process

When you’re creating your wireframes or actually going through building the dashboard there are a couple of things you can do to help ensure your success. First prioritize what you’re putting in your dashboard. I like to divide my dashboard real estate into four quadrants, understanding that most people read a dashboard in a Z pattering starting in the top leftmost corner.

most important emphasized dashboard

Next be deliberate in your pre-attentive attributes; these are the visual elements of a dashboard that the subconscious mind picks-up on before starting to think about the numbers. It’s the short mental homework that we don’t even think about that draws our attention to what’s good or bad about the reporting. Attributes like color/hue, size, or added marks (like up or down arrows) are incredibly important to be deliberate about.

For example, in the dashboard above, the use of stoplight colors in the table on the left may leave stakeholders with the immediate impression that bounce rate (red) was bad while pages per session (green) is good. In reality, the person who designed this dashboard just wanted to break up the columns in the table with color and made an unfortunate choice. Meanwhile, the table on the right uses red bars to highlight poor performance, but there’s not enough context to understand why. 

Building an effective dashboard is a moving target, because how people think about their business changes over time. However ,with a little bit of pre-work and attention to detail, you’ll be able to build the best version of the dashboard with what you have to work with.

Need Dashboarding Help?

If you're ready to take your analytics dashboards to the next level, contact the experienced team at InfoTrust.
Share on facebook
Facebook
Share on twitter
Twitter
Share on linkedin
LinkedIn
Share on email
Email

Other Articles You Will Enjoy

Getting Started with Tableau

Getting Started with Tableau

Tableau, a data analysis and visualization tool, was founded in 2003 and acquired by Salesforce Inc. in 2019. It gained a lot of popularity…

6 Considerations for Server-Side Tagging in Google Tag Manager

6 Considerations for Server-Side Tagging in Google Tag Manager

One of the hardest things about diving into a new technology is that you don’t know what you don’t know. Here at InfoTrust, we…

Google Analytics 4 vs. Firebase vs. Firebase Analytics: What’s the Difference?

Google Analytics 4 vs. Firebase vs. Firebase Analytics: What’s the Difference?

There’s a lot of anticipation surrounding Google Analytics 4, an update within the Google Analytics (GA) product. Until recently, web analytics remained separate from…

5 Key Benefits of Using BigQuery ML Clustering

5 Key Benefits of Using BigQuery ML Clustering

With the increase in U.S. data privacy laws and a cookieless world on the horizon, augmenting marketing strategies with first-party data is more important…

The E.A.R.T.H Principle: How to Run an Enterprise Analytics Team with Less … and Stay Sane

The E.A.R.T.H Principle: How to Run an Enterprise Analytics Team with Less … and Stay Sane

Recently, I worked for a large financial institution on the client side, leading a global enterprise-wide team that served 12 million customers and more…

Annual Retail Report 2021 | Evaluating the Marketing Technology Landscape

Annual Retail Report 2021 | Evaluating the Marketing Technology Landscape

Table of Contents In late 2020, I conducted and wrote an analysis about the “state of the retail industry” based on the growing marketing…

How Advertisers Should Plan for Activation in a Reduced Cookie World

How Advertisers Should Plan for Activation in a Reduced Cookie World

By now, you’ve likely heard Google Chrome will be removing the ability to use third-party cookies in 2022. Safari and Firefox have already removed…

How Does Google Data Studio Compare to Looker?

How Does Google Data Studio Compare to Looker?

Google Data Studio is a fairly prevalent tool for organizations using the Google marketing and analytics stack. Not only is Data Studio simple, free…

What are the Differences Between a GA4 Configuration Tag and a Settings Variable?

What are the Differences Between a GA4 Configuration Tag and a Settings Variable?

Universal Analytics (UA) was released in 2012. Nearly a decade later, Google launched the most significant analytics platform upgrade in that span with the…

Talk To Us

Talk To Us

Receive Book Updates

Fill out this form to receive email announcements about Crawl, Walk, Run: Advancing Analytics Maturity with Google Marketing Platform. This includes pre-sale dates, official publishing dates, and more.

Our website uses cookies and may collect user information to provide a good experience. Read our Privacy Policy here.

Leave Us A Review

Leave a review and let us know how we’re doing. Only actual clients, please.