Professional Documents
Culture Documents
Table of Contents
1. Uchaguzi: A Case Study 2. Case Study: Unsung Peace Heroes / Building Bridges 3. Toolbox #1 Self-Assessment 4. Toolbox #2 Implementation 5. Toolbox #3 Real-time Evaluation 6. Appendix: Evaluation Blog Series
Partnerships, Roles, & Responsibilities Maintaining coordination and upholding commitments were challenging. Sometimes members did not meet expectations of other partners. A workshop or meeting early in the project can establish a clear set of partner roles. Job descriptions may ensure accountability and place the project and the partners in the best positions for success. During the project there should be opportunities to check in (e.g., meetings) to improve communications and set positive expectations for involved partners. Civic education and media organizations should be considered as new partners. Mapping & Information Visualization Sometimes people were unable to access or actively look at the web maps. This was due not only to lack of high-speed bandwidth or Internet availability but also due to no knowing how to interact (e.g., zoom in/out & move) with the map. During the early planning stage (assessment phase) a group/ task force should assess users access to Internet and bandwidth and ability navigate online maps. This group should also identify opportunities to share paper maps if technology and web access is limited. Information flows & Communication The Uchaguzi platform added new communication pathways (e.g., SMS, twitter, email, web entries, etc.) to provide more efficient and near real-time access to referendum/election information. Future projects should identify and consider integrating existing information flows to avoid duplication. For example, partnering with media organizations, such as radio stations, can have a broad reach with the community. Strongly consider creating a communications strategy (including campaign & feedback loops) at the assessment/planning stage. When using shortcode, consider coordinating with other organizations who may be using similar shortcodes. Consider designing messaging campaigns together to minimize confusion with the public. Consider a simulation exercise to test information flows, communication, technology, and volunteer teams. Campaign Messaging The project successfully used many different methods in their campaign to inform the public about the project. Future efforts should create a campaign strategy and timeline that includes 1) establishing roles among partners responsible for shortcode and advertising 2) designing a message that not only informs the public about the project, but also informs the public about the project limitations. Information, Security, & Privacy Information security, privacy, and risks to people did not appear to be a major issue during this project, but future projects may face these very important risks and challenges.
A people, organization, data and system risk assessment should be performed for all projects, and a group strategy should be created. There is a quickly growing body of resources and working groups that can provide feedback, guidance and support for these activities. Partners should keep an open dialogue with one another about changing perceptions of risks during the project. Create contingency plans that aim to minimize threats to the public, project, partners and system. Technology & Instance Development One of the greatest strengths of the technical portion of this project was that the technical team was part of the Ushahidi organization and intimately familiar with the Ushahidi platform. Projects that are less familiar with Ushahidi/Crowdmap and/or the project location should strongly consider a technology assessment before beginning a project. Consider planning more time for technical development, prioritization of customizations, and a freeze point where new customizations are stopped in order to fix bugs. Volunteer Recruitment & Training Volunteers provided invaluable support. Training both CRECO monitors and volunteers improved the quality and the speed of information flows. Determining what constitutes an actionable or high priority message for the volunteers, and also defining the communication pathways to responders will set the stage for training volunteers on how to manage these incoming messages. One great resource available to future Uchaguzi projects is the lesson learned and training structure of the Standby Task Force. Consider having a simulation event as a way to train monitors and volunteers months before the referendum/election day. Contingency Plans The project did not appear to have a contingency plan and when interviewing project members almost all expressed interest in having such a plan in the future. The goals of these plans should be to 1. Maintain basic infrastructure 2. Maintain communication between lead members 3. Provide a backup network of information processing for highly actionable information. Creating a contingency plan can include plans for back up servers, volunteer groups, communication channels for coordinators, and connections to responders. Resources, Funding & Planning The most common recommendation was to plan earlier at least 6 months to 1 year prior to the event. Creating a project plan and timeline will help organizations determine what key parts of the project should be monitored over time. Aim to identify resources (funding and human resources) for campaign messaging, media volunteers, coordinators, and analysts (to identify hot spots and trends) as early as possible.
Output Phase
Information Flows 550 CRECO election monitors, Uwiano, and the public contributed over 2,500 messages, which resulted in over 1500 reports. 149 reports resulted in actions taken primarily through the CRECO network. Improvements in both the technology and people micro-tasking to filter incoming messages (e.g., color coding reports) would improve information processing, help identify priority messages, and facilitate communications to enable action. The project should position supernodes (individuals trusted among many groups who are action oriented) where they can troubleshoot unanticipated challenges, and open up communication channels to allow timely action. Prioritization, Actionable Messages & Feedback Loops There was strong communication between the Uchaguzi-Kenya project manager, Ushahidi staff, CRECO and SODNET. This helped strengthen the multiple feedback loops for urgent and high priority messages. CRECO played a very important role in communicating with the IIEC. 149 reports resulted in actions taken but there was confusion around what constituted an actionable message and how best to prioritize messages as they flowed in. During the implementation phase, partners should set criteria for action-oriented messages, and define priority levels so volunteers can appropriately and efficiently categorize reports. Consider creating an urgent response team. The role of this team would be to focus on validating messages and tracking priority reports. They would also be responsible for monitoring levels of tension and conflict and communicating important information to partner organizations in positions to respond.
Conclusion
Overall the Uchaguzi-Kenya project was a success. The collective action of all those involved provided a communication channel for Kenyans to share information about the referendum. It also enabled some organizations to take immediate action based upon the information on the platform. The project was not without its challenges. This case study aims to help bring light to some of them and share the creative solutions of dedicated and passionate participants. But more importantly it aims to help future users learn from the past, to spark fruitful conversations among future Uchaguzi/Ushahidi/Crowdmap deployers and to help others plan future projects.
Project goals/objectives/outcomes Visualization & mapping Partnership & audience Information & communication Campaign & messaging strategy Privacy & security Technology Resources & funding Planning & project timeline
Choosing Ushahidi vs. Crowdmap Roles & responsibilities Planning information flows Communication channels Planning categories Confirmation & verification Feedback loops Choosing the right map Your campaign & messaging: managing expectations Admin & volunteer teams Training
Evaluating goals/objectives Real-time evaluations Retrospective evaluations Checklists: 1. 2. 3. 4. 5. 6. 7. 8. 9. Partnerships Technology Campaign/messaging Information flows Action/feedback Communications Maps/visualization Information security Volunteers/teams
The interest phase discusses Uchaguzi project goals and objectives, partnerships, mapping and visualization. Experience from the perspective of roles and responsibilities, campaign messaging, and volunteer training are described in the implementation phase. Lastly, the output phase describes the information processing experience using the Ushahidi platform, and how this information was prioritized and translated into feedback and action. This case study is an example of an evaluation that can be achieved using Toolbox 3.
Assessment Phase
Uchaguzi Project Goals, Objectives, and Expected Outcomes I think what an organization really first needs to think is, OK were using Ushahidi, but why? And what are we going to get from it? What does it improve or speed up for us compared to what we were doing before? I think really approaching this from a program design perspective would be helpful. For CRECO for instance, our goal is to prevent or to resolve electoral issues so it doesnt lead to an outbreak of violence. And kind of take that back and say, what are our underlying assumptions about theories of change, and so, how do these particular actions lead toward that. The goal of Uchaguzi-Kenya was to provide a channel for Kenyan citizens to communicate openly about the 2010 Kenyan referendum using the Ushahidi platform. Although there was no unifying set of objectives, partners described the following: To provide a space for information sharing and collaboration To amplifying citizen voices To increase the efficiency of existing election monitoring system To create a mechanism through which citizens could actively monitor and report incidences related to the election process. Organizations involved in Uchaguzi-Kenya collaborated and complemented each other. This led to a successful collaboration, but organizations often had different objectives contributing to challenges during the project. Uchaguzi was a new endeavor, not only in technology, but also in partnerships and information flows. Document reviews and interviews show that a set of agreed upon project outcomes was lacking and this was likely due to the fact that each organization was learning how to integrate their missions into the overall project. I think Ushahidi (for election monitoring) works well if you have a broad selection of organizations supporting you But getting organizations to work together (with) mutual trust between them ...it takes time. Partnerships Before the referendum Uchaguzi partners met in Nairobi. Attendees included CRECO, SODNET, Ushahidi, Uraia, and HIVOS. Each group had unique assets and complementary strengths. For example CRECO had previous election monitoring experiences and consists of a large trusted network of monitors. Ushahidi served as the core technical partner for the project, providing developers and convening volunteers. The collective action among all five organizations was a success. Despite many challenges and areas for future improvements a single organization would not have succeeded alone because no one group had all the necessary skills and resources. According to interviewees, maintaining coordination and partner commitments was challenging and some people felt that the commitments of others did not meet their expectations. One thing I took away from the experience was understanding that there needs to be better communication. Recognizing the different languages that tech and nontech people speak, and that we cant always take for granted what is common knowledge and what is not. Communication between partners was essential during the project. Initial partnership meetings allowed groups to learn about each others aspirations. One lesson learned by project manager Jessica Heinzelman was understanding that different groups communicate in different ways.
6
Interviewees and evaluation reports recommend establishing a clear set of roles and responsibilities early in the project. Moderated discussions should seek to have organizations understand the perceived risks and benefits of partnerships throughout the entire project. Documents that reflect these discussions should be created and could also outline partner roles and responsibilities. Some participants recommended using memoranda of understanding (MOUs) as a way to improve partnership buy-in and commitment throughout the project cycle. Specifically, some believe that MOUs can provide clarity on expectations and improve communications. An MoU with all involved partners at the beginning will help to better map out what the objectives are in using Uchaguzi, reduce moments of friction during the process and enable better tracking of whether their capacity to effectively use the platform is indeed enhanced. This includes defining what the information will be used for by different organizations, what the platform can and cannot do for them, and what their own commitments need to be to the platform and other stakeholders. Many interviewees recommended partnerships with civic education and media organizations. They believe that these organizations and consortia have the potential to broadly disseminate campaign messaging and could improve the implementation and outcomes of a future Uchaguzi deployment. Future Uchaguzi deployments should bring partners together in a workshop or meeting during the assessment phase. New partners can be a part of this initial meeting to learn and decide if a partnership is possible. The meeting should aim to first expose any differing perspectives followed by a collegial process to agree on common goals and objectives. This process will improve collaboration and coordination because partners will approach challenges from common set of goals and objectives. The project should consider using MOUs to strengthen partnerships. Toolbox 1, slides 8-9 can be used as a guide for this activity.
And one of the things that I appreciated...was the fact that it ... was a deterrence, people could not do things because it would be discovered.
Information / Communication
The Uchaguzi-Kenya project planned to collect referendum information from CRECO election monitors and the crowd or public. Crowdsourced information was unstructured and information from CRECO monitors was structured using checklists and a code card. The plan was to use election-monitoring information to verify crowd reports. The Uchaguzi platform added new communication pathways (e.g., SMS, twitter, email, web entries, etc.) to provide more efficient and near real-time access to election information improving situational awareness. SMS was the major communication pathway for incoming information. Campaign planners used radio, television advertisements, tweets, and word of mouth to inform the public about the Uchaguzi project. Plans on how to communicate near real-time information back to the crowd and other stakeholders are less clear from this evaluation and the review of other evaluation reports. At the assessment phase, groups should think about what information already exists and how it is already being communicated. Existing information can flow through new communication pathways or new information may be best communicated along traditional communication lines. Partners should determine not only what new or existing information is needed to enter into the Ushahidi platform, but also discuss communication strategies. Partnering with media organizations, such as radio stations, can have a broad reach with the community. These strategies can include campaigns that inform communities about the project purpose, how it will happen, and open up discussions about how information can best be shared with the public, media and other interested groups. (Toolbox 1, slides 13-14) Uchaguzi-Tanzania participants recommend transforming the web-based map into paper maps. This would help local partners share the information with communities that are unable to access the map in its online format. Sharing maps in a newspaper immediately after the election would also broaden the reach of Uchaguzi efforts.
Plans on how to keep technology hardware (e.g., servers) safe and secure Plans for how volunteers and others should be trained to keep information private and secure, if necessary A contingency plan for security and privacy related events.
Two resources to help think about and plan a data protection, security and privacy strategy are particularly notable. Securing Crisis Maps, created by Rob Baker and George Chamales is a helpful infographic that shows different areas of information, security and privacy risks. A blogpost by Anahi Ayala Iacucci, Crisis Mapping and Cybersecurity describes one approach to addressing these issues. Questions from Toolbox 1, Slide 16 ICT, Privacy& Security can also be used as a guide to think about these issues in election monitoring projects.
Technology
Ushahidi developed the platform and first used it during the 2007 Kenyan post-election violence. Ushahidi staff and much of their volunteer community had prior experience with developing software, creating customizations and mapping information onto the platform. In 2010, 62% of the Kenyans were mobile service subscribers, texting approximately 10 times per month. Although voice and SMS may be widely used, the Communication Commission of Kenya statistical report does not describe the geospatial distribution of mobile use throughout the country. The geographical distribution of SMS and mobile phone use may influence how election information flows throughout the country during an election or referendum. As of late 2010, only 10.2 % of the population had access to the Internet. This statistic neither provides insight into how often users have access to the internet nor the degree of bandwidth that is reliably available, both elements that provide real-time, access to view Uchaguzi maps and report information. It is recommended that future Uchaguzi projects in other regions consider a technology assessment (Toolbox 1, slide 17) before beginning a project to understand and determine the internal technology needs and the capacity of their partners and public. This is also strongly recommended to organizations that seek to use a similar model.
Implementation Phase
Roles & Responsibilities
Implementation Phase Process Analysis
Choosing Ushahidi vs. Crowdmap Roles & responsibilities Planning information flows Communication channels Planning categories Confirmation & verification Feedback loops Choosing the right map Your campaign & messaging: managing expectations Admin & volunteer teams Training
The project included campaigns, a SMS shortcode, election monitors, and observers and multi-site information processing centers. During the implementation phase individuals and partners took on roles and responsibilities that resulted in a successful collection of information during the referendum period. Partners created campaigns, which provided different communication channels to spread the word. Overall, people wished for more defined roles and responsibilities at the partner and individual level. Another evaluation report referenced the need to, Establish partner organization roles and responsibilities and integrate them into an overarching project plan. Jessica Heinzelman described some of the challenges that she faced as project manager and from her experiences recommends a more structured way to communicate roles and responsibilities for future Uchaguzi deployments. Job descriptions would help ensure accountability and place the project and the partners in the best positions for success. If people were more aware of roles and responsibilities they would be able to reach out to one another for assistance and collaboration.
Implementation Toolbox 2, Understanding Roles and Responsibilities and Planning Roles and Responsibilities, can be used in future Uchaguzi projects. The first thing I would do differently is start planning much earlier. If we had had an extra month of optimizations, trials, and advanced training, I think we would have been much more prepared.
10
People thought that our shortcode was the same as theirs (3018)... and they were talking about similar things ... our publicity started like 2 or 3 days before the referendum. Theirs was also free, and ours was five Shillings to submit. .... there was a bit of (public) confusion. Once the information arrived into the Uchaguzi platform, different volunteer teams and coordinators at the iHub and CRECO offices categorized and mapped the information onto the public website. The plan was to have two separate flows of information: one from the crowd and another from the monitors. It was hoped that the crowd information would be verified by monitors, if necessary. Meeting during the implementation phase with all key partners may help identify obstacles and work through challenges. During these sessions, partners could create an information flow diagram that looks at all stages of communication and information flows. (see Toolbox 2, slides 10-13) Another opportunity for future Uchaguzi projects is to carry out a simulation of the election or referendum period. With existing datasets from prior projects, a simulation exercise could help a project work out bugs and unrecognized problems in workflows and communications. While the time and resources needed to integrate a simulation experience into the project requires planning at an early stage, this learning and adaptive exercise will likely expose many glitches that can be addressed prior to the actual election or referendum period.
11
Uchaguzi Tanzania Choosing the Map Not all individuals had adequate bandwidth to easily upload the maps and there were also anecdotes about individuals who sent information into the Uchaguzi-Tanzania instance who did not know how to drag, magnify, or perform other Google map functions on the Uchaguzi-Tanzania map. There was frustration and an initial perception that information was not being posted on the site. From these experiences, some have recommended finding a way to create a light version to enable low bandwidth users access to the information and map. It would be very interesting if Ushahidi could design a light version...[for some] it takes 5 minutes to upload and the dots come 3 minutes later. And if you dont know the dots are coming, youre not going to wait for them.
12
The Uchaguzi-Tanzania team had some difficulties estimating the number of necessary volunteers. During the election, the number of messages exceeded the volunteer capacity. One of the contributing factors was the time it took for people to translate messages from different dialects, and their ease in interfacing with computers. For future Uchaguzi projects the implementation phase should also try to anticipate SMS messages in different languages or dialects. If this exists, more planning may be necessary to recruit, organize and coordinate volunteers with different language capabilities. In addition, during the technology assessment phase, if the volunteer community has introductory computer and web skills, more training time and exercises will be necessary to prepare volunteers for large volumes of information processing. There must always be a back up and expectations of users need to be clearly adapted to this reality. This will not only help avoid tension between partners, but also reduce the risk of activities coming to a standstill without ICT.
Training around the identification and actions for high priority messages.
An information flow diagram could also inform volunteers of their micro-tasking roles within the larger project. Using a diagram, volunteer teams may find it easier to communicate needs and questions to the appropriate coordinators. Also, coming to an agreement among the team members of what constitutes an actionable message for the volunteers, and also defining the communication pathways to responders will set the stage for training volunteers on how to manage these types of incoming messages. One great resource available to future Uchaguzi project is the lesson learned and training structure of the Standby Task Force. There were two locations where volunteers processed information: the iHub and CRECO offices. These two groups, one from the iHub community and the other from the CRECO community were complementary to one another and the shared spaces allowed volunteers the opportunity to communicate with one another. It was an energizing environment. Although there were no security events, having multiple locations and also remote volunteers as backup support will mitigate some security concerns. Other volunteers worked remotely from their homes and were assisted via a Skype channel set up for the project. Depending on the security context, this may be another strategy for mitigating concerns. There may be instances in an election monitoring where it would be strategic to have pods located in multiple places if there are security concerns.
Contingency Planning
The volunteer iHub team functioned as a backup volunteer group for the CRECO team. Communication lines between CRECO, the IIEC and PeaceNet were available to facilitate information exchange for high priority events. The project did not appear to have a formal
13
contingency plan and when interviewing project members almost all expressed interest in having such a plan for future projects. The following are recommendations on how to think about a contingency plan. In the setting of violence and security events, the contingency plan should consider communicating information to the media, and also feeding information back to peace activities if possible. Consider back-up volunteers from the Diaspora or others who can process information remotely, and plan for the management of this community as well. Recognize that verification of information by these communities can be a challenge. Consider having a backup server at another location so that operations can continue. Consider having rotating volunteer teams to prevent volunteer fatigue.
Output Phase
This following section describes the Uchaguzi-Kenya referendum activities as well as the Uchaguzi-Tanzania election (grey boxes). It includes how information flowed into and out of the Uchaguzi platform. It also discusses feedback loops and communications between partners and the broader community.
would help microtasking and processing of information as it comes in. Others suggested coding information as pre-event, event and post-event as they believed these types of information have different purposes.
Uchaguzi-Kenya Platform Statistics 2010 Tanzanian Election Information Total messages received 2,525 Overload Referendum day messages 1,778 The Tanzania-Uchaguzi experience faced information overload challenges. There Uwiano messages 1,573 were thirty times more trusted sources who # reports 1,523 sent in coded information via SMS and the # total Uchaguzi messages 2,492 team faced technical challenges as well. SMS: 1,900 The instance was not set up to Twitter: 571 accommodate the large number of Email: 21 pre-defined trusted sources in the system. % verified reports 51% During the election day, when numbers arrived via text message volunteers spent 1,515 # of Actionable reports time calling people back to ensure that the 149 # of Action Taken reports numbers came from trusted sources. Top Categories: Although this provided a high level of Everything Fine (49%) Tensions (17%) verification, the number of messages, Peace Efforts (6%) coupled with the more novice computer skills of volunteers created an information-processing overload, limiting the speed of mapped information during the election.
Some people felt that the crowd reports included less information that could be mapped, including spam messages and other messages with no geographic locations. Some members felt that had the campaign commenced earlier this may have improved the quality of the crowd messages. In Tanzania we were struggling with 4,000 messages.
Communication
There were many pathways of communication during the referendum. At the iHub, volunteers communicated with coordinators troubleshooting platform glitches, and clarifying volunteer questions on how to process and map information. Erik Hersman (Ushahidi) and Philip Thigo (SODNET) sat side-by-side communicating information between Ushahidi and SODNET. Kawive from CRECO traveled to and from the iHub maintaining communications between the two information processing centers. He also maintained communications with IIEC staff. Some members felt that having two separate locations of information processing created a silo. Despite the intent to compare crowd and monitor messages during the referendum it was not possible to filter messages from election monitors and the crowd. This likely contributed to the feeling that the groups were silod. It will be good to build some easy steps by which you can actually separate your reports between your actionable ones and your non-actionable ones
Another challenge was identifying action or priority messages. Confusion likely stemmed from the lack of consensus around the definition of priority and actionable from a project level, volunteer training, and limitations in platform filtering functions. Despite these challenges, volunteers and leaders in the project
15
worked together to create work-arounds to achieve the project goals. Volunteers transferred Uwiano messages to Google Docs spreadsheets to identify high priority messages that required follow up and action. In the implementation phase bringing partners together to determine what constitutes feasible action-oriented messages will help define what actionable and priority means for the project. Volunteers can then be trained on how to identify and filter actionable or high priority messages. Developing action and priority buttons on the instance would also improve microtasking efforts to filter and allow key decision-maker to respond with the appropriate partners. Many recommendations have already been incorporated into the new Ushahidi platform. Developer George Chamales has built and tested new microtasking platforms that may address these challenges for future Uchaguzi projects.
Conclusion
Overall the Uchaguzi Kenya project was a success. The collective action of all those involved provided a communication channel for Kenyans to share information about the referendum. It
16
also enabled some organizations to take immediate action based upon the information received. The project was not without its challenges. This case study aims to help bring light to some of them and share the creative solutions of dedicated and passionate participants. But more importantly it aims to help future user learn from the past, to spark fruitful conversations among future Uchaguzi deployers and help others plan future projects. Thank you The content, analysis, and presentation of this case study could not have been achieved without the honest and creative insights of many interviewees during the project. Feedback from the Ushahidi community of users, Harvard Humanitarian Initiative staff, experts in the field of crisis mapping and crowdsourcing provided invaluable feedback. The Harvard Humanitarian Initiative hopes that this collaborative learning effort will contribute to not only evolving growth of Ushahidi as an organization, but also to the next steps that people, groups and organizations will take using their own Ushahidid/Crowdmap platforms in the future. With gratitude,
17
backgrounds and ways of life. Butterfly Works and MFAF announced the winners during live events, placed an ad in The Standard newspaper and posted the winners picture and biographies on the Unsung Peace Heroes website.
capacity. The project had two main objectives: (1) map peace initiatives throughout Kenya and (2) recognize and reward (with prize money) Kenyans who participate in peace initiatives and promote conflict resolution. Building Bridges launched in April 2009 and ran for three months as a competition in which individuals, community-based organizations, and civil society organizations were eligible to win a prize for their work. According to a press release sent out to Kenyan bloggers, Building Bridges is open to all Kenyans engaged in peace-building and peacemaking activities, including organising peace gatherings, community discussions, creative and sportive activities or even holding festivities and doing pro bono work to ensure peace in areas. Building Bridges is putting them all on the map and rewarding the most promising projects.
Unlike Unsung Peace Heroes, Building Bridges was not based on nominations, but rather on registrations. The project designers anticipated that people would register via a web form, email, SMS, voicemail or postal mail and then update their peace initiatives through the similar mechanisms. They expected most submissions to be sent through SMS. That data-handling team, a group of three former NairoBits students employed by the project, were responsible for managing the registrations and updates. They received most of their submissions via mobile phone, typically preceded by a text messages asking for more information about the initiative. According to Rukia Sebit, the leader of the data-handling team, any texts with info, Building Bridges, 5447 (the registration short code), or left blank were treated as inquiries for more information. When they received these messages, the data team would call the people back.
Some people wanted more general information about Building Bridges, others wanted to register their peace activities, and some people were simply confused about the initiative. The competition received more than 600 registrations from individuals and groups all over Kenya. The data team believed that the project had good reach and that Kenyans throughout the country were familiar with the initiative because of the advertisements, particularly the radio spots, and the strength of word-of-mouth, especially through their connections with PeaceNetKenya and other local partners. The partnership with PeaceNet-Kenya was critical for spreading the word about Building Bridges to communities with limited access to mass media. Analysis of the available data showed that the majority of registrations came from the Rift Valley and Nairobi provinces (36.9% and 23.6% respectively).1 There were 61 registrations from Nyanza province, 10% of all registrations in the country, with Eastern province accounting for 9.9% of registrations.
1 The
Building Bridges has 628 registrations posted, but only 618 have provincial data used in this analysis.
Activity Categories
There were a total of 1,409 activities entered into seven categories. This number is much larger than the number of registrations because some activities were tagged with more than one category. The three largest categories were Individuals, Organizations, and Educational Activities. Media and For Children were the smallest categories.
The Building Bridges jury selected five individual winners, two community-based organizations, and two civil society organizations. The winners were Jane Mweru from Eldoret; Amani Kibera, a CBO located in Nairobi; and the Rafiki Club, which works in Kakamega, Mumias, Msabweni, Mitaboni, and Nairobi. Mweru was injured in a church that was set ablaze during the postelection violence. After the crisis, Mweru opened a nursery school for children who were affected by the church fire. Amani Kibera is a youth program focused on peacebuilding and conflict management through the use of sports, arts, culture, and entertainment. Rafiki Club focuses on empowering women and girls in various Kenyan communities. After the post-election violence, the club developed a program that paired women of different ethnic and religious backgrounds with one another in a letter-writing program. On September 21, 2010, World Peace Day, the winners and runners-up were recognized and rewarded at an event at the iHub, marking the end of the project.
Challenges
Despite the overall success of the Building Bridges campaign, the team faced a number of challenges along three main fronts: technical, messaging, and personnel and capacity. These areas all present different types of challenge, some of which the team could overcome and others that were not resolved.
2 Unfortunately,
we do not have analytics after June 20, 2010, but it can be assumed that visitors stayed steady or perhaps even spiked at the conclusion of the project in July.
Technical challenges One of the projects biggest technical challenges was integrating Ushahidi with the Joomla! content management system. The Joomla! integration created challenges for the data handling team in Nairobi. Because of the design of the two administration sides, it was difficult to move data between the different systems. The data handling team developed a system for data
management using Joomla!, Ushahidi and Google Docs. Having three different databases created inefficiencies and slowed the data entry process and website updates. Two other major technical challenges: slow and unreliable Internet connections, and mobile limitations were challenges that the team worked to overcome despite little control over these issues. The data handling team relied primarily on Safaricom 3G modems for their Internet connections. These modems, although rather convenient, were often slow. And, if the Safaricom network was down, the team had limited access to a backup Internet connection. In addition, the lack of Internet access in much of Kenya prevented participants from accessing the website, which meant they werent able to register their projects online or view other projects. Because of this lack of Internet access, mobile phones were essential for communicating with participants and for registering projects. The 160-character limit of text messaging presented a challenge for Building Bridges because they needed to collect detailed information about the peace initiatives. It was not possible for people to register their initiatives using SMS because registration required that the projects were entered into the online system. The data team would use the information from the text messages to register the initiatives, but this was not an automatic process. Registrants could send in basic information name, location, and perhaps one detail but needed to either fill the web registration, mail in the registration or relay the information to the data team over the phone. In most cases, the team would receive a text message with some information about the initiative and then call the person back to get the remainder of the information. If the people responsible for the initiative had access to the Internet, they could update their projects online. If not, they could send updates via text message. The data entry process was often tedious due to the limitations of mobile and the complicated backend. However, the data team developed a system for collecting, entering, and managing the data, which is discussed in more detail below.
Communication and Message challenges Another set of challenges had less to do with technology and more to do with communication and the campaign message. Despite consistent messaging across media, it was not always clear to potential participants what Building Bridges was or what they should do to participate. Potential participants would SMS blank text messages or messages asking for more information about the campaign, but would often not submit initiatives. Building Bridges received 16,320 text messages and 628 usable registrations, which are posted to the site. The large discrepancy between the number of messages received and the actual number of registrations suggests that participants were unclear about the purpose of Building Bridges. They would text to the short code without a clear sense of why they were contacting the campaign. The team faced challenges communicating with people on the phone to get more information. It was difficult for the team to talk with people who did not speak English or Swahili. Other times, it was difficult to reach people: the team would call them back, but receive no answer. Some team members disagreed over what qualified as peace activities and what should be mapped. For example, one man said that he talked about peace with patrons in his store. He did not have an organized peace activity, but said he used daily interactions with customers to discuss peace. Some Building Bridges team members felt that this did not qualify as a peace initiative and did not want to add it to the map, while others thought that it did and should be added to the site. In other words, at times, the team disagreed over what should be posted to the site. It would not qualify for the prizes because it did not meet the criteria, but it could still be mapped to show the work going on in that community (see Appendix 2 for criteria used by the jury for selecting winners). More broadly, the Amsterdam team and the Kenya team worked in different environments and sometimes were unable to communicate effectively. Butterfly Works often wanted processes to move more quickly, but the Kenyan team had to cope with the inefficiencies in local systems and Kenyan bureaucracy, which often slowed them down. For example, any competition that awards prizes in Kenya needs approval by the slow-acting Betting Control and Licensing Board. This agency delayed the progress of Building Bridges as the team waited for approval. Capacity challenges The final set of challenges had to do with capacity and personnel. At times it was difficult to coordinate the two teams, one working in Amsterdam and the other in Nairobi. The distance, differential access to technology, and cultural differences sometimes hindered the two teams. For example, a Butterfly Works staff member in the Netherlands did the web development and Joomla! integration, but the data handling team responsible for using the site was based in Nairobi. When the site didnt work, they would need to contact Butterfly Works or try to come up with a fix independently. Not having the web developer in Nairobi with the data handling team slowed the process and sometimes led to confusion or misunderstandings between the team members. As previously mentioned, the data team said that the registration process was not as clear or easy to participants as it could have been, which slowed down the data entry process and created other inefficiencies in the system. For example, the team added a third database to the process, a Google Docs spreadsheet where they managed SMS. In addition, there was little separation of duties among data team members. In other words, all the team members did every step of the data entry process rather than separating the tasks.
each other as well as link up. As of early 2011, Butterfly Works and Media Focus on Africa Foundation had no plans to continue Building Bridges although they originally planned to run a second phase. They did not receive continued funding to work in Kenya, and therefore, the project has not moved into phase two. In April 2011, Butterfly Works released a toolkit, Social Change Initiatives, geared toward others interested in designing peace campaigns. The toolkit includes a how to guide, a case study of Building Bridges, the software download for the Joomla! component for Ushahidi, Building Bridges graphics, and guidelines for monitoring and evaluating. All the materials are available for download and are free for users.
10
Project (2 Respondents)
1 2 3 4 How successful was the project in enabling people to register their own peace initiatives, no matter how tech literate they were on where they were located? How well did the project visualize and map all registered projects including related information on a central platform? How well did the project allow people to connect and (potentially) offer support? How well did the project Inspire people to take their own action? 3 4.5 2 3.5 OK Well to Very well Not so well OK to Well
The data team felt that the Building Bridges project was somewhat successful in (1) encouraging all Kenyans to stand up and act for peace in their area, and somewhat successful in (2) encouraging all Kenyans to become active drivers of peace through development and registration of their own peace initiatives. The team also felt that the project was ok at supporting those that did great work. Respondents in the Buttery Works evaluation also shared this sentiment: A broad majority of participants would have wished for stronger direct support by potentially regional support teams to guide them and help moving their initiatives further, informing them on updates etc.5
11
The team felt that the project was neither successful nor unsuccessful at enabling people to register their initiatives because some never registered their initiative on their own. They also felt that the project objective to connect people together and potentially offer support did no work so well. One member of the data teams shared her thoughts: I strongly felt that what we could have done better was to organize community forums, sports events (something to bring the community together). Then used that avenue to link the peace makers together to avoid repetition of the same peace projects in one area, where they could link to work together to achieve the goal.
5 Ibid
12
Appendix 1
Performance test: Building Bridges
www.buildingbridges.co.ke/joomla
1. Please start with entering the url: www.buildingbridges.co.ke/joomla in the address bar of your browser. 2. How long does it take before you see anything (seconds)? 3. Does the website look well structured or is something out of place? 4. How does the design look? 5. Do you see the image player on the homepage? How does it work? 6. Could you test the website in another browser and answer the above questions again? 7. If you click on View Map in the menu, you will see a map, categories, and some time filter options. Can you tell me how long it takes before you see anything appearing? 8. Does it look structured to you or is something out of place? 9. Please play around with the map to see if it works. The dots in the map are links to projects. 10. If you click on Reports in the menu, you will see a list of all the projects that are on the website. Can you tell me if it works? 11. Please play aroud with the list of reports to see if it works. The titles of the reports are links to the projects. 12. Maybe you could visit the other pages to test if everything works and looks the way it should. 13. Any other comments? Thanks for helping!
13
Appendix 2
Selection Criteria 1. The applicant must be able to proof it realized a series (at least two but preferably more) of connected, consecutive activities which form one initiative/project 2. The applicant must be able to provide at least one independent reference in relation to the activity activities who are not family relations of the applicant or in any way related to/involved in the activity. 3. Applicants should be willing to have a video or audio interview made of them and be willing to appear in mainstream media in relation to the Building Bridges campaign. Specific for organisations: 4. In case the applicant is an organization, it must have registered the organization with e.g. the NGO council and be able to provide proof of registration upon request. 5. The applicant must provide evidence of the sustainability of the activity/activities. Within no more than two years from the start of the activity, it should: a. Achieve financial independence (i.e. not rely on donor funding for continuation, the activity should be able to pay for itself) OR b. Serve a continued need in the local community and have a steady support base (can be financially and/or voluntary). Specific for individuals: 6. In case the applicant is an individual, he/she must be not less than 18 years old at the time of entry. The selection process: Selection of the winning activities will be done by a panel of experts in the area of peace building and sustainable development; the jury. The jury will assess the applications based on the criteria above and their own interpretation thereof due to the expected variety in the types of activities that will be submitted and the nature of the criteria by which they are assessed. The decisions made by the jury are final and will not be subject to correspondence. NB. These criteria are subject to changes at the discretion of the jury, but with final approval by the implementing parties.
14
Toolbox #1
Self-Assessment
Checklist TOOLBOX 1- SELF ASSESSMENT TOOLBOX 2- IMPLEMENTATION TOOLBOX 3 - USING YOUR INFORMATION
TIP: An Ushahidi project doesnt start with setting up the platform and putting it on-line. You need to prepare your strategy, study the context, understand the implications, secure cooperation and knowledge of the tool for all of the actors involved. The launch of the platform is the last step of the project, not the first one. (Anahi Ayala Iacucci)
Self-Assessment
Helping you take the first steps to determine if the Ushahidi platform is a fit for your project
Toolbox 1
- Learn about Ushahidi - Find out if Ushahidi will fit into your project goals & objectives - Think about partnerships for your project - Identify the information, communication and technology needs for your project - Think about what resources are necessary to make your project successful
Lets Begin..
First Name:____________ Last Name: ____________ Are you an individual or part of an organization?
Organization Individual Organiza(on
Name:
____________
Email Address:___________________
You
can
use
the
Ushahidi
Pla[orm
for
informa(on
collec(on
and
sharing,
visualiza(on
and
interac(ve
mapping.
There
have
been
over
3000
uses
of
Ushahidi/Crowdmap.
Here
are
some
common
types
of
uses
of
the
Ushahidi
pla[orm
(Ushahidi
video
introduc(on)
(FAQs)..
And
more
Deployments
icon
Hot Flash
Ushahidi Prototype Hai( Crisis Map Uk Riot Cleanup Chicago Blizzard Japan Earthquake War on Gaza DRC Zim Poli(cal Crisis
icon
Slow Burn
For ongoing or complex emergencies, to track changes in communi(es or responding agencies . (crime mapping?)
icon
For events like elec(on monitoring, media campaigns with ending dates. (more text)
Uchaguzi-Kenya Sudan Vote Monitor Unsung Peace Heroes Voice of Kibera KANCO (health) Uchaguzi-Kenya
icon
For ongoing programs and ini(a(ves (human rights monitoring, media, environmental mapping, local gov mapping, resource mapping )
EXAMPLES..
TIPS: How will you achieve your goals? How will the collected information achieve the goal.
What
kind
of
project
are
you
working
on?
(please
check
all
that
apply)
Health
Water
and
Sanita(on
Media
HIV/AIDS
Environment/Conserva(on
Womens
Issues
War/Conict
Natural
Disasters
Human
Rights
Children
and
Youth
Educa(on
Gender
Based
Violence
Economic
Development
Security/Protec(on
Poli(cal
Violence
Elec(ons/Elec(on
Monitoring
Other,
please
describe______
new old
Is
this
a
development
or
humanitarian/crisis
project?
(deni(ons
and
examples)
Community
Programming
Development/Governance
Humanitarian/Crisis
Other
With the goal to _____Users can correct the auto- inserted text here________. The program/project objec(ves are Users can correct the auto- inserted text here__.
What
are
the
expected
outcomes/impact?
___________________________________________________________________
___________________________________________________________________
___________________________________________________________________
How
will
the
Ushahidi
pla[orm
help
you
achieve
your
expected
outcomes/impact?
___________________________________________________________________
___________________________________________________________________
TIPS: How will you achieve your expected outcomes?
Mapping
data
is
important
for
creaFng
responsibility.
The
fact
that
people
see
their
report
is
the
biggest
moFvaFon
to
engage
them.
-
Oscar
Salazar,
Cuidemos
el
Voto
Mapping
informaFon
will
benet
your
project
by:
What
kind
of
informaFon
will
you
map?
How
do
you
intend
to
use
it?
Who
do
you
want
to
view
the
map?
TIPS:
The
mapping
system
in
Ushahidi
is
not
automa(c:
you
need
to
geo-reference
informa(on
manually.
You
can
do
it
at
the
admin
level
with
volunteers
or
other
people.
If
you
plan
to
use
it
as
a
crowd-source
system,
you
need
to
have
a
big
number
of
people
mapping
those
messages,
or
you
need
to
do
it
only
by
web- submission
(it
means
also
forget
about
the
media
monitoring,
SMS,
e-mails
and
twieer
submissions).
What
level
of
precision
does
the
mapping
require?
Do
you
want
data
points
or
data
areas?
(Anahi
Ayala
Iacucci)
icon
Learn more
case studies
instance sites
Blogs/media
Allocation of Time
In an Ushahidi Deployment
Ushahidi setup
Requires some tech skills and training, but not much work Set up a server, run installer, poke around
Learn More: Why technology is 10%- Anahi Ayala Iacucci Allocation of Time Chris Blow
Just because you bought a domain name and ran the Ushahidi installer doesnt mean that anyone is going to use the system and even if you somehow get a lot of reports, you might not be relevant to the exisFng systems (that is, all the other people who are working on the same problem). So as Ory said in Cape Town, Dont get too jazzed up! Ushahidi is only 10% of soluFon. Systems like Ushahidi have turned enormous communicaFon barriers into a trivial installaFon and training process. But there is a whole other 90% of real work. (Chris Blow) Lets focus on that 90% and identify potential partners in your project.
TIPS- One of the major partners in project is a technical administrator. If you envision customizing your instance a lot you should think about having a developer as a partner if you do not have one in your organizaFon.
Who are your Audiences? Why do you think they will use your plaAorm?
TIPS-One of the fundamental parts of your project is the deniFon of your audience. Who do you want to visit the site and use your informaFon and who you want to be your reporters?
icon
Learn more
Information
Your Ushahidi instance will help you collect, organize and communicate information for the goals of your project (ExisFng
project)-
What
informaFon
are
you
currently
collecFng?
What
informaFon
do
you
want
to
add
with
this
project?
(New
project)
What
informaFon
do
you
want
to
collect?
How
will
this
informaFon
allow
the
project
to
achieve
its
goals?
TIPS:
Does
someone
else
have
exisFng
indicators
or
iniFaFves
or
informaFon
needs
or
formats
that
you
should
be
linking
in
with
and
following
or
supporFng?
(Linda
Radree)
case studies icon
Learn more instance sites
Type
IMPORTANT! What is the exis(ng informa(on ow and how the informa(on ow you propose will change or modify the exis(ng one? The idea is that the more you modify the exis(ng informa(on ow the less your project will be successful.
blogs/articles
Communication
Your Ushahidi instance will help you collect, organize and communicate information for the goals of your project. Collecting information into Ushahidi platform is only half the battle. How will you communicate information to your audience? Partners? Media?
From slide 11, this is your audience: Example The people who Media Focus on Africa ___________________________________________________ FoundaFon are targe(ng do not have Internet access - We want to bring the How do you plan to tell people about your project and how to results back to the people using mass send informaFon into the plaAorm? media. As a result of MFAFs goals, Internet is only one part of the larger project and SMS Television AdverFsements campaign. This is not only true for the Othe Unsung Peace Heroes campaign but for all Radio word of mouth of MFAFs work. Bueery Works uses Newspaper mul(ple media types in their work as well so Morning shows Flyers the mul(media approach for Unsung Peace Twifer Internet Heroes was familiar to both organiza(ons Facebook and important to achieving their goals. How do you plan share the informaFon with your audience? Bueery Works and MFAF used a mul(media approach, including a website, newspaper ads, radio and television appearances, par(cipa(on in live events and TIPS: think about how your audience commonly views/ word-of-mouth. (Melissa Tully) accesses informaFon)- and what way they are most likely to view informaFon during a crisis. icon case studies Learn more blogs/articles Type
The communication strategy can be: 1) Announcement of the project/service 2) Setting expectations 3) Plan for responding to individual messages 4) Communicating information to different audiences
The Unsung Peace Heroes project in Kenya used a mul(media publicity strategy, including placing ads in the newspaper, making TV and radio appearances, handing out iers, par(cipa(ng in local peace events and having an online presence, to spread the work about their project and to collect nomina(ons of Peace Heroes throughout Kenya. This strategy allowed them to target various diverse audiences and in the end they received over 500 nomina(ons for Unsung Peace Heroes throughout Kenya. (Melissa Tully)
TIPS Be sure that you get clearly the message out: what you want to do, why and if the issue is urgent or not.
Type
icon
Learn more
case studies
blogs/articles
Example materials
icon
Type
case studies
instance sites
blogs/articles
Learn more
Technology
Ushahidi is a software, which means it requires access to certain technologies.
1
Do
you
have
regular
power/ internet
access?
Are
your
team
members
volunteers
comfortable
with
computers/the
internet,
etc?
Do
you
have
a
technology
person
on
your
project?
Is
he
or
she
a
PHP
developer
and/or
designer?
Do
you
want
a
lot
of
customiza(ons?
Yes
No
If
you
project
area
has
limited
power,
and
limited
access
to
internet
this
will
limit
the
ability
to
use
Ushahidi
/Crowdmap.
Consider
using
another
tool
or
start
with
a
small
pilot
project
How
do
your
partners
and
audience
currently
communicate?
What
are
they
comfortable
using
to
communicate?
(cell
phones,
sms,
internet)
What
do
they
have
access
to
and
can
aord?
If
YES,
then
have
this
person
take
a
look
at
the
Ushahidi
Manual
to
see
if
this
ts
their
capacity.
If
NO
then
take
this
technology
assessment
test
here.
If
NO,
then
consider
using
crowdmap.
Link
Here.
CustomizaFons,
or
****,
will
require
a
developer
and
likely
a
designer.
And
you
have
YESs
for
ques(ons
3
&4
Yes No
3 4 5
What is the local use of ICT in the country? How do people in the community use the internet and mobile phones? Take the tech assesment! Learn more
TIPS: How do your partners and audience communicate now? What are they comfortable using? (cell phones, sms, internet) What do they have access to and can afford? case studies blogs/articles
TIPS: Have a clear budget and take into account advertisement campaign, dev work, PHONE EXPENSES if you use SMS and alerts, server space, and time to dedicate to the project. Also fundamental, have a monitoring &evaluation line in the budget and in your project plan and do periodical review of the project according to goals. (Anahi Ayala Iacucci)
Resources
Here are some resources you may need. Fill out the cost that you will need too.
Resource
Project
Manager
Developer
Designer
Project
Manager
Volunteers/Coordinators
Campaign
Adver(sing
Servers
Computers
Phone/SMS
expenses
Monitoring/Evalua(on
Training
Workshop
Planning
Workshops
General
Oce/Equipment
Other
Cost
Make
sure
you
have
a
clear
budget
and
think
about
the
resources
that
will
you
need
for
your
project.
TIPS
Find out about any poten(al licenses you might need, for example for holding a compe((on, this can ocen be bureaucra(c and take (me to organise. NOTE Calculate ?me for the design and prin?ng or produc?on of all your materials, making a website or yer and prin?ng it can take a few weeks. (Bufery Works Toolbox)
TIPS
If you are looking to gather, share and make decisions with many dierent people & partners. Consider: Planning mee(ngs& workshops early to make sure that all partners have similar expecta(ons and understand their roles/responsibili(es Plan your media/adver(sing campaigns early, determine the cost, and how you will inform people of your project and set expecta(ons.
TIPS
ELECTION MONITORING Sta and Volunteers for the Uchaguzi Kenya Project ( 2010 Kenya Referedum) recommend 3-6 months for planning around a specic elec(on days.
PROJECT EXAMPLES
icon
Type
blogs/articles
Learn more
(On the online tool, what you have lled out in the previous panels will automaFcally show up here!)
Below is informa(on about your project that you entered in the rst toolbox
Informa?on/Communica?on
_____________________________________________________________________________
_____________________________________________________________________________
Marke?ng
Media
Plan
_____________________________________________________________________________
_____________________________________________________________________________
Technology
Assessment
_____________________________________________________________________________
_____________________________________________________________________________
I
would
like
to
make
changes..
Toolbox #2
Implementation
Checklist
TOOLBOX 1- SELF ASSESSMENT TOOLBOX 2- IMPLEMENTATION TOOLBOX 3 - USING YOUR INFORMATION
Toolbox #2
Implementation
This toolbox will help you implement your project using the Ushahidi/Crowdmap instance : Review of your work from Toolbox #1 Choosing the platform that will work best for your project (Ushahidi or Crowdmap) Understanding and planning roles and responsibilities Think about information inflows and outflows Plan a verification process that will link directly to action Create a marketing plan Build a feedback loop Plan for a volunteer team Plan and implement training for your members and partners
Before moving into toolbox 2, here is a review of your work from the assessment toolbox. The database will auto-generate the following: Project Goal/Objec/ves/an/cipated impact
________________________________________________________________________________________________________________ ________________________________________________________________________________________________________________ ________________________________________________________________________________________________________________ Reasons for mapping ________________________________________________________________________________________________________________ ________________________________________________________________________________________________________________ ________________________________________________________________________________________________________________ Partnerships ________________________________________________________________________________________________________________ ________________________________________________________________________________________________________________ ________________________________________________________________________________________________________________ Informa/on/Communica/on ________________________________________________________________________________________________________________ ________________________________________________________________________________________________________________ ________________________________________________________________________________________________________________ Marke/ng Media Plan ________________________________________________________________________________________________________________ ________________________________________________________________________________________________________________ ________________________________________________________________________________________________________________ Technology Assessment _______________________________________________________________________________________________________________ ________________________________________________________________________________________________________________ ________________________________________________________________________________________________________________
Choosing the platform that will work best for your project
A
pla?orm
for
organizaCons
with
more
tech
experience.
Needs
to
be
downloaded
to
your
own
server
A
good
t
for
a
project
that
has
tech
experience
and
developer
support.
Allows
for
customizaCon.
You
can
own
the
data
Check
out
the
demo..
Allows you to set up your own deployment of the Ushahidi Pla?orm without having to install it on your own web server Does not require installaCon Fastest and simplest installaCon of the Ushahidi pla?orm. Built to handle informaCon coming out of a crisis. No need for a developer Fewer plug-ins Open data / unable to password protect Learn more on the website
TIPS: A technology developer (or tech savvy person) can install your Ushahidi instance and you or other team members can install Crowdmap. There is a very comprehensive Ushahidi User guide, that will help take you every step of the way.
Understanding Roles/Responsibilities
TIPS:
Community
users
believe
that
dening
roles
and
responsibiliCes
early
in
a
Ushahidi
project
is
very
important
to
its
success.
Planning roles and responsibilities for your project will depend on the size of your project. Choose the option that best fits your project:
LARGE
Planning a country-wide project, one that involves many partners, or will be collecCng large amounts of informaCon
medium
Planning a small audience outreach program to collect and share with a single, specic community
small
Short-term deployment with one to three volunteers. Lower targets for volume and outreach.
STOP HERE and consider having a workshop with your partners and audience to agree upon
Lets collaborate!
Admin Coordinator
Technology Coordinator some example roles from other deployments: managing all technical problems. For example, will O_en a technical advisor who is responsible for Here are change categories, basemaps, & sms syncing programs Works with a PHP Developer and/or GIS expert. Not all projects require a PHP or GIS expert, especially if you are using Crowdmap.
He/she will keep track of the volunteers and will coordinate the division of volunteers (ex, mappers, monitors and admins). Requires three dierent tasks: recruiCng, training and coordinaCng. Responsible for the pla?orm messaging to the crowd/community and media and manages relaConships with journalists and general media in general. You may have two people on this team one for the community/crowd and another for the media/journalists. Works closely with the PM on the media/outreach strategy. For Crisis related Projects: Responsible with a team to constantly monitor and process reports to idenCfy emergencies and to provide informaCon to responders. Communicates closely with the project manager or core team.
This is not a complete list! Consider having a workshop with your partners and audience to agree upon roles and responsibili@es for your project!!!
icon
Example TORs
Roles in Crisis
Community users from other deployments recommend a leadership team. Who will be part of your leadership team?
icon
Learn more
Job TORs
When responding to a crisis, you will likely need to plan, recruit volunteers, and build partnerships at the same @me. We recommend the following resources: - The StandbyTaskForce- hZp://blog.standbytaskforce.com/ - The CrisisMappers Network www.crisismappers.net/ - The Ushahidi Manual - wiki.ushahidi.com
A trusted or bounded community Individuals or Groups that are part of the community and
also part of known set of reporters to the platform. For example: NGO workers reporting to a UN system, election monitors reporting into the system. Pre-identified trusted community members sending in human rights information, and even known first responders during a disaster.
Other organizations/partners- Organization that are partners involved in the program. This
can be the organization that represents a bounded community (ex. Election monitoring group, UN Cluster, consortium) They can also be organization that wish to received analyzed information as well. ( Media/ Journalists)
Ushahidi/Crowdmap Platform- This is where information from the group above will come into
and will also be the location where analyzed or processed information may come from. Within this platform there may be more people involved to process/analyze and present information back to the wider community. Remember that on major part of the platform is internet and web-based!
Your thoughts?
EXAMPLES
UNDP/OCHA COLOMBIA HAITI CRISIS MAP LIBYA CRISIS MAP
(is it possible to do a drag/drop function here? Where they would drag a group/partner into a circle? )
Drag your partners/group into the shapes- (auto-generated from assessment) Add more partners.
Information / Communication
Here
is
a
recap
of
your
informaCon
communicaCon
strategy
from
the
assessment
toolbox
make changes
List the specific types of information that you will collect for your project:
How do you plan to collect information the information you wish to map on the Ushahidi platform? SMS Web TwiNer Smart phone apps Email Call Center Voice Message Facebook Face to Face Radio Other________________ Other________________
Before creating / choosing categories, first understand how you will use the information
EXAMPLE: You are quickly setting up a crisis map. Your goal is to identify the location of refugee camps to share who/ what/where maps and share information about hospitals/ and clinics at UN Cluster meetings so organizations can plan shelter and health services.
1
The information for the UN meeting will be maps with refugee locations and functioning hospital locations 2
Categories you can create are Camp Locations and Hospitals (functioning) 3
Now think about how this information will feasibly be collected. a) crowd information b) NGO individuals reporting into the system. 3
Informa/on
How
will
it
be
collected?
2
CATEGORY
Camp
LocaCons
Hospital
(funcConing)
Informa/on
(drop
down
or
write
in..)
1
How
will
it
be
communicated
out?
(drop
down
or
write
in..)
(is it possible to do a drag/drop function here? Where they would drag a group/partner into a circle? )
Drag your information types next to the red and green arrows above (auto-generated from
assessment)
One of the challenges of using a crowdsourcing tool is verification. When information enters the Ushahidi/ Crowdmap platforms you or your team will need to verify and confirm reports. Here are some ways that deployments have verified information:
You have the information from multiple reliable sources You have two or more text messages from different phone numbers about the same incident. Someone on your team has spoken with the person on the ground to get more detailed information about the report. On of the providers of information is a partner or part of your trusted network
Verifying Information
What will be the rules to verify a report? (enter text here) If you have large numbers of reports coming in all at once, how will you prioriCze which ones to verify quickly? How will you train your teams on how to verify? (enter text here)
TIPS: If there is any doubt about a report, a good first step would be to mark the report as unverified, until you have the opportunity to investigate further.
icon
Twitter challenges
Example verifications
Consideration #1: What is the scope or size of your project. Do you plan to collect information for an entire country, a city, or just a community? Consideration #2: Is there a map that exists of the areas that you are interested in? Some maps services may not have the area mapped. You should always check. If it does not exist? What are the next steps? What are your options?
Ushahidi has 4 available providers, if you have a developer you can have them add another map to better fit your needs. The only customizable map is OpenStreetMap (OSM) Check out the following map providers here:
I
cant
nd
a
map
for
my
project
..
Visual Earth
TIPS: How large is the area that you will place information on the map? (country, region, city, community)?
Messaging / Campaign
How will people find out about your initiative?
If your project involved receiving messages from the crowd or the open community, it is very important that you have a clear message and strategy about what type of information you would like people to send in, and for what purpose you will be using the information.
Here
are
some
things
to
think
about:
HOW
DO
PEOPLE
ALREADY
BROADCAST
INFORMATION
TO
ONE
ANOTHER?
Think
about
the
ways
that
people
communicate
with
one
another
about
informaCon.
If
the
community
that
you
want
to
send
in
message
watches
television,
reads
the
newspaper,
or
listen
to
the
radio,
this
may
be
a
very
eecCve
way
to
inform
people
of
your
project
and
why
you
want
them
to
send
you
informaCon.
KEEP
IT
SIMPLE
Dont
forget
about
face
to
face
communicaCons!
Think
about
how
people
can
spread
the
word
in
local
meeCngs,
through
community
leaders,
and
other
basic
communicaCon
pathways.
TRUST
If
you
are
asking
people
to
provide
sensiCve
informaCon
how
can
you
create
trust
so
that
they
will
feel
safe
and
comfortable
to
provide
informaCon?
Who
will
help
you
achieve
this?
(community
leaders,
etc)
and
how
long
will
it
take?
TIMELINE
Think
carefully
about
the
Cme
it
will
take
to
launch
your
campaign.
If
you
are
planning
on
using
dierent
media
plan
for
Cme
to
contact
radio
staCons,
money
for
prinCng
iers,
and
more
Cme
to
build
relaConships
and
trust
with
community
leaders
who
may
promote
your
project.
SMS
USE
The
presence
of
mobile
networks
does
not
always
mean
that
people
will
easily
and
freely
SMS
text.
If
you
expect
most
of
your
informaCon
to
come
by
SMS
,
invesCgate
whether
or
not
people
are
literate,
feel
comfortable
texCng,
etc.
COST
Although
using
more
media
channels
increase
your
campaign,
it
will
likely
also
increase
the
cost
of
your
project.
One
inexpensive
and
very
eecCve
way
is
to
use
community
leaders
and
community
organizaCons
but
this
requires
Cme
and
trust-
which
you
may
not
always
have
especially
during
an
emergency
or
crisis.
TIPS: Many users believe in the importance of advance outreach via media coverage, adverCsing, workshops & demonstraCons.
The Message
This web banner was one of many message that Building Bridges use to have people map peace iniCaCves around the world.
MORE EXAMPLES
TIPS: There are different ways to manage expectations, like conducting local media campaigns, or sending automatic responses to
messages saying "thank you for message, now the message will be processed", and so on. (Anahi)
Messaging / Campaign
How will people find out about your initiative?
How will people find out about your initiative? What communication pathways will you use?
Write down some sample messages that you will you for your campaign
How will you manage expectation from communities and the crowd?
TIPS: If you have Cme, we recommend that you touch base with your partners and users to see how they will interpret your message.
Training
Appendix
Local
AssociaCons
Key
node(s)
Community
Individual(s)
Policy
CollecCve Report
-Informa@on management -Maintain ow of informa@on from nodes to commiNee - technical knowledge to maintain plaWorm infrastructure
Rapid response
CommiZee
-validate/monitor/and analyze informaCon - local organizaCons rapidly respond -Coordinate & collecCvely present informaCon to government -key representaCve of organizaCons
Government
-Governor
-Secretariats
-Advisors
- Monitoring
Local Responders- police, redes social Agencies/Intl Orgs- PDP, defenseria, NGO, UN
Next Example
Return
Departamento del Cesr United Nations Development Programme Redes United Nations Office for the Coordination of Humanitarian Affairs
Next Example
Return
Next Example
Return
Toolbox
#3
Real-Time Evalua-on
So youve done all of the planning to implement your Ushahidi/Crowdmap pla?orm. Were here to help you self-evaluate how its working!
The project has : Goals from implementa5on toolbox, panel #4, imported here
Strongly disagree
disagree
undecided
agree
Why?
Which
parts
of
your
project
is
working
well?
and
helping
to
achieve
your
objec-ves?
Partnerships
Communica-on
Technology
Campaign/Messaging
Informa-on
Flows
Ac-on/Feedback
Maps/Visualiza-on
Informa-on
Security
Volunteers/Teams
Other,
please
describe______
Which
parts
of
the
project
need
improvement
and
may
be
preven-ng
the
project
from
achieving
its
objec-ves
Communica-on
Partnerships
Maps/Visualiza-on
Technology
Informa-on
Security
Campaign/Messaging
Volunteers/Teams
Informa-on
Flows
Other,
please
describe______
Ac-on/Feedback
User
ac5ons:
A)
select
2
from
working
well
and
2
from
needs
improvement.
B)
select
all
that
apply
So
now
youve
learned
from
&
evaluated
your
project
What
are
your
ac-on
plans
for
change?
Findings
(EXAMPLE)
Partnerships-
We
have
a
strong
rela-onships
with
our
community
partners,
we
trust
each
other.
We
have
monthly
mee-ngs
to
keep
our
rela-onship
strong.
(SUCCESS!)
(EXAMPLE)
Informa-on
Security-
our
informa-on
security
plan
is
working,
Our
servers
are
secure
and
there
is
a
con-ngency
plan.
Our
partners
provide
monthly
feedback
about
their
concerns.
There
has
been
no
security
events
yet.
(SUCCESS)
(EXAMPLE)
Volunteers-
It
has
been
hard
to
keep
our
volunteers.
They
say
the
long
hours
and
travel
are
dicult.
It
is
dicult
for
the
project
manager
to
train
each
new
volunteer
every
day.
(CHALLENGE)
Some way to auto-import the selected categories on slide 6. Here is a RTE example
Ac<on
Plan
(write
your
ac5on
plan
here
)
We
will
con5nue
to
have
monthly
mee5ngs,
and
will
look
for
people
to
support
the
workshop
space
to
help
con5nue
to
bring
people
together.
Check-in
(when
will
you
check
in
to
see
how
youre
doing
with
your
ac-on
plan?)
Partnerships Checklist
1. Which partnerships in your project are working well? Why? 2. Which partnerships in your projects are dicult? Why? 3. Is there trust between your partnerships? Why or why not?
4.
If
your
audience
include
local
communi-es
are
they
also
your
partners?
How
is
it
going?
Technology Checklist
1.
How
is
the
technology
support
(
example,
server
support,
PHP
support,
***)?
What
are
the
challenges?
2.
Do
you
feel
your
partners,
volunteers,
and
audience
are
comfortable
with
the
technology?
(SMS,
ushahidi
instance/crowdmap,
etc,
viewing
the
map)
3.
Are
your
volunteer
or
teams
who
are
responsible
to
processing
messages,
reports,
comfortable
with
the
technology?
What
are
the
challenges?
Campaign/Messaging Checklist
1.
Do
you
believe
that
your
audience
(or
crowd)
understand
the
purpose
of
sending
in
informa-on?
Why
or
Why
not.
2.
Do
you
believe
that
your
audience
understands
what
you
are
doing
with
the
informa-on?
And
how
they
will
be
able
to
see
the
results?
3.
Are
the
expecta-ons
of
your
audience
the
same
as
your
expecta-ons?
Why
or
Why
not?
4.
What
needs
to
con-nue..
to
keep
your
messaging/campaign
successful
and
sustainable?
to
improve
your
campaign
strategy.
1.
Are
you
collec-ng
the
type
of
informa-on
you
planned
on?
Is
it
helping
you
achieve
your
goals
and
objec-ves?
How?
How
not?
2.
How
are
you
analyzing
informa-on
(
verifying,
conrming,
mapping)
What
is
working
well
and
what
can
be
improved?
3.
Do
you
feel
now
that
your
categories
are
appropriate,
why
or
why
not?
3.
Click
here
to
evaluate
and
revise
(
or
re-evaluate)
your
informa-on
ow
diagram
Ac-on/Response/Feedback Checklist
1.
Is
the
informa-on
collected
being
used
in
the
way
you
planned?
2.
Have
you
been
communica-ng
back
to
your
target
audience/or
the
public?
3.
How
well
do
you
and
your
partners
feel
the
report
and
maps
are
returning
to
decision
makers
for
program
change?
4.
If
it
has
been
more
dicult
than
you
thought
to
share
informa-on
and
the
maps
with
your
par-cipants
and
audience,
why
do
you
think
this
is
happening?
5.
Click
here
to
see
your
informa-on
ow
and
feedback
diagram,
what
would
you
keep
the
same
and
what
would
you
do
dierently?
Communica-ons Checklist
1.
Are
your
par-cipants/crowd
communica-ng/sending
you
informa-on
in
ways
that
you
thought?
Why
or
why
not?
2.
What
part
of
these
communica-on
successes
are
due
to
technology?
3.
What
part
of
these
communica-on
successes
are
due
to
trust,
other
reasons?
Maps/Visualiza-on Checklist
1.
What
do
the
dots
on
the
map
mean
to
your
project?
To
your
par-cipants?
To
Others?
2.
Are
people
specically
using
the
map
for
decision
making
and
ac-on?
How
are
they
using
it?
If
they
are
not,
what
are
they
telling
you
as
the
reasons
why
they
are
not
using
it?
3.
How
do
all
of
your
audiences
have
access
to
the
map?
Do
they
know
the
way
to
nd
needed
informa-on
on
the
map?
If
they
cant
or
have
diculty,
why?
How
have
they
told
you
ways
to
improved
the
access
and
nd
informa-on
on
the
map?
1.
Do
you
have
a
current
program
strategy
for
privacy
and
security?
If
so
what
is
working
well,
what
will
need
improvements?
If
not
write
here
what
your
strategy
will
be.
2.
How
is
your
project
managing
the
risks
of
sharing
informa-on
(including
the
maps)?
3.
Ask
all
of
your
partners
and
contact
your
par-cipants
to
ask
them
if
they
feel
secure
providing
informa-on.
List
the
answers
here.
3.
If
your
partners
and
par-cipants
tell
you
they
are
worried
about
privacy
what
are
their
recommenda-ons
on
improving?
Teams/Volunteer
Checklist
1.
2.
3.
3. The analysis & evaluation module will support users as they actively collect, map and make decisions with their Ushahidi instance. It will also provide tools with which to evaluate the project helping organizations report their successes and challenges to donors, the user community and others. This image is an example of a screen shot of the Assessment Tool. Organizations can learn about the instance types (icons on the left) and link to examples of how other organizations have used Ushahidi. We hope that this will help new and existing community users learn and make decision for their projects and programs. Jennifer is off to Nairobi this week to share our progress and get feedback from the local Ushahidi community. We are completing our first case study on Unsung Peace Heroes and Building Bridges. These two projects used Ushahidi to map peace related information. Unsung Peace Heroes was designed to recognize individuals who participated in peace efforts in the violent aftermath of the December 2007 Kenyan General Election. These heroes often risked their lives to help members of their community. Building Bridges is an extension of Unsung Peace Heroes. Building Bridges was designed to map peace initiatives throughout Kenya as well as recognize and reward Kenyans who participate in peace initiatives and promote conflict resolution. These two projects offer interesting lessons for the greater Ushahidi community. Media Focus on Africa Foundation and Butterfly Works, the implementing organizations:
Relied on strong partnerships with local organizations. Used multimedia strategies including radio, television, newspaper and online advertising; interpersonal communication at events throughout Kenya; mobile communication and social media. Produced materials in English and Kiswahili. Had clear goals and timelines. Customized the Ushahidi platform to meet their needs. This was particularly true for Building Bridges as they integrated Ushahidi with Joomla, a free and open source content management system.
The full case study will be available for download later this year. As we wrap up this phase, we will move onto phase two, which includes a case study ofUchaguzi in both Kenya and Tanzania and completion of the self-assessment tools. We look forward to continued feedback from the Ushahidi community.
Schedule (subject to change) 10:00 10:30 Introductions and Research overview 10:30 10:45 iHub Research Program 10:45 11:00 Break 11:00 11:15 Ushahidi.ke demos 11:15 12:30 Toolkit interactive sessions 12:30 13:30 Lunch 13:30 14:45 Policy working groups (eg. usability, security) 14:45 15:00 Break 15:00 16:00 Group Brainstorm and Next steps We will provide lunch and toolbox documentation. We ask that participants register to help us plan accordingly. The Ushahidi.ke Evaluation Launch is in partnership with the Harvard Humanitarian Initiative and supported by the Knight Foundation. More details
We will be using Meetup to build community events around the world. Whenever possible, well provide streaming and interactive participation. There will be more event announcements soon. If you have ideas or want to host a meet-up, Id be happy to hear from you. Thanks! Heather L.
Highlights:
OUTREACH: Communication targeting of audiences differed for rural and urban areas and diverse age groups. For example, rural areas were reached by radio rather than newspaper. However, the radio programs were sometimes aired in different vernacular language to accommodate all listeners. The impact was great, even neighbouring countries such as Uganda received the information from the website and created their profile online. This required more intensive report verification based on location. The power of mobile in .ke is amazing. Telco providers like Safaricom will allow short codes to accompany hash-tags which will redirect to a website, like Building Bridges. The campaign was successful due to the SMS program and pervasive use in .ke. REPORTS: As part of the campaign, the Building Bridges team telephoned over 6000 people. These calls were often to verify the content or to request clarification. Some content was translated into English for the map from telephone calls. Some reports were web-based submissions in Swahili. It would have been useful to have a bilingual map: Swahili and English. People who filed reports often required feedback or follow-up on their content. These involved counselor-type telephone calls. This community approach was essential to build comfort and trust. Some report providers preferred that their content be provided verbally and their report listed by peacemaker to maintain their privacy. The majority of the reports were submitted via SMS with the other reports far below in numbers (in descending order): telephone calls, email and, lastly, web-based form reports. KEY LESSONS: The plan was revised to accommodate more SMS reports (sometimes 700 a day). Education (digital literacy) was a large component of the telephone calls for feedback loops. The number targets were given less weight over time in lieu of qualitative content and relationship-building with the reporters. And, this type of project is easily replicable in other regions using Ushahidis platform.
A very special thanks to Rukia and Tobias for their contribution to this project and for their time today. Check out their other projects including mobile education games such as Get H20. There are still a few spots left open for the Ushahidi .Ke Evaluation Launch. Register via Meet-up. We will be testing toolboxes, talking best practices and building forward. Heather L.