A Dashboard Designer's worst nightmare is to have their dashboard criticized. Or worse.. To have their skills questioned. There are so many things that can go wrong when developing dashboards. These can include: - A limited understanding of the data. - An inability to access users - A pressure from management - The wrong tools stack - A lack of resources - A lack of method - A lack of training - A lack of time - And more And 90% of the time, when a project or dashboard fails, it's one or other of these two elements that suffers: - The tool - The developers A tool can be changed. But when it's the teams that suffer, it can cause a loss of credibility and confidence, and lead to tensions or people leaving. It's unfair. Most if the time, there's just one brick missing between the audience, the ambitions and the plan. Over the last few months, I've been working on the dashboard assessment checklist, which aims to close this gap. It's such a simple product that all you need is a pencil and a single sheet of paper. Inside, I've concentrated several years' experience in observing what goes wrong in dashboarding projects. With the checklist and the ready-to-draw diagrams, in just a few minutes you'll be able to visualize the 'identity card' of your dashboard, as well as its strengths and weaknesses. This simple page linked to a dashboard will enable you to : - Structure the project - Identify the audience - Identify the complexity of the data - Identify the purpose of the dashboard - Assess whether your developments comply with best practice - And visualize inconsistencies between assessment components For instance, once the assessment is complete, you will easily be able to see anomalies such as : - A massive volume of data + an extra-granular level of detail + several years of data history = excessive loading time and business trying to put everything in the same dashboard - An exploratory dashboard + 4 different purposes = Scope is overly broad and an audience with limited data maturity. I'm pretty sure you'll be as excited to use it as I was to design it. Source: Aurélien Vautier