# HackTogether

Guides, tips, and templates for running issue-focused, social good hackathons.

## Hosting a Hackathon That Centers Grassroots Movements&#x20;

As we close in on the 2020 election, there’s an enormous surge of civic tech enthusiasts and eager volunteer technologists seeking and try to counter the chaos. We today have a lot of opportunities to lift up and build community with the activists, organizers, and organizations that have been laying decades of groundwork on the most important social issues facing the world.

Hackathons can be one way to not only re-center these organizations and their increasingly important work, but onboard new people who are eager to learn, work, and channel their energy and multi-disciplinary talents productively in to learning about and joining this movement, and forging lasting relationships.

In this guide is a non-exhaustive list of templates and tips on how to run a civic or social issue hackathon. This is just one model that we’ve found helpful in organizing the Abortion Access Hackathons, assisting with the Debug Politics hackathons, and helping to bring social issues in to “regular” hackathons like Ether Hack.

{% hint style="info" %}
Have suggestions you'd like to add to this collection of open source resources? Open an issue at the [Hack Together Guide Github](https://github.com/kate-rose/HackTogether).
{% endhint %}


# Choosing your theme

**Pick an institution and defend it.**

Who is already doing the work that moves you most? Why does it speak to you? What is your personal experience with the issue? Keep this story and this connection at the front of your mind as you move through the next steps to turn the theme from an idea in to an event that directly supports the issue's grassroots community.

1. Do your research and find who is already doing this justice work to reach out to. The sweet spot is often orgs that are trying to grow their grassroots work and unlikely to have a dedicated technical team.
2. Email them, @ them on Twitter, find them at an event, talk to your friends and get an introduction to a few groups already working on something you care about.
3. This starts with thoughtful outreach to about 10+ organizations who are often very very busy, who may need an introduction to what is a hackathon anyway, and what tech volunteers specifically can do for their organization.

Key Organization Outreach tips:

* invite orgs to “bring their wishlist” of projects that could use some tech volunteer lift.
* highlight that these projects can include (and most often do) resolving admin load that plagues most nonprofits
* suggest bite-sized projects like redoing a website, building a database from spreadsheets, or prototyping an experimental tool that can be hard to justify on their usual budget

These orgs will lead your hackathon teams on the day of the event, and it’s important to note to them that they don’t have to be a “tech person” or an expert to do this. They’re already doing this work every day, just with a different terms, and we’ll help build a shared vocabulary together in the tips in the rest of this guide.


# Organizer Roles

No person is an island, and the best hackathons have lots of organizers to divide and conquer among the areas of need. People who can make great co-organizers:

* hackathon vets
* civic organizer vets
* people new to tech
* people enthusiastic about an issue
* community organizers
* event planning experts

You should start your recruitment as far out from the event as possible, but 3+ months at least is recommended. The easiest way to recruit is to tell everyone you know, and new people you meet, you're planning your event, and asking if they know anyone who would be a strong fit.

Cold emails can go a long way in communities of folks who all care about the same issues. Don't be afraid to reach out to the people you look up to at organizations whose work you follow, subject matter experts you follow on Twitter, or tech folks in your hack circles whose open source work you find useful. You'd be surprised who has hackathon experience, and has considered putting on one of their own if they found the right co-conspirators.

It's critical to make sure that your organizing team doesn’t all look like you. The best way to build an inclusive hackathon is to have an inclusive leadership team. Racial, gender, sexuality and presentation, difference in abilities or technology preferences, people with different adaptive and functional needs, all should be helping to organize your hackathon.

Invite your fellow organizers to take complete areas of ownership including:

* volunteer recruitment
* participant recruitment
* tech company outreach for sponsorship
* vetting applications
* keeping nonprofits engaged and supported
* coordinating venue including security/catering needs (see sponsorship)
* marketing and press outreach

Check in once a week on a call or in person meeting. Make sure you let people decide how best to get their own work done, just express what you need, and the dates by which you need it. People accomplish some really cool things you could have never thought of when you give them sufficient autonomy.

As the lead organizer, your job is to help ensure your fellow organizers have the information and resources they need to do their best work. During your check-ins, ask if they have any blockers keeping them from accomplishing their next task, and then try to focus some time on helping to clear their path.


# Sample Volunteer Roles

All the organizers need to be hands on to get people to this event and keep them motivated to cross the finish line on Sunday. Reiterate to your volunteers that there is always something to do during down time, whether it's tidying up, checking in with groups and ensuring everyone has all the resources and supplies they need, or preparing for the next event on the schedule.

