Related Posts
Additional Posts in Data Analytics & Data Science
New to Fishbowl?
Download the Fishbowl app to
unlock all discussions on Fishbowl.
unlock all discussions on Fishbowl.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Download the Fishbowl app to unlock all discussions on Fishbowl.
Copy and paste embed code on your site

Scan your QR code to download
Fishbowl app on your mobile

Just keep it high level and doing get into the technical stuff but do point out why you took that approach and how it’s beneficial -for any analytics you do (assumptions you took, edge cases you considered,etc).
For dashboards - depends on your audience. For executives or senior leadership - you’d want to showcase metrics/KPIs and the landing view snapshot should tell a story without having to dig into the data/charts. Keep it high level and only the most important/impactful stuff. Don’t have to be overly complicated -make it stupidly easy and interactive and you’ll see a much wider adoption rate. You could also build your own metric and in that case it’s best to have a hover over definition so your audience knows what to expect.
Thank you so much for this insight
Mentor
Storytelling is the key element of any dashboard. If you convey your story to your stakeholders through the dashboard, they will be hooked!
For me, gathering data requirements also is a crucial step before you dive onto the project and start building.
First, you need to understand what this dashboard needs to answer for your audience, what metrics do they like to see.
Keep the discussion within the key stakeholders or better yet SMEs who have been using the data and most familiar with it.
Having a clear direction on what the dashboard is for would help a lot in producing one that solves the problem and saves time for everyone.
Keep only relevant charts and metrics, lessen the clutter/ noise. Most of the time making it simple and less complicated is the way to go.
Great insight, Thank you