Feeds:
Posts
Comments

Posts Tagged ‘design’

As the world became more digital in the wake of COVID-19, the number of mobile applications and online services and support increased exponentially. Many of these apps offer important support to people who live and move in contexts where they are at risk. Digital apps for sensitive services (such as mental health, reproductive health, shelter and support for gender-based violence, and safe spaces for LGBTQI+ communities) can expose people to harm at the family, peer, and wider societal level if not designed carefully. This harm can be severe – for example, detention or death. Though people who habitually face risk have their own coping mechanisms, those designing digital apps and services also have a responsibility to mitigate harm.

At our March 8 Technology Salon NYC (hosted at Thoughtworks), we discussed how to create safe, private digital solutions for sensitive services. Joining were Gerda Binder, UNICEF’s Oky Period Tracker App for Girls; Jonathan McKay, SameSame Collective; Stephanie Mikkelson, United Nations Population Fund; Tania Lee, Trestle, Jane Piercy, Reproductive Equity Now Foundation; and 25 others, making for a rich discussion on this critical topic!

Key Takeaways from the conversation

1. Do constant threat modeling. Threat modeling needs to include a wide range of potential challenges including mis- and disinformation, hostile family and community members, shifting legal landscapes, and law enforcement tactics. The latter are especially important if you are working in environments where people are being persecuted by government. Roughly 70 countries criminalize consensual same-sex activities and some forms of gender expression, most in Sub-Saharan Africa, for example. The US is placing ever greater legal restrictions on gender expression and identity and on reproductive rights, and laws differ from state-to-state, making the legal landscape highly complex. Hate groups are organizing online to perpetrate violence against women, girls and LGBTQI+ people in many other parts of the world as well. In Egypt, police have used the dating app Grindr to entrap, arrest and prosecute gay men. Similar tactics were used in the US to identify and ‘out’ gay priests. Since political and social contexts and the tactics of those who want to do harm change rapidly, ongoing threat modeling is critical. Your threat models will look different in each context and for each digital app.

2. Involve communities and other stakeholders and experts. Co-creation processes are vital for identifying what to design as well as how to design for safety and privacy. By working together with communities, you will have a much better idea of what they need and want, the various challenges they face to access and use a digital tool, and the kinds of risks and harms that need to be reduced through design and during implementation. For example, a lot of apps have emergency buttons designed to protect women, one Salon participant explained. These often alert the police, however that might absolutely be the wrong choice. “Women will tell you about their experiences with police as perpetrators of gender-based violence” (GBV). It’s important to hire tech designers who identify with the groups you are designing for/with. Subject matter experts are key stakeholders, too. There are decades of experience working with groups who are at risk, so don’t re-invent the wheel. Standards exist for how to work on themes like GBV, data protection, and other aspects of safe design of apps and digital services – use them!

3. Collect as little data as possible. Despite the value of data in measuring impact and use and helping to adapt interventions to meet the needs of the target population, collection of personal and sensitive data is extremely dangerous for people using these apps and for organizations providing the services. Data collected from individuals who explicitly or implicitly admit to same-sex activities or gender non-conforming behavior could, in theory, be used by their family and community as evidence in their persecution. Similarly, sexual activity and fertility data tracked in a period tracker could be used to ‘prove’ that a girl or woman is/was fertile or infertile, had sex, miscarried, or aborted — all of which can be a risk depending on the family, social, or legal context. Communication on sensitive topics increases the risk of prosecution because email, web searches, social media posts, text messages, voice messages, call logs, and anything that can be found on a phone or computer can be used as evidence. If a digital app or service can function without collecting data, then it should! For example, it’s not necessary to collect a person’s data to provide them with legal advice or to allow them to track their period.

4. Be thoughtful about where data is stored. When using third party apps to help manage a digital solution, it’s important to know exactly what data is stored, whether the data can be deleted, and whether it can be subpoenaed. Also consider that if an app or third-party data processor is sold to another company, the data they store will likely be sold along with the app, and the policies related to data might change.

While sometimes it is safer to store data on an individual’s device, in other cases it might be safer for data to live in the cloud and/or in different country. This will depend on the threat landscape and actors. You’ll want to also review data privacy regulations for the countries where you are based, where the data is stored, and where your target end users live. All of these regulations may need to be complied with depending on where data is collected, processed, and stored. Some countries have “data sovereignty laws” that dictate that data must reside in the country where it was collected. Some governments have even drafted laws that require government to have access to this data. Others have so-called “hostage” laws that require that digital platforms maintain at least one employee in the country. These employees have been harassed by governments who push them to comply with certain types of censorship or surrender data from their digital platforms. If government is your main threat actor, you might need to decide whether non-compliance with data laws is a risk that you are willing to take.

