September 21, 2017

Showing developments over time in a Theory of Change: Unicode Sparklines ▇▆▅▃▂

Sometimes in Theories of Change it is very useful to be able to present simple developments over time, for example an increase or decrease or stagnation. Theories of Change are not famous for their ability to deal with time at all, for which they are often criticised. I’ve written before and here and here about the problem of Variables which may or may not exist across a whole project duration - here, I’m tackling the problem of reporting changes in the value of a Variable when it does stretch across the whole duration of a project.

Tufte’s Sparklines can do this well.

But I am looking for the simplest kind of display which is readable on Variables within a Theory of Change or Logframe even from afar. Sparklines, simple as they are, are still too detailed for a crowded diagram with many Variables which can get quite small. Plus, they suggest a degree of accuracy which I’m not looking for - I just want to be able to indicate the roughest rises and falls.

Plus you can’t easily cut and paste sparklines into a report, say.

So, enter Unicode Sparklines - the Flintstones of data display for Theories of Change.

So for and the new interactive version I’ve implemented simple Unicode Sparklines just with these five blocks: ▇ ▆ ▅ ▃ ▂. To produce them at, when typing the names of your Variables, you just type !1 !2 !3 !4 and !5. !1 produces a small bar and so on up to !5 which produces the tallest bar. To get a sequence of bars you can write for example !1!2!3 but abbreviating to !123 works as well.

Here’s an example diagram.

Because these five little blocks are plain Unicode, so you aren’t tied to Theorymaker. You can write them directly in text, like this: temperatures have been changing lately, ▂▅▇. You can use them directly in Office documents - find them in your insert/symbol” dialogue in your word processor or just copy them from this post. In MS Word, there’s a special trick - type 2582 and then immediately type Alt+x - that will get the smallest bar. For the others you have to type 2583, 2585, 2586 and 2587. Primitive, but expressive - like the Flintstones.

Funnily enough, the Unicode implementation of these kinds of block isn’t very consistent - I had to mess about to find just these five which look consistent everywhere, which explains why unfortunately the height intervals aren’t quite even.

(Turns out the idea of Unicode sparklines isn’t new: see here.)


Previous post
Moved to Clevedon, UK! This is just to say that I’ve moved with my family to Clevedon, UK - leaving Sarajevo after very nearly 20 years, … leaving a whole heap of dear
Next post
Links for my AEA eval2017 presentation, Washington DC AEA program listing. A short post here on this blog The book is not an easy read But there is an Epilogue right at the back of the book which

This blog by Steve Powell is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License, syndicated on r-bloggers and powered by Blot.
Privacy Policy