How to create an effective BI dashboard
Credit: Dalle on Microsoft Bing

How to create an effective BI dashboard

You have identified your dashboard's audience, clarified the questions it will answer, and identified the relivant data. See previous article. What is next?

Choose the correct visualization.

Use bar charts when comparing various categories while keeping time constant—for example, the number of EVs sold by country. To avoid possible misinterpretation, start at zero.

Never use a donut or pie chart because the slices are hard to compare. A bar chart can almost always replace pie charts. Check out this video for more information.

Avoid stacked area line charts as, similar to pie charts, the contribution of each item to the overall total is difficult to interpret when multiple items are decreasing and increasing simultaneously. Instead, a summary line chart combined with small charts depicting each item's contribution to the whole can be used.

Use line charts to show change over time. Use descriptive titles, label your axes, and differentiate your selections by using contrasting colors and thick lines. Ensure they are accessible to the color-blind.

Data considerations.

Group relevant metrics. If the metrics depict a time process, use that to lay out your dashboard and improve its ease of use. For example, one way to describe a sales-specific dashboard could be to include it step by step in a sales funnel.

Only include critical data points. Including too many data points will make your dashboard confusing. Your dashboard should be understandable in 5 seconds or less, and any data included should address the specific question your dashboard is designed to answer.

Provide context. Always include an introduction tab in your dashboard describing its use and a data dictionary tab that your audience can refer to if they have questions about how KPIs are defined. Color your KPIs and add a legend so that your audience is immediately aware of what metrics are overperforming and underperforming.

Choose the proper precision or rounding for your KPIs. Apply them consistently for ease of interpretation. For example, income shouldn't be represented down to the last dollar, and if you also include revenue, be sure that both are shown at the same precision.

Lastly, wireframing with dummy data is recommended. Sharing your dashboard ideas early and often with your stakeholders and others will help you incorporate improvements early in your dashboard design process and deliver a better dashboard faster.

What are your recommendations for creating a great dashboard?


Saurabh S.

Analytics Leader | Data driven decision making Evangelist | Business problem solver | Unlocking value from data | Mentor | Business Transformation |

7 个月

Mark Koss - excellent share Mark. Definitely agree on wireframing early version and collaborating and not wait until final release. Avoiding usage of certain charts like pie chart is useful. I would add a couple: 1) Less is more. Build a Dashboard that acts like a Dashboard and not a detail report. Ensure it's simple in layout and conveys message quickly. A hyperlink can be added to a detail report if needed. 2) Have a landing page with metrics definition & useful info. This pre-empts any question on definitions, numerator/denominator (for percentages) etc. And end user focus more on impact and less on what the metrics mean.

赞
回复
Frank Zijlstra

Wilt u uw huis verhuren of wilt u huren? 123Wonen is de verhuurmakelaar van Nederland. Gespecialiseerd in verhuur aan expat! Het beste vastgoedbeheer!

7 个月

Thanks for sharing your experience Mark Koss

赞
回复
Kelly Ferguson Saracco

Financial Services at Salesforce | Commercial Banker | Proud Mama | Former D1 Athlete | Food Lover | Weekend Golfer

8 个月

Great advice Mark Koss Your last point about collaborating with others while you build out the dashboard is key! Getting feedback and more eyeballs, will ensure its effectiveness when released.

赞
回复

要查看或添加评论,请登录

Mark Koss的更多文章

  • Why banks need the Banking Industry Architecture Network (BIAN) model

    Why banks need the Banking Industry Architecture Network (BIAN) model

    Historically, banks who wanted to connect to a new fintech service or replace legacy systems faced several roadblocks…

  • What is a semantic layer and why do you need it

    What is a semantic layer and why do you need it

    We have all been there. Your numbers differ from another team's on a critical sales campaign or key metric, and you…

    1 条评论
  • Why Snowflake versus SQL Server?

    Why Snowflake versus SQL Server?

    As an expert in database architecture, I am often asked what the business benefits are of moving from SQL server to…

  • Cascade Bicycle Club - Why I Love Seattle

    Cascade Bicycle Club - Why I Love Seattle

    Are you new to Seattle and looking to meet great people? Do you want to experience the beauty of the Pacific Northwest…

    6 条评论
  • The lost art of data storytelling

    The lost art of data storytelling

    As dashboard technologies like Power BI and Tableau become more powerful and dashboard design becomes more efficient…

    2 条评论
  • What is a data vault, and when do you use it?

    What is a data vault, and when do you use it?

    Companies transform data through an ETL (Extract, Transform, and Load) into an enterprise data warehouse to analyze and…

    1 条评论
  • Other Variants: ELT, EtLT, and Reverse ETL

    Other Variants: ELT, EtLT, and Reverse ETL

    What is ELT, and how is it different from ETL? ETL transforms the data before loading it into the data warehouse using…

    5 条评论
  • How does Zero ETL differ from a traditional ETL approach?

    How does Zero ETL differ from a traditional ETL approach?

    Recently, AWS released Zero ETL at Re: Invent 2022, with Microsoft, Google, and data warehouse providers Snowflake and…

    1 条评论