This is a guest post by Paul Goodman, who is spending the month of May supporting Plan Benin’s Violence against Children (VAC) prevention and response project. The post appears on Paul’s own blog and also on Plan USA’s blog.
I’m working with Plan Benin to support the Violence Against Children project. The team here has established a system whereby victims of violence and observers of violence can send text messages to Plan to report violence in their communities. Plan then processes and maps the messages and works with the government of Benin to investigate the cases. In about a year of operation the system has received more than 80 reports of violence against children. The reports include physical violence, sexual violence, psychological violence, and other abuses including kidnapping, negligence, and so on.
At the beginning of the year the team identified a number of technical challenges that they’re facing using the system, which rests on the foundation of two stellar open source technologies FrontlineSMS and Ushahidi. Those technologies are the focus of my time here in Benin though along with everything else in life, nothing is black and white.
“Technical” issues are often social, social issues often have no technical remedies, and things become confused. Beyond the division of technical and social, there are many other factors to consider. Thorough problem definition and planning for the short, mid, and long term are necessary to help define expectations, support project evaluation, and improve the chances of sustainability. These themes should be revisited periodically and updated as necessary.
In recent months Plan Benin lost two staff that were key to the day-to-day management of the system. Their departure temporarily disrupted the flow of information through the system but also created an opportunity: with a renewed organizational focus on the system we have an excellent opportunity to revisit the purpose of the initiative, consider the day-to-day functionality of the system, and ask (and hopefully answer) questions about the initiative’s future.
Today I worked with Elsie S., Plan Benin’s Project Coordinator, to chart out the operation of the system. The purpose of the exercise was to clarify the day-to-day operation of the system and revisit the roles and responsibilities of the many actors that interact with this project. Getting a firm grip on all of this information and documenting it for others will make it easier to train staff and partners and build further support inside Plan and within the government of Benin.
A few of the questions we asked and answered today:
— How long should it take for incoming messages to be processed (stripped of personally identifying information, mapped, and so on)?
— What model is best for managing this process? Should the responsibility be centralized at the Plan Benin Country Office? Or should it be distributed to the Plan Benin Program Units (PUs) where the majority of the reports originate?
— How can we modify Ushahidi to support a distributed model, where focal points in the PUs take responsibility and have agency?
— How can we create a shared vocabulary around the various actions within the Ushahidi system? What does “approve” mean? What does “verify” mean?

Me describing my version of the workflow and discussing realistic timelines for different actions within Ushahidi.
In the coming weeks we’ll work with Plan Benin staff to ground truth any revisions to the workflow and modify the system as necessary. We’ll also spend quite a bit of time creating the documentation that will ensure the continuity of operations in the future: reference guides for Plan staff, guidelines for maintaining the privacy of victims, and documentation of the relevant technical aspects of the system.
In parallel, I’ll continue working on some necessary tweaks to Ushahidi including establishing security protocols, enhancing the system’s mapping capabilities (thanks John Etherton for your location highlight plugin and support), and more. In ten days we’ll be joined by Jacqueline Deelstra, a recent graduate of the Fletcher School at Tufts, who will continue these activities and dig deeper on the relevant social issues.
More from Benin soon.
Note: For background and additional posts on child protection, child participation and the VAC Benin project, click here.
A comment to Paul: As Ushahidi has become a hammer for lots and lots of different kinds of nails, the “distributed processing” is a nail that will emergingly crop up, in my humble opinion (it came up in some work we did in Kosovo). This ability you describe, or reports processed by a wide variety of people, will grow more and more in demand.
It is a bit expensive to make work, but if/when you do, it may very well become of wider use within NGO/organization-run (maybe not as much within community-run) projects, something worth keeping in mind!
Prabhas – thanks for the comment. I totally agree. Empowering people to participate is a major selling point of new media, and organizations’ ability to train their staff to collect and manage all this information in a distributed manner will help unlock the potential of crowdsourcing. A good example comes from the work of election monitoring using mobiles – trained agents work at the polls, reporting irregularities in a standardized format.
[…] Update from Benin: charting a course forward (also by Paul) […]