Sometimes it just takes training users to get that insight out of the dashboard that they need. So technical skills obviously make a really good analyst, but the ability to be able to connect the data to the business and drive that impact takes you a whole lot further than just a technical analyst and a business analyst. So it takes you really to the next step of what a good analyst is and who a good analyst is and when it comes to creating dashboards. So I'll wrap up with those five rules again. So one, make sure that whenever you're starting out building a dashboard, you want to understand the problem before even touching the data. You want to make sure you're having those conversations with your end users.

Understand exactly what they need out of it instead of just, hey, can you build me a dashboard that shows me X, Y, and Z? What are you looking to get out of this? Know exactly who you're building it for. One dashboard isn't going to fit the needs of both an executive and a manager or a manager and an analyst. Know exactly who you're building it for. And if it takes multiple versions of the same data to achieve that, then that's okay as well. Don't confuse more information with more value. Just because you have more KPIs on the screen doesn't necessarily mean that you're getting, your end user is getting more value out of this. All you're doing is telling them another number, right?