This article is intended to help organizations be successful in a social-good hackathon. Its a mix of experience and vision, and, by no means intended to be a hard-and-fast rule. Using these guidelines will help you be more successful.
Types of organizations that are a good fit
- Localized effort of a wider-scope problem: There are many social issues that affect citizens across the city and country and around the world. Solving a problem that has the potential to propagate and give value to others will have the most impact. For example, imagine a project of listing free recreational activities on a map could be used for community organizations across a city but likely applicable across the country too.
- Well-connected with city-wide and nation-wide counter parts: To ensure a project can have the most impact to the organization and outside the scope of the organization, it helps to connect with other similar organizations to share news of the hackathon as you may gather some lessons learned or other supporters to continue the projects after the hackathon. At the very least we may find users or testers of the software. For example, a health community centre would likely have related, interested parties across the city, country and connecting in advance is a good way to gather requirements to make a product suitable for a wider audience.
- Affinity for technology experimentation: It helps when you or your organization understands the opportunity that exists in experimenting with technology and adopting new concepts. It is most important for the organization to understand the value of access to smart people who like to experiment and do good with technology but having an appetite with the organization is a plus.
- Organizations that value Collaboration, Transparency, Sharing & Empowerment: Seems obvious but its not a given. It may be ingrained in people if not in the organizational DNA. If the values sit with the people and not the organization, the hackathon may be a success but the sustainability of the project might be at risk.
What makes up a good project
- The project itself should be Specific, Measurable, Attainable, Relevant, Timely.
- The project owner will want to present well to garner support.
- The project itself should be technically challenging and somewhat unique.
- The technology doesn’t exist and if it does the project owner needs to research and evaluate precedent. We don’t want to re-invent the wheel, but more importantly, we want to promote concepts of sharing and collaboration.
- The project is a concept that can be shared with counterparts across the country or around the world. Build it to be shared and make it sharable by design.
- The project should be operational and help support programming- as contrasted to administrative tasks or fundraising tasks. While these tasks are important, the impact on the cause is less measurable.
- A project that can continue to grow and evolve.
- A project should be architected and named such that it can be shared with other, similar organizations. For example, a project name or project nomenclature shouldn’t include the city name or a building name or an organization name but rather an appropriate name for the app.
What projects don’t work well
- Website design or redesign
- Social media properties
- Fundraising or marketing projects
- Games – these projects are too big
Some examples of projects that worked well
- Directory of businesses. In this case used for the Social Enterprise sector. See We All Profit: Ottawa Social Enterprise MarketPlace and WeAllProfit.ca. This particular project started with a team of 8 and then reduced to 4 to get completed. This project is deployed for the organization that started and has been shared to other jurisdictions.
- A simple tool that does one thing such as Data Integrations for Ten Oaks Project. This simple tool extracts data from one system and loads it into Salesforce. This project started with a team of 4 and reduced to 1 to get deployed.
- Mapping projects are usually a good fit. eg Plotting locations on google maps (or OpenStreetMap). The requirements are easily communicated, foundational technology and toolkits are readily available and participants can really make the most out of the weekend. See Ottawa Community Housing Foundation – Directory of Recreation Activities and Locations and a FairVote.ca Canvasing Tool. The projects are ideal for 4 – 6 people but really need a mapping expert (can be google maps as well as open street map) to be successful.
- IoT (Internet of Things, devices and sensors connected to the internet) projects are possible and can be successful but need a lot of preparation in advance. They tend to be successful because they attract the best talent and the advance preparation certainly helps. Advance preparation would include procuring all the hardware necessary and enlisting a champion/expert to ensure requirements are complete. See Growing Futures Hydroponic Monitoring System and HiveSense: The Beehive IoT Project. These projects need diverse members and the participants will likely split up into these possible teams: hardware, embedded systems software, cloud systems software, and maybe visualization.
- Platform based projects – eg. those built on WordPress, Drupal or Moodle -are also a good fit because you can leverage existing technology via plugins and themes and there are a lot of developers. See Refugee Sponsorship Support Program – Lawyer Onboarding and Gourmet Express – Order Platform. These projects can support larger teams because there requirements in design and development but also content.
What can be done to ensure sustainability
Organizations can follow some of these ideas to help project continuation after the hackathon.
A few key concepts would be:
- Preparation in advance to secure funding for ongoing development to pay or hire developers to finish the project.
- Look for grants before and after.
- Investigate partnerships that can enable funding for a project.
- Aim to have a prototype that can be used in conjunction with funding.
- Acquire contact information of team members who are willing to stay involved.
- Engage with developers and follow up. Have initial meeting on the books during the weekend. Have follow up meetings in-person or in the Slack channel.
- Stay connected on Slack.
Organizers can also put effort into building the infrastructure (technical and otherwise) that will support the projects as they go from hackathon weekend to further development:
- Encourage (very strongly) developers to use github (or equivalent) for code sharing.
- Have infrastructure available to host apps. A relationship with a cloud provider such as AWS goes a long way to provide a technologically advanced platform for development. A secondary benefit is the organizers have the resulting code and infrastructure after developers leave the weekend. We have traditionally provided ongoing free hosting for all RHoK projects. We do this through an AWS sponsorship.
- Connect with local Civic Tech group to provide ongoing support and venue for working on projects. Also a good place to find extra help or other talent to bring project to completion.
- Find a company who may want to adopt project after hackathon weekend. This concept needs to be explored further, but we have had interest in this.