Yearly Archives: 2008

The Innovation Fallacy, Part 2

Previously I laid out my position that the humanitarian community is not good at successful innovation, and asked the question – why not? You won’t be surprised to learn that I have a theory about that. The theory depends on you accepting my assumption that innovation doesn’t happen in isolation – it requires a supporting framework to enable it. The stereotype of the mad scientist toiling away in his isolated laboratory is almost entirely inaccurate – somebody has to pay the electricity bills for that lab.

So where does innovation happen in the humanitarian community? I would argue that it happens primarily at the coalface of humanitarian action, where the rubber meets the road. Emergency situations are like real-time laboratories where the resources are limited and the stakes are high. At the same time as being unwilling to risk the lives of affected communities and individuals, humanitarian practitioners are prepared to try anything to save those lives – an internal tension that I think serves as the motor for innovation.

If I have such faith in innovation in the field, why do I argue that we’re not good at innovation? Well, we’re not good at successful innovation – taking the experimentation in the field and replicating it over distance and time. What tends to happen is that an individual practitioner will move to a new position and/or a new location, and take any innovations they’ve been involved with along.

Now this model of spreading innovation is fine – the “pollinator” is a key figure – but it does mean that, unless that innovation is adopted more widely, it’s limited to the places where that pollinator lands (and possibly doesn’t survive after they take off again). As Michael pointed out in the comments to the previous post, this is one area where our staffing patterns really cripple us – staff turnover is high and institutional memory is poor.

And it’s those staffing patterns that reveal the wider problem in the sector, the one that really prevents successful innovation. I mentioned that the stereotype of the lone inventor really isn’t very accurate at all1 and that any invention or innovation needs a supporting framework in order to make it successful. This is what’s missing in the humanitarian sector – the elements of that framework.

This means that innovation frequently withers on the vine. Now I wouldn’t argue that other sectors have perfected the art of cultivating innovation, but they’re certainly far ahead in terms of creating those frameworks. In the medical sector, for example, innovation is formalised and embedded outside the practice of medicine, through a combination network of public (such as research and university hospitals) and private vehicles (such as pharmaceutical companies).

What does that framework provide? It creates the possibility of creating a “chain of value”, which is the key to successful innovation, where each link in the chain adds value to the initial innovation and has a stake in ensuring its success. With our fragmented sector, we simply don’t have the possibility to do this – staff turnover is only one symptom of that, but there are many others. I think people glimpsed what might be possible with all the excess funding from the tsunami, but cash alone is not the key to success here.

Unless we can create more cohesion both vertically (from field to HQ) and horizontally (between organisations), our innovations will never be that successful. Oh, we’ll get one or two hits – but we need more if we’re going to be able to meet the challenges of the new century, because they’re not the challenges that we’re used to.2 In the next post, I’m going to look at how we might achieve that – using the tools that have been provided by the information revolution, and illustrated by the projects that I’ve been involved with.

  1. And you’ll be glad to know that Malcolm Gladwell agrees with me, for what that’s worth. []
  2. As our panicked response to rising food costs has shown… []

The Innovation Fallacy, Part 1

I spoke last week with Conor Foley, who’s looking at innovation in the humanitarian sector for the next ALNAP annual report. As any fule kno, innovation is a particularly interest of mine, particularly technology innovation, but I wasn’t surprised to hear that most of his interviewees shared my perspective: that the humanitarian community is not much good at innovation.

I should qualify that. The humanitarian community is built on innovation – on just getting things done despite a lack of resources – but successful innovation is very hard to come by. I define “successful” in this context as innovations that become widespread and enduring – that is, that they spread widely and last over time. I should probably qualify that as well:

  1. All innovations have a distinct lifespan, and are often superceded by a new innovation (or more rarely a completely new invention). So if an innovation endures over time, that is evidence of its success; but if an innovation doesn’t endure, that isn’t necessarily evidence of its failure.
  2. All innovations are context-specific, and sometimes don’t translate into other contexts. So likewise, if an innovation spreads geographically / organisationally, that is evidence for its success; but if it doesn’t, that isn’t necessarily evidence of its failure.

These two qualifications makes successful innovation sometimes hard to identify – but not impossible. In terms of projects that I’ve been involved with inside the sector, I think the Humanitarian Information Centres, the ECB Project and NetHope all qualify without any doubt (although the innovation in each project is exhibited in very different ways). What interests me more is innovation outside the sector.

I’ve been involved with Sahana for a long time now, and I wouldn’t hesitate to identify it as the single biggest innovation I’ve seen – potentially revolutionary. You can also point to projects like Ushahidi, FrontlineSMS and so forth – projects that, while not “humanitarian” in themselves, have definite humanitarian applications – but the strange thing about all these is that they haven’t managed to get significant traction inside the “traditional” humanitarian sector.

The question is, Why is this the case? What makes the humanitarian community unable to recognise and replicate innovation? And that, my friends, will be the subject of the next post…

