10 Tips for Successful ICT4D Interventions: An Interview with ICT4D Pioneer Ken Banks

ImageKen Banks, founder of kiwanja.net and FrontlineSMS, devotes himself to the application of mobile technology for positive social and environmental change in the developing world. He has worked at the intersection of technology, anthropology, conservation and development for the past twenty years and, during that time, has lived and worked across the African continent. He is a Pop!Tech Fellow, a Tech Awards Laureate, an Ashoka Fellow and a National Geographic Emerging Explorer. His latest project, Means of Exchange, is looking at how everyday technologies can be used to democratize opportunities for economic self-sufficiency, rebuild local community and promote a return to local resource use.

 Q:  You’ve been working in this field for some time – is it surprising to you that there is no “best practice” guide for ICT4D, or is this to be expected in a field that is being transformed so rapidly by changes in technology?

A:  A lot of people have opinions on what works in ICT4D and what doesn’t. Just because a particular tool or lesson might apply in one place doesn’t mean it will work everywhere. This oversimplifies the issue of replication, scale and getting things to work in what are often very different environments. The idea of “best practices” almost assumes that there are commonalities that you can apply globally. This may be true in some cases, but it won’t be true in all.

Q:  What about your experience in creating and growing FrontlineSMS – what factors have you found to be important in building a successful ICT4D project?

A:  There are a handful of important factors – I can list off my top 10, in no particular order.

  • Build for what people already have in their hands. It’s critical to understand the hardware and device landscape, particularly which technologies your users have access to and ownership of. Many projects still have this problem – looking at smart phones or other top-of-the-range technologies that don’t work for the people they’re trying to help.

  • If your product needs an installation guide, that’s a barrier. When ICT4D tools are developed, there are often things that need to be plugged in, connected or configured. Any installation process needs to make sense to people – especially people who need convincing that they can do it themselves. If people can get a tool to work on their own, they often feel incredibly empowered.
  • Projects have to be sustainable, but by charging users you often put barriers up to adoption. The target users of your ICTD tool may not be able to pay, or have a mechanism to pay. Good business models in the field are few and far between. Joel Selanikio’s ‘freemium’ model with Magpi may be one of the best. It certainly seems to work.

  • If you need to fly in and out to carry out installation, you’re going to struggle to get to scale. For ICT4D projects to scale, you need replication on the ground by users to other users. If users can share, learn, and replicate among themselves, there’s a chance you’ll get a viral effect. Some projects try to generate a degree of financial sustainability by creating a need for users to draw on paid services – but for many this becomes a barrier.
  • If you build your ICT4D tool to work without the Internet, then it will work anywhere.  Always start off with assumption that there’s no Internet. Too many projects that fail start off with the opposite assumption. Not only that, just because a user has a smart phone doesn’t mean that they are online. They may swap out their SIM card so frequently that their phone isn’t configured to access the Internet, or they may not be able to afford data services, or they may not live in an area with reliable data coverage.
  • Community is absolutely critical. This is often the hardest thing to create because you can’t force people to engage. In ICT4D, community is the Holy Grail. You want to create an environment where users can connect and provide technical support to one another – one where you don’t get in the way. One thing I always used to ask myself with the FrontlineSMS community was, if I stopped providing support to it tomorrow, would users take up the reins themselves?
  • We need to think of appropriate technology as a discipline. The ICT4D field would undoubtedly benefit if there was a stronger appreciation for the ethos of the appropriate technology movement. We need to keep E. F.  Shumacher in mind when building tools to ensure that they are designed to work with the local environment, culture, and people in mind.  So much of what we see doesn’t work, and yet people continue to do it.
  • Collaboration is key.  There isn’t enough collaboration in the development space as a whole. Everyone wants their own project with their own name and sense of objectives. Some people also see ICT4D as competitive, pitching tools against one another when, in reality, no one ICT4D tool is inherently better than another. It all depends on the context in which the tool is being used, and that can vary a lot.
  • Think beyond technology. Good technology has a certain spirit and meaning, and can connect with people on a non-technical, higher level. How you feel when you buy an Apple product, for example. There’s something special about it, it feels part of you. FrontlineSMS has done an amazing job of not only helping people do their work better, but feel better about themselves. It empowers and encourages. Tools need to engage, entertain and connect with the user on multiple levels.
  • Don’t lose sight of the bigger picture. People often get carried away with the technology, so much so that it can be easy to forget why you started doing what you were doing in the first place.  Ask yourself every day why you’re doing what you’re doing, and whether it gets you any closer to that wider goal. Looking to simply build a cool app isn’t likely why you got started. Keeping the big picture in mind, and the challenges you’re looking to help people overcome, reminds you to stay focused.

