War-game a hackathon brief before builders, sponsors, and legal treat a soft draft as the official rules of the event.
Hackathon briefs fail when judging criteria are vague, when IP and data rules surprise participants mid-build, when prize math conflicts with sponsor goals, and when scope invites unsafe or out-of-policy work. A colorful landing page is not evidence that the event can run without disputes, dropouts, or a scramble to rewrite rules.
Freeze the brief
State the theme, eligibility, timeline, judging criteria, prize structure, data and IP rules, and the single ask of participants. Attach sample datasets or API limits, sponsor constraints, and the FAQ you actually intend to publish. If the brief mixes recruiting goals, a product experiment, and a public PR moment, split them. One move under fire at a time.
Write the decision you will make if the war game finds nothing new, and the delay criteria if judging, legal, or tooling is not ready.
Seats that matter
- Builder. Ambiguity, tooling gaps, and the rule that feels unfair on first read.
- Sponsor. Brand risk, success metrics, and claims the brief overpromises.
- Legal and security. IP assignment, data handling, and unsafe challenge patterns.
- Judge. Criteria that cannot be scored consistently across teams.
- Skeptic. The claim that looks strongest and is least sourced.
Same pack for every seat. Secret "we will clarify on Discord" notes create fake agreement and a second rumor cycle during the event.
Loop the review
Feed Pingpong the brief draft, prize rules, and seating briefs. First pass steelmans the event. Later passes attack from builder, sponsor, legal, and judge seats. Final pass turns surviving objections into clearer criteria, tighter scope, or a hold. Delete dual-counted outcomes and invented tooling that is not ready.
Prefer one precise judging rubric with weighted criteria over a long list of soft adjectives. Ask the judge seat to score two invented submissions using only the brief. If scores diverge without a clear rule, the criteria are not ready.
Force a mid-event narrative: what happens if judging criteria are challenged, if a dataset has PII nobody noticed, or if a sponsor walks back a prize. If those stories are stronger than your FAQ, fix the package before publish.
When the brief invites use of company APIs or customer data, force security and legal seats to map every access path and retention rule. Sandbox limits and deletion clocks count. Related: war-game a product launch, war-game a community guidelines change, pretend you are the power user, war-game a press release, and the war-game decisions hub. Process: how to run a Pingpong.