Where technology meets anthropology, conservation and development
Random header image... Refresh for more!

A glimpse into social mobile’s long tail

Although I’ve only been writing about the social mobile long tail for a couple of years, the thinking behind it has developed over a fifteen year period where, working on and off in a number of African countries, I’ve witnessed at first hand the incredible contribution that some of the smallest and under-resourced NGOs make in solving some of the most pressing social and environmental problems. Most of these NGOs are hardly known outside the communities where they operate, and many fail to raise even the smallest amounts of funding in an environment where they compete with some of the biggest and smartest charities on the planet.

Long tail NGOs are generally small, extremely dedicated, run low-cost high-impact interventions, work on local issues with relatively modest numbers of local people, and are staffed by community members who have first-hand experience of the problems they’re trying to solve. What they lack in tools, resources and funds they more than make up with a deep understanding of the local landscape – not just geographically, but also the language, culture and daily challenges of the people.

After fifteen years it should come as no surprise to hear that most of my work today is aimed at empowering the long tail, as it has been since kiwanja.net came into being in 2003, followed by FrontlineSMS a little later in 2005. Of course, a single local NGO with a piece of software isn’t going to solve a wider national healthcare problem, but how about a hundred of them? Or a thousand? The default position for many people working in ICT4D is to build centralised solutions to local problems – things that ‘integrate’ and ‘scale’. With little local ownership and engagement, many of these top-down approaches fail to appreciate the culture of technology and its users. Technology can be fixed, tweaked, scaled and integrated – building relationships with the users is much harder and takes a lot longer. Trust has to be won. And it takes even longer to get back if it’s lost.

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.

Here’s a video from Lynman Bacolor, a FrontlineSMS user in the Philippines, talking about how he uses the software in his health outreach work. What you see here is a very simple technology doing something which, to him, is significant.


Watch this video on the FrontlineSMS Community pages

In short, Lynman’s solution works because it was his problem, not someone elses. And it worked because he solved it. And going by the video he’s happy and proud, as he should be. Local ownership? You bet.  \o/

Now, just imagine what a thousand Lynman’s could achieve with a low cost laptop each, FrontlineSMS and a modest text messaging budget?

54 comments

1 GeorgeS { 01.22.09 at 8:36 pm }

Kenny – It’s very hard to argue against this. Simple and inspirational stuff from Dr. Bacalor. One can only imagine what hundreds of Doctors could do with this, and quickly. Maybe what Mobiles In Malawi are doing could be done in the Philippines? Your points about replication and solutions for the long tail are spot on. All we need to do now is make it happen!

George

2 J.A. Ginsburg { 01.23.09 at 2:27 pm }

Great post! In fact, I linked to it on http://www.TrackerNews.net – an aggregator that focuses on health issues, humanitarian work and technology that supports both.

Re centralized vs localized solutions – it applies to so much, whether communication systems or power generation. And yet it always seems like such a surprise that one-size-fits-all answers usually only fit a few. The challenge is figuring out whether and how smaller tailored solutions might dovetail into a larger whole – something analogous to a smart power grid.

best & cheers,

Janet
http://twitter.com/TrackerNews

3 Josh Nebsit { 01.24.09 at 4:19 am }

GeorgeS – Absolutely! 2009 needs to be a year of action.

For updates on Mobiles in Malawi and the project’s expansion, follow http://jopsa.org and http://twitter.com/_jopsa

See you there!

- Josh

4 Stephane Boyera { 01.24.09 at 9:28 am }

Great post Ken ! i’m, at 95%, sharing your view. There are other cases where the sum of very very small, narrow little local actions led to a global positive effect at the worldwide. The best example is the history of the Web. it started with one user at Cern, and then some friends replicated, and so on to reach the situation where we are today. So jsut to say that i strongly believe in this process.
But then, there is this 5% on which we might have a slightly different view. This is about your last sentence. I personnaly believe that the current requirements to run an sms service is high. having a pc running 24hours a day is hard for many people (just having a pc, and then having it powered…). There are also many issues around text-based only approach which limit the access for people with low reading skills. All in one, i tend to believe that while SMS is great, there are alternate options (voice, mobile web) that might be alternate options, and it is important to develop tools and disseminate expertise round these technologies that might empower even more people.

