m4d: The fun is over. Time to get tough?

I’m all for discussion and debate, and I’ve taken part in my fair share over the past eleven years. But I’m now beginning to wonder if, after all this time, everything we could have said has been said. The fact we’re still talking about the same handful of challenges and issues implies that very little, if anything, has changed where it matters – on the ground. Have we really made so little progress?

I’ve been thinking about this for a while, but it wasn’t until the recent Guardian Activate conference that the scale of the problem finally drove home.

It’s worth mentioning that I wasn’t at the event this year, but I did follow from a distance. To be honest, sometimes it’s better to listen and reflect from the outside, and as my train hurtled towards London it became increasingly obvious that much of the early conversation followed a similar pattern to many of the other technology-for-good conferences I’d attended over the years.

If, about a decade ago, we’d listed all of the questions, unknowns, problems and challenges faced by the ICT4D community, it would probably have looked something like this:

  • How do we replicate and scale?
  • How do we measure impact?
  • How do we stop the reinventing of wheels?
  • How do we avoid being ‘technology-lead’?
  • How do we break out of our silos?
  • What is our business/sustainability model?
  • Is open source a help or a hindrance?
  • How do we maximise the opportunity mobile brings?

If we made the same list today, it would probably look something like this:

  • How do we replicate and scale?
  • How do we measure impact?
  • How do we stop the reinventing of wheels?
  • How do we avoid being ‘technology-lead’?
  • How do we break out of our silos?
  • What is our business/sustainability model?
  • Is open source a help or a hindrance?
  • How do we make sense of the countless pilots taking place?

The only difference is the last one. We’ve gone from not really knowing what to do with mobile phones to a position of everyone everywhere trying to solve something with them, whether or not they’re the right tool for the job. It’s still a problem, but arguably a more serious one.

These questions – and many others like them – might keep academics in work, but they’re serious issues for practitioners, too. Project owners and tools developers are rarely clear on their positions on open source, or scale, or their interpretation of ‘appropriate technology’. Among other things this leads to confusion and unnecessary competition (yes, the non-profit world is competitive). I attempted to put a stop to some of this in a post called “Our “social mobile” line in the sand” way back in May 2009, without success. I wonder if the time is right for someone to try again?

None of us surely want to sit in yet another conference, gathering or workshop and hear the same things over and over again, but that’s often what we do. And more often than not we pay good money for the privilege. Messages I personally don’t want to hear again include:

“We need to stop talking in silos”
“Projects need to build for scale from the outset”
“We need to stop reinventing wheels”
“We need more collaboration”
“We need to become sustainable”
“We need to embrace failure”
“Mobile technology has huge potential”

Can’t the m4d community come together and fix some of this? Create a code of conduct, a directory of terms and meanings, a set of best practice? With the billions of dollars funding mobile projects the world over, can’t we siphon a little off and create an overarching set of guidelines that projects and donors adhere to? Almost everything we see out there has been funded by someone, so if only the donors seriously tried to grapple with the problem – and got strict with what they funded – we’d almost certainly make serious progress.

Some of this stuff isn’t difficult. Take the problem of silos. Most of the events where this comes up are silos themselves. How can someone stand up at a mobile health conference packed with only people who use mobile phones and only for health, and say we should stop talking in silos? How about a mobile health practitioner attending an agriculture conference, instead? Or one focussing on human rights? Don’t tell me mobile health projects can’t learn something from non-mobile agriculture? If, as we constantly hear, innovation and opportunity happen in unexpected places, we need to put ourselves in them a little more, as Tim Smit suggested at the Emerge Conference in 2010.

Perhaps as a sign of things to come, mentions of mPesa are increasingly banned at meetings I attend. If we have to use the same example of a successful mobile money project over and over again, doesn’t that say something about the state of mobile money?

I was recently asked what progress I thought we’d made since I wrote “Technology’s new chance to make a difference” for the Guardian in January 2012. In the areas of best practice, adopting more appropriate technology and mainstreaming ICT4D, sadly I had to admit very little. As I wrote three years earlier:

