Sparklines inside a horizontal bar chart

http://duelingdata.blogspot.com.au/2017/02/spark-bar-chart.html

Thinks I like about it

- it's a bar chart :-)

- muted non-data

- horizontal allowing good labels

- etc, all the good things about a bar chart

Things I don't like about it:

- the sparklines are distracting when trying to read the bar chart

- the sparklines are hard to compare across the x-axis due to inconsistent horizontal alignment

- I prefer having the values in a column of their own rather than as labels at the end of the bars

Putting the sparklines back into a column of their own would fix the readability issues.

It's an interesting idea. I do sometimes get tired of only using the basic chart types and experimenting is fun - sometimes lots of failures lead to a lightbulb.

Category: Graph design
]]>

Quick question....do you think people interpret the month on a line graph quicker if we give them the first letter of the month, or the number itself on the x-axis? Space is tight! I generally lean on MMM format.

I’ve seen some back and forth on this.... My opinion is that in general people interpret the number of the month quicker than the first letter of the month. We use numbers all the time in dates (ex. 6/5/16, 10-15-99 etc), so it should come quicker to us. First letters of the month not so much.

I would appreciate your thoughts!

Thanks,

Joe

Category: Graph design
]]>

We're having an internal debate in my company over which graph type to use....a YOY graph, or an LTM graph. With the information given, which one would you find more useful?

https://promachinc.co1.qualtrics.com/SE/?SID=SV_9AGewBMz8ER5R09

These are the 2 graphs in question....thanks for the feedback guys.

Category: Graph design
]]>

In the below example each cell represents the average for the skill/area. What I lose is the range of results and particularly for a large area the results end up in the yellow.

Other thoughts?

Category: Graph design
]]>

"tells a story through making your data simple, fun and engaging. It can be used in various situations like a dashboard screen in a room where everyone can see it and notice changes day to day and empathise with the data to rally efforts"

Larger fish = larger numbers.

Fish floating upside down = negative numbers. I pointed a few of these out in the image with arrows.

I've been a long time fan of Stephen's work and made my account for this board today - simply to share the silliest chart I think I've ever seen.

Category: Examples of bad graphs and dashboards
]]>

I am creating a few scenarios on what our revenue will be based on four variables with three different outcomes. For each combination I will calculate expected sales e.g. High product quality / Mid Sales Commission / Low marketing budget / Slow time to market = 10 MUSD sales.

How would you visualize this? There are 3 x 3 x 3 x 3 = 297 combinations. (I use other variables in my calculation which are very sector specific but I think these are easier to understand)

I want to highlight 3-4 scenarios to draw attention to the scenarios which are of most interest. High Product quality Mid Low High Sales Commission Mid Low High Marketing budget Mid Low Fast Time to market Mid Slow

Thanks

Peter

Category: Graph design
]]>

What are your thoughts about the article? We invite you to post your comments here.

-Bryan

Category: Articles by Stephen Few
]]>

Category: Examples of bad graphs and dashboards
]]>

Category: Examples of bad graphs and dashboards
]]>

Best wishes,

Scott

Category: Dashboard design
]]>

Here is an example: http://grommet.github.io/docs/meter-examples#17

To my eye, this stacked bar is way too narrow to clearly see the color segments. From a color science perspective, it's generally determined that 2 degrees field of view (~thumbnail at arm's length) is a minimum for accurate color difference perception. I'm wondering if there's any work (here or elsewhere) that addresses this from the perspective of bar charts.

Thanks,

Douglas G.

Category: Examples of bad graphs and dashboards
]]>

I've inherited some reports with visualisations that I have attempted to improve and would appreciate any feedback whether there are any further improvements that I have missed.

The first graph shows the number of contacts received by the organisation before and after a date on which some organisational change/restructure took place.

I've decided to break each graph down into multiple graphs so that they are less cluttered. As below, the contact types with the highest number are in the top graph and lowest in the bottom graph. I am a little concerned about the gradient of the lines in the lowest graph compared to the highest. Could this be misinterpreted?

Again I am concerned with the gradient of the lines in the bottom graph. Are axis scales in the bottom sets of graphs too small? Also think my choice of colour in the Outcomes of completed contacts could be better. I'm also a little worried by the amount of page real-estate that 6 graphs take up instead of 2 graphs. Would it perhaps be better to place the two sets of graphs side by side?

Any feedback would be greatly appreciated.

Thanks,

quetzalc0atl

Category: Graph design
]]>

Category: Visual data analysis software
]]>

Category: Graph design
]]>