| **Role Title**                                                                                                                   | Responsibilities                                                                                                                                                                                                                        |
| -------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <p><strong>Ambassador</strong></p><p>Available the week before and entire weekend</p>                                            | Understands the agenda of the event and could field tough questions from local media if necessary. Can deal with tough situations while maintaining composure. Delegates tasks well. Focuses mostly on media and community outreach.    |
| <p><strong>MC</strong></p><p>Available the week before and entire weekend</p>                                                    | Owns the mic. Can keep an audience entertained. Makes sure everyone is included and having fun. Keeps the event on schedule. Provides consultation to teams.                                                                            |
| <p><strong>Coordinators</strong></p><p>2-3 available at all times throughout event</p>                                           | Quick on their feet. Proactive. Willing to help with anything, including helping introduce wandering attendees to a group to work with. Not afraid to get their hands dirty. Friendly, personable, and curious. Productive in downtime. |
| <p><strong>Photographer & Videographer</strong></p><p>Available on Friday, occasionally on Saturday, and for demos on Sunday</p> | Anticipate memorable moments. Interview consenting participants with provocative questions. Gets filmed media off cameras and onto the internet efficiently. Organized, personable.                                                     |
| <p><strong>Security</strong></p><p>Full time at event<br></p>                                                                    | May come with a venue. May be owned by Ambassador. Be aware that an open event format can result in wandering bystanders that can often consume a lot of organizer resources.                                                           |

Other roles, like Social Media Manager, can be necessary to the success of an event. We encourage you to add volunteer roles that suit your audience and process. You may have more complex logistical needs, help on hand for sourcing hardware supplies, or mediators to help your attendees work through difficult conversations.&#x20;

Bring your entire organizer team together to define these roles, as ideas about where help is needed are best assessed from multiple points of view, and in response to all the kinds of work already being done to prepare.


# User Interviews = Great Project Ideas

**Invite participants to do UX and issue research ahead of time**

Having organizations with existing work to do included early is critical to recruit passionate participants. Stress that there is existing work we need help with, and as participants sign up, add them to a Slack team or other collaborative tool right away. Yes, even before the event starts!

As soon as we began getting applications for our last hackathon, we added people to Slack and invited the general channel to volunteer for a UX research project. We started our UX work about 2 months out from the date of the hackathon. But taking the time to have these conversations with the folks doing the work on the front lines in this area is valuable whether it's done months ahead of time, or a week ahead of time.

Sample pre-hackathon user interview process:

1. Let your experience researchers and UX folks lead the way, deputize willing volunteers to lead the UX group and give them independence.
2. Make intros with participating orgs so volunteers can meet/call to discuss their workflow and areas where they hit friction in trying to get their jobs done.
3. If possible, provide a study guide to your interviewers with suggested questions to help guide them in their conversations. An example study guide can be found [at this link](/templates-and-resources/user-research-interview-guide).
4. Distill the key takeaways from your interviews in to a deck that can be distributed to participants at your event.
5. Add this deck to a folder of resources for all participants to get background on the issue, including your study results, stats, articles, and intersectional issues that affect this problem set.

Remember, working with your UX team is also a great time to get organization feedback on your code of conduct and agreement (including open source licensing suggestions) for participants, and to ensure that they’re available to read in your distributed materials and prep for participants. Copies of some CoC examples can be found in this repo.


# Fundraising Tips

Having an organization that can receive donations is helpful, but absolutely not required to pull off a great event. You're basically hosting a party with computers, just a space, internet, and food are all that's really needed to ensure a hackathon WILL happen, and these tips can get you started:

* Get a free venue (most important first step!) usually someone’s tech company has a giant all-hands space and they can sign up to host for free.
* Invite tech companies, especially developer products, to donate free software, press contacts, or individual concrete expenses like “can you sponsor $1k for food?”
* Once you have a host and a sponsor or two, note that to other potential sponsors in your emails and meetings by name, solves the “first penguin problem.”&#x20;
* If you don’t have a sponsor org to channel nonprofit donations through, asking for in-kind donations of stuff like paying a food bill or sending refreshments via delivery service tends to be easier for donors.


# Sample Schedule Overview

This schedule is for the organizers but there are key events that the participants need to be aware of too. It’s the MC's and Ambassadors' responsibility to make sure that everyone knows what the next 24 hours look like at all times. Also, consider having a large omnipresent countdown timer running.