UPDATE: To my eternal guilt and shame, I forgot to mention a fourth project that I was involved with, Aid Workers Network – again, work that was well ahead of its time, mainly thanks to Mark Hammersley.

Quickbits November 2008 UPDATE

The links are coming fast and furious this month – it must be something to do with the US elections…

  • I was busy with work when Ushahidi launched their alpha version, just in time for a test run in DRC. Hopefully lots of lessons learned will come out of that one, lessons that will be relevant not just to Ushahidi but other projects as well.
  • An interesting article in Science Daily on Collecting Health Data in Areas with No Power Supply – in this case, Sierra Leone. Useful insights into the specific problems of poor countries, although it’s not strictly speaking about “no power supply”, it’s about a broader lack of physical and – more importantly – institutional infrastructure. I want to know more about the actual system involved – any details, Jeff?
  • Another interesting article on how Sahana emerged from the Indian Ocean tsunami, Does it take a disaster to understand the power of open development? Now I think that this narrative needs some tweaking in order to keep it relevant, nearly 4 years after the event (hard to believe it’s been so long), but this is a good opportunity to point you to TalkSahana, for all your… erm, Sahana Talking requirements.
  • It’s all Sahana all the time, isn’t it? I wouldn’t be doing my job (well, it’s not really a job) if I didn’t announce the great news that Sahana will be the basis for OpenEvSys, a human rights violation reporting tool; and that Respere will be the company developing the software. Congratulations are due on all sides, particularly as this means that we add another member to the Humanitarian Open Source community.
  • The Google Flu Trends website goes up, using search terms to track the progress of flu. Now this is an interesting supercruncher sort of project which could form the basis of a tracking system – but only in countries where internet access is sufficiently deep and local-language content available.
  • Finally (unless somebody sends me yet more links) Crisiswire has just launched. As a Web2.0 aggregator for crisis-related information, it’s the sort of project that I need to be persuaded about – but it looks like they’ve designed it well, which is always a good start.

Quickbits November 2008

  • Shelter Centre unleash their new website upon the world. Finally a humanitarian website that’s highly-functional, well-designed and thinks hard about the community – in this case the shelter sector (obviously). Give it a spin, and kudos both to the Centre and to Development Seed for a job well done.
  • NetHope gets some play in the NYT, in an article entitled Wiring Disaster Areas to the Outside World. Nice enough, but nothing that hasn’t been said before, which leaves me wondering why it’s appearing now?
  • You’ve read the BBC World Service Trust Report Left in the Dark, and now you can meet the Project Managers at an HPN Event at 12.30-2.00 on 4 December in London. No online links (yes, HPN are that backward) but you can reserve a space by emailing hpn <at> odi <dot> org <dot> uk. Sadly I won’t be attending, so please ask a reasonably informed question on my behalf.
  • Is the obvious avenue for Aid Workers Network the street called Facebook? I’m not convinced, for a number of reasons, but it’s nice to see the sector trying these things out. However we seem to be back to flogging the old dead horse with debates about the platform… Also worth joining – Humanitarians for Fashion.

Kill Your Reports

Alanna:

Most people picture international work as feeding hungry people, providing health care to refugees, or building schools. In reality, it makes no sense to pay an expatriate to do that. Instead, we do what cannot be hired locally: English-language paperwork. We write reports to HQ and donors, proposals, and program guidelines. We write even more reports. We can go days without seeing anybody who is helped by our work.

Owen:

It seems to me that we must de-escalate the amount of paperwork involved in international development. There has to be some record-keeping to enable us to account to the people whose money we are spending.  But the bureaucracy involved in designing and getting funding for projects, for hiring people, and for monitoring and reporting, has become an industry in itself.

All true. The ECB research showed clearly that while nearly every expat staff member – and many of the senior national staff – in an international organisation is required to contribute to situation reporting, donor reporting, co-ordination reporting and so forth, precisely none of them believed that the reporting process added value to their work.

Agreed that reporting has become an industry in itself, as Owen says – but why? Cui bono? The beneficiary of these reporting processes is headquarters (sometimes regional offices) – the senior management and support staff in the organisation. Now this wouldn’t be an issue if we could demonstrate that their receipt of reports had a positive impact on the organisation’s work in the field.

Yet time and again, it seems there is no such impact. Country offices receive little or no feedback on their reports, and individual staff receive none. It’s also hard to identify any link between the reports that are generated in-country and any strategic decision-making, although it’s clear that there is some benefit there. This is a tremendous problem – a waste of money and time in situations (especially emergencies) where those resources are at an absolute premium.

There’s no single solution to this problem, but there are a few strategies you can adopt.

  1. Cut reporting to the bare minimum, in terms of both frequency and length.
  2. Revise reporting processes so that they add value to the staff tasked with doing that reporting.
  3. Develop multiple reports from single processes, rather than having multiple (and redundant) processes.
  4. Make use of new technology to cut down on traditional narrative reporting in favour of (for example) SMS flash reporting.