Steph

5 kiwanja { 01.24.09 at 9:57 am }

Thanks for the comments!

@GeorgeS @Josh Nesbit – Totally with you both. We have a great opportunitiy to reach out this year, but nothing will happen if we just sit on our bums. The whole social mobile sector needs to get out there and make it happen, as many of us are. Really positive about 2009!

@J. Ginsburg – Thanks Janet – nice to hear from someone who understands and supports the notion. Looking forward to keeping the “distributed vs. centralised” conversation going

@Steph – I agree that we do need to be thinking wider than just SMS-based tools. The real challenge is how we learn the lessons from successful SMS implementations and transfer them over to the ‘newer’ technologies. It won’t be easy, and hasn’t really happened yet. Of course, it will – and hopefully sooner rather than later. When we build MMS into FrontlineSMS that could see the start of a move in kiwanja’s work, at least, to embrace things like voice and data into the platform

6 New links for January 26th | Working Wikily { 01.26.09 at 3:11 pm }

[...] Facebook-Style – Can Social Networking Turn Young Egyptians Into a Force for Democratic Change? * A glimpse into social mobile’s long tail * iPhone Apps for Nonprofits (summary and commentary after the [...]

7 Social mobile: Myths and misconceptions | Build it Kenny, and they will come... { 02.02.09 at 9:43 pm }

[...] 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 [...]

8 FrontlineSMS: Now with Forms | Build it Kenny, and they will come... { 03.02.09 at 9:02 am }

[...] of FrontlineSMS. In short, FrontlineForms compliments our existing focus on empowering the social mobile long tail with an entry-level, usable data collection [...]

9 Girish Babu { 04.18.09 at 7:04 am }

will Mobile MMS be acessible with Low bandwidht of GPRS in remote villages .

How about applications to track the health of Individuals in Villages and do preventive work in Mother, Child and Chronic Diseases.

Can it be a self sustainable model for scale up to other regions?

10 Social mobile: Myths and misconceptions { 04.22.09 at 10:31 pm }

[...] 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. [...]

11 FrontlineSMS: Data collection just got easier { 04.22.09 at 11:25 pm }

[...] of FrontlineSMS. In short, FrontlineForms compliments our existing focus on empowering the social mobile long tail with an entry-level, usable data collection [...]

12 kiwanja (Ken Banks) { 05.19.09 at 4:16 pm }

Why we should empower the social mobile long tail, and the fail culture of top-down solutions. A reminder: http://is.gd/gQJc

13 ttim (Tim Terpstra) { 05.19.09 at 4:25 pm }

RT @kiwanja: Why we should empower the social mobile long tail, and the fail culture of top-down solutions. A reminder: http://is.gd/gQJc

14 Tim Terpstra { 05.19.09 at 4:25 pm }

RT @kiwanja: Why we should empower the social mobile long tail, and the fail culture of top-down solutions. A reminder: http://is.gd/gQJc

15 woodwardmw (Mark Woodward) { 05.19.09 at 4:31 pm }

RT @kiwanja: Why we should empower the social mobile long tail, and the fail culture of top-down solutions. A reminder: http://is.gd/gQJc

16 Mark Woodward { 05.19.09 at 4:31 pm }

RT @kiwanja: Why we should empower the social mobile long tail, and the fail culture of top-down solutions. A reminder: http://is.gd/gQJc

17 jmtrombley (Jeremy Trombley) { 05.19.09 at 4:37 pm }

RT @kiwanja: Why we should empower the social mobile long tail, and the fail culture of top-down solutions. A reminder: http://is.gd/gQJc

18 Jeremy Trombley { 05.19.09 at 4:37 pm }

RT @kiwanja: Why we should empower the social mobile long tail, and the fail culture of top-down solutions. A reminder: http://is.gd/gQJc

19 jlamontagne (Juliette LaMontagne) { 05.19.09 at 4:50 pm }

RT @kiwanja: Why we should empower the social mobile long tail, and the fail culture of top-down solutions. A reminder: http://is.gd/gQJc

20 Juliette LaMontagne { 05.19.09 at 4:50 pm }

RT @kiwanja: Why we should empower the social mobile long tail, and the fail culture of top-down solutions. A reminder: http://is.gd/gQJc

21 jlamontagne { 05.19.09 at 4:50 pm }

RT @kiwanja: Why we should empower the social mobile long tail, and the fail culture of top-down solutions. A reminder: http://is.gd/gQJc

22 Jon Camfield { 05.19.09 at 4:54 pm }

I agree; it’s a difficult (but oh so important) line to walk between individualized tools and scalable projects — something, mind you, that FrontlineSMS does particularly well, being a “simple” tool that can be used in a variety of ways for a variety of different challenges.

23 jon camfield { 05.19.09 at 5:03 pm }

#JonTag A glimpse into social mobile’s long tail | Build it Kenny, and they … http://tinyurl.com/oy6bwu

24 joncamfield { 05.19.09 at 5:03 pm }

#JonTag A glimpse into social mobile’s long tail | Build it Kenny, and they … http://tinyurl.com/oy6bwu

25 johnkeithhart (Keith Hart) { 05.19.09 at 6:30 pm }

RT @jmtrombley:RT @kiwanja: Why we should empower the social mobile long tail, and the fail culture of top-down solutions. http://is.gd/gQJc

26 Keith Hart { 05.19.09 at 6:30 pm }

RT @jmtrombley:RT @kiwanja: Why we should empower the social mobile long tail, and the fail culture of top-down solutions. http://is.gd/gQJc

27 johnkeithhart { 05.19.09 at 6:30 pm }

RT @jmtrombley:RT @kiwanja: Why we should empower the social mobile long tail, and the fail culture of top-down solutions. http://is.gd/gQJc

28 Ken Banks { 05.19.09 at 8:50 pm }

Why we should empower the social mobile long tail, and the fail culture of top-down solutions. http://is.gd/gQJc

29 kiwanja { 05.19.09 at 8:50 pm }

Why we should empower the social mobile long tail, and the fail culture of top-down solutions. http://is.gd/gQJc

30 bryanrieger (Bryan Rieger) { 05.19.09 at 8:54 pm }

Why we should empower the social mobile long tail, and the fail culture of top-down solutions. http://is.gd/gQJc (via @kiwanja)

31 Bryan Rieger { 05.19.09 at 8:54 pm }

Why we should empower the social mobile long tail, and the fail culture of top-down solutions. http://is.gd/gQJc (via @kiwanja)

32 bryanrieger { 05.19.09 at 8:54 pm }

Why we should empower the social mobile long tail, and the fail culture of top-down solutions. http://is.gd/gQJc (via @kiwanja)

33 calweb (Calvin D. Webster II) { 05.19.09 at 8:55 pm }

RT @kiwanja: Why we should empower the social mobile long tail, and the fail culture of top-down solutions. http://is.gd/gQJc

34 Calvin D. Webster II { 05.19.09 at 8:55 pm }

RT @kiwanja: Why we should empower the social mobile long tail, and the fail culture of top-down solutions. http://is.gd/gQJc

35 calweb { 05.19.09 at 8:55 pm }

RT @kiwanja: Why we should empower the social mobile long tail, and the fail culture of top-down solutions. http://is.gd/gQJc

36 Kevin Donovan { 05.21.09 at 1:57 am }

“Of course, a single local NGO with a piece of software isn’t going to solve a wider national healthcare problem, but how about a hundred of them? Or a thousand?”

That really drove home your point. Important stuff.

But, I think the key to making those long tailers effective is enabling collaboration and coordination. How best to get the small FrontlineSMS-wielding NGOs to collaborate?

37 Kevin Donovan { 05.21.09 at 1:59 am }

Important post from @kiwanja on the social mobile long tail: http://tr.im/lWNL but we need convo about enabling collaboration b/w NGOs

38 kevindonovan { 05.21.09 at 1:59 am }

Important post from @kiwanja on the social mobile long tail: http://tr.im/lWNL but we need convo about enabling collaboration b/w NGOs

39 kiwanja { 05.21.09 at 8:39 am }

@Kevin – Thanks for your comments, and for joining the discussion. I agree that this is an important part of the social mobile mix, but one which remains under-discussed.

As for enabling collaboration, the online community (http://frontlinesms.ning.com) is providing a platform for NGOs to share stories and work together, and we’re already seeing this happening. We’re also organising email lists which will allow users to send messages to others outside of Ning.

Community is notoriously hard to create – at least genuine, engaging, active community is. We’re certainly getting there, but it does take time. One idea we do have for the future are FrontlineSMS Conferences, where people can meet (users, developers, practitioners, etc) and discuss their use and ideas for the software

40 Ken Banks { 05.21.09 at 8:41 am }

@Kevindonovan Thanks for your comment, Kevin. I’ve posted a short response. Great to be having this discussion. http://is.gd/gQJc

41 The Social Mobile Long Tail explained | Build it Kenny, and they will come... { 05.23.09 at 10:48 am }

[...] What follows is a short extract from the recent “Soul of the New Machine” human rights/technology conference hosted by UC Berkeley, in which I explain my theory of the Social Mobile Long Tail. [...]

42 Kevin Donovan { 05.26.09 at 3:10 am }

Thanks, Ken. I sympathize with the difficulty of creating a community, but I do think it’s amazing how much you’ve been able to do so far.

Admittedly I am not familiar with the specifics of the technology, but in the midst of creating personal relationships through conferences, etc., it would be great to encourage technical means for sharing/collaborating/etc., as well as the ‘human layer’.

43 meowtree (Linda Raftree) { 09.15.09 at 10:37 am }

(old but good) RT @kiwanja: Why we should empower the social mobile long tail, and the fail culture of top-down solutions. http://is.gd/gQJc

44 Linda Raftree { 09.15.09 at 10:37 am }

(old but good) RT @kiwanja: Why we should empower the social mobile long tail, and the fail culture of top-down solutions. http://is.gd/gQJc

45 meowtree { 09.15.09 at 10:37 am }

(old but good) RT @kiwanja: Why we should empower the social mobile long tail, and the fail culture of top-down solutions. http://is.gd/gQJc

46 Dilemmas of innovation and invisibility | Build it Kenny, and they will come... { 10.24.09 at 8:53 am }

[...] and my work is no exception. These things still trouble me, but at least I think we’re on the right path – not just technically, but more importantly, [...]

47 peter_laugharn (Peter Laugharn) { 11.18.09 at 1:24 pm }

RT @kiwanja.net @FrontLineSMS A glimpse into social mobile’s long tail | Build it Kenny, and they will come… http://is.gd/gQJc

48 Peter Laugharn { 11.18.09 at 1:24 pm }

RT @kiwanja.net @FrontLineSMS A glimpse into social mobile’s long tail | Build it Kenny, and they will come… http://is.gd/gQJc

49 Technology decisions in organisations great and small « Aptivate | A Blog for ICT4D { 01.21.10 at 2:03 pm }

[...] Banks often writes about Social Mobile’s Long tail – it’s a really helpful concept; one that I find myself frequently using when [...]

50 Reflections on eight years in mobile | Build it Kenny, and they will come... { 12.13.10 at 12:52 pm }

[...] were a number of reasons for this, but the idea behind FrontlineSMS seemed to solve all of them. Build a messaging system which could run without the need for the Internet, make it simple to use, [...]

51 The innovation/entrepreneurship divide | Build it Kenny, and they will come... { 03.10.11 at 1:41 pm }

[...] introduction, in which I briefly touch on our work with FrontlineSMS and why we focus on the “social mobile long tail“. It ends with a summary of some of the challenges entrepreneurs and innovators face working [...]

52 Interoperable Technologies in International Development: Access to FrontlineSMS | Gnovis Journal { 08.04.11 at 12:59 am }

[...] Banks, K. (2009). “A glimpse into social mobile’s long tail | Build it Kenny, and they will come” kiwanja.net :: Where technology meets anthropology, conservation and development. Retrieved December 20, 2010, from http://www.kiwanja.net/blog/2009/01/a-glimpse-into-social-mobiles-long-t… [...]

53 Rethinking socially responsible design in a mobile world | Build it Kenny, and they will come... { 10.05.11 at 7:41 pm }

[...] 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 [...]

54 Katy Digovich { 07.12.12 at 12:17 pm }

@botsping I really like this concept:http://t.co/QFccqSQ2 from @kiwanja but where does PING sit as we exhibit traits from both tail ends?

Leave a Comment