Category Archives: Humanitarian

At least Google Earth is good for fundraising

So UNHCR releases a Google Earth layer to great fanfare:

Unveiling a new UNHCR layer in Google Earth before invited guests at UNHCR’s Geneva headquarters, Deputy High Commissioner for Refugees L. Craig Johnstone hailed the project as means to educate people worldwide on the plight of refugees and on the humanitarians who help them.

“Google Earth is a very powerful way for UNHCR to show the vital work that it is doing in some of the world’s most remote and difficult displacement situations,” said Johnstone. “By showing our work in its geographical context, we can really highlight the challenges we face on the ground and how we tackle them.”

I download the UNHCR KML file, fire up my creaky old version of Google Earth and have a look. The first thing I notice is that every time I click on a link for more information, it tells me how much it costs to buy school or farm equipment, and gives me a link to UNHCR fundraising so I can cough up right there.

So Google Earth – one of the most powerful yet accessible technology tools ever created, at the vanguard of a geospatial data revolution – is reduced to lining the pockets of UNHCR – an agency, incidentally, that recently came bottom of Ranking of Donor Agencies on Best Practices in Aid (Where Does The Money Go? [pdf], Easterly and Putze 2008). I don’t think that this is the best way to reach out to the public if you’re serious about educating them about refugee issues.

Now that I’ve got that rage off my chest, what’s positive about the UNHCR Google Earth layer? Well, it’s a start, and there are some interesting features; if you click on the layer for accessibility, it presents you with a visualisation of the catchment areas of water points in a refugee camp.

This is useful because it starts to give people an idea of one of the key issues for refugee management and the complexity of running a refugee camp. However it doesn’t really go much further than that – there’s no explanation of why those catchment areas are important, or how this information could be used. I’d also be surprised to hear that UNHCR staff working in the field are using this sort of tool to plan camp construction and management, but I’d love to hear from any UNHCR staff if I’m wrong… but that’s exactly the sort of thing we should be doing.

It does give a sense of the global span of refugee issues, and by focusing on three different locations it does present a range of different environments. However it’s still peddling the message that refugees are fundamentally people who need help, and that international organisations are the only ones that can help them. There’s nothing (that I saw) about the primary responsibility of governments to address the needs of refugees, or about the fact the primary source of support for most refugees is the refugees themselves.

If you’re interested in finding out how great UNHCR is, it’s a fantastic resource. If you’re interested in getting a deeper understanding of refugee issues, you probably want to look somewhere else. I realise that I’m starting to sound really bitter in these sorts of posts, but please understand – that’s because I think we should be doing better. Much, much better.

InSTEDD publishes!

Well, not yet, but they will [pdf]. Janet Ginsburg explains the development of the idea of the Humanitarian Technology Review, while Bruno Giussani covers the recent TED breakfast, where Eric Rasmussen gave an update on InSTEDD.

Initially the idea of a Humanitarian Technology Review sounds like a good idea – if it’s done right. The first two questions – remember the first two questions, everybody! – are: who is the target audience, and what do you want them to do with the information you’re providing? The briefing paper I linked to above says

The Review’s readers, like the Review itself, span many niches: medical researchers, software developers, policy-makers, funders, doctors, veterinarians, communities trying to prepare for or reeling from disasters – even other media.

The one group that is noticeable by its absence is – well, me. People like me, anyway, who seem to fall under the catch-all term “practitioner”. I see doctors and veterinarians in there, but which doctors and veterinarians, exactly? I think it’s likely that I’ve misunderstood – the briefing is explicit that this is about building connections between disciplines, and it’s clearly aiming at a wider audience than the humanitarian community.

If we look at the disciplines that they’re talking about, it’s a wide selection, so it’s probably easier for me to focus on the technology examples given in the review:

  • lightweight fabric + satellite technology = a cheaper portable satellite dish
  • software + cell phones = real-time surveillance for bird flu
  • GIS + interactive mapping = real time tracking of fires and floods
  • solar panels + refrigerator = reliable field transport for vaccines
  • filter + straw = a mobile water purification device
  • open source water tech + microfinance = funding for small water projects
  • genetic sampling + fast data analysis = identifying a pathogen in hours

I’m going to think about those examples over the next few days, but I’m struggling to see how a publication can cover all of these and still appeal to a coherent audience. That’s why communities of practice exist around epidemiology, water and sanitation, and the like – because they’re focused enough to hold peoples’ attention.

The success or failure of the HTR will be in the delivery, and on that front I’m very positive about their proposal to combine different delivery streams. At the very least, InSTEDD’s deep pockets will enable them to experiment and see what works, although I’d warn them not to expect collaboration to magically appear – two years on ECB teaches you that for nothing.

