What the Data Tells Us About our Self Help Group App Community

Over the two and a half years that our Self Help Group (SHG) app has supported facilitators of this high-impact program model, we have seen our user community grow to almost one thousand users. As we look to the future to plan how to further improve the resource, we wanted to share and summarize how and where the app has been used to date.

The Self-Help Group app is a digital resource for facilitators who are actively learning facilitation skills and mobilizing and mentoring active SHGs. If you’re not familiar with the SHG model, we’ve summarized it briefly below before exploring what the data tells us about our community of users.

A Quick Introduction to Self Help Groups

Self-Help Groups are microsavings and microcredit groups who voluntarily come together, both for social support and to provide the group with savings and access to credit for their businesses or income-generating activities.

They usually comprise about 15 members who meet weekly, buying shares in a joint savings pool that grows substantially over time and is used to give business loans to members with interest. Members also typically pay into a social fund that is used to give emergency loans to members for personal reasons, interest free.

SHGs differ from another savings and credit group model called Volunteer Savings and Loan Associations (VSLAs), most significantly because the group stays together over many years and does not pay out the join savings pool, but rather allows it to accumulate into what can become sizable capital.

When we first started to digitize the SHG program model, we did so because we found this approach to social and economic empowerment to be among the most effective and long-term that we’d seen, both for individual members and the larger community.

Our Reach to Date

So far, thanks to the support of private donors and the UK Department for International Development (DfID), we have been able to introduce the SHG app to both Tearfund and World Vision International, for their SHG and their VSLA programs respectively. Although the app’s curriculum for groups follows the SHG, and not the VSLA, model, we have heard from VSLA facilitators that it remains an effective resource for facilitators.

To date, the community of SHG members whose groups are using the app numbers approximately 1,000, at around 75 installs for groups of about 15 members each, taking into account the devices that Code and our developers use for testing, and that prospective partners are exploring to see if the app is a good fit for their savings and credit group programs.

Between Phase 1 (Ethiopia only, 2014) and Phase 2 (Ethiopia and Tanzania, 2015-16), our user base has grown by a factor of ten. It is our goal in future iterations to double our community base, and a stretch goal to multiply our numbers by another factor of ten, in this case to reach 10,000 total SHG members. Our three to five-year goal is to reach one million SHG members with this resource, although clearly we have a long way to go to get there.

Our Geographical User Base of Supported and Unsupported Users

self help group app platform graph of installs by country
self help group app platform graph of installs by country

When we look at the data about where the app is being downloaded, we see something interested and unexpected for this stage of our app’s development. We are still in progress building and testing the app, and collaborating actively with our facilitators and user community as we do so, to co-design and truly create a useful product for our clients, i.e. SHG facilitators supported by organizations and governments all over the world.

Even though the app is not finished, we see that only 35% of our installs are from facilitators supported by partner organizations in Ethiopia and Tanzania. The rest of the installs are from groups or facilitators that are unsupported by our team directly, and we see from our administrative back-end that many of these installs are active, i.e. they are hosting groups with names, who meet regularly and move through the curriculum, and even answer our in-app evaluation questions to provide us with valuable member data.

This observation is particularly interesting because of 27% of our total installs come from unsupported groups in India, where the Self Help Group model originated and where the government has institutionalized the SHG model as an effective poverty alleviation strategy.

This remains unexpected and will be an interesting metric to track over the coming months and years. In future app versions, we hope to add a data field when new groups register that encourages them to provide contact information, so that we can learn more about what is happening.

Hardware Connectivity Challenges for Self Help Groups

self help group app platform graph of installs by app version
self help group app platform graph of installs by app version

We built the SHG app to be used without mobile data or wifi connectively, once the device has been installed and the language options selected by the user. In the areas where our facilitators work, the cost of data connectivity can be prohibitive, even when there is signal available – and usually, a data signal can be hard to find.

This poses a challenge when we release new versions of the app, because if facilitators cannot access the new version wirelessly by using their data – and most of them cannot, nor do we expect them to – a program coordinator is responsible for physically visiting the facilitators and installing an APK by hand onto their device from their laptop.

This is rather arduous and time consuming, so we attempt to limit new versions to only one per quarter, and to coordinate with our partners so that they are confident of how to perform and troubleshoot an APK install of the app onto multiple different devices.

About 50% of our installs are currently running the latest version of the SHG app, while approximately 35% of the rest are running quite recent versions that include notable user experience and user interface improvements from our initial app. This leaves approximately 15% of users who are likely running a very old version of the app that has not had an opportunity to connect to any network or update itself.

Whether this is because of connectivity issues or attributable to other things, we understand the importance of having facilitators use the most recent app version and of working with coordinators to ensure that they have an opportunity to update the app on their program hardware, whenever possible.

Hardware Availability where SHGs Operate

self help group app platform graph of installs by app device
self help group app platform graph of installs by app device

Another important area for us to focus what type of Android device is being used to access the app. The majority (62%) of our users are on unknown devices and less than 10% are using the program-provided Tecno tablets purchased locally in Ethiopia and Tanzania.

This is promising, as we chose to purchase hardware for partners who were eager to pilot the app within their program models as an incentive to reduce the risk of them joining our user community. However, we understand that providing hardware is neither sustainable nor advisable as we move from our initial pilot towards a more mature product and are already bridging away from this model.

Already, we have partners who do not rely on us to support the costs of hardware, but as we scale we anticipate potentially continuing to cover the cost of a small portion of devices upfront, as we have seen it reduces the risk for new communities who want to use the app as a digital resource but who do not yet have the wider organizational buy-in to pursue large-scale hardware purchases.