Q:   The United Methodist Communications agency first reached out to you in 2008 and now has a number of active projects using FrontlineSMS. What are your thoughts on the importance of ICT4D to the work of the United Methodist Church?

A:  Anybody anywhere trying to improve peoples’ lives naturally wants to figure out how to best maximize their impact, and how to get the biggest bang for their buck. It’s refreshing to see a church looking so openly at how technology can improve their work. The [United Methodist] church is going out with the single objective of improving the lives of their community.  This is something they’ve dedicated their lives to. To them it’s not just a job, but something that needs to be done, and that’s their purpose in life. For me, that’s exactly the right way [for ICT4D] to be done. Start with the problem. People like technology because it can do good things for them, just like a spade or a ruler can. At the end of the day, you can’t eat a mobile phone.

Advertisements

10 thoughts on “10 Tips for Successful ICT4D Interventions: An Interview with ICT4D Pioneer Ken Banks

  1. This is a very informative post and I agree with Ken’s main points here. I think Ken’s ideas could be put into a framework that involves thinking about these implementations as socio-technical systems and there is a lot of great theoretical work on this that could be translated into pragmatic strategies and design processes. Many of these points connect nicely with some of the human centered design approaches developed by IDEO and others. These more open-ended, critical thinking types of frameworks would be useful to develop with digital health implementations but also include a lot of deep thinking on issues like EA, policy frameworks, etc. I think the issue of scale could be framed in a more open-ended way. On one hand, some of the sacrifices that scaling up requires may have negative effects for some users but scale can also mean lower barriers to access in other contexts. In healthcare we need surveillance systems that can scale and provide regional, national level pictures to inform policy so I think that issue is a bit more complex but there are certainly trade-offs. This is an interesting discussion that could be useful in catalyzing the creation of better tools for planners.

  2. Some great points here — I was looking for exactly this a few months back when I put together this post: http://www.joncamfield.com/blog/2013/04/stop_doing_technology_for_good . The ICT4D landscape has some clear best practices, but it feels like we as implementers often have to fight (our various orgs, funders, or simply just timelines, expectations and path dependency) to keep projects on track for long-term sustainability. Many thanks for this first pass at codification!

  3. Totally agree and can speak to a lot of this. Having been involved in international online collaborative learning platforms for teachers, two things that Ken has said really stand out for me: (1) keeping the installation simple (guides can often just create more confusion); and (2) making sure the community can run itself even if you, or your technology, are no longer around. I think that a major part of ICT4D is creating community, developing networks, sharing practice. If we can make these connections, we can then continue to walk on our own. Three cheers for FrontlineSMS – a source of great inspiration for many ICT4D initiatives.

  4. I also agree with Ken’s point of view. Sometime, the users of technology find themselves in a situation where there is no one to help solving a problem along the use of the material or software. Is the user is able to solve some of these problems himself then the technology will contribute for the development because when the user is stuck, the development stops also.

    Also, Ken understands well the worldwide situation after traveling or working worldwide. There are many people or conceivers’ of technology materials who think that the conditions in the USA or Europe are the same everywhere. In my country the D.R. Congo, more than half of the population is not using the machine (computer) and some did not yet see a computer. In this situation, trying to complicate the use of a machine or material will not help those people to use them. They will prefer to continue doing their old behaviors because it is difficult to comply with the new ways of doing things. So keep it simple and easy.

    I like also this “If you build your ICT4D tool to work without the Internet, then it will work anywhere”. Binu, has worked in that direction by putting a software which is now helping us to read and even answer our mails even outside a café or an office because this software allows us to connect to our mails, send sms messages or chat without paying and even without internet connection.

    Finally, I like this statement “Build for what people already have in their hands” Everyone is not able to buy a laptop or a smartphone… bur majority of the population today can get a cellphone. Coming up with SMS Frontline program was of great imagination because it is a program which is using what people to be served have always at hand. I have learned a lot from reading this and I am empowered.

    Thank you Ken for the innovation….

  5. Thanks Pierre, everyone, for the positive response to the post. It’s great to hear that so much resonates. I’ve written a lot about this over the years and you can find more in the “Technology” and “Development” sections (among others) in the http://www.kiwanja.net/blog

  6. Thanks Ken for innovation. I really agree with your main points. I have an active project ongoing using Frontline SMS which is helping us to read and send health messages or chat to without connecting to internet. This project is rural based where electricity and internet is a challenge.

    Thank you for sharing Ken.

  7. Pingback: Transition to Electronic Health Records in Rizgari Hospital | ICT4D simulated project.html

  8. Pingback: » Weblieblingebetterplace lab betterplace lab

  9. Pingback: Tech Project Specifications and Social Change - FabRiders

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s