I spent the best part of my university years critiquing the efforts of those who went before me. Countless others have done the same. Looking to the future, how favourably will the students and academics of tomorrow reflect on our efforts? If the next thirty years aren’t to read like the last then we need to re-think our approach, and re-think it now

The development sector is hardly awash with success. The m4d community have a great chance to buck the trend. The big question is, will we?

Further reading
An inconvenient truth?

An inconvenient truth?

Exactly ten years ago this month I was preparing for my first ever piece of work in mobile, two years of work which would lead to the development of an innovative conservation service in 2003 – wildlive! – and the release of one of the earliest reports [PDF] on the application of mobile technology in conservation and development in 2004. A lot has happened since then, not least an explosion in interest, buzz, excitement – and, yes, hype – and a sense that mobile can be the saviour of, well, everything. Back then you’d likely be able to fit everyone working in mobile-for-development (m4d) into a small cafe. Today you’d need at least a football stadium. m4d – and it’s big brother, ICT4D – have become big business.

Not that I needed more proof of mobile’s status at development’s top table, earlier this week I attended Vodafone’s “Mobile for Good” Summit in London. It was a high-profile affair, and an extremely upbeat one at that. I left with mixed feelings about where m4d is headed.

My five takeaways after a day of talks, debates and demonstrations were:

1. Everyone is still excited by the potential of mobile
2. The same projects surface over and over again as proof mobile works
3. Mobile is still largely seen as a solution, not a tool

4. It’s up to the developed world to get mobile working for the poor
5. The top-down mindset is alive and well

Suffice to say, all of these conclusions troubled me as I sat on the train home.

I’ve been thinking for some time about the future of m4d, and how far we’ve got over the past ten years or so. I’ve written frequently about the opportunities mobile technology offers the development community, and my fears that we may end up missing a golden opportunity (see Time to eat our own dog food?” from March 2009). I’ve long been a champion of platforms, and understanding how we might build tools for problem owners to take and deploy on their own terms. Yes, we should provide local entrepreneurs and grassroots non-profits with tools – and where appropriate and requested, expertise – but we shouldn’t develop solutions to problems we don’t understand, we shouldn’t take ownership of a problem that isn’t ours and we certainly shouldn’t build things thousands of miles away and then jump on a plane in search of a home for them.

But this is still, on the whole, what seems to be happening. And this, I’m beginning to believe, is rapidly becoming ICT4D’s “inconvenient truth”.

A fulfilled future for ICT4D (of which m4d is an increasingly dominant part) is not the one I see playing out today. It’s future is not in the hands of western corporates or international NGOs meeting in high-profile gatherings, and it’s not in our education establishments who keep busy training computer scientists and business graduates in the West to fix the problems of ‘others’. The whole development agenda is shifting, and my prediction for the future sees a major disconnect between what ‘we’ think needs to be done, and what those closest to the problems think needs to be done. Call it “disruptive development“, if you like. As I told the Guardian in an interview earlier this month:

The rise of homegrown solutions to development problems will be most crucial in future. That means African software developers increasingly designing and developing solutions to African problems, many of which have previously been tackled by outsiders. This, I think, will be the biggest change in how development is ‘done’

I’m not the only person to be saying this. Many good friends working at the intersection of African development and technology have been doing the same for some time. The real change, and the big difference, is that it’s finally happening. A message which was previously given in hope, a message that was previously given out of an inherent belief that there was a better, more respectful and appropriate way of doing things, is now becoming reality. ICT4D is changing, and the balance of power is changing with it.

FrontlineSMS has always spoken to an approach I’ve long believed in, one where users are empowered to develop solutions to their own problems if they so wish. There are many reasons why FrontlineSMS continues to work – the decision of the new Management Team to shift software development to Nairobi is one of the more recent ones. But fundamentally it’s about what the platform does (and doesn’t do) that really resonates with innovators, entrepreneurs, non-profits and problem owners across the developing world. As the Guardian put it in the recent article, “As open-source technology for mobile platforms, innovations like FrontlineSMS are essentially a blank canvas for grassroots organisations to apply to any local context”.