5. Improve consent processes and transparency. Consent cannot be conceived as a one-time, one-off process, because circumstances change and so does consent. Generally digital platforms do a terrible job at telling people about what happens to their data and informing them of the possible risks to their privacy and safety. It’s complicated to explain where data goes and what happens to it, but we all need to do better with consent and transparency. Engaging people who will use your app in designing a good process is one way to help develop easy to understand language and explanations.

6. Help people protect themselves. Add content to your website, app, or bot that helps people learn how to adjust their privacy settings and understand the risks of using your service and how to protect themselves while doing so. Some features that were mentioned by Salon participants include those that allow people to disguise the apps they are using, quickly delete their data and/or the app itself, mask or ‘forget’ phone numbers so that the number won’t appear in the contact list and so that text message content won’t repopulate if the number is used again to send a text, and using different phone numbers for the organization’s website and for outreach so that the numbers are harder to trace back to the organization or a service.

7. Plan for the end of your project and/or funding. It’s important to plan for how you will safely delete all your data and any data held by third parties at the end of your funding cycle if the app or service is discontinued. In addition, you’ll need to think about what happens to the people who relied on your service. Will you leave them high and dry? Some organizations think of this as an “off ramp” and recommend that you plan for the end of the effort from the very beginning.

8. Take care of your staff. Ensure that you have enough staff capacity to respond to any incoming requests or needs of the people your service targets. Additionally, keep staff safe from harm. Countries, like Hungary, Russia and Indonesia have laws that make the provision of educational material related to LGBTQI+ identities challenging, especially to minors. Similarly, some countries and some US states prohibit any type of counseling related to abortion or gender affirmative care. This poses a risk to organizations who establish legal entities and employ people in these countries and states and to their staff. It’s critical to ensure that you have enough resources to keep staff safe. You will also want to be sure to provide support for them to avoid high levels of burn out and to deal with any vicarious trauma. Keeping staff safe and healthy is not only good for them, but also for your service because better morale will mean higher quality support services.

9. Accept that there will be trade-offs. Password protected apps are more secure, but they can pose higher barriers to use because they introduce friction. If your app doesn’t collect personal data it will be safer, but it will be more difficult to offer a password reset or recovery options, which is a usability challenge, especially in places where people have lower literacy and less experience using apps and passwords. When data is stored locally, it’s less susceptible to large scale data mining, however it might be more at risk of a family member or law enforcement forcing the data to be shared, and if a device is lost or broken, the data will be lost.

Large platforms may be more prone to commercial privacy risks, yet in some ways they provide greater data security. As one person said, “We decided to just go with WhatsApp because we could never develop a platform as secure as theirs – we simply don’t have the engineering power that they do.” Another person mentioned that they offer a Signal option (which is encrypted) for private messaging but that many people do not use Signal and prefer to communicate through platforms they already use. These more popular platforms are less secure, so the organization had to find other ways to set protective parameters for people who use them. Some organizations have decided that, despite the legal challenges it might bring, they simply will not hand over data to law enforcement. To prevent this situation from happening, they have only set up legal entities in countries where human rights protections for the populations they serve are strong. You’ll want to carefully discuss all these different privacy and usability choices, including with potential end users, to come to the best decision for each app or service.

Additional resources on this topic include:

Technology Salons run under Chatham House Rule, so no attribution has been made in this post. If you’d like to join us for a Salon, sign up here. If you’d like to suggest a topic or provide funding support to Salons in NYC please get in touch!

Read Full Post »

Verone Mankou of VMK with Senam Beheton of EtriLabs, who organized Verone's US trip.

Verone Mankou of VMK with Senam Beheton of EtriLabs, who organized Verone’s US trip.

We switched things up a little for our May 21 Technology Salon and had an evening event with Verone Mankou, the head of VMK, a company in Congo Brazzaville that designs and produces the Way-C Tablet and the Elikia smart phone. The event was graciously hosted by ThoughtWorks, and Verone’s US trip was organized by Senam Beheton of EtriLabs.

