Time to eat our own dog food?

Is the future of social mobile an empowered few, or an empowered many? Mobile tools in the hands of the masses presents great opportunity for NGO-led social change, but is that the future we’re creating?

In The White Man’s Burden – Why the West’s Efforts to Aid the Rest Have Done So Much Ill and So Little Good”, William Easterly’s frustration at large-scale, top-down, bureaucracy-ridden development projects runs to an impressive 384 pages. While Easterly dedicates most of his book to markets, economics and the mechanics of international development itself, he talks little of information and communication technology (ICT). The index carries no reference to ‘computers’, ‘ICT’ or even plain old ‘technology’.

But there is an entry for ‘cell phones’.

"Small is Beautiful"E. F. Schumacher, a fellow economist and the man widely recognized as the father of the appropriate technology movement, spent a little more time in his books studying technology issues. His seminal 1973 book – Small is Beautiful – The Study of Economics as if People Mattered” – reacted to the imposition of alien development concepts on Third World countries, and he warned early of the dangers and difficulties of advocating the same technological practices in entirely different societies and environments. Although his earlier work focused more on agri-technology and large-scale infrastructure projects (dam building was a favorite ‘intervention’ at the time), his theories could easily have been applied to ICTs – as they were in later years.

Things have come a long way since 1973. For a start, many of us now have mobile phones, the most rapidly adopted technology in history. In what amounts to little more than the blink of an eye, mobiles have given us a glimpse of their potential to help us solve some of the most pressing problems of our time. With evidence mounting, I have one question: If mobiles truly are as revolutionary and empowering as they appear to be – particularly in the lives of some of the poorest members of society – then do we have a moral duty, in the ICT for Development (ICT4D) community at least, to see that they fulfill that potential?

You see, I’m a little worried. If we draw parallels between the concerns of Easterly and Schumacher and apply them to the application of mobile phones as a tool for social and economic development, there’s a danger that the development community may end up repeating the same mistakes of the past. We have a golden opportunity here that we can’t afford to miss.

But miss it we may. Since 2003 I’ve been working exclusively in the mobile space, and I’ve come to my own conclusions about where we need to be focusing more of our attention if we’re to take advantage of the opportunity ahead of us. Don’t get me wrong – we do need to be looking at the bigger picture – but there’s not room at the top for all of us. I, for one, am more than happy to be working at the bottom. Not only do I find grassroots NGOs particularly lean and efficient (often with the scarcest of funding and resources), but they also tend to get less bogged down with procedure, politics and egos, and are often able to react far more quickly to changing environments than their larger counterparts. Being local, they also tend to have much greater context for their environments, and in activism terms they’re more likely to be able to operate under the radar of dictatorial regimes, meaning they can often engage a local and national populace in ways where larger organizations might struggle.

So, waving my grassroots NGO flag, I see a central problem of focus in the mobile applications space. Let me explain. If we take the “Long Tail ” concept first talked about by Chris Anderson and apply it to the mobile space, we get something like this. I call it “Social Mobile’s Long Tail”.

Social Mobile Long Tail, kiwanja.net

What it demonstrates is that our tendency to aim for sexy, large-scale, top-down, capital- and time-intensive mobile solutions simply results in the creation of tools which only the larger, more resource-rich NGOs are able to adopt and afford. Having worked with grassroots NGOs for over 15 years, I strongly believe that we need to seriously refocus some of our attention there to avoid developing our own NGO “digital divide”. To do this we need to think about low-end, simple, appropriate mobile technology solutions which are easy to obtain, affordable, require as little technical expertise as possible, and are easy to copy and replicate. This is something I regularly write about, and it’s a challenge I’m more than happy to throw down to the developer community.

Another key problem that we have emerges as a symptom of the first. Because larger international development agencies, by their very nature, tend to pre-occupy themselves with the bigger issues, they often inadvertently neglect the simple, easier-to-fix problems (the “low hanging fruit” as some people like to call it). The Millennium Development Goals (MDG’s) are good examples of the kinds of targets which are far easier to miss than hit.

In mobile terms, using the technology to enhance basic communications is a classic “low hanging fruit”. After all, that’s what mobile phones do, and communication is fundamental to all NGO activities, particularly those working in the kinds of infrastructure-challenged environments often found in the developing world. Despite this, there are few tools available that take advantage of one of the most prolific mobile communication channels available to grassroots NGOs – the text message (or SMS).

Much of my own work with FrontlineSMS has sought to solve this fundamental problem, and in places such as Malawi – where Josh Nesbit, FrontlineSMS, a laptop and one hundred recycled mobile phones has helped revolutionise healthcare delivery to 250,000 rural Malawians – the benefits are loud and clear. In other countries, where activities of international aid organizations may be challenged or restricted by oppressive, dictatorial regimes, grassroots NGOs often manage to maintain operations and often provide the only voice for the people. In Zimbabwe, Kubatana.net have been using FrontlineSMS extensively to engage a population not only starved of jobs, a meaningful currency and a functioning democracy, but also news and information. In Afghanistan, an international NGO is using FrontlineSMS to provide security alerts to their staff and fieldworkers. The software is seen as a crucial tool in helping keep people safe in one of the world’s most volatile environments. With a little will, what can be done in Zimbabwe and Afghanistan can be done anywhere where similar oppression exists.

Destined for the rubbish

In cases such as these – and there are many more – we need to stop simply talking about “what works” and start to get “what works” into the hands of the NGOs that need it the most. That’s a challenge that I’m happy to throw down to the ICT4D community. There’s only a certain amount of talking and critiquing we can, and should, do.

There are, of course, many issues and challenges – some technical, some cultural, others economic and geographical. The good news is that few are insurmountable, and we can remove many of them by simply empowering the very people we’re seeking to help. The emergence of home grown developer communities in an increasing number of African countries, for example, presents the greatest opportunity yet to unlock the social change potential of mobile technology. Small-scale, realistic, achievable, replicable, bottom-up development such as that championed by the likes of Easterly and Schumacher may hardly be revolutionary, but what would be is our acknowledgement of the mistakes of the past, and a co-ordinated effort to help us avoid making them all over again.

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.

Social mobile: Myths and misconceptions

A couple of weeks ago – in “The long tail revisited” – I briefly touched on the topic of “myths in the social mobile space”. It wasn’t the major focus of the post, but as is often the case it kicked off a completely separate discussion, one which took place largely off-blog in the Twitterverse and via email. I’ve been thinking more about it since, particularly as the social mobile space continues to hot up and people begin to face tools and projects off against one another – sometimes for the right reasons, more often for the wrong.

So, here’s my current “Top Ten” myths and misconceptions in this emerging field. Feel free to add, remove, agree, disagree, debate or dismiss. In no particular order…

1. “High-end is better than low-end”
Firstly, one mobile tool should never be described as being better than the other – it’s all about the context of the user. There is just as much a need for a $1 million server-based, high bandwidth mobile-web solution as there is for a low-cost, SMS-only PC-based tool. Both are valid. Solutions are needed all the way along the “long tail“, and users need a healthy applications ecosystem to dip into, whoever and wherever they may be. Generally speaking there is no such thing as a bad tool, just an inappropriate one.

Server Farm - via Flickr (Jemimus)

2. “Don’t bother if it doesn’t scale”
Just because a particular solution won’t ramp-up to run an international mobile campaign, or health care for an entire nation, does not make it irrelevant. Just as a long tail solution might likely never run a high-end project, expensive and technically complex solutions would likely fail to downscale enough to run a small rural communications network. Let’s not forget that a small deployment which helps just a dozen people is significant to those dozen people and their families.

3. “Centralised is better than distributed
Not everything needs to run on a mega-server housed in the capital city, accessed through “the cloud“. Okay, storing data and even running applications – remotely – might be wonderful technologically, but it’s not so great if you have a patchy internet connection, if one at all. For most users centralised means “remote”, distributed “local”.

4. “Big is beautiful”
Sadly there’s a general tendency to take a small-scale solution that works and then try to make a really big version of it. One large instance of a tool is not necessarily better that hundreds of smaller instances. If a small clinic finds a tool to help deliver health care more effectively to two hundred people, why not simply get the same tool into a thousand clinics? Scaling a tool changes its DNA, sometimes to such an extent that everything that was originally good about it is lost. Instead, replication is what’s needed.

Toolbox from Flickr (_sarchi)

5. “Tools are sold as seen”
I would argue that everything we see in the social mobile applications ecosystem today is “work in progress”, and it will likely remain that way for some time. The debate around the pros and cons of different tools needs to be a constructive one – based on a work in progress mentality – and one which positively feeds back into the development cycle.

6. “Collaborate or die”
Although collaboration is a wonderful concept, it doesn’t come without its challenges – politics, ego and vested interests among them. There are moves to make the social mobile space more collaborative, but this is easier said than done. 2009 will determine whether or not true non-competitive collaboration is possible, and between who. The more meaningful collaborations will be organic, based on needs out in the field, not those formed out of convenience.

7. “Appropriate technologies are poor people’s technologies”
A criticism often aimed more broadly at the appropriate technology movement, locally-powered, simple low-tech-based responses should not be regarded as second best to their fancier high-tech ‘Western’ cousins. A cheap, low-spec handset with five days standby time is far more appropriate than an iPhone if you don’t live anywhere near a mains outlet.

kiwanja Mobile Gallery

8. “No news is bad news”
For every headline-grabbing mobile project, there are hundreds – if not thousands – which never make the news. Progress and adoption of tools will be slow and gradual, and project case studies will bubble up to the surface over time. No single person in the mobile space has a handle on everything that’s going on out there.

9. “Over-promotion is just hype”
Mobile tools will only be adopted when users get to hear about them, understand them and are given easy access to them. One of the biggest challenges in the social mobile space is outreach and promotion, and we need to take advantage of every opportunity to get news on available solutions – and successful deployments – right down to the grassroots. It is our moral duty to do this, as it is to help with the adoption of those tools which clearly work and improve people’s lives.

10. “Competition is healthy”
In a commercial environment – yes – but saving or improving lives should never be competitive. If there’s one thing that mobile-for-development practitioners can learn from the wider development and ICT4D community, it’s this.

Social mobile: Doing what it says on the tin

About a year ago I was asked to give an interview to the Africa Journal. They were looking at ICT innovators and entrepreneurs in Africa and I agreed, despite being mildly uncomfortable being labelled an ICT innovator or an entrepreneur (and an African one, at that). At the end of the interview, however, they captured a brief moment which beautifully encapsulated what FrontlineSMS is all about. The interview ended:

FrontlineSMS provides the tools necessary for people to create their own projects that make a difference. It empowers innovators and organizers in the developing world to achieve their full potential through their own ingenuity

FrontlineSMS has always been about empowerment. It’s never been about telling people how to use mobile phones to monitor elections, to increase market transparency, or help raise awareness around HIV/AIDS issues, even though it’s been used for these things and many more. At the end of the day, it’s a tool which allows organisations to figure out how to do these things for themselves. Combine that with a connected community and you have the makings of something quite powerful.

The decision to build a platform – and not a specific solution to a specific problem – has turned out to be one of the key strengths of the software. The new functionality we’ve added to the latest version takes this one step further allowing, for example, St. Gabriel’s hospital in Malawi to figure out how to do automatic remote top-ups of their health workers’ phones, or CP-Union in the Philippines to share incoming SMS data – human rights reporting in this case – with their own K-Rights Monitoring software. When users start adding contacts, keywords and actions in FrontlineSMS, or integrating it into existing systems, they’re essentially creating something new, something from scratch, a communications environment all of their own making.

In ideal circumstances platforms become something of a blank canvas, and the brushstrokes the user-generated ‘content’ (actionable ideas, in this case). Not only does this encourage a culture of do-it-yourself thinking, it also creates instant engagement and ownership. Combine these with the local knowledge and level of engagement many NGOs already have with their stakeholders, and you’re half-way to a positive outcome. Approaches which allow initiatives to grow from the ground up, focusing on technology as the enabler (not the owner) generally have the greatest chance of success. The uses of FrontlineSMS, for example, are bewildering, and they’re growing all the time. Few, if any, were anticipated. Lower the barriers to entry and all sorts of things can happen, it seems.

Local ownership, the use of appropriate technology, ease-of-use, high replicability and accessibility, and a low barrier to entry should be among the key ingredients of any grassroots-focused social mobile tool. If we’re to make real, tangible progress then the tools we create don’t only need to set out to empower, they need to empower. In other words, they need to do exactly what they say on the tin.