That local context is becoming increasingly vibrant as university students across Africa graduate with Computer Science and Business Management degrees; as innovation hubs spring up across the continent meeting a growing, insatiable demand for places to meet, work and network with like-minded problem solvers and entrepreneurs; and as investors launch funds that show they’re starting to take young African tech startups seriously.

This activity hasn’t escaped big business. Google, IBM, Microsoft, Nokia, Hewlett Packard and Samsung have been opening offices across the continent, snapping up much of the talent in the process (ironically often at the expense – and despair – of locally-based NGOs). But while technology businesses take note and develop local capacity that enables them to develop more appropriate local solutions, the broader development ‘community’ seem trapped in an older mindset of technology transfer.

Technology transfer, of course, is big business – there’s no shortage of donor money out there for projects that seek to implement the latest and greatest proven Western innovations in a development context, and there are countless tens of thousands of jobs that keep the whole machine running. A lot has to change if the development community is to face up to all its new realities, yet it’s looking more likely that the destiny of the discipline lies in the hands of the very people it originally set out to help.

So, if the future of ICT4D is not university students, NGOs or business graduates devising solutions in labs and hubs thousands of miles away from their intended users, what is it?

Well, how about something a little more like this?

It seems rather obvious to put a local technology entrepreneur on a bus and have him chat to a rural farmer, but imagine what might be possible if this approach became the “new ICT4D”, not that the entrepreneur or the farmer would see it as that, or ‘development’ at all. You can see more of the fascinating TV series which linked local technologists to local problems on the TVE website. There’s a lot that’s right with this approach, particularly if you consider what would usually happen (hint: it involves planes).

I’m not usually one for making predictions but it is that time of year, after all, and it is my ten year anniversary in mobile. So here’s a biggie.

Development is changing, powered by accessible and affordable liberating technologies and an emerging army of determined, local talent. A local talent that is gradually acquiring the skills, resources and support it needs to take back ownership of many of its problems – problems it never took original ownership of because those very skills and resources were not available.

Well, now they are. The ICT4D community – education establishments, donors and technologists among them – need to collectively recognise that it needs to ajdust to this new reality, and work with technologists, entrepreneurs and grassroots non-profits across the developing world to accelerate what has become an inevitable shift. Or it can continue as it is, and become increasingly irrelevant. “Innovate or die” doesn’t just apply to the technologies plied by the ICT4D community. It applies to the ICT4D community itself.

[This post was edited down and republished in the Stanford Social Innovation Review in January 2013 here].

Further reading
m4d: The fun is over. Time to get tough?

The innovation conundrum

When I started out trying to understand the complexities of international development well over 15 years ago, one thing struck me. The trick, I was often told, to increase chances of funding was to apply a liberal sprinkling of the words gender, scalable or sustainable into any project proposal. Donors apparently liked those words, however they were used.

I’m beginning to wonder if the same thing is happening today with the word innovation.

For organisations seeking to deploy technologies to put right social wrongs, innovation is the hottest date in town. If the solutions themselves are not described as “innovative” then often the organisations behind them are. Innovation hubs have sprung up across the developed and the developing world, seeking to create the perfect environment for innovation. There are books galore extolling the virtues of innovation in three, four or five steps, or how we might foster cultures of innovation. If only it were that easy.

Over the past few days I’ve read three separate articles, all of which touch on different aspects of the innovation phenomenon. They’re interesting on their own, and collectively, as examples of the various debates currently taking place. As with all things “development” (which is the hat I wear as I write this) there’s as much discussion about what things mean as there is real-world activity.

Harvard Business Review

