Have a slice

Even if they are not recommended, pie charts are widely used. We might come across a client or user that will not accept alternative visualizations forcing us to use them.

When this is the case, we need to make sure to make pie charts as clear and easy to use and understand as possible. There are some tips and tricks to take into account when using pie charts.

Number of slices

Pie charts are not the best choice when our data is represented by more than 10 slices. Our eye can’t distinguish what’s the biggest or smallest slice and of course we cannot tell anything about the other slices. If we cannot tell much about the slices, then the chart becomes useless.

Colors

Can you tell which is the biggest slices in the following pic chart? I can’t either, and the colors don’t  help as there is no clue of what color represents the maximum or minimum value.

Image 1

Image 1



Now take a look at the following chart. Can you tell which is the maximum value? Most of us will say the the biggest slice is the one with darker color and we will be right most of the time. However, we will not be sure until we hover over each slice and compare the values.

Image 2

Image 2

Whatever the case is, it is recommended to use shades of colors. In my example, blue. This can be achieve with the ColorMix1 or ColorMix2 functions.

Highlight

One simple trick consists of highlighting the biggest slice as shown in the chart below. Our eye is first drawn to the slice which is slightly out of the center of the pie. This can give as a better idea of what the biggest slice is.
Even if we have a highlighted slice with the darkest color, it can represent the smallest value.

Image 3

Image 3

Adding extra information

Depending on the pie chart, it is adviceable to add data points to each slice. These can be real values, or a percentage representation over the total.
Bear in mind that absolute values could be large which will make the pie smaller. Percentages on the other hand work better.

Pie Chart Percentage uniformed colors

Image 4

Image 3 and 4

Image 5

ORDER

Things are getting a bit cleaner but we still need to define some order. In the previous images, we can’t tell if the slices are sorted in a particular order or not. Sorting is usually very important as allows you to follow or spot patterns. For pie charts, there is no much that can be done regarding sorting. If you have not noticed it, the previous images show a pie chart where the biggest slice is on the top left side followed by the smaller ones from left to right (counter clockwise).
You won’t notice this until you actually compare the values.
We tend to read text on rounded things in a clockwise sense. Things might change a bit if  your language is read/written from right to left.
Having mentioned this, we could sort the pie chart with the highest value first (top right corner) followed by the others in a clockwise order. To make it even clearer, we can add a ranking with 1 being the highest value.

Image 5

Image 6

So, next time you create a pie chart, use all or some of these tips to make sure everybody is able to read and understand what you are trying to communicate. You can even mix most of them like adding percentages and ranking to provide even more information.

I would like to invite you to read a previous entry about Attribute types.

JV

Advertisements

Tags: , , , , , ,

6 responses to “Have a slice”

  1. Albert Surrounding says :

    In all those pies that are shown in this post, the main idea is not what’s the biggest; the main idea is that they are all equal. That’s what your brain see at a glance. Pies are not to show accurate results. They are meant to show the general idea. If you want to know which one is the biggest, use another graph or table and order it.

    • Business Intelligence Experience says :

      Hi Albert,

      I agree with your comment. You can’t understand the exact values from the charts and that’s what I wanted to express. But, you depending on the slices you won’t be able to understand the general idea either. I would avoid using pie charts if possible, but if you must use them, I would make sure to show as little dimension values as possible.

      • Albert Surrounding says :

        Exactly! Pie charts have limited use. They’re many times confusing. But in this case, with those very tight values you’ve placed, do you think a bar chart with no values on it, would solve the problem? Only if it is sorted maybe.

  2. Business Intelligence Experience says :

    Hi Albert, this is a very peculiar example that helped me present an idea. It’s very rare to have few values each close to each other but it can happen (small standard deviation). You can play a lot more with bar charts so I would recommend this over pie charts. In bar charts you can show horizontal and vertical grids, set the max and min scale which will help with the visualization, you can add values on the axe or on top of each bar, you can also set the static step which will make things even clearer. Even more, for my example I would use a bar chart and untick the option “Forced 0” in the Axes tab. This will help distinguish all bars at a glance. All depends on your data and you are the one that knows your data best.

    Juan

  3. Anugraha Jain says :

    Hello Juan,

    We have developed a new gen developer friendly BI framework with some extremely unique features. Would like to give you early access & love to hear your opinion. Please do let me know of how to reach out to you. Would be launching product in 1 week from now.

    Also could you please share your email details for further communication.

    Regards,
    Anugraha

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: