social mobile

Rethinking socially responsible design in a mobile world

"The Curry Stone Design Prize was created to champion designers as a force for social change. Now in its fourth year, the Prize recognizes innovators who address critical issues involving clean air, food and water, shelter, health care, energy, education, social justice or peace". Yesterday was an exciting day for us as we announced FrontlineSMS had won the prestigious 2011 Curry Stone Design Prize. This award follows closely on the heels of the 2011 Pizzigati Prize, an honourable mention at the Buckminster Fuller Challenge and our National Geographic "Explorer" Award last summer. It goes without saying these are exciting times not just for FrontlineSMS but for our growing user base and the rapidly expanding team behind it. When I think back to the roots of our work in the spring of 2005, FrontlineSMS almost comes across as "the little piece of software that dared to dream big".

With the exception of the Pizzigati Prize - which specifically focuses on open source software for public good - our other recent awards are particularly revealing. Last summer we began something of a trend by being awarded things which weren't traditionally won by socially-focused mobile technology organisations.

Being named a 2010 National Geographic Emerging Explorer is a case in point, and last summer while I was in Washington DC collecting the prize I wrote down my thoughts in a blog post:

On reflection, it was a very bold move by the Selection Committee. Almost all of the other Emerging Explorers are either climbing, diving, scaling, digging or building, and what I do hardly fits into your typical adventurer job description. But in a way it does. As mobile technology continues its global advance, figuring out ways of applying the technology in socially and environmentally meaningful ways is a kind of 21st century exploring. The public reaction to the Award has been incredible, and once people see the connection they tend to think differently about tools like FrontlineSMS and their place in the world.

More recently we've begun receiving recognition from more traditional socially-responsible design organisations - Buckminster Fuller and Clifford Curry/Delight Stone. If you ask the man or woman on the street what "socially responsible design" meant to them, most would associate it with physical design - the building or construction of things, more-to-the-point. Water containers, purifiers, prefabricated buildings, emergency shelters, storage containers and so on. Design is so much easier to recognise, explain and appreciate if you can see it. Software is a different beast altogether, and that's what makes our Curry Stone Design Prize most interesting. As the prize website itself puts it:

Design has always been concerned with built environment and the place of people within it, but too often has limited its effective reach to narrow segments of society. The Curry Stone Design Prize is intended to support the expansion of the reach of designers to a wider segment of humanity around the globe, making talents of leading designers available to broader sections of society.

Over the past few years FrontlineSMS has become so much more than just a piece of software. Our core values are hard-coded into how the software works, how it's deployed, the things it can do, how users connect, and the way it allows all this to happen. We've worked hard to build a tool which anyone can take and, without us needing to get involved, applied to any problem anywhere. How this is done is entirely up to the user, and it's this flexibility that sits at the core of the platform. It's also arguably at the heart of it's success:

We trust our users - rely on them, in fact - to be imaginative and innovative with the platform. If they succeed, we succeed. If they fail, we fail. We're all very much in this together. We focus on the people and not the technology because it's people who own the problems, and by default they're often the ones best-placed to solve them. When you lead with people, technology is relegated to the position of being a tool. Our approach to empowering our users isn't rocket science. As I've written many times before, it's usually quite subtle, but it works:

My belief is that users don’t want access to tools – they want to be given the tools. There’s a subtle but significant difference. They want to have their own system, something which works with them to solve their problem. They want to see it, to have it there with them, not in some "cloud". This may sound petty – people wanting something of their own – but I believe that this is one way that works.

What recognition from the likes of the Curry Stone Design Prize tells us is that socially responsible design can be increasingly applied to the solutions, people and ecosystems built around lines of code - but only if those solutions are user-focused, sensitive to their needs, deploy appropriate technologies and allow communities to influence how these tools are applied to the problems they own.

Further reading FrontlineSMS is featured in the upcoming book "Design Like You Give a Damn 2: Building Change From The Ground Up", available now on pre-order from Amazon.

Our "social mobile" line in the sand

The depth and range of discussion generated by my last post on "the cloud" and "appropriate technology" may have come as something of a surprise, but one thing is clear. There's a great deal of misunderstanding around the topic, particularly with people who are either developing or promoting tools based on the very technology I was challenging. The only way to avoid this kind of confusion is to spell out our positions clearly, and I made this point in that very same post. So how do we move on from here? Well, we need to set out our positions clearly as a marker in the sand for future discussion. So, let me go first. To clear up any present and future confusion, here's the official FrontlineSMS / kiwanja.net position on what I consider five key "mobile tools for development" areas - location in the "long tail", scaling, replication and growth, open sourcing and access to "the cloud".

1. Who are your target audience?

Some time ago I butchered Chris Anderson's "long tail" concept and adapted it for mobile. It seemed like the best way of categorising the different focus areas for mobile tools - high-end for larger organisations down to low-end for small grassroots ones. Here's what I came up with.

Social Mobile Long Tail, kiwanja.net

The basic rationale behind the diagram is this. Tools in the red area are technically and financially out-of-reach of many grassroots NGOs, many of whom sit in the green space. Tools at the higher end of the graph are generally more complex, server-based systems which require a high degree of technical competence, and often the Internet, to set up and use. Tools in the lower end are simple, low-cost, need few technical skills, work on easily available hardware, don't require the Internet, and are easy to install and run. Tools in the green space can be quickly adopted and replicated - within hours - whereas tools at the other end need much more planning, i.e. more people and more lead time, and most likely a degree of training.

Note: There is no right or wrong or good or bad place on the tail. There are just different places

From its early beginnings in South Africa in 2004, FrontlineSMS has been totally focused on grassroots NGOs in the green space, an area which I believed back then was heavily underserved (and to a large degree still is). We're not particularly interested in big users such as international NGOs or government departments. So if our tool isn't considered right for the kinds of big projects they're likely to be running, then that's fine with us.

I wonder where the other social mobile tools would place themselves on the tail?

2. What is your position on scaling?

Believe it or not, not everyone wants to build tools that can grow into large centralised solutions, which is how many people seem to define scale. No one is ever going to run a nationwide election monitoring campaign running into millions of text messages using a single laptop, cable and mobile phone. FrontlineSMS is based on "horizontal scaling", gained by an increase in the numbers of individual users with their own systems. In other words, a hundred systems in a hundred clinics serving 10,000 people each, rather than one system adapted and "scaled up" to serve a million. We're happy and comfortable with this approach, as are our target audience of grassroots NGOs.

3. How does it replicate and grow?

Growth is based on patience, and a "pull" rather than "push" approach, i.e. awareness-raising and then letting NGOs decide if they want to try out the tool or not. Those that do then go and request it from the website. Everything is driven by the end user, who needs to be independently motivated to download and use the tool. There is no need for us to be involved at any stage, so no-one flies anywhere and no-one does any training - note that the approaches of FrontlineSMS:Medic and FrontlineSMS:Credit may be different - and no-one tries to "sell" FrontlineSMS to anyone. The solution is designed to allow users to do everything themselves. No core FrontlineSMS implementations are driven by us, and none are our projects. Use is replicated by users sharing experiences, talking about their use of the tool to others, and growing numbers of champions who are either building their own solutions around FrontlineSMS, or bloggers and researchers who write about its use and impact.

4. What is your position on open sourcing?

Again, from the very beginning we have been unashamedly focused on our end user - NGOs in developing countries seeking easy-to-deploy mobile tools. Our end users are not programmers, coders or technical developers, and few if any of our FrontlineSMS user base would have any idea what to do with source code. We decided that we would focus on the open source community once we believed we had something worth working with, and that time is about now. In between working on everything else, we plan to launch a developer community soon. That all said, there are already a number of developers bolting on new functionality to the core FrontlineSMS platform, and 90% of the code is already available online and accessible through SourceForge.

5. Does access to "the cloud" matter?

Cloud image courtesy versacevistas.wordpress.com

FrontlineSMS only came about four years ago because of a critical lack of tools that allowed for group messaging without the need for the Internet. Building a tool which is able to operate in Internet-free zones has therefore been central to our thinking since the very beginning, and continues to this day. Beyond basic messaging, FrontlineSMS can make use of an Internet connection when and where available - messages can be forwarded via email, or posted to websites, for example (that's the functionality Ushahidi takes advantage of) - but no Internet is not a show stopper for us. And as time moves on and connectivity does improve, we'll be ready. We're adding picture messaging in the next couple of months (for example), and other web-based features are in the pipeline. We are not anti-Internet, but realistic when it comes to its availability and reliability.

So, that's our line in the sand. If anyone else has a mobile tool - or is working on a mobile tool - I'd encourage them to clear up any possible confusion and write a post outlining their thinking in these five areas. The alternative is more confusion, and more false arguments and comparisons.

I know I'd love to know the thinking behind more social mobile tools, and going by the reaction earlier this week, it looks like I'm not the only one. Now is a good-a-time as any to join the conversation.

Read responses and "lines in the sand" from:

FrontlineSMS:Credit FrontlineSMS:Medic

(As of 20th December, no other mobile tools providers have responded, which is a shame. May the confusion and misrepresentation continue...)

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, focussing 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-focussed 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.