This post also appears on Disruptive Witness.
Citizen feedback on development and aid projects has been a kind of “holy grail” for aid for a few years now. The latest discussion comes in a recent blog post, “Consumer Reports for Aid“, by Dennis Whittle of the Center for Global Development. This is one of my very favorite topics, too. And, I eagerly sought the same kind of thing in 2009 when we began working in the Kibera community.
When we tried to activate a citizen feedback loop in Kibera with Map Kibera, we thought that having a communication mechanism for residents to post comments about aid projects on the ground could revolutionize the way not only NGOs practiced, but the way the community viewed and took ownership over development. On Yelp, if I leave feedback, either positive or negative, I feel more connected to the businesses in my community and helping them succeed, fail or improve. In short, I feel a subtle sense of ownership. If the local NGOs and projects in a place like Kibera could be put online and rated by citizens, or various services commented upon in a detailed way, then maybe we’d have some real and meaningful feedback. USAID and big donors would respond to that, not to some puffed up self-reporting.
In fact, when we launched Voice of Kibera, that was one of the first ideas we had about what it might become. It wouldn’t necessarily be the news reporting site we have now; maybe it would allow people to mark services and organizations and comment on them.
It’s clear to me now why that didn’t happen – though, as you’ll see, we’re still working on the broader goal.
1) It’s hard to overestimate the complexity of a neighborhood of some 200,000 citizens, several tribes, a variety of languages, and little government whatsoever, that has existed in spite of the government’s desire to wipe it out and whose often transient residents have to struggle every day to make a living. I’m talking about one place, but I might be referring to many urban informal or extremely poor neighborhoods in the world which are the target of large amounts of aid dollars. There is a way things get done, and a reason why they get done that way – an entrenched system in which both the aid donors, government, and local actors play a role. People are very sensitive to the micropolitics that could impact their lives much more seriously than in wealthier environments. Offending the wrong person, or pleasing the right one is an important determinant of success.
Being in the business of engaging people, soliciting and publicizing their honest and informed views, and getting accurate data out there is a big job, and in my view far too little attention is being focused by techies or donors on the community side of this equation. Ultimately that’s what Map Kibera seeks to do, but it takes a lot more than setting up a web platform.
In this context, the role of a trusted representative is very important – who represents local opinion? Is it just whoever gets on Twitter while their neighbors still don’t have a mobile phone? In our excitement over technology there are always those who figure this out and can then hijack the process. System gaming problem? Not solved.
2) International aid is a mainstay of the Kibera and many other poor communities’ economies. This is what the international aid juggernaut has wrought. Yes, most Kiberans work outside of the aid industry and its various projects, but were you to do a critical analysis of the local economy and jobs, you would find that NGO jobs are the best paid and most stable, and come with a reputation upgrade, while “appreciations” – a soda at the end of a meeting, or a bit of airtime, cash or t-shirts – will be given out to a myriad of community members who attend any sort of event or meeting. Therefore, how do you build loyalty and good ratings on your Development Yelp? By intelligently executing a project that everyone relies upon day to day, that has impact, and legitimate sustainability (meaning the NGO jobs “should” be phased out eventually)? Or by winning a popularity contest by fitting the expectations for other perks? It’s a lot easier to do the latter. The incentives and potential rewards for supporting a claim that an NGO is doing great work are very high. Saying something negative can get you in trouble. We’re talking about tight-knit communities here. Why spend time giving critical feedback when it’s potentially going to get you in trouble?
3) In fact, why spend time giving feedback at all? Time and energy are very precious resources when you live in a place where parents are forced to leave small children to play unsupervised all day because they need to work and can’t pay for daycare. You’ll need to distribute some appreciation to get participation, unless participants are using a system for rating large-donor projects they’ve been beneficiaries of (see Danish Refugee Council example below), in which case much of the feedback might be in the form of calling out the continuing need for more assistance.
4) Many might respond that anonymizing this information will solve some of the problems I’ve mentioned. That’s essentially the route that Global Giving went with most of the stories on its Storytelling platform. But in that case, you don’t have very detailed knowledge about specific interventions or programs, which to me is the ultimate goal. Also, in most instances, asking for anonymous information from people is perhaps the purest yet least effective method of crowdsourcing. Anonymous inputs means you cannot hold people accountable for false information, and also removes a key incentive – to have an online presence and visibility. Even with Yelp, that’s clearly a motivator – a little bit of egotism.
So how do you make visible the inherent knowledge in a community of what works and what doesn’t? Certainly every Kibera resident has a lot of valuable knowledge, that, for instance, the vaunted bio-toilet is just stinking up the corner and no one’s using its supposed cooking gas. There is indeed a desire in Kibera, at least, to weed out the unproductive and even fake “briefcase” or “ghost” organizations that are supposed to reside there, but which aren’t in evidence on the ground, which means there is some latent incentive to provide data.
That’s why we hope our teams on the ground at Map Kibera and others like them will become the trusted informational resource for the community and will do a kind of due diligence on the local organizations and projects. In fact, this is a standard role that journalists play in a community – accountability and investigation. New kinds of citizen journalists and information centers can fill this role in places where there is limited news coverage. These informants aren’t anonymous at all – but they are protected by association with a network and local reputation.
In fact, an idea the Map Kibera team had was to create a directory of organizations and projects in the area where each group could have a page explaining what they do. The neutral nature of this project would invite in organizations in order to allow people to know who’s doing what where, and basic transparency would be built in. It would also help those tiny initiatives of regular community members – the orphanages, day cares, and youth groups – without much money or tech savvy to have some visibility and essentially prove their value. Mikel and I worked on this a little bit in a different format with Grassroots Jerusalem at www.grassrootsalquds.net. We are still seeking funding to finish this platform and establish it in Nairobi. Once that’s done, I think we can rely on our dedicated team to fact-check reports and post about various initiatives, and because they’re trusted members of the community, they can retrieve detailed opinions of citizens, both positive and negative and quote them on the site.
There is another way this could all work, which is to create a loop about government and large donor projects (those less likely to have a presence in the community) or simply highlight needs that require attention locally. This is more akin to the FixMyStreet concept, calling out local issues which have no project yet attached in hopes of triggering government or other support. We’ve tried to do this in Tandale, a slum in Dar es Salaam. There, we trained a team of reporters who’ve mapped the area and now post blog reports about conditions in the slum. See http://tandale.ramanitanzania.org/blog/. In this case, the loop has so far failed to close on the government or other responder’s side, in spite of initial promise. Here is where an influential third party can play an important role, such as the World Bank or UN.
I also found interesting this example of the Danish Refugee Council trying to solicit feedback on its work, which might not be a model to copy but gives a pretty accurate picture of what types of complaints a system might field. This is what a loop would often amount to: “We are requesting for power to charge our mobile phones, in order to reduce the challenges about the power and sent more SMS feedback.” Response: “According to your prioritization, DRC doesn’t provide electricity to any community.” Basically, that’s a no. I’m not sure that gets us much further, yet, than fielding such requests for more assistance. But, it does make public a normally very private exchange between donors and beneficiaries, when they are in that traditional relationship common to development schemes. I think this is a step in the right direction, because the more we open up these processes the more likely they will be open for questioning and productive critique.
The fact is that every “complaint” about “service delivery” is actually a citizen claiming a right – clean water, for instance – often in a place where there is no easy solution and there is a systemic and ultimately, political reason why neither NGOs nor government have yet to provide for such needs. Usually, that reason has little to do with the government (or big NGO/World Bank/UN etc) not knowing that the problem exists, sometimes in great detail.
The more that trustworthy community information representatives can detail and report and map and publicize and pressure and comment – and, do real journalism about – about the particular issue, the more likely that some downward accountability will be injected into the system. It’s also more likely that community members will begin to understand the forces at work in their neighborhoods and analyze what’s happening around them. It’s hard to imagine an information asymmetry as critical to address as that between residents of poor communities and major players in the development and government arenas, the 6 foot view vs the 30,000 foot.
When the community of Tandale mapped itself in OpenStreetMap, they opened their community’s data to the creativity of the entire web. This visualization from our friends at Development Seed shows the dramatic before and after mapping in Tandale, with bright cartography and integrated Ushahidi reports. Hope this sparks more ideas for Tandale and other communities around the globe just now adding their voice to the web. Maya posted the details on how they put the map together.
Check it out at explore.ramanitanzania.org.
Recently finished a technical review of WWF’s Moabi platform, their geodata sharing platform to track deforestation, and came out with some important technical challenges for the GeoWeb I want to share with the mapping nerds.
Post continues on Brain Off
The keystone to GroundTruth’s trip to India was the Cartonama workshop in Bangalore.
My comrade in maps was the amazing Schuyler Erle, in a reprise of our epic 2008 Free Map India tour. India, Banalore, and its OpenStreetMap have transformed (as you can see in this heart-filled animation of OSM Bangalore). This time, rather than visit 7 cities in 4 weeks, we crammed even more information into two days. As ever, I learned a ton from Schuyler. Perhaps the choicest bit being, “Canada is often projected as if the Earth was wearing a dunce cap”.
This was an intense two day workshop, covering everything needed to make an open web mapping application: from data collection in OpenStreetMap, to data juggling with OGR/PostGIS etc, making tiles with TileMill, and finally building an Ajax Web app with Leaflet and the OSM API. Oh, and also a survey of basic geographic concepts (geodesy, projections, etc), and the intricacies of the operation of GPS satellites. Really it was four workshops in one. Or maybe 10. Possibly a semesters worth. I think it’s a format worth replicating.
The end result was a modification to the amazing POSM POSM by Yuvi Panda. He built this HTML5 web app for first collecting bus stops in Mumbai. There were wonderful audible gasps when we integrated our home baked MapBox tiles into the locally running POSM app (even if we discovered lingering problems with handling of Indic fonts in Mapnik).
Cartonama was an Editor’s Pick in TimeOut!
Another great moment, during the ice breaker we stole from Gunner: “What’s your first memory of a computer?” “We had to take our shoes off before going in the lab because computers are holy, right?”
HasGeek did a wonderful job bringing bringing the workshop together, and are lighting up the geek event space in India. They’re really fostering community in the best way, and I’m excited to see what happens with all the mappers from our workshop, and the upcoming full Cartonama conference. So big thanks to HasGeek, and the Centre for Internet and Society for hosting and sponsoring the workshop.
I wanted to experiment with the new HOT Tasking Server, so I set up a task using the Swaziland GPS tiles, but I didn’t bother to promote the effort at all. One month later, and the task is 100% complete, and about 25% verified. Amazing work by the community, and a quickly proven, easy to use, compelling tool.
Here’s Mbabane, the capital of Swaziland, before the editing.
And here are the GPS traces of Mbabane, today.
And finally, the map today.
New roads have been filled in throughout the country. It would be interesting to calculate the growth in road features over this month.
There are still lots to do. There are gaps in the GPS coverage, and Bing might help. This was only roads, and unnamed, unclassified roads at that. It’s really now up to the small and growing community of mappers in Swaziland to bring the map alive.
I asked some of the incredible top contributors about why they took part in the mapping, and how the tasking server helped out.
The tasking tool is really nice to keep the motivation up and to keep track of what’s already done. You see the progress and the small chunks are mostly manageable.
It is good for my inner self. It is rewarding on both a greater scale (creating a needed map) as well as a smaller scale. Also, I find tracing a very relaxing activity that leaves my analytical programmer’s mind open for podcasting, talking or just recuperating from the day.
It was a chance to contribute to a very underdeveloped part of the map and make a real difference to what was available in that country. This is also a country that would take a long time to reach a critical mass of roads without outside work. Hopefully this will give a base for people when they look at a rendered map, which in turn might encourage other people in/near Swaziland to fill in the gaps.
I like mapping because you get to look at somewhere in more detail than you normally would. I now have a real feeling for the geography of Swaziland.
I’ve been interested in HOT for a while and participate when I can, but it’s not always clear how to contribute. The task manager made that easy. To the larger question of why do this at all: it’s like knitting a sweater for millions of people at once.
I think it’s important to get the tile size right. For the Swaziland tracing, it was perfect. I peeked at another task (tracing buildings in Indonesia) and a single tile was too overwhelming.
stethoscope’s insight on the right tile size was among many great points of feedback. We’re learning lots about how to improve the experience of the tasking server even more, that’s getting captured in issue requests, and Pierre continues to push development.
It was after Haiti that this idea began brewing, with identified need for “Mechanical turk style process for working through and importing individual features from large imports” and “Tools for ongoing coordination and identifying needs, addressing the problem of what to map now?”. And really, it goes back to the search for Jim Gray. At my talk at Microsoft last weekend, I was fortunate enough to meet some of the team who worked on the first mechanical turk process for collaborative imagery interpretation … the inspiration has results!