As smart phone penetration continues to increase, and we believe strongly that these trends will continue, we anticipate the need to purchase hardware for new partners to rapidly diminish. We have already observed that Android handsets, rather than tablets, are owned by a growing portion of SHG facilitators and even by some SHG members. In addition, to further decrease barriers to using the resource, we hope to make a feature phone-accessible version of the app for users who are on older and more affordable devices as well.

Mobile Network Operators Serving the Digital Self Help Group Community

self help group app platform graph of installs by app carrier
self help group app platform graph of installs by app carrier

Although almost half (44%) of our installs do not have carrier information to share with us, we can see the major East African mobile network operators (MNOs) are represented by our community: MTN, Safaricom and Airtel. At the moment, this data is not particularly useful, however, if we were to create a feature phone version of the SHG app and want to use shortcodes, knowing which MNOs are most accessed by our community in any given country would help us chose the correct carrier or carriers to partner with.

In Summary

We are at an important juncture in our SHG app project, and it’s important for us to share where our community is, what devices, networks and app versions they’re using, as this data can help us as we look to the future, where we hope to finish our app build and further grow our user community.

We hope that this overview has been useful to the ICT4D community and are eager to learn from others doing similar work and facing similar challenges. If you’d like to get in touch about using the SHG app in your programs, or you’d like to learn more about the project and our plans for the future, please get in touch by emailing info@codeinnovation.com.

Our Rape Crisis Counseling App is 100% Funded!

RCC.jpg

Crowdfunding our Rape Crisis Counseling app for survivors of gender-based violence to receive emergency medical care (www.codeinnovation.com)

Code is happy to announce that our Rape Crisis Counseling app project is now 100% funded, thanks to support from the Imago Dei Fund after our crowdfunding campaign ended.

During the campaign, we saw support come from many sides and perspectives. We heard from colleagues that news had spread about the project from West Africa to Geneva, from the Philippines to Washington DC.

Rape Crisis Counseling App Social Media Update - Gloria Steinem posts about our project on Twitter (www.codeinnovation.com)One highlight of the campaign? When we received a Monday morning email from the "Office of Gloria Steinem," sharing that she would post a project endorsement on Twitter. This email was one of the most exciting that we received.

We're very proud to have the support of the important advocacy and research organization Report the Abuse, AWID and, since the campaign ended, we have also been joined by a national US sorority and several more women's rights and anti-violence organizations in sub-Saharan Africa.

Rape Crisis Counseling App Social Media Update - Gloria Steinem posts about our project on Twitter (www.codeinnovation.com)

Code created an extensive African-language mobile app, "About Ebola," with Snapp.cc, and we welcome partners who would like to see the basic content of the Rape Crisis Counseling app in their own languages.

Interested in joining us? Get in touch with me (elie@codeinnovation.com) to introduce yourself.

We are looking for women's rights organizations, anti-violence organizations and communities who would like to use our Rape Crisis Counseling app curriculum for training their own volunteers in crisis centers and health programs.

Also, we are designing the resource to provide in-hand support to rape survivors and their advocates, to help them navigate through the health system.

Next Step: Mobile Curriculum

Right now, the Code Innovation team is hard at work on a first version of our mobile app's content and curriculum. This is a big process, and we're taking our time to get primary training materials from partners including the Pittsburgh Action against Rape coalition, the Washington DC Rape Crisis Center and the Victim Assistance Training from the US Department of Justice.

Sign-up HERE for Updates on our progress!

Thank you for supporting the Rape Crisis Counseling app and spreading the word.

 

 

Digital Tools for Cooperatives and the Regenerative Economy

Ugandan women in a cooperative (www.codeinnovation.com)Code is looking forward to building on the success of our Self-Help Group app by optimizing it for other savings groups and other cooperative models. We’re also keen to explore how these tools might help to spread the influence of the Transition Network.

If you're at the Rotary Convention in Seoul, Korea, Nathaniel Calhoun is leading the first break-out session, "Rotary Business School: Innovation."

He'll be speaking on the future of learning, work and business and highlighting some of the first successful platform cooperatives and blockchain-based decentralized organizations.

Come and say hello!

Our Article on Open Source Aid and Development @ UNICEF Stories

ICT4D Digital Principle 6 is Open Source in the future of international development and humanitarian aid (www.codeinnovation.com)UNICEF recently published our piece over at their Stories of Innovation platform to celebrate Digital Development Principle #6: Use Open Standards, Open Data, Open Source and Open Innovation Often the discussion around adopting Open Source is framed very narrowly as a challenge to the financial sustainability of a project.

Our post explains why that frame is inadequate, missing the opportunity to learn from emergent trends in commons management, digitally supported cooperatives and more.

READ THE ARTICLE HERE.

PRESS RELEASE: Global Partnership is Crowdfunding to Create Digital Resource for Volunteer Rape Crisis Counselors

Indonesia, 22 February 2016 –  Code Innovation is leading a crowdfunding campaign on Indiegogo to create a Rape Crisis Counseling mobile app to support rape survivors and their advocates as they access medical care anywhere in the world. “One in five women will be raped in her lifetime,” says Elie Calhoun, Director at Code Innovation. “Where rape crisis centers and their volunteer counselors exist, they provide a vital resource to survivors and their communities. But rape crisis counseling isn’t a luxury – it should be available to everyone who needs it, regardless of where they live. And anyone who wants to become a volunteer rape crisis counselor should be able to access the basic training they need to support survivors as they access critical health services.”