| Timeframe                  | To-do                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 2 months prior             | Secure space: consider security, A/V, high capacity wi-fi, and live streaming capabilities                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
| <p>1 month</p><p>prior</p> | Send email to all event participants and let them know the format of the 3-day Hackathon, the logistics for each day, and application                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
| Week of event              | Visit space to test PA and video system.  Ensure you're able to stream on Facebook live.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
| Thursday                   | <p>Send email answering the following questions:<br></p><ul><li>Where?</li><li>When?</li><li>Bring your own water bottles; leave no trace</li><li>What’s an Elevator Pitch?</li><li>Team building exercise</li></ul>                                                                                                                                                                                                                                                                                                                                                                         |
| **Friday**                 |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
| 7pm                        | <p>Check-in; mix & mingle<br></p><ul><li>Check names against list of registered participants</li><li>Have walk-ins register on an iPad (having more than one can help avoid a bottleneck)</li><li>Create a name tag and list expertise (e.g., design, engineering, hustle, marketing, policy, product, research)</li><li>Refreshments (don't forget non-alcoholic options) and light hors d'oeuvres </li></ul>                                                                                                                                                                               |
| 8pm                        | <p>Welcome!<br></p><ul><li>Ambassador introduces Hackathon</li><li>MC acknowledges sponsors</li><li>MC pep talk; sync with organizers if this is your first time</li><li>MC discusses pitch logistics for evening and weekend schedule</li></ul>                                                                                                                                                                                                                                                                                                                                             |
| 8:15pm                     | Elevator Pitches - [Sample Pitch Process](/hackathon-weekend-logistics/sample-elevator-pitch-process)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
| 8:30pm                     | Groups form, introductions and initial planning work begins.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
| 12am                       | Go home!                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
| **Saturday**               |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
| 9am                        | <p>Good, strong coffee</p><p>Work until lunch<br></p><ul><li><p>Focus on project scope</p><ul><li>What does this thing do?</li><li>What does this thing not do?</li></ul></li><li>Mockups</li><li>Prototypes</li><li>Plan of approach</li></ul>                                                                                                                                                                                                                                                                                                                                              |
| 12:30pm                    | <p>Lunch & idea feedback while people eat<br></p><ul><li>Live QA with MC and “experts” (1-2 people)</li><li>MC asks each team to summarize idea and scope of project</li><li>MC and other teams challenge each idea and lend outside perspectives</li><li>This should be fast-paced </li></ul><p>For participants: have a clear plan; know what you’re building and what you’re not building (sometimes more important!)</p>                                                                                                                                                                 |
| 1:30pm                     | Work, work, work                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
| 6:15pm                     | Invite participants to an optional, lighthearted stretch, deep breathing, or aerobics/calisthenics session; think Richard Simmons                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
| 6:30pm                     | Dinner                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
| 12am                       | Go home                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
| **Sunday**                 |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
| 9am                        | Light breakfast & coffee                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
| 12:30pm                    | Lunch                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
| 2pm                        | <p>Dry runs<br></p><ul><li>Teams must perform a dry run in order to present live</li><li>MC and any other startup pitch “experts” (1-2 people) give feedback</li><li>If a live demo is available, trim introductory slides and emphasis the demo—cut the fluff, where possible</li><li>Aim to have demos last no more than 5 minutes, including A/V setup</li></ul><p>For participants: try to be ready with a live demo. A deck of slides are a good backup. Make sure there is some call to action (e.g., “if you’re interested in hearing more, visit… and sign up with your email…”)</p> |
| 4pm                        | Open doors for Product Showcase                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
| 5pm                        | <p>Demos!<br></p><ul><li>Ambassador gives another spiel about the event</li><li>MC again acknowledges sponsors</li><li>Optional keynote - try to keep it to 20 min</li><li>Teams come up and give 5 minute presentations</li><li>MC brings everyone up at the end to congratulate the teams</li><li>MC does shout outs to a couple key players of the weekend (participants and/or organizers)</li></ul>                                                                                                                                                                                     |


# Sample Elevator Pitch Process

In the days leading up to the hackathon, you might choose to have people registering for the event and adding them to a shared space like a Slack team. This can be helpful in allowing people to:

* Add Ideas to a shared Google Doc&#x20;
* Create a Slack channel for their idea, and add the Slack channel name to the shared ideas Google doc

While this can help groups get a head start, there's still plenty of room for new groups to pitch and form. One format that we've seen work well goes like this:

1. Everyone gets 30 seconds to present an idea; timer required
   1. The person making the pitch also gives the Slack channel name where folks will initially coordinate (e.g. #seethespectrum)
   2. The person making the pitch states where in the room they'd like interested attendees to gather
   3. Event coordinators help ensure the Slack channel can be made immediately
   4. Set the Purpose of the Channel as a summary of the pitch
   5. Add the person pitching to the Channel
   6. Set the topic of the channel to "Project lead: \[name of person who gave the pitch]
2. Event coordinators should also summarize pitches on a whiteboard, so that folks don't forget which is which after they leave to find their groups.


# Tips for Day-of Success

These tips are for the organizers, try to discuss them with your team during one of your prep meetings before the event.&#x20;

1. **You are the Hackathon** — This is an idea the event organizers must take to heart and pass on to the participants. Be attentive, listen, and anticipate opportunities to lend a helping hand. Spread that mindset.
2. **Quality products are crucial to the hackathons success** — The success of these hackathons is measured by the quality and subsequent success of the products being built. Keys to quality products:
   1. Exercising important fundamental skills
   2. Great team dynamics
   3. Hands-on support from industry experts
3. **Have fun** — People show up on the first day because they like what you have to say, they stay for the rest of the weekend because they're having a good time and building relationships. This event is exhausting so having fun with it keeps up everyone's stamina. Look to the MC to organize stretch breaks, icebreakers, and to generally keep the mood light hearted. Manage perception. If you look like you’re in a bad mood, attendees will be in a bad mood.
4. **Leave no trace** — Do not provide water bottles. We learned this the hard way. Set the expectation upfront and lead the troops in daily sweeps. Have fun with it. Leave the venue better than you found it.
5. **Focus products around real, tangible problems** — a social good hackathon is a forum for anyone to step up and work on any idea they think will help organizations and organizers doing this work to tackle institutional issues. But it’s also important that we solve meaningful and relevant problems. To that end, these hackathons should be able to help participants connect with not just the issues at the event, but the issues in this space in general, inspiring them to take action beyond the weekend.
6. **Set an objective** — At our hackathons we asked participants to "find a barrier their organization experiences in doing their work and build something to fix it." This language was repeated over and over again and was useful with the press too.
7. **In Slack we trust** — Slack (or a similar collaboration chat tool) is a Hackathon’s secret weapon. Some suggested channel conventions that can help keep things organized:
   1. Participants are added to a #general local channel (e.g., #nyc) automatically.
   2. Anyone that wants to get more involved should be invited to #organizers, a private channel. They can also be added to other channels as necessary.
   3. Product channels are “top level.” In other words, an idea like #abortionmap requires no special prefix. This is to reduce complexity and encourage participation. It is crucial that these channels have the purpose set.
   4. There are also general channels for engineers, designers, brainstorming ideas, etc. These are all prefixed with #\_ to keep it clear that they’re not products.
   5. Some ideas get merged into others and some ideas are abandoned. Unique ideas with merit can snooze by adding #zzz\_ to the front. Otherwise, they should be archived.
   6. Profile pictures make a huge difference. Whenever you see someone without one, politely explain that a profile picture makes it easier to put a face to a name and makes the whole group more friendly.

Add your own tips for success based on the experiences your volunteers bring to this event. Have more we should add? [Reach out and let us know](https://github.com/kate-rose/HackTogether).


# Centering Orgs at the Event

Tactical ways to keep movement leaders and their expertise at the forefront of your hackathon activities and conversations

If you’re lucky, you’re about to get a few hundred people in a room who have already opted in to learning about this problem and working on it, and you have an amazing opportunity to help onboard them to this movement’s community for the long haul. This hackathon is about making space, so the resistance groundwork and its leaders can fill it.

You can do this a few ways:

* Ask an organization to give a keynote intro after you give the introduction to the functional details of the weekend.
* Invite organization staff to walk around to the different teams to find out what they’re working on and offer feedback.
* On Saturday, ask organizations to give lightning talks on their mission or a core issue they encounter in their work during lunch.&#x20;
* Invite an organization leader (especially an elder!) to give a short keynote talk or fireside chat before demos start on Sunday.
* Invite organizations to be your “judges” and give feedback after demos.

True magic can happen when the voices of people who traditionally don’t get the mic in tech spaces now fill the room.&#x20;

You’ll find that when the final day of your hackathon is done you’ve now put hundreds of people through a weekend bootcamp on an issue that matters to your community, and to our world. Now they’ll take this experience, relationships, and knowledge back with them to their workplaces, communities, and decisions about where their volunteering and donations can do greater good.<br>


# Planning an Engineering Meetup

Ensuring your technical attendees are prepared to hit the ground running ahead of time.

Meetups for engineers, set about a week in advance, can be a great way to ensure that the day of, you have a crack team of people who know what to expect, and who can help other engineers figure out how to find where they fit in these org projects. An engineer meetup can be a great place to:

* Set up repos, Heroku instances, refresh on old skills, or learn about developer tools that can make the weekend work easier.
* Learn about intersectional issues in tech products and events, with a guided discussion by a meetup leader on ex: accessibility in design.
* Invite participating orgs to do a meet and greet, and talk live about their work and needs.
* Collaborate on writing a set of guiding code principles that can be distributed to all participants.

Remember, engineers are critical but a good balance of attendees is needed. I always find us short on front-end eng, designers, copywriters (don’t forget, engineers hate writing copy, help them!) and people to help do research to answer questions about an issue as they come up, and help put together final presentations. There is space and need for everyone’s work.<br>


# Engineer Prep Meetup Agenda

We've found the agenda below to be a good starting place for a meetup of engineers about a week before the main event. People tend to be eager to get started ahead of time, so using this time to help folks set up their resources is valuable. The attendees of this meetup also then can help get folks who can only show up to the weekend of up to speed, and be your allies in the room to keep the event and the projects moving.

* **Our mission statement - reviewing our values**
  * We are driven by a duty to serve the folks leading this movement. Our role is not to disrupt \[ISSUE AREA] — we are organizing to better serve organizations and groups already working in \[ISSUE AREA].
  * We acknowledge that workers on the ground know the fight best, and it is our role to listen and make their lives easier.&#x20;
  * In short, we build with the existing community, not for.
  * To build the power of these communities, we are cooperative, not competitive.
  * We respect the abilities of our teammates. We expect that our teams will be made up of people at different levels of understanding, and we recognize that people learning new things empower them to contribute to our cause in new ways.
* **We are working on a sensitive issue, with sensitive data**
  * These organizations are doing crucial work in a challenging political climate. \[DISCUSS SOME THREAT MODELING SPECIFIC TO YOUR ISSUE HERE]
  * To reflect the fact we’re working with sensitive data, we should follow some specific guidelines in our work:
    * Avoid discussing individual-level cases on social media! Talking about the work you’re doing for an organization and how important it is -- A+ and a great idea! Talking about the experiences of someone who hasn’t told you it’s cool to talk about their experiences is a bad look.
    * Minimize the collection of personally identifiable information to what you need to make the app run, especially at first. If you aren’t collecting it, it can’t leak!
    * Follow general best practices for development. At a minimum, use SSL and don’t store passwords in plaintext. The HIPAA guidelines (<http://info.medisked.com/blog/bid/266364/Your-checklist-for-HIPAA-compliant-software> - see especially unique identifiers and auto logoff) and 2-factor authentication are good practices to follow as well.
* **General How To Hackathon guide**
  * What to expect
    * Pitches are Friday night, and teams form shortly after
    * Advertise yourself on Slack on team channels or your #skill channel
    * You get to go home at night. Self-care is important.
    * Drink plenty of water! Take a walk once in awhile!
  * Resources
    * Hackathon app skeleton repos: [there](http://hackoose.github.io/boilerplates.html) [are](https://github.com/sahat/hackathon-starter) [tons](https://github.com/developit/express-es6-rest-api) [available.](https://github.com/yhnavein/express-starter)
    * Lets also assemble off-the-shelf dev service trials. Add them here:
      * <https://cloud.google.com/free/>
      * <https://www.twilio.com/try-twilio>
* **Guide to organizing teams with technical and non-technical contributors**
  * Any contribution is appreciated.
  * If you’re excited to guide/mentor less experienced engineers, invite them to your project!&#x20;
    * Pair program the scaffolding of your project, then break up to work on sub-problems
    * Less experienced techies can test!
  * [DCAF](https://github.com/colinxfleming/dcaf_case_management) is an example of a super well-organized org built on volunteer time by folks of a range of experience levels - what can we learn from their example?
    * Narrowed goals to a very strict MVP for a single user and ignored as much other stuff as they possibly could
    * Took features in MVP and turned them into two week sprints, which let them work around things that turned out to be time consuming or hard
    * Carved features up into sub-items and steps, and had people work on them either individually or in pairs (preferring pairs!)
    * Utilized a project manager whose job it was to keep things moving, get questions by engineering team members resolved, and keep everyone well fed
    * Avoid every hard engineering problem possible
    * Got the first iteration of the product in front of end users as soon as possible


# Template Primary Event Document

A Google Sheets document set up to be the central organizing "source of truth" for running your event.

The template Google Doc linked below has been used for several different social good hackathons, and is broken in to several components:

1. Volunteer role signup tab
2. Volunteer contact info tab
3. Public schedule draft (this will be written up on a whiteboard at the event)
4. Tabs for each of the day's detailed schedules (this one presumes a standard Friday thru Sunday weekend hackathon)
5. A tab with a list of all social media and other online accounts for the hackathon, and who is responsible for maintaining them
6. Supplies and equipment checklist tab
7. Organizer areas of responsibility and check-ins tab

This document is intended to be transparent and shared with volunteers, but not all hackathon attendees unless your group finds it helpful. Make a copy of this document and change it to suit your event's needs:

[Hackathon Primary Event Document](https://docs.google.com/spreadsheets/d/1CFbg-liVdLXEEQxA7zf2Wg-ElZyKMi-wpAxSfZ_9bTY/)


# Sample Code of Conduct

Sample text for code of conduct, sometimes also called a hackathon participant agreement or similar.

## HACKATHON PARTICIPANT AGREEMENT

By entering in to the \[NAME OF EVENT] hackathon you agree to abide by this Code of Conduct. Our hackathon is dedicated to providing a harassment-free experience for everyone, regardless of the following:

* gender
* physical appearance
* age
* sexual orientation
* disability
* body size
* race
* ethnicity
* nationality
* religion
* previous hackathon attendance or lack of
* computing experience or lack of
* chosen programming language or tech stack

We do not tolerate harassment of hackathon participants in any form. Sexual language and imagery is not appropriate at any hackathon venue, this includes the following:

* hacks
* talks, presentations, or demos
* workshops
* any parties associated to the hackathon
* social media
* any other online media

Hackathon participants violating these rules may be sanctioned or expelled from the hackathon at the discretion of the hackathon organisers.<br>


# Sample Notice of Photography & Filming

The following template was used at several events and may not fit your event's photography and filming needs. We recommend having this reviewed by someone with expertise in the filming needs and legal constraints of any facility you'll be holding your hackathon in.&#x20;

This notice of filming and photography should allow attendees to opt out using a visual identifier that has been designated at your event, like a bright sticker on a name badge or different color lanyard to indicate that they do not wish to be recorded.

Please note at the end of this agreement we chose to give our attendees the right to request removal of posted materials, as this can help groups working on especially safety-sensitive issues to reassess their needs at a later date.

## **NOTICE OF PHOTOGRAPHY AND FILMING**

When you enter a \[NAME OF HACKATHON] event or program, you enter an area where photography, audio, and video recording may occur. By entering the event premises, unless indicating on your badge with \[OPT OUT STICKER, LANYARD OR OTHER INDICATOR] that you would like to be excluded from photography and filming you consent to interview(s), photography, audio recording, video recording and its/their release, publication, exhibition, or reproduction to be used for news, web casts, promotional purposes, telecasts, advertising, inclusion on websites, social media, or any other purpose by \[NAME OF HACKATHON] and its affiliates and representatives. Images, photos and/or videos may be used to promote similar \[NAME OF HACKATHON] events in the future, highlight the event and exhibit the capabilities of \[NAME OF HACKATHON].<br>

You release \[NAME OF HACKATHON], its officers and employees, and each and all persons involved from any liability connected with the taking, recording, digitizing, or publication and use of interviews, photographs, computer images, video and/or or sound recordings. By entering the event premises, you waive all rights you may have to any claims for payment or royalties in connection with any use, exhibition, streaming, web casting, televising, or other publication of these materials, regardless of the purpose or sponsoring of such use, exhibiting, broadcasting, web casting, or other publication regardless of whether a fee for admission or sponsorship is charged. <br>

You as attendee retain the right to inspect or approve any photo, video, or audio recording taken by \[NAME OF HACKATHON] or the person or entity designated to do so by \[NAME OF HACKATHON], or request its removal at any time. You have been fully informed of your consent, waiver of liability, and release before entering the event.<br>


# Supplies Checklist

| Checkbox | Item                                                            |
| -------- | --------------------------------------------------------------- |
|          | Tables and chairs (roughly 6 participants per table)            |
|          | Power strips / extension cords                                  |
|          | PA system                                                       |
|          | Large TV or projector for demos                                 |
|          | Wifi to handle the number of participants                       |
|          | Caution tape to mark inaccessible areas of venue (if necessary) |
|          | Large whiteboard or poster board for event schedule             |
|          | Paper, pens, post-its, and other office supplies                |
|          | Garbage situation                                               |
|          | Check-in                                                        |
|          | Swag: pins, stickers; ping #design for brand assets             |


# User Research Interview Guide

## Issue Expert/Participating Organization Interviews - User Study Interview Guide

This guide was composed by volunteers at the Abortion Access Hackathon and is intended to be a starting place for empowering your User Experience volunteers to come up with their own process based on their own experiences. We hope this guide fosters productive discussion on the questions and approaches that best fit your issue area experts and organizers.

### Overall objective

Get information from issue experts and organizations on: their intended process for conducting their work, their actual process in conducting their work, what the experience of their work is like, how it affects who and how many they can serve etc. &#x20;

The goal is to identify problems/opportunities for the hackathon participants to provide solutions which can make all of the above easier.

Example: Many orgs are tasked with arranging volunteers to help with transport, housing for a client. This tends to be time-consuming for fund organizers. How can we help?

This will be especially important to get a primary source for our teams to use so that they know how this experience of conducting this area of work can vary wildly from state to state based on laws, geography, and demographics.

### How we will use this guide

We’ll use this guide as a method to conduct user interviews with subject matter experts, participating organizations, and ideally those they serve.

For more info on conducting user interviews, check out these resources:

Feel free to add more resources here!

* <http://www.qualres.org/HomeInte-3595.html>
* Excerpt from “Interviewing Users: How to Uncover Compelling Insights” by Steve Portigal (excellent book!): <http://www.core77.com/posts/24830/check-your-worldview-at-the-door-and-other-advice-for-interviewing-users-exclusive-excerpt-24830>
* <https://confluence.sakaiproject.org/display/UX/Ethnographic+Interviews+-+Interviewing+and+Observing+Users>
* <http://designresearchtechniques.com/casestudies/semi-structured-interviews/>
* <https://www.interaction-design.org/literature/article/shadowing-in-user-research-do-you-see-what-they-see>
* Example video of a User Interview: <https://www.youtube.com/watch?v=Qq3OiHQ-HCU>

## Methodology

* Up to 60 minutes in length
  * Minimum 30 minutes if participants have limited time
* Each session has three roles:
  * Participant (1 or more members from organizations, providers, etc.)
  * Notetaker (silent, “transcribing” answers as much as possible, debrief afterwards)
  * Interviewer (ask primary questions and probing with secondary questions, etc. as needed, guide the conversation, debrief afterwards)

## Interview Questions

Please don’t be shy! List any questions you think will help us understand the challenges and opportunities that stakeholders face. We’ll work together to pare down and edit this list, and format it so that it can be easily used for interviews, emails, or online surveys.<br>

### Organizational/stakeholder research questions

These will help us prioritize problems to solve for movement organizations. Which solutions might provide the highest value to the organization? <br>

* What is your organization’s mission, or highest goal?&#x20;
* How does your organization define, or measure its success?&#x20;
* Who are your patients/clients? What demographic or other characteristic information do you know about them?
* As you try to reach your organizational goals, what are the challenges you’re facing?
  * Does your organization have the capacity to address these challenges?
    * If so, what are you currently doing to address those challenges?
    * If not, please describe the limitations that prevent you from addressing these issues.
  * What has worked so far? What hasn’t?
* Briefly describe: the key roles in your organization, and how they work together.&#x20;
  * Are there any challenges these role face within their own specific workflows, or in workflows with each other?&#x20;

### Financial Questions

This could be a subset from above..

* Who/what are your primary sources of funding?
  * What mechanisms do you use for development? (i.e. Networkforgood, Salesforce, events, raffles, Paypal, ..)
  * Do you have untapped resources in mind but not the means to reach?&#x20;
    * Such are running large crowdfunding campaigns, or community benefit drives.
* How much time is dedicated to fundraising/grant-writing etc?
  * What mechanisms do you use for development? (i.e. Networkforgood, Salesforce, events, raffles, Paypal, ..)
  * Who does the development work?  Is this their primary responsibility?
  * What areas could be automated?

### Subject-matter Expert interviews:&#x20;

These are meant to help us get an informed view of the space, dig into questions we have about any secondary research we’ve done.

* What motivated you to do what you do now?&#x20;
  * This question may elucidate what they think is the absolutely most pressing problem to solve, in an anecdotal way.&#x20;
* Who are the types of patients or cases you tend to see? (geography specific)
* What are the biggest challenges you face in your profession today? (geography specific)
  * What are the biggest barriers in access for your patients? (P) (geography specific)
* What is the one big thing that you would want someone to walk away understanding about the services you provide?&#x20;
  * What is the most common thing you hear from your patients / clients?&#x20;
* What do you envision for the future of the work you do?&#x20;
* How do you feel about your role in the larger movement?
* If you had the ability to pause time for a whole month and have your team work on something that would make your work better/easier, what would that be? &#x20;
  * What big, blue sky ideas have you had in this space? If we could do anything for this space without any constraints (budget, resources), what do you think of?
* What policies prevent you or your patients from accessing the care they seek?
* What policy work would you prioritize at this time?
  * How can the public better support policy change?

### User research questions&#x20;

Questions for intended end-users or beneficiaries of a particular solution.

Please take a look at all the questions listed here, so you have a sense for what you can talk about in your interviews.&#x20;

#### Introduction / Workflows

* What is your role and your day-to-day responsibilities?
* What parts of your job do you wish you could spend more time doing? What parts of your job do you wish you could spend less time doing?
  * At what stage in an individual’s experience of this issue does your organization involve itself? Where does your specific role fit in? &#x20;
* Who are your typical clients, or who usually benefits from your services?&#x20;
* What does the intake/onboarding process look like?&#x20;
  * How do new clients find you? E.g., online searches, word of mouth, advertising.&#x20;
  * What kind of information do you need to collect from clients before providing service? (How do you determine if they’re eligible?)&#x20;
  * What kind of communication is needed to guide the client through the process?
* What are some problems you encounter in your daily work?&#x20;
  * What are challenges that arise in getting funding or other services?
* How do you track impact of the services that you provide?&#x20;

#### Privacy

* How do you protect the privacy of your clients and volunteers today? (P, F)
* What concerns, if any, do you have for your security, privacy, and overall personal safety?

#### Tools + Resources&#x20;

* What tools and resources do those you serve use?  What tools and resources does the staff use to help your audience? What tools and resources do you use in your daily work?
  * To the best of your knowledge, how well are these resources you use helping these audiences?
  * Do you have concerns about any of these current tools and resources?
  * What technologies and software platforms are your staff/volunteers comfortable using?&#x20;
  * What kind of hardware? Phones, computers, tablets, PC or Mac, etc..
  * How much do you currently spend on software and other tech per month?&#x20;

#### Volunteers

* What kind of volunteers do you seek?
  * How many volunteers do you work with?
  * What are the main areas they provide support in?&#x20;
  * What kind of communication is needed to connect volunteers with those seeking your services or support?&#x20;
  * What are some problems you encounter in the process of coordinating and managing volunteers?&#x20;
* How easy is it for you to recruit for volunteers, or to organize the work they do?&#x20;
  * How do new volunteers find you?&#x20;
  * How do you determine if volunteers are eligible, what is the screening/onboarding process?&#x20;
  * What kind of communication is needed to get them volunteer training?
  * What are some problems you encounter in the process of getting volunteers trained?&#x20;

#### Direct, leading questions&#x20;

* What keeps you from helping more people? Eg facility space, human resources, funding, lack of demand (P, F)
* What do you think are potential difficulties that might arise during our work, if any, based on your experience in this space?
* Do you have an opinion of what should be available right away and what should be added later?  What might be developed over time?

#### Meta (about the hackathon)&#x20;

* Are there any other people we should be talking to or information we should be reviewing?
* Are you aware of any initiatives that have done similar work to us?  If so, how have they fared?
* Are you aware of any constraints that we need to consider?  This could include patient privacy, technology restrictions, government policy, etc.
* What is your definition of success in your work?
* What are the top 2-3 things that we can do that would make this a success in your eyes?
* Any thoughts, advice, or suggestions?&#x20;

## Interview Script

### Intro

Today I would like to learn more about your experience in this area of \[ISSUE AREA] work. The participants of our hackathon come from all walks of life and my pre-hackathon work-group’s aim is to arm them with the most direct, up-to-date, and accurate information from people like you. Your experience in this work is crucial for us to make certain that we understand the issues as you know them best.

The questions are to better inform us and the participants about your experience and expertise, so that the hackathon members can try to come up with the most relevant tools and solutions possible. Some of these questions might not appear to be related directly to the project, but I ask them in order to get a fuller picture of the space.  It shouldn’t take us more than \[insert time length] to get through all of them. Sound good?

\[Great.]

If you need clarification on any of the questions I am asking, or if you feel that a question doesn’t apply to your situation, let me know. If you don’t have an answer or opinion, that’s ok too. Depending on your answer, I might ask you to expand on what you said. I might also repeat what you said to make sure I heard you correctly. If you need to go at any point during the interview, let me know that as well and we can try to schedule a follow up. Do you have any questions?

### Questions

1. Begin with&#x20;
   1. Introduction / Workflows section
2. If stakeholder / organization, ask those
3. If provider, ask those
4. As indicated (whether directly or indirectly) by the interviewee,&#x20;
   1. Tools / Resources&#x20;
   2. Volunteers&#x20;
   3. Privacy&#x20;
5. If these questions have not been answered, proceed with
   1. Direct leading questions
6. Wrap up with&#x20;
   1. Meta / hackathon questions

### Wrap Up

Thank you for taking the time to chat with us! Please feel free to contact me if you have any further questions, or if anything else comes up. \
\
\ <br>


