The difference between a dashboard and detailed report is that the former gives you an overview or summary of data while the latter displays all available information. Let’s take this example: Take 11 seconds to look at any dashboard, then go write up 3 pages per what you saw on the monitor. If it took longer than 11 seconds for you to understand what was being displayed on your screen, there are perhaps more details in which case it isn’t a dashboard but rather a detailed report. Where does “11” come from? We have been designing dashboards for 18 years now and figure that “11” is long enough time frame in order to get all of our analytics across with accuracy without taking too much time out of an employee’s day.
Here is an example.
Take a look below, these are dashboards that we see every day. You might have been thinking what is so special about these displays? Well, to be honest with you they all tell the story of an engine and its complex components. We want to understand how each one can give us an accurate picture of the current state of our engines in order for us to build reliable decision making systems which will deliver insights into various factors that affect customer experience and brand perception.
Our approach is simple: use what you’ve got! If it works well then just keep using it by adding additional reporting modules where necessary or investing in better technology if available – but if not don’t fix it! Over time we experienced this transparency between dashboard display screens and many data sources within our ecosystem- from business processes down to integration point configurations-will result in meaningful reports on customer experience quality over time.
Our experience cuts across this wide range of technologies:
Microsoft Power BI & PowerApp
Deltek Project & Portfolio Management
Oracle Prima Vera Cloud