On the Harvard Business Review blog, good friend Bright Simons focuses on the cost of innovation, and argues that low-GDP countries and smaller businesses are in danger of falling into an “innovation poverty trap” while their richer counterparts ride off into the distance. Cost may indeed be a barrier, but it would be wrong to assume that if we provided every resource you could possibly wish for that people would suddenly become innovative. Money doesn’t make you innovative, although for innovative individuals and companies it arguably helps. Some bigger companies have fallen from their perch at the height of their success, crucially at a time when they had peak resources available to innovate, including money. Take Nokia as a more recent example. (For more on why big companies fail, see the excellent “Innovators Dilemma” by Clayton Christensen).

Stanford Social Innovation Review

In the Fall 2012 volume of the Stanford Social Innovation Review, Christian Seelos and Johanna Mair argue that innovation should not be the holy grail, and that instead “it is time to move from innovation as an ideology to innovation as a process”. In particular, they argue that a relentless focus on innovation as an outcome can undermine an organisation’s appetite for experimentation. This is particularly true when that experimentation may have a high chance of failure:

Although productive innovation does not always translate into desired outcomes or impact, systematic learning and building of a knowledge base about what works and what does not constitutes an important indicator for an organisation’s ability to innovate

Failing to recognise this carries a number of risks:

Glorifying innovation as the solution to social and environmental needs and problems has led to well-intended efforts to increase the population of social innovators and entrepreneurs. This certainly has its merits but it has come with a detriment to investments in established social sector organisations that operate at scale and that create value mainly through incremental improvements

The rampant rate of innovation in the commercial sector has provided risk and opportunity in equal measure for the non-profit world. The ICT4D toolbox is a lot bigger than it was two or three years ago, but as I like to point out in my numerous talks on appropriate technology, many of these new tools don’t yet work in the places where the need is greatest. Donors sometimes fuel the frenzy by their willingness to fund the next big thing, leaving us with ‘innovative’ projects such as “iPads for Africa” (this is one I made up a couple of years ago, but it may now exist in some form). Although these projects may look great in the glossy pages of an annual report, and sound incredibly disruptive, they look less compelling on the ground (where they largely fail).

Organisational Capacity to Innovate

The Rockefeller Foundation recently launched organizational capacity to innovate, a new website based on the findings of “Learning from Experimentation: Sustaining Innovation to Achieve Impact” (available as a PDF here). They focus on the importance of seeing social innovation as an outcome rather than a tool, and an ongoing process rather than a single moment of inspiration. Two organisations are used as case studies in the report – our very own FrontlineSMS, and Circle of Blue – both seen as good examples of building capacity for continuous innovation through experimentation. The report is particularly interesting because it covers organisational innovation as much as technological innovation. As I’ve written before, organisations themselves need to innovate (business models, organisational structures, funding, leadership, messaging, and so on).

Creative Advantage list over a dozen definitions of “innovation” on their website, and therein lies the problem. We need to be careful we don’t overuse the term to the point of it becoming meaningless, and that when we do we’re clear about what kind of innovation we’re talking about.

Further reading
Since drafting this post, the Stuff Expat Aid Workers Like blog has published a more critical, tongue-in-cheek critique of the development community’s emerging obsession with innovation. You can read their “#182 Innovation Tourette’s” post here.

Social innovation and the art of reinvention

Big companies are on the move.

Within the next few weeks Microsoft will officially launch Windows 8. Their flagship operating system has undergone a complete redesign on a scale not seen since Windows 95. Myspace are going through a vigorous rebranding exercise ahead of a major relaunch. And Nokia are feeling the pain as they work through a huge shift in their approach to the smart phone market. Three different organisations. Three different challenges. One thing in common.

Windows 8 is Microsoft‘s response to the growing threat of the smartphone and tablet, two high-growth markets where they’re not yet major players.

Myspace are attempting a fight back for fourth time as their value and online membership continue to lose ground on the Facebook’s of this world.

And Nokia, like many device manufacturers, got totally caught out by the iPhone which did, in fact, change everything. As market leaders they had furthest to fall. The rest is history.

