13 tEAms composed of 88 of the top designers, researchers, strategists, and engineers


What it looks like

Two weeks before the hackathon, teams will be sent a research packet and problem brief so participants can understand the problem space before the event begins

The hackathon will last for 12 hours on Sunday, October 1st; a more specific agenda will be sent to participants several weeks before the event

A keynote and focused presentation will ensure all teams are primed and headed in the proper direction

During the hackathon, participants will use the research provided, conduct their own, and speak with stakeholders we'll have on-site to develop human-centered strategies they can use in prototyping (not building) their solutions

Participants will comprehensively document work to prime output for continuity

Teams will have a technical consultant off-site to ensure all solutions are grounded in reality and feasibility

At the end of the day, projects will be pitched to a panel of distinguished judges

what happens next

The hackathon must have impact. but participants are almost never in a position to carry on their projects afterward, so that's when we step in and take over

For the first two weeks following the event, hackathon output will be read, re-read, re-re-read, analyzed, and synthesized

Our projects will begin to take shape based on the hard work and expertise of our participants

As our team conducts our own research and experiments, we'll be able to determine which strategies are likely to be both feasible and effective so we can stretch our limited resources as far as they may possibly go

We will collaborate with refugee orgs to test our ideas in a cost-effective way

After thorough testing, we will build that which should be built using one of our development partners

We will deploy our solutions and grow our team