Confessions of an ICT4D Advisor: I Hate Technology.
February 1, 2015 Editor 0
The jig is up: I hate technology.
I can’t tell you how many times I’ve cursed at an airline check-in kiosk because my battered passport won’t scan properly or the new “e-visa” system has frozen in the midst of processing my payment. I always cringe at new public-sector technology releases because they rarely meet stated aims. Which is a nice way of saying “they don’t work.” Case in point: Healthcare.gov.
Despite my job title, I don’t consider technology a close friend; rather, it’s a necessary acquaintance. I deleted Facebook in 2007, haven’t updated my Mac OS in at least a year and still mourn the loss of my Motorola Razr. Simply put, I’m much more Luddite than digital native.
So – why have I made a career promoting the use of technology within NGOs?
Because it’s not about the tech.
I’m just coming off a month of visiting field teams in northern Iraq and Syria, attending the Mobile Money Conference in Istanbul, meeting some of our most seasoned livelihoods staff based in Pakistan and bookending it all with an “Innovation Brief” at the UNOCHA Global Policy Forum. What was I doing the past 30 days? Watching and listening. No building, no solutioning, no piloting. Why? I have to build trust in people first to get to a point of even floating the idea of piloting something new.
Outside of supporting some basic mobile data-collection work, I’ve spent the majority of my short tenure at the IRC visiting country teams to build internal trust around programmatic concepts and pilots, for example, that may (or may not) heavily leverage technology. Time well spent? We’ll soon see. But at very least, I’ve been able to message to field teams that “the future is certain, give us time to work it out.”
Any role that attempts to evangelize information and communications technology (ICT) use within an NGO is about building trust with “users” (field staff, beneficiaries, etc.) first and foremost. Then, it becomes a game of filtering through the noise: deciphering software developer jargon, explaining technical design best practices, weeding through “social enterprise” salesmen and, ultimately, bridging stated wants with obvious needs. Then, we distill all of that insight into meaningful deliverables to experts (public or private) who can “build” solutions in the least operationally disruptive ways possible.
The blessed curse of pilots
At the moment, humanitarian response organizations are dabbling in a spectrum of ICT solutions that range from custom software-development projects to a swathe of deployments that leverage existing ICT products out of the box. Most of this work is still considered piloting — not scaling. Reading between the lines, it seems many organizations are still very much trying to understand what sustained user adoption for technological solutions actually entails. (Here’s a hint — it’s not about the tech.)
The blessing and curse of working in a sector where ICT work is still relatively new (when compared to say mobile health in the development sphere) is that while some program teams are keen to explore ways to leverage ICT, they struggle to figure out how to kickstart the ICT design process.
For example, who should they engage and what will it all entail? And perhaps most importantly, how can a non-technical person lead a conversation with seemingly technical experts in a way that results in the most relevant solutions for all? Thus, people get frustrated, can’t figure out how to operationalize ideas, or worse — get irrelevant, unsustainable solutions handed to them… which ultimately pushes people back into the “I hate technology” camp.
Solutions are everywhere
But maybe we’re looking for guidance on ICT adoption in the wrong places. I recently had a conversation with a team member from Jordan regarding a cash distribution program run by UNHCR. They chose to partner with a bank that already used ATM machines to take retinal eye scans to identify “clients” (instead of the traditional card + PIN system).
While I’m still getting warm to the idea of using retinal scans with traumatized displaced populations (it seems too Children of Men for me), I was fascinated by one comment she made: that throughout the Zaatari camp, the Arabic word for “iris scan” [basmat al-ain] has now become synonymous with “cash assistance.” How wild is that? UNHCR’s programmatic design choice to use a bank with fancy ATMs inadvertently forced a rapid adoption of new technology to the point that it changed local vocabulary. It’s the same way that we say we’re going to “Google” something rather than “search the interwebs.”
When I hear anecdotes like that, of affected populations rapidly integrating new technologies into their lives, and when I think back to field teams who are still skeptical of collecting data digitally, I realize there’s still hope… even for the haters.
Rosa Akbari is an advisor for information and communications technology for the International Rescue Committee and this post was originally published on the IRC’s Acting, Fast & Slow blog.
- Gender-Violence 2.0: The Digital Safety Gap for Women
- Mobiles for Development Partnerships are Still Hard!
- Technology View From Youth in Sierra Leone, Sweden, Indonesia and Uganda
- Learning is a Two-Way Street with Hack at Home by Innovate Salone
- Dear Sierra Leone, Liberia, and Benin: Have You Heard of Wikipedia?
- The economic cost of gender inequality
Subscribe to our stories
- The Partnership for Economic Policy Call for Project Proposals September 29, 2017
- 3 Uncommon Ways ICT Can Aid Delivery of High Impact Agricultural Research and Development September 29, 2017
- 20 Reasons You Should Integrate Tourism into Your Development Agenda September 29, 2017
- How Mobile Applications are Documenting Property Rights in Zambia September 29, 2017
- Which African Governments Spy on Technology Users the Most? September 29, 2017