“DCRCC is pleased to be collaborating on this important global initiative,” says the DC Rape Crisis Center, the oldest rape crisis center in the U.S. “It is important that the International Community come together to not only address gender based-violence, but create resources and tools to enable self –determination and freedom for all. This mobile app does just that, it is a game changer for being able to educate and access resources for sexual assault survivors in a timely manner.”

The Rape Crisis Counseling app will digitize information and training for volunteer rape crisis counselors, who accompany and advocate for sexual assault survivors in emergency rooms as they access crucial medical services to prevent pregnancy, HIV and STIs. The app will also serve as an in-hand resource for family, friends or colleagues who accompany a rape survivor to the health center, and for survivors accessing medical care alone, to help navigate the medical system and to get the care they need to begin the journey to healing.

###

To support the campaign, visit: https://www.indiegogo.com/projects/rape-crisis-counseling-app/x/3176191#/story

For updates, visit http://codeinnovation.com/blog/.

About the DC Rape Crisis Center

Since 1972, the DC Rape Crisis Center has been making a significant contribution to the health, economic, social and cultural well-being of society. Dedicated to creating a world free of sexual violence through conscience and action, DCRCC’s call to action obliges us to build the capacity to respond to survivors of sexual assault with compassion, dignity and respect, regardless of race, class, gender identity or expression, sexual orientation, immigration status, ability, age or religious affiliation.

About Code Innovation

Code Innovation digitizes and scales programs that help vulnerable populations. We create educational materials and social innovations that strengthen communities and enable them to lift themselves out of poverty. We've had projects in more than a dozen countries and specialize in challenging, low-resource environments.

For more information, please contact:

Elie Calhoun, Code Innovation, Tel. +62-812-3802-3425, email: elie@codeinnovation.com

PRESS RELEASE: Code Innovation Launches a Crowdfunding Campaign for Rape Crisis Counseling App to Help Survivors Get Medical Care

Crowdfunding our Rape Crisis Counseling app for survivors of gender-based violence to receive emergency medical care (www.codeinnovation.com)Indonesia, 14 February 2016 - To celebrate V-Day today, a global day of action to end violence against women, Code Innovation launched our Indiegogo crowdfunding campaign to build a Rape Crisis Counseling mobile app. The resource will digitize the training that rape crisis counselors receive to become volunteer emergency room advocates for sexual violence survivors. A coalition of U.S. rape crisis centers, gender-based violence experts and women's rights defenders and non-profits are partnering with Code to adapt and create the content so that it's relevant and applicable for the international community. A network of experts and non-profits eager to use the free, Creative Commons resource in their own communities are ready to translate the content into Arabic, Farsi, French and Spanish. One of the crowdfunding campaign's perks is to allow a supporter to determine which language we add next.

"One in five women will be raped in her lifetime. That's more than 700 million women and girls. We're launching the campaign on V-Day to join our efforts with the global day of action to end violence against women. The Rape Crisis Counseling app will put advocacy resources directly into the hands of rape survivors, their family and friends, and would-be volunteers. Anyone who wants to be of service to survivors of sexual violence should have access to the information and training resources they need, wherever they are in the world," says Elie Calhoun, a Principal at Code Innovation.

Since the 1970's, rape crisis centers have provided advocacy and support services to survivors of sexual violence in their local communities. These non-profits train networks of volunteers to become Rape Crisis Counselors, who accompany sexual violence survivors through the process of getting life-saving emergency medical care, including services to prevent pregnancy, HIV and sexually-transmitted infections.

"Even in industrialized countries with well-resourced hospitals, a rape survivor isn't guaranteed to receive the medical care they need," says Calhoun. "In any context, health care providers can let their cultural beliefs and personal opinions about rape and sexual violence interfere. Even in the U.S., there are numerous cases of doctors and nurses being unwilling to provide full emergency services. This is why Rape Crisis Counselors are so important.”

"In other countries, health systems may be under-resourced and health care providers may be unaware or unable to provide a survivor with the services they need. In those cases, it's up to the survivor and whoever accompanies her to the health center to understand and advocate for her needs. Right now, there's no mobile resource that helps them do that,” says Calhoun.

Smartphone ownership and adoption is growing rapidly around the world. According to GSMA Intelligence’s most recent Global Inclusion report, “an additional 1.6 billion citizens worldwide will become mobile internet users over the next six years, bringing the total number of 3.8 billion, or around half of the world’s expected population in 2020.”

"We see smartphones as an essential tool to empower rape survivors, their family and friends, and the wider community to help ensure that survivors get the emergency health care they need,” says Calhoun. “Even if just one person in a community is able to access the Rape Crisis Counseling app in their language, they can share about the resources and help to educate others."

###

#rapecrisiscounseling

To support the campaign, visit: https://www.indiegogo.com/projects/rape-crisis-counseling-app/x/3176191#/story

For updates, visit: http://codeinnovation.com/blog/

About Code Innovation

Code Innovation digitizes and scales programs that help vulnerable populations. We create educational materials and social innovations that strengthen communities and enable them to lift themselves out of poverty. We've had projects in more than a dozen countries and specialize in challenging, low income environments. For more information about our work, visit http://www.codeinnovation.com.

For more information, please contact:

Elie Calhoun, Code Innovation, Tel. +62-812-3802-3425, email: elie@codeinnovation.com

 

Co-Creating a Free Rape Crisis Counseling App

Crowdfunding our Rape Crisis Counseling app for survivors of gender-based violence to receive emergency medical care (www.codeinnovation.com) An estimated one in three women is sexually assaulted over her lifetime. If the woman (or girl) is able to access emergency medical assistance with the support of a rape crisis counselor advocate, the chances of her healing increase exponentially. Without appropriate medical or psychological care, she is more likely to suffer from physical, mental and emotional after-effects that prolong her suffering and impact not just her own quality of life and productivity, but that of her family and community.

