Arena · Paper 01 · 12 min
The prize is a social object
You are not shipping a product. You are shipping a story that a tired room can compare. The object is social before it is technical.
Judges do not evaluate products. They evaluate the feeling of having a defensible favourite, then they backfill a rubric.
Thesis
Why this paper exists
Teams optimise for completeness. Rooms optimise for a story they can repeat without looking foolish. Those are different sports.
- See a hackathon as a social comparison, not a build contest
- Design for corridor-repeatability
- Treat the judge's self-image as part of the brief
A room, not a market
On Sunday afternoon a dozen teams file through a room. The judges are behind. They have eaten badly. They are comparing, not analysing. The third team that says 'we used a large language model to' has already spent the room's patience.
Your job is to give them a favourite they can defend to each other. That favourite has to fit in a sentence, survive a snarky 'doesn't this exist', and make at least one of them look tasteful for having liked it.
Self-image is the hidden rubric
A design-forward judge cannot champion a mess. An engineer-judge cannot champion vapour. A sponsor-judge cannot champion a roast of their own API unless you have made them the hero of the roast. Read the panel the way you would read a system: who is afraid of what.
If you cannot name the panel, default to: tired, comparison-driven, allergic to being the person who fell for slop.
Residue
After you leave, they have your sentence, one image, and a feeling. That is the entire residue. Build those three as if they are the product — because for scoring purposes, they are.
Drill
Write the corridor sentence, the still frame, and the snarky objection with its answer. Do this before a single component is scaffolded.
Knowledge check