I’ve been advocating these approaches for years now, with almost no impact – organisations are wedded to the idea that reporting is an intrinsic part of their work, rather than a tool that can be optimised. If there’s one critical step every organisation should take, though, it’s that individual reports must be linked clearly with specific decisions that need to be made within the organisation. If the information in a report is not going to be used to make a decision, then why are we asking staff for that information?

Paper, Rock, Scissors, Information

I previously wrote about Imogen Wall’s post-tsunami report The Right To Know: The Challenge of Public Information and Accountability in Aceh and Sri Lanka, which laid out the case that there is a right to information in the same way as there is a right to shelter. The Red Cross World Disasters Report 2005, picked up on this theme and extended it to the technology, demonstrating that “Information and communications technology must be recognised as a form of aid in itself.” Both of these reports were entirely correct, yet the humanitarian community has largely failed to address their conclusions. No surprises there.

Wall has now published (via BBC World Service Trust) a policy briefing that recapitulates and updates her original points, entitled Left in the dark: The unmet need for information in emergency response (PDF) and an accompanying article entitled After Disaster: Information for Life. While I might disagree with some of the solutions she proposes (if you think I ever agree 100% with anybody, you obviously haven’t been reading this blog long enough…), these reports should be on the shelf not just in every communications and public information unit, but all programme units as well – a reminder that our work is not just about providing food, water, shelter, but about enabling beneficiaries to regain control over their own lives.

Quickbits October 2008

YouTube Preview Image

And before I forget: ISCRAM Live

From Bartel:

We have been working in the past few months on the development of ISCRAM LIVE, an “ISCRAM 2.0” dynamic site gathering and publishing content that is being posted on popular “web 2.0” websites by ISCRAM members. The ISCRAM LIVE website is at http://www.iscram.org/live .

 

ISCRAM LIVE currently interfaces with slideshare, youtube, flickr, twitter, delicious and Facebook, and collects (on a daily basis) all posts on these sites that are tagged with the word “ISCRAM”. I would now like to ask you for your help and a bit of your time in the coming week and try out ISCRAM LIVE in the coming week (say until October 16), by posting and tagging items on these sites that you think are relevant or of interest to the ISCRAM Community – blogs, pictures, tweets, slides, videos and del.icio.us bookmarks.

 

 

Now: this was what we were hoping for with the ICT4Peace website. The problem was two-fold – the original web designers couldn’t deliver web2.0 (admittedly it was 4 years ago…) and there wasn’t a community around the concept. ISCRAM now has both of these, so the question is – what’s the magical x-factor that will make this take off? I’m doing my bit – TAG!

Back on the data wagon

It bears repeating, especially when the guy doing the repeating isn’t exactly “one of us”:

The federal government has made aggressive use of so-called data-mining tools since the attacks of Sept. 11, 2001, as counterterrorism officials in many intelligence agencies have sought to analyze records on travel habits, calling patterns, e-mail use, financial transactions and other data to pinpoint possible terrorist activity… But there is little evidence to confirm that the techniques work to actually find terrorists, despite the growing use in the last seven years, committee members said…

“More data does not mean better data,” said William J. Perry, the former defense secretary who was co-chairman of the panel

That’s right, folks – despite the work of the Supercrunchers, more data does not mean better data. What’s important is what comes before the data and after the data – planning exactly what you’re going to collect and how, and analysing and applying what you’ve collected. If you haven’t got those right – for instance, if you’re handing out a “rapid” assessment that’s 40-odd pages long – then any data collection is likely to yield less-than-useful results.

I’m thinking specifically about this sort of field-based data collection, of course, the processes that require a heavy investment and careful management (because they’re taking place at the sharp end of an emergency). The key to success is to focus on the most essential key indicators, and be very clear about exactly what you expect to learn  from them. Think of it this way – you’re not looking for an in-depth photo essay that tells the whole story, but a polaroid snapshot of the scene that you can refer to later.

A massively detailed picture isn’t going to be any use to anybody – it takes too much time to gather, it takes too many resources to analyse, it’s out-of-date too quickly and it’s rarely possible to match the data collection process to the form. So boil those forms down people, boil ‘em right down until there’s barely anything left. Then boil ‘em down again. Then give them to me so I can boil ‘em down even more…

(HT: Siva Vaidhyanathan)

I write for free: the problem with academic publishing

I’m on the editorial board of a new journal, the first issue of which will be published in January 2009; the International Journal of Information Systems for Crisis Response and Management (IJISCRAM – snappy title, I know). I’ve also contributed an article to the first issue of the journal, and so a few weeks ago I received a copyright release form from the publishers of the journal.

It was only then that I realised just how much of a problem I have with this model of academic publishing.

Continue reading