For over 40 years, rape crisis centers around the world have provided emergency room advocacy for survivors of sexual violence, ensuring that they receive appropriate treatment and care to begin the healing process. However, in low-resource environments and socio-cultural contexts where the seriousness sexual assault is minimized, survivors are often confronted with hostile or uninformed health care workers who may be unwilling or unable to provide the basic emergency services that help prevent pregnancy, STIs and HIV.

In these cases, which are by far the global majority of rape cases, a rape crisis advocate would make a significant difference in the survivor’s ability to secure adequate care while helping to mitigate the incidence of trauma.

Within the best medical systems, local rape crisis centers offer face-to-face training that prepares new crisis counselors for volunteer service in local hospitals. But in many countries and cities, these trainings are not available and advocates are not present.

We are digitizing the training curriculum of the Pittsburgh Action against Rape coalition and other U.S. rape crisis centers to create a free Rape Crisis Counseling mobile app that will make it easier for women around the world to get the support they require. The app will be released into the Creative Commons and include:

  1. M-learning Rape Crisis Counselor training material for anyone interested in learning the skills to be of volunteer service in their community;
  2. In-hand resources (a script, essentially) that enable a colleague, family member or friend to advocate for a survivor of sexual assault to emergency medical services;
  3. In-hand resources for a survivor herself, so that women without access to advocates can be as empowered as possible on their own.

We are partnering with U.S. rape crisis centers and coalitions to transform their rape crisis counseling training course into an m-learning resource. We also have approval from the U.S. Department of Justice to adapt and use their training resources.

Women’s rights associations and human rights defenders from around the world, as well as a network of aid worker survivors of sexual assault, will review the content for its appropriateness in a variety of challenging use cases and environments.

To date, no mobile resources exist that support survivors and their advocates as they access what can be life-saving medical care. We’re going to change that.

On Sunday 14 February, a global day of action to end violence against women, we’re launching a crowdfunding campaign to raise the funds to develop and translate the first Rape Crisis Counseling app for Android and iOS.

Join us in supporting rape survivors around the world on their road to recovery.

To get involved, email Elie Calhoun at elie@codeinnovation.com.

#rapecrisiscounseling

Design for Scale vs. Bootstrapping: Reflections on Digital Development Principal #3 (Design for Scale)

SHG-Joachim-Nasoni-Nguji-Village-Kongwa-District-Dodoma-Region-CCT-Tearfund-Tanzania-Code-Innovation.jpg

Tanzanian villagers with Self-Help Group facilitator and our savings and credit group Android mobile app (www.codeinnovation.com) We are eagerly anticipating the first time that Code Innovation receives the funding to design a technological tool that is optimized for scale from the moment of its official launch. Building for scale, as a fantasy, in my head, sounds something like this: We could incorporate a customized content management system that enables us to add new activities and modify our material painlessly in real time across a variety of languages. We could incorporate an unobtrusive yet unavoidable monitoring and evaluation protocol that feeds data into a back end that is easy to sort and clean, one that produces donor and media-relevant reports at the click of a button. We could bake in critical APKs for our social media strategy and optimize our design for the ten most common screen dimensions and the thirty most used Android devices—incorporating modular design elements to enable seamless re-branding that sweetens the deal for donors and partners hungry for visibility. We could have a big team, content gardeners, bug support in local languages . . .

Most of the innovations that we hear about in the ICT4D space do not enjoy circumstances like this. Instead, we are often bootstrapping minimum viable products through multiple too-brief program cycles each called a “pilot” phase—kicking down the road the choices about when to spend real money and hoping to transform our hacked together little tool into something robust and versatile enough to be picked up and used by the development community at large . . . and hoping, lastly, that this makes our code stylish and widespread enough to be maintained by the open source community out of love.

The Constraints of Scale with Limited Resources

