Hackathon goals and executive sponsor
This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Teams run hackathons for very different reasons: morale, exploring a new platform, clearing internal tooling pain or finding the next product bet, and an event that tries to do all four usually does none well.
First tasks
- Write the one reason this hackathon exists in a single sentence
- Book thirty minutes with the likely sponsor to agree the goal
- Draft three outcomes you would expect to see six months later
- Share the goal statement with engineering leads and product managers