Verone told his story of starting the first African company to make mobile devices. In 2006, he said, the cheapest computer in Congo cost $1000 USD, and the cheapest Internet package was priced around $1000 per month. Verone worked in the tech industry and wondered why there was no computer or Internet that could be reasonably accessed by people in Congo. Everyone laughed and said he was young, fresh out of school, and that within 2 years he would understand the business and stop dreaming.

Verone persisted with his idea that computers and the Internet were not just for people in offices with suits. Everyone wanted to access Internet, he believed, but they just didn’t have the money. So in 2006, he started working on ideas for a laptop. After 6 months he concluded that it was impossible. To create a laptop you need a lot of money for research and development, and, unfortunately, his bank account only contained about $100 USD. He had no contacts with suppliers. Verone had a big dream but problems executing it, so he put the laptop project on hold.

In June 2007, a friend told him to hurry up and turn on the news. Steve Jobs was presenting the iPhone. “This is what I want to do,” Verone thought. “Make a big iPhone.” He felt keyboards were a deterrent for most people who were new to a computer, and that “a big iPhone” would be a solution. He started working on the idea of a tablet. It was difficult to find any suppliers on the African continent – no CPU factory, no battery factory. He could not find hardware engineers because in Congo there is no engineering high school. He realized he needed to go outside, to Asia. He made a first trip to China in 2007 and learned many things. By 2009 he had a plan, an Android system, and a finished project.

The next problem, however, was that he had no money for mass production. “In Congo we don’t have venture capitalists. Also as a youth, you cannot get any money. You will have a bad experience if you go to the bank to ask. People will tell you to start a hotel and not to waste your money on something different.” Verone did not go quiet when he could not find capital, however. He kept looking.

Meanwhile, Steve Jobs presented a new device: a big iPhone – otherwise known as the iPad. Verone was disappointed that Jobs had moved more quickly than he could with his tablet launch. On the other hand, everyone suddenly understood Verone’s project.

His miracle came a few months later when a minister from Congo was on a plane from Brazzaville to Singapore and came across a magazine article talking about a boy in Congo making a tablet. The minister could not believe someone in his country was doing this and he did not know about it. He contacted Verone and asked how he could help. Verone asked for $200k USD and gave the minister a prototype. Within 2 hours, the minister secured the funding and Verone was able to begin manufacturing.

He had enough funds to do a mass prototype of 1000 tablets and imagined that he could sell them in 3 months if they were marketed well. There was a buzz around the tablets, however, and they sold out in 1 week and he increased production to 10,000. Compared to the cost of an iPad in Congo (around $1500), Verone’s tablet was going for $200-300. He set his sights on making a good quality, low-cost smart phone.

Good quality is key for Verone. “Why do Samsung and Nokia come to Africa and think Africans need cheap, low quality devices?” As an African, Verone felt uniquely placed to create something for the continent – something cheap but good quality. He did this by eliminating unnecessary features and keeping only the necessary elements.

Next he needed to ensure that there was good content and an opportunity for monetization. Africans needed applications and content for their own purposes and context, he felt. Not maps of pharmacies in New York City. However most Africans do not have credit cards, so another way to pay for content and applications was needed. VMK created a marketplace for Africans that used scratch cards for payment, since everyone understands how scratch cards work.

VMK launched their smart phone in December of last year and  plans to sell 50K units in Congo Brazzaville. The company is also working on a cheaper phone with lower capacity that should run about $50 USD. In addition, they are working on identifying content partners and launching an “updateable school book” that would be accessible also at around $50 USD, so that students and teachers are not using outdated text books, which stunt the development of African children’s minds.  Verone’s vision is to give people access to good quality technology at a good price.

How will VMK compete with Chinese products as prices continue to go down over the next 10 years? “We will learn fast,” Verone says. “We will not sit while others advance.” He believes that expanding to African countries and developing the industry there will be good for the continent, good for developers and good for business. It’s not yet possible to do mass production in Africa because of poor education and lack of / high cost of Internet. People still cannot easily access relevant and updated information. But Internet is getting cheaper, access is improving and things are changing. People are starting to understand the importance of education. VMK currently has teams working in China and India, but they hope to move these functions to Africa as soon as possible. VMK plans to train staff up, offer internships and to get African youth skilled up in order to do this work.

The important thing is not to sit still, Verone says. “We can’t just keep waiting for things to change. We need to change them ourselves.”