Three companies, three challenges, all responses to external market pressures. In a sense, you might argue that the ultimate destiny of these companies is no longer in their hands. Out of the three, Microsoft are best placed in that they’re responding at a time they’re still relatively dominant. It’s the opposite for Myspace and Nokia, who in reality are on the slide and attempting to fight back from much weaker positions. If either gets their new strategy wrong, it could be curtains.

Today, Apple are riding high and can do no wrong. But they’d be the first to admit that they’re in a precarious position – they, after all, have it all to lose. Despite the rhetoric, we’re yet to see a true iPhone killer, but there will be one. And Apple need to make sure it’s them who build it. Apple, in a sense, have to kill their own product if they’re to succeed in an increasingly competitive future.

This kind of “inward reinvention” is not so common in the ICT4D world. Solutions come and go, pilot projects come and go, some organisations even come and go. The vast majority of the changes we see are driven by one single external factor – technological innovation. Think of all the new projects and organisations that have come about as a result of the growth of smart phones in emerging markets. And think of all the new ones that will exist when tablet computers, or 4G, become ubiquitous.

Once they’re up-and-running, few ICT4D-focused organisations undergo radical changes in their approaches or technologies, instead focusing on incremental upgrades to policies and technologies. Some of those are voluntary, but many are forced by new entrants into the market, new technologies, or some kind of paradigm shift. It’s those that strike first – adapting their approaches and offerings before change is forced upon them – that will survive in an increasingly competitive world. And, yes – developing solutions to the world’s social and environmental ills is a competitive industry.

Although technology-focused non-profits don’t face the same problems as their commercial counterparts, this doesn’t mean they shouldn’t regularly rethink their strategy, their brand, their leadership or their technology solutions. If they’re to succeed in the longer term they need to be the ones in the driving seat, not the ones simply responding to external pressures or developments. ICT4D as a sector is still relatively new in the grand scheme of things, and as things hot up – as they will – increasing numbers of organisations will end up calling it a day. Fortune will favour the brave.

Many find themselves under pressure in a few key areas:

Increasing competition for funding. The number of technology-focused social enterprises is rising at a higher rate than available funding, putting a squeeze on donors. Social enterprises responding with hybrid models – allowing them to raise investment as well as donations – will stand a better chance in this brave new world, as will those who master the emerging crowd funding phenomenon.

The democratisation of development. As I wrote in a recent BBC Future article, the spread of the Internet and mobile phones means there are likely more people working on solving social and environmental problems in the world today than ever before in human history. There’s a lot of competition out there, and a lot is coming from garden sheds, bedrooms and kitchen tables.

The rise of local innovation hubs. For quite some time there’s been general agreement that the best people to solve developing world problems are people in the developing world. I’ve always maintained that the greater the distance between a problem and the problem solver, the less likely the chance of success. The rise of local innovation hubs around the world – Africa in particular – means that not only is that distance shrinking, it’s nurturing entirely new industries in developing countries.

An increasing focus on emerging markets from large companies. Non-profits have historically only had to compete with other non-profits, but that’s no longer the case. Designing (mobile) applications for the next billion, or the bottom of the pyramid, or the other 90% – whatever you choose to call it – is big business. IBM’s announcement earlier this month that their next research centre will be based in Nairobi – their first in Africa – is further proof. According to IBM, “We want to help train Africans to innovate in Africa. The best minds there should be working on big national problems and African problems”. Google, Microsoft, Nokia, Hewlett Packard and Samsung – among others – have set up shop there, too.

In a couple of months time I’ll be celebrating my tenth year in mobiles-for-development. I’ve been incredibly lucky to have been there from almost the beginning, and I’ve seen first-hand the growth of the discipline and the impact of the technology on communities across Africa. The next ten years will present a whole new set of challenges for our sector, and if many ICT4D-focused organisations are going to survive they’re going to need to work very hard – and be very brave – to stay one step ahead of the game.

Something Myspace, Nokia (and Blackberry, come to think of it) – with all their resources – failed to do.