Here we are again. It is the day before a mass of hackathons occur around the world. It is exciting and important. Really. We all dream of using our knowledge and technical skills for a cause.
Earlier in the week I mentioned that we need to get more organized as a global community. Inspired by my colleague, John Crowley who wrote in Time Ideas: “Stop Catastrophizing Relief Efforts in the Philippines“, I ask that we please “Stop Hacking without Specing”. (Spec’ing = build a specification = a plan)
In the past week, I have had no fewer than 30 conversations with individuals, groups, governments and fellow organizers all about How to Help. They have been so amazing in their earnest need to include the technical community. We have come along way. Folks are asking tons of questions to prepare for the weekend. This is fantastic. I am so impressed with their fresh eyes, warm response and desire to make a difference.
I have two points to make: Organizers need to get connected/organized and we, collectively, need a TOP 10.
So you want to Hack for Emergency Software for change
Welcome, we are so excited for you to join us. Sorry that we have not got this quite sorted yet. This is new ground. We are all trying to build a common language. This is my short list of considerations:
1. DO YOUR HOMEWORK
Please don’t hack or organize a hackathon without looking into what was done previously. Yes, of course, if you have a brand new idea: great! But first, check the following;
a. Random Hacks of Kindness website
c. Google foo (trust me, it sometimes works)
2. ASK THE GLOBAL COMMUNITY
d. ASK our community – ask Geeks without Bounds, ask Random Hacks of Kindness, ask Crisis Commons and ask Crisismappers. We apologize in advance that we have not organized this yet. Trust me, we know this is an issue. Join us and help make it better. We have community skype windows open, just add me and I’ll introduce you – username- heatherleson
3. OPEN SOURCE IS LOVE, BUILD ON EXISTING SOFTWARE
We don’t need another Ushahidi, Sahana, SMSSync, Person Finder, etc.
4. IF SOMETHING NEW, DOES it have an OWNER
…(And, will the owner be at your event) Serving an audience and having an owner be part of the design, testing and implementation process equals better software.
5. CHUNKS, DON’T TRY TO HACK THE OCEAN
Bring the problem down to hackathon size. The hackathon leaders need to really think about the problem statement and what is actually feasible to build or build-on during a weekend.
6. KEEP THE TECHS WANTING MORE
People are using their weekend to DO something. Every interaction is a gift. Honest. But, we want to build trust and have them know that their small contribution matters in the bigger picture. This is a really hard one. Honest. We know. Help everyone feel like they are part of the second or third wave of a very long process to build this collective effort.
7. IS IT SUSTAINABLE, USABLE
Who are you really serving if you build the shiniest tool that cannot be used in the field? Infuse your hack with local knowledge. Do they really have a need for an HTML5 enabled phone app when there is no CELL PHONE COVERAGE? Can you write a feature phone (DUMB PHONE) app?
8. Emergency Hack Lab
Emergency Hack Lab tackled the question of how to credential, task and thank volunteers in times of crisis. We hacked and built proto-workflow for the UN OCHA Noun Project sets to the Mozilla Open Badges programme. More details from session organizer Jessica Klein. You can add to this.
9. MAP instead?
Why not contribute to OpenStreetMap? The community has been mapping all week. Join the Humanitarian OpenStreetMap team and add to the map. Why is this important? UN OCHA, Red Cross and Doctors without Borders are already using it in the field and to inform their decisions. If you want to have an impact, map it!
Ok, that is part 1 – Helping the Hackathons in the interim. Yes, it is only 9 items. Please feel free to add something in the comments as I have probably missed one or 2.
What is our top 10 Hacks that we need in Crisis/Emergency response
We are here again. How can we make sure that new hackathons, new techs learn from our experiences and build on efforts that already exist? I think that we have to have a TOP 10 wishlist that we know needs to happen.
I call on my fellow global community leaders to review and improve these. AND, I promise to make this a session at the International Conference of Crisismappers next week. I am sad that we are here again, but we deserve it. We need to get more organized and help the hackathon surge folks know what we need. Yes, we are still trying to figure it out, however, we have got to get better organized.
1. Humanitarian Exchange Language
NGOs and Governments need to share information better. UN OCHA is building this to help improve flow. This hack has been part of RHOK, International Space Apps Challenge and others. The code is online.
2. Google Person Finder
Ka-Ping Yee has worked tireless to document Google Person Finder. It has been deployed numerous times in the field and has been reviewed by many people in the humanitarian field. Help improve it.
Bias alert: I am an Ushahidi former staffer and permanent fan girl. This has been deployed many times in the field. There are bugs. And, they have a new version. I believe that if we put our heads together with techs that we could make is so much better. This means that Ushahidi has to meet us half way (What are the top 10 hacks that people can do to help?) We need to see the power of citizen voices and how this project could help amplify real needs. Ushahidi can help on this. But, it needs community support. (love you guys)
4. Micromappers, Crowdcrafting, SwiftRiver and Tweek the Tweet
All of these tools work on helping people manage signal to noise. The help volunteers get engaged and curate mass volumes of information. How can the technical community help?
5. ALL YOUR DATA SETS BELONG TOO….
Last night I handed a population of Philippines dataset to Medicine Sans Frontieres. Some friends had scraped it from Philippine National Statistics website (http://www.nscb.gov.ph/activestats/). Not sure on the license, but folks need to have data with an open license to be able to layer it to maps. Why don’t we have a package of all the top datasets ready by country for emergency response?
6. MAPS ARE LOVE
We need common sharing among all the various map projects. And, a standard that lists all the active maps and provides interoperable layers so that people can pick and choose. When I say people, I mean those in the field who are helping.
Truly, we all dream of satellite imagery, citizen data, open data and sensor data on one map. Maps are love. What can we do to make this happen?
I am purposely leaving the remaining 4 items empty. What is on your list?
…..Happy hacking! Really, I am so very excited to see techs using skills to help. Just be aware, you may get hooked and change your life like I did.
I would add, “Don’t get offended when someone forks your project and does it differently / better.”
I’ve seen several of these projects start well, and then die because of personal fiefdoms. Don’t be the proverbial dog in the manger that won’t eat the hay, yet keeps others from eating the hay!
There is a more insidious back-room issue as well. Tech developments that are substantially better/more capable than what’s commonly used are going to emerge as more people get interested in the disaster space. Good people coming fresh to the scene WILL have the obvious “we can do that” and “Duh, why didn’t they just…” and the sad fact is, that many decisions have been made from personal bias, not from a purely functional point of view. The Best solution requires everyone to be nimble and discard previous assumptions in favor of meeting the overall objective.
Another important factor in disaster work is the toll that being exposed to the urgency of human suffering induces. None of us are immune and most are poorly prepared. This aspect of development needs to be addressed.
As for the user-driven approach, are we really doing a social benefit by increasing the efficacy of groups that don’t focus on community self reliance? The communication tools now available are unprecedented and pre-date the operating standards used by most “Big-Aid” agencies, and the governments they advise. Change can come from within but disruptive change comes from outside. Citizens need to be part of their own solution for anything to last, and helpers need to accept their own ethnocentric tendencies before providing ‘solutions’.
The emerging trend for coders is to do it fast and iteratively. It can be hard to take-the-hands-away-from-the-keyboard but it is a great first step. Making stuff for the heck of it is awesome for practice but spending a little more time considering the impact of a project can do more good than creating another unused app (as mentioned in the article above). Don’t be cowed though; if a new tool works better AND is lighter weight AND more reliable, etc. then sometimes it *is* time to move forward. Do so with care though. The Aid environment is still political in many ways and practicality doesn’t always win the day. Entering the space with the wrong approach will get an actively negative response, affecting the receptivity of your future inputs.
That said, uptake cannot be argued with. If ‘the people’ are using it and it serves their purpose, then ‘the helpers’ will have to adapt.
Thanks for the great list Heather. Of course connecting these efforts to the responders during an emergency can be tricky business. The ones responding (who you want to be connected to) are often extremely busy and very stressed out. Having said that, with a few of us who have been actively liaising with external groups outside emergencies, we have had great collaborations this time around (e.g. the UN-OCHA’s activation of the Digital Humanitarian Network). And, having been connected onto an email recently, OCHA just submitted at least 5 hackathon project suggestions for what people could do to help us improve philippines.humanitarianresponse.info.
So, as much as we all might rush to ‘hack’ things out now, it is probably going to be the in-between-crisis relationships that are built which will make such hackatons more successful in the future.
Rog, Om and Andrej, Thanks! I really just wanted people to consider these things and iterate on the list.
I completely agree in user-centered design and keeping that creative space for new and potentially better ideas. WE do need that too. It is hard to be fierce, but it comes from many disappointed hackers in past events.
Truly, I can’t wait to see what is invented.
I see mention of #hack4good missing: https://geekli.st/hackathon/52793a2660fb3f52d50001f8
Also some useful links at: http://opencrisis.org/typhoon-yolanda
Greetings from http://tiny.cc/CrisisCampGraz
Sahana welcomes anyone looking to contribute their tech skills to a well-established tool with 3 different deployments supporting the Philippines:
I’m completely biased as part of the Humanitarian OpenStreetMap Team but we need better mobile collection as it relates to OSM. There currently are many applications for collecting OSM data, editing, etc but they aren’t aimed at development and emergency contexts.
In the immediate time after a disaster is not when people on the ground are going to be mapping, but there needs to be easy ways to contribute during the recovery phase. These solutions need to be open source, run on cheap phones and work disconnected.
On #5, about datasets, Andrej and his colleagues have a repository of datasets for many countries called COD-FOD (ask him about the name!)
39 Philippines sets are here: https://cod.humanitarianresponse.info/search/field_country_region/164