Read Full Post »

There are a lot of great ideas floating around about how Information and Communications Technology (ICTs) and technology in general can help to rebuild Haiti.  I hope these ideas keep coming.  I would love to see international development organizations, aid agencies and non-profits in general open up more to ideas on how technology can improve the lives of the people they are trying to support as well as facilitate coordination and program implementation.

But I also hope that the technology folks who haven’t worked in a crisis context such as that in Haiti will lend an ear to those who have experience working in past disasters and on-going development programs, human rights work, volunteer initiatives and advocacy. Those experiences shouldn’t be tossed out as old-school.  Good programs and experiences exist that can be examined, processed and built on.

I work globally, with one foot in community development and the other in ICTs, and I notice a gap between these 2 sectors, though they could really learn a lot from each other and work nicely together.

Cool technology ideas, just like cool program ideas can flop on the ground if the local culture and context are not taken into consideration, users were not involved or consulted during design and testing, the supposed ‘problem’ really wasn’t a problem at all, the proposed idea is not sustainable, a better/preferred local solution already exists, etc., etc.

Sometimes when I hear enthusiastic people sharing ideas for new applications, innovations or program ideas that they want to implement in ‘developing’ countries, I find myself thinking:  “Wow.  They have no idea what it’s like on the ground.”  I don’t want to shoot down someone’s excitement.  But I do wish that those who are not intimately familiar with their end users would slow down, think for a minute, and realize that local context is king. I wish they would remember that ultimately this is not about them and their ideas for other people. I wish they would stop being mad that abc organization won’t take that shipment of xyz technology that they want to send over, or that no one wants to implement such and such program that was so successful in such and such place.  Solutions looking for problems are not the best way to go about things, even when you have the very best of intentions.

However, non-profit organizations (large and small)  can be totally resistant to trying new tools, technologies and programs that could make a huge difference in their effectiveness, impact and quality of programming. They can be bureaucratic and slow to put new ideas to work.  They can be risk averse, afraid of failure, and resistant to innovation and new ideas.  The seemingly limitless relationships that need to be negotiated around can really slow things down.

Sometimes I see non-profits doing things they way they’ve always been done and I find myself thinking “Wow.  I wish they’d be open to trying ________.” I wish organizations would be more willing to test out new technologies and new ideas that don’t come from within their sector. I wish it were easier to make change happen.

When it comes to the Haiti earthquake response, the technology and non-profit sectors are 2 of the key players.  I’m worried that the outpouring of interest in helping will lead to a lot of wheel re-inventing.  I’m worried about local relevance and executability (if that’s even a word) of some of the ideas I am seeing.  I have concerns about the amount of projects being conceived and designed from afar.  I also see that there are new program and technology ideas out there that have the potential to make people’s lives easier if they were well integrated into the local reality, yet there are many factors that prohibit and inhibit organizations from exploring them or using them.

The technology and non-profit sectors benefit quite a lot from each other when they work together and understand each other.  It would be great to see a bigger effort to bridge the gap between these sectors.  Regardless of whether people believe NGOs and/or private enterprises and/or technologists or the Haitian government or the UN are good or bad, there are a lot of experiences that can be learned from and/or improved on from all sides.

The links below might be helpful for thinking about designing technology, ICT and programs in ‘developing’ country contexts and to help avoid known pitfalls and overcome obstacles. They can help reduce the amount of time and other resources wasted on projects that are not sustainable or impactful, or at worst are actually harmful in the short or long term to the very people that we all want to support and help.  There are certainly many more resources out there… please add ones that you find helpful in the comments section.

ICT Works and The 4 C’s of ICT Deployment

Mobiles for Development Guide by Hannah Beardon

IDEO Human Centered Design Toolkit

Changemakers and Kiwanja collaboration: SMS How To Guide

Mobile Active‘s case studies

ML4D:  Mobile learning for development’s design narratives

Ushahidi Blog: February Archives have a lot of information on the Haiti response

iRevolution: thought provoking posts on technology and crisis situations

Educational Technology Debate:  Sustaining, rather than sustainable ICT4E and Designing and sustaining a sustainable ICT4E initiative

Posts on Wait… What? that might be useful:

7 (or more) questions to ask before adding ICTs

Finding some ICT answers in Benin

Meeting in the Middle: A good local process

It’s all part of the ICT jigsaw

I and C and then T

Read Full Post »