Creating a KPI dashboard is an iterative process that requires a bit of thought. It’s one thing to know you want to monitor key performance indicators (KPIs) on a dashboard; it’s quite another to actually build a dashboard.
I think a lot of folks jump right into the building phase of creating a KPI dashboard. They think they can just select their dashboard software and poof! their dashboard will be auto-magically created.
I’ve written about the challenge of assuming technology equals solution before, and this applies to KPI dashboards as much as anything. Dashboard software is not an end unto itself. Building a great KPI dashboard is a process that extends far beyond your computer.
So let me challenge you to think of creating a KPI dashboard a bit differently. Instead of thinking about the data or the software or even the KPIs, think about who is going to use the dashboard and why they’re going to use it.
Among our customers, a critical success factor is getting alignment and buy-in for a KPI dashboard solution. You can put your dashboard in Excel for all I care, but if no one views or cares about the dashboard, then you’re not going to get very far.
As with all things technology, it’s the human element that poses the biggest obstacles.
Here’s a framework for creating a KPI dashboard. I’ll dive into each topic in more detail below.
Well-defined KPIs are the beating heart of your dashboard. Without meaningful KPIs, you might as well be watching the sky for signs that your business is successful.
Defining KPIs is about matching business objectives to internal processes. There are lots of KPI examples out in the wild to help guide you, but the path to success is asking tough questions about your business.
How do you know you’re monitoring a KPI? Discerning the difference between metrics and KPIs can be tricky. I like to think of KPIs as having specific targets that directly impact business outcomes. Revenue is a solid KPI for every business, but how about social media follConsult with stakeholders
Communications professionals live by the following rule: know your audience.
A KPI dashboard is simply another communication medium, like email or a slide presentation, so being in-tune with your audience is critical. Take the time to understand who you’re building the dashboard for, and you’ll soon understand why you’re building a dashboard in the first place.
An executive will have very different data requirements than a manager. This includes the latency of the data, the design of visualizations, and the amount of data shown. Executives may lean more towards a reporting dashboard while a manager may need an operational dashboard.
Take your time on this step. Every minute spent consulting with stakeholders will save you time designing and improve adoption of the end product.
Every dashboard I’ve ever built starts with a napkin drawing. Designing an effective dashboard is challenging. Choosing the most effective visualization for a KPI isn’t always obvious.
As you start to collect KPIs, a cohesive design may present itself. Maybe it’s a combination of charts and bullet charts, or tables and sparklines.
By creating a low-fidelity prototype of your dashboard and then reviewing it with stakeholders, you’ll get an immediate sense of the impact of the dashboard. Design choices may seem indefensible when an executive is scratching her head wondering what the data is telling them.
As a general rule, data visualizations should be simple enough that a new employee can understand the message you’re trying to convey. This is challenging. But by starting with something you can throw into a trash can, you spare your ego and save time in designing the dashboard.
Here are a few factors to consider when choosing KPI dashboard software:
You absolutely can build an effective KPI dashboard in Excel. The challenge comes later on when you want to update the data on that dashboard. At the end of the day, KPI dashboards ought to save you time and effort when creating and distributing reports.
Dashboards within software solutions can also serve an important role. Again, you may find yourself outgrowing these solutions before too long. Dashboards are designed to get data out into the organization. For example, building a Salesforce dashboard to share sales KPIs with your executive team.
Well, it might be, if that’s a success factor for your business. If having 100,000 Instagram followers means you put food on the table, you’d better be tracking towards that target.
In defining your KPIs, you must start having conversations with stakeholders, executives, managers, and employees from all areas of your business. Asking for input is the first step in drumming up buy-in for a KPI dashboard. Folks will tell you what’s important to them, and this will make your job of designing a dashboard much easier.
Cue hyperbolic comments about big data, the amount of data we have available, and the increasing complexity of data. Got it? Good.
Gathering your data likely requires going to multiple services, working with your operations team to craft some SQL queries, and even using APIs to automate data retrieval.
Each KPI you track will have at least one data point originating from one system or another. Take some time, create a spreadsheet, and map out the data picture behind your most important KPIs.
At this stage, you’re going to need to spend some time building your data sources. This step causes the most headaches. I can offer aspirin, but that’s about it. For non-technical users, APIs are challenging.
Most software vendors offer professional services, which may be something you want to consider if the challenges in this step are insurmountable. It’s a pain point every dashboard software vendor is working to solve, some better than others.