# Hackathon plan · [Event name] · [Dates] **Sponsor:** [Exec] **Owner:** [PM] **Planning started:** [date, about four months ahead] ## 1. Goal [What the roadmap needs answered. Measurable: e.g. "three prototypes that pass eval X".] ## 2. Theme [One theme tied to a named bet.] ## 3. Competition or cooperation [Choice and why. Shared assets teams can reuse.] ## 4. Stakeholder involvement - Customer or partner participants and judges: [names] - Security pre-approval of data and system access: [name, date] ## 5. Participant recruitment [Who, how many, which skills. Include domain experts, not only engineers.] ## 6. Specialized preparation - Sandbox environment and connectors: [list] - Data set (anonymized, approved): [description] - Eval set and scoring method: [description] - Templates, starter code, model access: [list] ## 7. Duration and breaks [Length, hours, rest. No overnight heroics unless chosen.] ## 8. Ideation [Before or during the event; problem list seeded from customer evidence.] ## 9. Team formation [How people find teams; maximum team size.] ## 10. Agenda | Time | Activity | |---|---| | | Kickoff: goal, rules, judging | | | Build | | | Mentor check-ins | | | Evaluation run on the shared eval set | | | Presentations and judging | ## 11. Mentoring [Who mentors on product, security, AI, domain.] ## 12. Continuity (agreed before the event) - Each winning project gets: [named PM owner, follow-on slot, budget] - Other outcomes we'll keep: [reusable components, connectors, eval cases, people to recruit into the bet] - Decision review date: [date] ## Judging rules - Measured results on the shared eval set: [weight] - Customer value against the bet's question: [weight] - Safety and security: [pass/fail gate] - Demo polish: not scored ## Tensions we're managing [Organizational vs personal goals; concept vs useful output; challenge vs achievable; speed vs quality.]