(NOTE: Full disclosure – I thought about a similar idea a few years ago, but gave it up because I didn’t think it was viable. Two attempts have been made to develop this sort of thing previously – ReliefWeb’s HIN and CMI’s PeaceIT [pdf] – but the InSTEDD concept is much wider.)

DisasterTech at eTech 2008

The O’Reilly Emerging Technology conference is another one of these confabs that I watch from a distance, filled with a mixture of awe and dread. (Awe at the sheer brainpower that you can see in the many presentations, and dread at what might happen next.) This year, Jesse Robbins and Mikel Maron gave a presentation on DisasterTech to the poor and huddled masses that attended, updating some of their earlier thoughts on areas such as SMS, open source and distributed approaches.

Now I like Jesse and Mikel, and I agree with the lines along which they’re thinking, but when I see slides that say “225,000 deaths preventable with existing technology”, I start to worry about whether the expectations of those poor and huddled masses from the technology world are being raised just a little too high… but I’d rather wait until I can hear the audio rather than just read the slides.

One point they did make that’s worth picking up (because as far as I know, this is the first time it’s been explicit) is that disaster technology tends to follow this pattern:

  1. Disaster
  2. Ad Hoc Adaptation
  3. Championship
  4. Iterative Improvement

That’s pretty accurate – most of the more interesting developments of the last few years have followed that model. However there are definitely problems with Championship – not as a concept, but in terms of where to target your “championing” efforts.

I believe that most technology dissemination in this sector isn’t through organisational adoption – there’s just too much autonomy at the local level – but through word-of-mouth. Somebody sees something working, tries it out and takes it forward (or not) – but only within their particular part of their organisation. What this might mean is that we need to take a viral approach to this, rather than seeking to get management (i.e. top-down) approval, particularly if we want to reach smaller groups on the ground.

With that in mind, we have to be anthropologists as well as technologists. Cultures are different, communities are different and people are different; what “works” in terms of viral dissemination in the US is simply not going to work in Bangladesh. It’s not just the technology that has to adapt to these different environments; it’s us as well. Hopefully the start-up jockeys at the conference realise that…

Stamping on Statistics

The government are very keen on amassing statistics. They collect them, add them, raise them to the nth power, take the cube root and prepare wonderful diagrams. But you must never forget that every one of these figures comes in the first instance from the village watchman, who just puts down what he damn pleases.

Josiah Charles Stamp was many things during his lifetime, including President of the Royal Statistical Society between 1930-32, and his view on government statistics is well worth bearing in mind whenever we look at the sort of statistics that tend to crop up in humanitarian and development work. International organisations tend to act in much the same way as governments when it comes to statistics, which we usually refer to as indicators.

Until very recently, all the information we had during a disaster was based on eyes on the ground – from residents in or visitors to affected areas. With the advent of remote sensing, we have a new source of information that doesn’t rely on actual presence – but even so, it’s worth noting that remote sensing without some form of ground truthing is frankly useless. I remember when we were looking at crop patterns in Afghanistan – an expert could pick out opium crops from a satellite image, but it was still necessary to send people to verify (and get shot at, of course – all part of the fun). So we still rely on eyes on the ground, which means that there’s always a human factor involved in data collection.

Where there’s a human factor, there’s always the scope for creativity that Stamp noted, or for deliberate manipulation. On the micro scale, that’s unlikely to make a huge difference, since when you aggregate up to a national level many of the irregularities will be levelled out – unless everybody at the micro level is fiddling the numbers in the same way. For example, anybody affected by a disaster is likely to exaggerate their needs if they think it will mean more assistance; any organisation responding to a disaster is likely to accept those exaggerations if it means they are likely to get more funding. As always, it’s good advice to follow the money.

So what does this mean for the poor information manager, tasked by his bosses to tell them what’s going on? Well, Stamp wasn’t saying that statistics were useless, only that we need to remember where they come from, which is rule number one: scrutinise your sources. He wasn’t saying that the village headman is out to cheat you, only that the village headman is human, so rule number two is: minimise the ways in which errors can be introduced to your data collection. As I noted above, those errors tend to get levelled out when you aggregate up – or at least to get less obvious amongst the mass of data – so rule number three is: where possible, always cross check your data against other sources.

Rule number four, of course, is: don’t expect statistics to solve all your problems. We tend to get a little fixated with a fetish for figures in this field (and I’m as guilty of that as anybody – look at the pretty pictures!) but, if our analysis or presentation aren’t solid, those figures aren’t going to be much use to managers.

Ben Ramalingam is a complex guy

