If you follow Jakob Nielsen’s Alertbox, you know I’m shamelessly stealing this post title from him. He says that most of the time a list is sorted alphabetically because a) it’s easier to find a name and b) designers are lazy and don’t want to bother finding a better sorting key. While he writes from a design and usability point of view, it fully applies to data visualization too. Data (like people) “rarely think A-Z”.

Alphabetical order is one of the stupidest choices we can make when displaying data visually and in our field we do it out of ignorance or laziness.

I already discussed how to sort bar charts but here is a simple and colorful example of what you can lose when using the infamous alphabetical order. The bars are color-coded for Census Regions and Divisions. On the left the chart is ordered alphabetically and what do you get? A useless rainbow. Yes, it’s easier to find your own state, but if that’s what you want, use a table.

On the right, you can easily see which states are the fattest and which ones are the leanest. So, the first benefit of a well sorted chart is obvious. But since there is a spatial pattern in the data, this pattern emerges too: the top 10 fattest states are all in the South region (and the District of Columbia is clearly an outlier in the region)

Obse Adult Population by State

The chart on the right contains exactly the same data but it’s richer and we can process it more efficiently just because we didn’t overlook how to sort the data.

It doesn’t matter how Tufte-compliant your chart is. If the sorting key hides relevant patterns don’t use it. Always use the data itself and don’t be afraid to make more than one chart with different sorting keys. And, quoting Jakob Nielsen again, “when you reach for an A–Z structure, you should give yourself a little extra kick and seek out something better”. Amen.