Code Innovation is hitting an inflection point with one of our favorite projects that is forcing us to consider how to optimize our code for scale, but with highly limited resources. The project: an Android application that supports the facilitation of small groups that come together on a weekly basis, saving tiny sums of money, learning about businesses, starting businesses and then loaning to one another, thereby lifting one another out of poverty (take a peek at our free and open source Self-Help Group app here. Early versions of this application needed to function in Amharic and English. They needed to digitize about 70 pages of existing facilitator guides and meeting curricula and they needed to present these materials in an orderly, device-optimized way that technological novices could grasp after, at most, one quick training. Other requests piled on: social media component (sigh), interoperability with a pre-existing, ODK-based M&E app (gulp), report generating back end for funders and partners and so on and so forth.

But, at the beginning we had at most 30% of the money that it would cost to build a sufficiently rugged content app and it would mean contributing weeks of pro bono time to get our alpha version into the hands of vulnerable populations in Ethiopia. It didn’t feel like building for scale. It felt like proof of concept.

Then the usual thing happened: new partners came along with just enough money to add exactly what they want the most (a new language, perhaps, or some modules about disaster risk reduction); but not enough money to conduct a proper build. Not enough for us to build for scale. And sure, we apply a few times for large pots of Gates Foundation-type money, hoping to up-level our technology, to bring on new countries and hit our stride; but our reality continues to be bootstrapping from one version to the next, giving exceptional weight to the feature and content requests that come from whichever funder is willing to support our development next. There’s often a gentle tension between the requests of a short-term donor and the interests of our imagined, global, future customer base.

But suppose we have some promising leads? Suppose we allow ourselves to imagine building for scale just as a thought experiment? What would that look like? Or, more interestingly, what it would it look like if it were done in hefty stages rather than all at once? What if we had to prioritize the that would bring us to scale and scalability?

We admire all of the RapidSMS-based systems that our colleagues and friends have built and rolled-out through national ministries or with the paid-support of well-distributed program officers and we’re entirely aware of the benefits of short codes, dumb phones and standards. But our content and use case has driven us onto a more troublesome format (smartphones) and into an arena that is not as cut and dry or hierarchical and organized as Ministries of Health. In fact, the different partners who are most likely to adopt and scale our product do not agree about content or program models—quite apart from the fact that they often speak different languages.

So how do we articulate and prioritize the different investments into our content and technology that would help transform a narrow, bespoke application into a robust open source tool that is best in class?

Tanzanian women with Self-Help Group facilitator and our savings and credit group Android mobile app (www.codeinnovation.com)

Our primary considerations for taking an open source Android app to scale:

* Connectivity Management:

This isn’t a feature. It’s a constant high level development consideration until free Internet rains down from the heavens. Whenever we forget this variable, we open ourselves up to unnecessary failure. We need to ensure that our app respects the hyper-low and infrequent connectivity of our users by refusing to incorporate any commands or experiences that rely upon wifi or data signals. We must also anticipate database-device conflicts that result from infrequent connectivity, for instance groups naming themselves identically when offline that might become confused when they first connect. Building for low to zero connectivity is our primary constraint; it means we can’t rely on user logins or passwords, it complicates things and it makes it harder to use out-of-the-box chunks of open source code.

* Inbuilt Monitoring and Evaluation with administrative back end:

In early phases, it’s feasible to conduct monitoring and evaluation personally and to rely on Skype calls or emails as a fallback in case user information from the App is sparse or unreliable. But as we scale, our technology must gather and sort this information for us more dependably and we need to ensure that this information is visible and actionable for backend administrators who are not also our coders and developers.

* Support more Devices:

We will need to optimize our code for a growing number of devices and screen sizes. At first we could control what hardware was used with our product. But going to scale will mean the loss of this control and a bunch of design work will be required to keep content legible and navigation pathways obvious. We also have to set funds aside for keeping up with changes to the Android operating system. (For others operating in Africa, we’ve found that Tecno tablets are good for our purposes. They are widely available, robust and not big targets for theft. There are some quirks that make them a bit difficult to code for; but they’ve been hassle free in the field.) Sometimes affluent allies to our project bemoan the unavailability of our app on the Apple Store. The only justification we can see for coding this for iOS is that it might be useful for fundraising and visibility at some point when money is not an object.

* Social & Sharing:

Because we have partners who are committed to creating a social media component: we need to build out a way for groups to “share stories.” This will ultimately require an interface for reviewing, moderating and even editing the content that is uploaded to our system. (We also need to build out trainings for our end-users about the privacy considerations of sharing stories about themselves and their businesses.) We anticipate eventual requests for APKs with locally relevant social networks for cross-promoting stories and insights and can see the utility of this when begin to pursue unstructured growth amongst individual users.

* Solid Content Management System:

We will need a better content management system. Our current system was the cheapest and most familiar thing our developers could find; but it isn’t suitable for the use of our program officers because the interface requires use of html and is tiny and hard to search. Adding new languages and changing content should be easy enough in the future that relatively low-skilled, non-technical team members can do it. Our future CMS should also make it easy to change pop-ups, buttons and navigation prompts.

* Inbuilt bug Tracking:

Crash reports are great; but we need to adopt and move onto a formal issue-tracking system like Redmine and incorporate into the app some way for our users to let this system know when they encounter inclarities with content or problems with usability.

* Branching Curriculum:

Because we want to create one application that is sufficiently useful for a number of similar but different program models, we need to invest considerable time (and consensus building) into the maintenance of a one-size-fits all curriculum that will probably soon require a new user interface feature for when content branches. So, for example, the activities about supplying loans would have to branch to accommodate Islam’s prohibition of interest-charging or an activity about group milestones would have to split to address Volunteer Savings and Loans Association (VSLA) program models that pay-out from the communal kitty. The Self-Help Group model that inspired our work seems the most impactful of these initiatives and has drawn the attention and support of Melinda Gates. But it isn’t the most widespread model—in order to increase its reach, we’ll want to accommodate the needs and interests of closely aligned programs.

* New Content & Content Architecture:

We need to expand the scope and functionalities of our resources and supplementary materials. At the beginning it was fine to create a little directory of hard-to-see pdfs to satisfy an unanticipated partner request. But the quantity of high-quality material that we are now hosting deserves a whole ecosystem, complete with loads of new instructional language and the option for users to email themselves forms and templates that they find helpful.

* Finance Tracking:

Hovering in the future is the expectation that the app itself start to track the savings and money-usage of the groups, perhaps synching up with mobile money or sources of external capital. We’ve had good reason to postpone this so far; but it will be requested or required of us sooner or later. Here also we anticipate some healthy tension between a digital development principle six, which encourages us to use Open Data and principle eight which reminds us to address privacy and security concerns.

* Inbuilt Trainings:

To move away from conducting trainings during field visits, we should create some digital tutorials that help tech novices understand how to use the app—and these will have to be in a variety of languages, with a directory of audio files (optimally). From our point of view, the chief rationale for digitizing a successful development work initiative is to remove the cost of scale created by field visits, workshops and trainings. Where these Self-Help Groups are growing traditionally, organizations strain to raise funds for facilitators who require transport, accommodation, connectivity, benefits and so forth. So even though building dynamic trainings into an app can feel like an extravagance, it pales in comparison to the cost of field visits—especially from senior staff who command hefty day rates.

What We Have So Far

There’s more. But these represent some considerable investments of time and money. In an ideal scenario, we get a war chest and we build the seventh wonder of ICT4D in the next three months, our product wows our implementing partners who want it in the hands of ten thousand facilitators ASAP and program officers around the world begin inviting us to collaborate with their field workers.

But I suspect we’ll be juggling this list of priorities and I suspect we’ll be juggling them along with heavily-weighted surprise requests from partners that we can’t anticipate. For example, we’ll probably have to persuade a new partner that instead of paying us to adapt and incorporate new modules about their favorite Sustainable Development Goal, they should pay us to update our content management system. Or we’ll learn that they’re only interested in the possibility of upgrading our underlying code after they field-test a version of that has been slightly modified to include their urgent priorities. In such cases, the implementing organization may be building our app for scale within their ecosystem, even as, from a technical standpoint, they are encouraging us to make it less appropriate or robust for a wider, general scale up.

There are heuristics to help us make sensible decisions about what to develop when funds for tech improvement are scarce. Investing in structural or systemic modifications that facilitate additions of content and upgrades is better than making ad hoc additions and upgrades. From a programmatic standpoint, we need to prioritize helping our users with their primary duties before we create new ones for them (such as becoming story-tellers or youth journalists). We also must do what we can to assist with data gathering and monitoring and evaluation so as to capture, quantitatively, the results of our tinkering.

There’s often a slight tension with the Digital Development Principles, too, in the area of being collaborative. Because making the decisions that truly build a technology for scale can mean behaving inflexibly in the face of stakeholder and beneficiary requests. If we figure out any magic tricks, we’ll definitely let you know. Stay-tuned to our blog at Codeinnovation.com to follow the noble struggle between bootstrapping and building for scale!

Scaling Up our DIY Self-Help Group App with Partners in East Africa

2015-10-19-14.03.28.jpg

Community-savings-and-credit-group-rural-Tanzania-East-Africa-open-source-mobile-app-code-innovation In early 2015, Code Innovation and our partners at One Hen Inc. visited the implementing partners for our Self-Help Group app in Ethiopia and Tanzania. After a successful pilot in 2014, our plan was to scale up the use of the app by 1000% focusing on new users in food insecure areas of both countries.

We met with partners at Tearfund Ethiopia and with Tearfund Tanzania's local NGO implementers, the Christian Council of Tanzania (CCT) to decide on a viable plan for multiplying our impact and rolling out a new-and-improved iteration with content that we estimated would last for about six months worth of weekly Selp-Help Group meetings. According to our previous coordinator, during our 2014 pilot in Ethiopia this was about the time it took for new groups to raise enough capital and develop enough business acumen and group momentum to begin to give their first loans.

This is a write-up of how Phase 2 of the project went, in terms of fidelity to our plan and also around ICT4D best practices and lessons learned. Wherever possible, we'll tie what we're doing and learning into the Digital Principles because we're proud to be one of the endorsing organizations contributing to this emerging field of practice.

 

An Overview of our DIY Self-Help Group App

(If you're already familiar with our project, feel free to skip this section. You can also read more background here and here.)

For those of you new to the project, in 2013 we began working with the US non-profit One Hen Inc. to digitize and scale Tearfund Ethiopia's successful Self-Help Group model of savings and credit groups, themselves adapted from the model pioneered by Myrada in India. The groups have shown a cost-benefit ratio of approximately 1:100* with long-term and far-reaching social and economic impacts on members and their communities, lifting people out of poverty over time with very little outside support.

Working closely with Tearfund Ethopia, we adapted their Self-Help Group modular curriculum to a mobile interface on a free and open source Android app you can download from the Google Play store here -- although it's very much still in Beta for now. Over a 12-week pilot, we found that the facilitators thought the app was a useful professional tool and facilitation guide and that they'd already begun using it to start new Self-Help Groups not officially involved in our pilot.

 

Our Plan for Phase 2, a.k.a. How to Scale 1,000% in Six Months

rural-East-Africa-Tanzania-dry-season-food-insecurity-savings-credit-group-open-source-app-code-innovation

Based on the positive feedback we got from Self-Help Group facilitators, we sought to expand our reach in Ethiopia and begin working in a new country, Tanzania, with the same organizational partners. With DfID funding, we were able to focus on food insecure regions facing hunger because of the failure of the previous year's rains. Due to a poor harvest because of the drought, families and communities in these regions were considered particularly at risk for hazards related to food insecurity. Our partners selected the Humbo and Angacha regions in Ethiopia and Kongwa in the Dodoma region of Tanzania to scale-up our pilot with 25 new Savings and Credit Groups to be created in each country over six months of field implementation.

Because we were working in two districts in Ethiopia, and also to see if closer supervisory support would yield better weekly reporting data, we tried a new approach to coordination, appointing one District Coordinator for each area, supervised by a single Project Coordinator based in Addis Ababa. In addition to regular check-ins by email and phone, the Coordinator visited every other month in person to ensure the District Coordinators were feeling supported with the technology and the savings and credit group formation process.

In Ethiopia, we worked with experienced Self-Help Group facilitators working in new parts of the country starting groups of primarily young people out of school and over age 18. The focus on youth created some challenges because there was an assumption that young people did not have any source of income, although Tearfund's program model specifically addresses this assumption with a reframe of available local resources and close-to-home economic activities. Nonetheless, we did see below average group retention rates in Ethiopia because the SHG system itself was not established in the communities we selected and was, instead, fairly unknown. Accordingly, parents and youth members were quick to get discouraged and to discourage others from attending the groups. In the Nazaret region, where we first piloted, SHGs had been established for over a decade and belonging was considered to be admirable and beneficial, so this was our first time as a partnership facing a situation where people did not show up with motivation because of a favorable context. Also, in some cases youth decided to enroll in school or move to urban areas to look for work during the pilot program period, so SHG membership was more variable than is usual for Tearfund Ethiopia programs.

In Tanzania, our partners at CCT decided to work with entirely new and inexperienced facilitators in regions where Pamoja groups ("Pamoja" means "together" in Kiswahili and is CCT's name for our Savings and Credit Groups) had not yet been established. This created a number of early challenges that were evaluated to be worth the extra effort because of the acute community need for this kind of support system, given the hazards and risks members were facing around food insecurity and with the drought. It meant that our Coordinator spent half of his time directly working with and training facilitators on the mobile technology, app functionality and reporting protocols, but also that the gains that we saw over time there showed that the program can work in a new and extremely challenging use case.

Because we're still early in the app development and digitization process, we continued our system of weekly feedback from facilitators to get specific inputs on areas of the curriculum that worked well and that need expansion. This system continued to give us the real-time, actionable data that we need to make strong iterations between phases, and we anticipate continuing it in the future until we move out of Phase 2 (testing with new countries, partners and in new world regions). Phase 3 will happen when the app can be used by a new, inexperienced facilitator to successfully learn facilitation skills, recruit and start a group, and save and lend while building group ties over time. We have a ways to go, but we'll get there!

 

What Went Well in our Rapid Scale-Up

Tanzania-facilitators-mobile-app-open-source-code-innovation

We are happy to report that a number of key areas went extremely well. We're going to summarize them here, but do get in touch (info@codeinnovation.com) if you'd like to hear more details as we're keen to share what we know with our ICT4D community.

  • App Functionality and Usability: The app did not require repeated training for new facilitators to use, especially around the key curricular areas of meeting content.
  • Expanded Content around Case Studies, Games and Stories: We hoped to include content in the app that would take group members well into six months of weekly meetings, and we succeeded in doing that with our expanded curriculum around social business skills development, conflict resolution and disaster risk management/disaster risk reduction. Facilitators and group members enjoyed the illustrative content in particular, and over the course of Phase 2 we've collected a wealth of additional content to help us build out the curriculum further.
  • Facilitator Training: Our new module created a step-by-step training guide for new facilitators to learn basic skills, recruit group members and develop self-organized learning for their own professional development. We heard from facilitators throughout field implementation that it was an appreciated part of the content.
  • Facilitator Preparation: Before each module throughout the content, we expanded the information needed to prepare facilitators for their weekly meeting. We heard that this was an extensively used part of the app this time around and were requested to continue building it out as a resource for planning meetings.
  • Hardware: We selected locally-purchased Tecno tablets available for about $200 in Ethiopia per device and about $100 in Tanzania per device. The higher cost in Ethiopia is due to national taxes on ICT, as the tablets themselves were almost identical. Every device continues to function without damage at the time of writing, a testament to the care with which our facilitators treated them and also to the durability and appropriateness of the tablets themselves in rural East Africa.
  • Reporting and Supportive Supervision: Weekly reporting kept facilitators, coordinators and us in close contact to problem-solve proactively and ensure that our content and UI/UX was meeting their needs in running groups and also in their own professional support and development. In Tanzania, reports were sent via facilitators' Gmail accounts and our users created a What's App group on their own initiative to share success stories, keep in touch and help each other resolve group, tablet or meeting challenges.
  • Secondary Benefits of Accessible Mobile Technology: In most cases, facilitators used their tablets for professional and personal development, including engagement with LinkedIn, online news and Facebook social networking. In many cases, facilitators began to pass around the tablet during meetings so that members took turns facilitating the key discussion points during group meetings. In a few cases, facilitators made their tablets available to community and group members to access the internet, creating strong secondary benefits in areas that did not previously have easy access to mobile technology.

What We Learned for Future Partnerships

There were some key areas for lessons learned as well, detailed in brief here. Again, please do get in touch (info@codeinnovation.com) if you're keen to hear more about these, as we'd love it if no one in ICT4D ever made these same mistakes again!

  • Solar Chargers: In all cases where hardware is provided, we will be advising partners to purchase locally sourced solar chargers to enable the tablets to be charged directly by the facilitators whenever needed. Relying on local charging stations is both time-consuming and expensive, and could in the future be a source of low motivation to use the app.
  • App Updates: Because access to mobile data is so slow and wifi is often completely unavailable, we needed a new system to update new app versions so that facilitators would be sure to be using the latest app version. We are using our Coordinator's laptop and installing APKs directly onto tablets during field visits in the future. But this is a function of our beneficiaries being in unusually remote areas underserved by electric infrastructure. If we were targeting robust growth in an urban area, this recommendation would likely not apply.
  • New Group Formation: We had anticipated that 25 groups would be fairly easy to form over six months in each country, but in fact we will only reach our target in late 2015/early 2016. In Ethiopia, working in a region where SHGs were not known by the community made their establishment slower than anticipated. In Tanzania, new facilitators were only ready to create new groups after their existing ones had been established for about three months, so relying on facilitators to create multiple groups should anticipate some phasing delays. At the moment in Tanzania, new group creation is on hold because members would not have the income needed to contribute to savings, since it is the very end of the dry season and family resources are very scarce. A few weeks after the short rains begin (in December or January, we hope), members will once again have the financial resources and be able to begin group savings.
  • UI/UX and Usability Testing: Secondary app functionalities were not as easy for new users to navigate as the curricular modules, namely our Community (or social media) section and our group login system. Based on usability testing directly with facilitators in Tanzania, we have a great list of priority fixes in this area.
  • Multimedia When Possible: Adding photos and illustrations, especially for case studies, will help to make the content more personal and come alive for members and facilitators. It was a repeated ask from our group interviews and something we're looking into while keeping in mind that we don't want the app (already around 10MB) to become too heavy to download in low-bandwidth areas.

 

What our Self-Help Group App Group Members Had to Say about the Project and our Process

During a recent field visit to CCT's Pamoja Groups in Kongwa, Dodoma region in Tanzania, we were able to interview nine groups in four village areas.

In our Self-Help Group model, each group member contributes weekly through buying two types of shares, social shares and savings shares. Each week, each member contributes one share to the social fund, for use by group members in emergencies. In addition, they can buy savings shares at a minimum and maximum set by the group.

In all Pamoja groups, the social fund is repaid without interest and had minimum 1 share @ 500 Tsh contribution per week, slightly less than $0.25 at the time of our visit.

In Mautya Village in Kongwa District, Dodoma Region, participants reported:

  • "We are facing hunger in our families and communities because we are primarily agricultural and because of the lack of rains last year and the failure of our crops."
  • "We are using the social fund to buy food."
  • "Group social ties give us strength to face the challenges of the drought together. We do not feel alone."

In Nguji Village in Kongwa District, Dodoma Region, participants reported:

  • “We are facing hunger in our families and communities because we are agricultural and because of the lack of rains and the failure of crops.
  • "We are using the social fund to buy food and pay school fees."
  • "Because of the group, we are not facing too much hunger at the end of the dry season and we feel supported by each other."
  • "Belonging to the group helped to improve my existing business and my profits have increased."

One-third of the participants in Nguji owned their own mobile phones and 80% had their own businesses.

In Machenje Village in Kongwa District, Dodoma Region, participants reported:

  • "There is no rain, and everyone here are farmers. Bad harvest means hunger. Lack of rain increases the price of food."
  • "If I don’t have money, I can take a loan to invest in a business and use the profit to pay back the loan and buy food for my family."
  • "Our economy is so much affected by the drought because we depend on agriculture and there is no rain or harvest. It is difficult."
  • "Because I now have a small business, I can buy food and eat with my family."
  • "If someone is sick, a loan [from the social fund] can take them to hospital and pay for their immediate needs."
  • "If a group member has any emergency, anything in life, we can support them."
  • "These groups are good. We encourage anyone to join. However, know that if you take a loan, it can be challenging to pay it back so that another person is able to take a new loan."
  • "The community originally thought that these groups were a trick, but now that they've seen our success and the capital we've raised, they themselves want to join."
  • "I had a business before, but I was inexperienced. Belonging to the group helped to improve my business skills and share with others. Now, I am helping my family to have a good life."
  • "Belonging to the group has really helped my family. With a loan, I have been able to expand my tomato selling business."
  • "This is a bad year because of the lack of rain, so buying shares every week is difficult, especially now that it is dry season. My savings come from collecting firewood in the bush and selling it in the village."

30% of the group members had businesses before joining and 46% do now. 58% own their own mobile phones.

In Laikala Village in Kongwa District, Dodoma Region, participants reported:

  • "Life is difficult. I joined this group to get out of poverty."
  • "In most cases, we struggle to pay for school fees and because of the group, we make sure that we pay for all the school expenses."
  • "Using the tablet has introduced me to new things and ideas, and it is good for me."
  • "The social fund is for problems or unexpected disasters."
  • "Our group made an IGA whose profit goes back into the social fund, because we depend on it so heavily now. The IGA involves buying sugar and rice wholesale and each members sells some and returns with the profit."
  • "People should join groups because they are sustainable. Members are there for each other and will continue to be there to help each other."
  • "This community depends on agriculture. Without rain there is no food. We have hunger and no money to buy commodities. We are all affected."
  • "Without a good harvest, there is no money and without money, you cannot buy anything. There is no water for gardening."
  • "Without food at home, after a poor harvest, loans help our families to eat."
  • "With the problem of the lack of rain, most people are bankrupt so others can’t help, but the group can help, especially with a small business."
  • "I didn't have a business, but then I took a loan and now I have a profitable small restaurant."

13% of the group members had businesses before joining and 52% do now. 55% own their own mobile phones.

Next Steps for our DIY Self-Help Group App

We are in discussion with CCT, Tearfund Tanzania and Tearfund Ethiopia to continue to scale up with their new and existing Pamoja and SHG facilitators in the coming months and into 2016. In addition, we have a new partnership with World Vision Tanzania working with their Volunteer Savings and Loan Associations with groups in the Babati regional cluster (of Tanzania). Stay tuned for more developments early in the new year, when we'll be releasing a new-and-improved iteration based on what we learned during this Phase 2.

Our own goal at Code is to scale the Self-Help Group App impact to 1 million direct beneficiaries within three years. Because of the economic and social need, we hope to concentrate mostly in sub-Saharan Africa but it will depend where we find implementing partners and funding. Of course, as we iterate closer to a stand-alone app with full functionalities, , our own inputs for consecutive iterations will become less necessary.

We hope to find partners in all parts of the world, but in Africa in particular, who are interested in using our Self-Help Group app to train and support facilitators starting their own groups in their own communities, helping to empower people to create social and economic support systems that reduce their vulnerability to stresses, shocks and poverty.

Want to partner with us on this or other projects? Get in touch (info@codeinnovation.com)!

* Cabot Venton, C et al (2013). “Partnerships for Change: a cost benefit analysis of Self Help Groups in Ethiopia.” Tearfund, Teddington, UK.