Outside of humanitarian work, I have a passing interest in complexity theory, particularly around ideas of emergence. As a result, I’m deeply envious of Ben Ramalingam at ODI, who shares this interest but has actually found the time to write something substantial about it. The Working Paper that he has written with Harry Jones, Toussaint Reba and John Young – Exploring the science of complexity: Ideas and implications for development and humanitarian efforts has just been published by the ODI RAPID programme.

This line of research is one of the most important developments in humanitarian and development studies in many years, a potentially critical addition to the ideological foundations of our work (such as the Humanitarian Accountability Partnership), the technocratic scaffolding (such as Human Development Indicators) and the technical ornamentation (such as the Sphere Project).

I don’t agree with everything that Ben and his co-authors have written; in particular I share concerns that applying this framework to what is essentially a social science field has many, many pitfalls. In the paper’s terms, I’m a champion of complexity theory in general – but a pragmatist in the specifics of how we apply it to our work, simply because the stakes are so high. If we’re going to hijack a theory from the domain of pure science, we need to make sure that we are rigorous and open about how that works out in the real world.

So, now I just need to get around to applying for that PhD in the role of complexity theory in humanitarian crises. Someday.

(Full disclosure: I contributed to the peer review for the paper, along with some other people whose names will be more familiar to anybody else working in the sector.)

Instedd surfaces!

An email from CEO Eric Rasmussen tells me that INSTEDD is finally flying in radar (and apparently I’m mixing metaphors, unsure of whether INSTEDD is a whale or a plane). In his words,

InSTEDD has been invisible, a rumor and a ghost, for the few past months, but we surfaced today in a media call with Google.org in the launch of their first-ever Initiatives.

I’ve known Eric virtually for a couple of years, although we’ve never managed to actually meet in person. He’s a very solid choice for CEO – his thinking on civil-military affairs was always more lateral than I expected for somebody in his position, and I think that it reflected his willingness to listen and learn from others. That open attitude will be the single most important tool in INSTEDD’s box, at least in its early days, and in fact that’s why they are only launching now – for the last few months, the team has been travelling around meeting with various actors and hearing out what their needs might be.

If you don’t know anything about INSTEDD, I recommend that you visit the website, as it gives you the right flavour. It’s moved away from Larry Brilliant’s 2006 talk at TED and morphed into something that’s somehow broader yet less ambitious (a good combination if you can manage it). Yet I still harbour doubts about how successful it will be, doubts which don’t have anything to do with the goodwill or competence of the staff (or the fact that they’ve got a ton of funding behind them, not least from Google.Org).

Where do my doubts come from?  I’ll freely admit that part of my concern is rooted in my essential antipathy towards advice from experts (yes, including myself – it keeps me on my toes); part of it is based on my lack of faith in the power of technology to save us from ourselves; and part of it is linked to my sense that the entire system of disaster response has been built with a fundamental flaw at its foundation, and trying to make it more effective may simply be throwing good money after bad.

Having said that, INSTEDD’s philosophy is healthy.  It’s not proposing overarching systems that will solve the whole set of problems in one go, but a piece-by-piece approach that addresses key problems in the field as they arise.  So I welcome their launch, and I definitely welcome their presence on the scene – it’s definitely healthy for the sector to have more non-traditional actors bringing some new perspective.

And new tools, of course!  INSTEDD will be releasing any tech tools it develops, and it looks like on an open source basis (more specifically, the MIT license).  First out of the gate is a GeoSMS system, which is built on a bunch of existing Google tools and some GeoRSS.  And yes, we hope to discuss how Sahana might fit into these developments…

Quickbits December 2007

  • The November issue of Scientific American carries an article by Sheri Fink entitled “The Science of Doing Good” [purchase required, unfortunately]. Full disclosure: I was interviewed for the article. Initially I wasn’t convinced that this was going to be much good (sorry, Sheri!) but I was wrong. It moves between different areas – refugee registration, GIS, human rights, and so on – quite smoothly, while communicating the main obstacles that we face without making excuses. As an overview, it hits most of the initiatives in the sector that are accessible to general readers, so it should engage a wide audience and give them a pointer towards the area that might interest them the most. This is A Good Thing.
  • Mapping for Better Accountability in Service Delivery” [pdf] by Katharina Welle is the latest ODI Briefing Paper. The paper uses WaterAid‘s work as a case study to demonstrate how the use of mapping can be turned into a policy tool. Although the paper was actually funded by WaterAid, it’s an interesting approach to emphasise that gets away from the “cool” factor of mapping.
  • The latest Peace IT newsletter [pdf] is just out from Crisis Management Initiative, with articles on a range of recent developments including Humanitarian FOSS and the Global +5 Symposium. Again, this is a very nice overview of some interesting projects, although not much in the way of analysis, so be prepared to follow up on specific projects.
  • NPR carries an interesting audio segment on the Reverse 911 service. From their blurb: “The Reverse 911 communication system was given the lion’s share of credit for successful and fatality free evacuations from San Diego County’s wildfires a month ago. But the program may not have been as effective as previously thought.” The clip is still pretty positive about the concept, but once again it seems that the cheerleaders for technology may have underestimated the reality on the ground.

