Creating a Fusion (Hack+Policy) Project!
New to hack+policythons? Don't know what to expect? Confused about what a Fusion project is? Don't worry! Find out all you need to know in this article!
First of all, what IS a Fusion project? The purpose of hack+policythons is to bridge the gap between hack and policy and use both areas to solve the world's largest issues. This means creating both written analysis and overview of the problem, as well as providing an implementation of the solution. Some hack+policythons may allow teams to submit only a hack project or a policy brief, but a Fusion project consists of both! If you decide to create a Fusion project, you are expected to submit a hack project along with the demo video, as well as a written policy brief.
Here are some quick tips to help you get started!
Step 1: Find your Teammates
Both the hack project and policy brief are required and essential in creating a good Fusion project. This means that a team should consist of hack and policy members. Having both skills on your team is essential to ensure the team creates a well-rounded project. If you find that your team has only hack members or only policy members rather than an even split, it may be a good idea to create a Hack-Only or Policy-Only project instead. (Please check out our complete list of requirements for a Fusion project here)
Step 2: Ideation
After you've formed your team, it's time to decide on an idea. Communication is essential for any team project, but it's even more important in a team where everyone has a wide range of skillsets and backgrounds. Remember that something that seems intuitive and obvious to you may be confusing to others, so make sure you communicate your ideas in a way that both hack and policy members can understand. Work with your team members to create a cohesive project where the technology and policy build upon each other.
Step 3: Keep Everyone Updated
Since everyone on the team will be working on different areas of the project, it's important to keep everyone updated on your progress and notify everyone of any big changes regarding the direction of the project. This prevents confusion and ensures that the project comes together. It's also a good idea to let your team know when you're taking a break or going to sleep so they know when you're available.
At the end of the day, a hack+policython works very similarly to a conventional hackathon. You can find our list of hackathon tips here and our module for policy brief writing here. If you have any questions, please don't hesitate to contact an organizer on our Discord server, or email us at firstname.lastname@example.org.