OCHA +5 Symposium fallout shelter

Unlike me, Sanjana did attend the +5 Symposium, but he wasn’t too impressed. He’s posted some thoughts on why exactly that was, including a post entitled “Where was the innovation?” where his perspective can be summed up best by a single line:

There was not a single point that came up during the discussions that I had not covered in this blog, sometimes over a year ago.

If we put it in those terms, I’d guess that not a single point came up at the Symposium that hasn’t been discussed in the field within the last 2-3 years. There’s always going to be a lag between innovation as it happens in the field and mainstreaming that innovation into the agencies – for example, GIS is still not part of the basic kit a decade after it was first introduced to the sector – but the way our organisations are set up actually prevents that from happening.

Sanjana has an interesting perspective on the event, which I would characterise as being an informed external, and – while in general terms I can’t disagree with his overall frustration – I find myself simultaneously agreeing and disagreeing with him on several points. Continue reading

I’m not liveblogging the Global Symposium +5 in Geneva

… for one very good reason, and that’s because I’m not at the Global Sympsium +5 in Geneva. However it would be remiss of me not to blog about it, since it’s a pretty big deal. I’m also not liveblogging the NetHope Bi-Annual Summit in Panama, and that’s because I’m not there either. I’m sure that there are good explanations for my otherwise inexplicable absences, but that’s not important right now.

The Symposium +5 is being held five years after the Symposium on Best Practices in Humanitarian Information Exchange (hence the +5 title – do keep up). That first symposium was a very mixed bag – it was the first time that the various actors in the sector had come together, so it was a very big deal. Because it was the first time, however, it was a little unfocused – nobody was really sure where the sector was going, although we weren’t short of ideas.

The Final Statement [pdf] that came out of that meeting wasn’t a bad one, but I had a lot of concerns about whether any progress would be made on the key points. This was partly because the wording was quite vague, as always with consensus documents, but mainly because there was (and remains) a lack of leadership in the perenially fragmented humanitarian sector. So where are we, five years later?

Continue reading

Beware of Geeks bearing Gifts

In the run-up to the OCHA +5 Symposium (which apparently I’m not going to), Dennis King asks:

How do we get more “Non-geeks” to use information technology and tools on a consistent basis?

This has been the central problem with most of our work over the last decade.  It’s particularly obvious in the field, where staff do not have the time to learn how to use new tools.  There seem to be a range of considerations if we want any of our projects to succeed:

  1. Embed new tools into existing processes where possible.  New processes are even harder to introduce into an organisation than new technologies, so enhance existing processes first.  This builds the credibility of the technology and familiarises people with it, strengthening your position within the organisation for future developments.
  2. Build on existing and familiar technologies (mobile phones) rather than introducing new and unfamiliar ones (standalone PDAs).  If you want staff to use a tool, it will be easier for them to accept and adopt if they are comfortably with it.  This is why Sahana is browser-based, for example, since most people are now comfortable using services on the web.
  3. Invest in preparedness by a) training key staff in tools that we want them to use, and b) getting management support for their implementation.  The first one may rely on the second, since you’ll need budgets to pay for training, but as I said above – don’t ever try to introduce something new in the middle of an emergency response.
  4. Make them useful.  This might seem really really obvious but it feels like a lot of us forget it.  We might think our project is the best thing since sliced bread, but if the rest of the organisation doesn’t agree, then we may as well not bother.  Let’s start by helping staff to articulate how technology can help them in their work, and then move on to designing what they really need.
  5. It’s not just “non-geeks” that we need to persuade.  IT departments in many of our organisations are seldom enthusiastic about new ideas, since they have the tough job of making sure that the old ideas keep working.  We need a) to make sure that our IT strategies have room for innovation and b) our IT staff are aware that it’s acceptable for them to innovate.  This will get ideas flowing.
  6. The final issue is our very own digital divide question.  None of the above can be accomplished if we do not build better working (and personal) relationships between tech staff and non-tech staff.  In nearly every organisation I’ve worked with, the links between the IT department and the Emergencies department has been very poor (if it exists at all).  This has to change, otherwise we’ll never get anywhere.

These points were off the top of my head – any other thoughts are welcome.