Mindset · Paper 03 · 12 min
Constraints are the brief
Amateurs hide the ugly constraint. Hackers put it on the title slide. The missing designer is not an insult. It is the assignment.
The constraint is not blocking the work. The constraint is the work, written in a meaner font.
Thesis
Why this paper exists
36-hour rooms are made of missing things. The team that treats missing as fatal builds a worse version of the brochure. The team that treats missing as the brief often wins.
- Name the real constraint, not the theatrical one
- Flip a constraint into the product's edge
- Kill work that does not pay the constraint
Theatrical versus real
Theatrical constraints: 'we need more time', 'if only we had a designer', 'the API is janky'. Real constraints: you have eight hours of attention, one person who can ship, a judge who is a nurse, a demo laptop that cannot reach the internet.
Write the real list. If a constraint would still be true after a miracle of staffing, it is theatrical. Ignore it.
Flip
One developer, no designer, eight hours: you do not 'do design later'. You ship a product that looks like a terminal, a form, or a receipt — things that are allowed to be ugly if they are true. Ugly-and-true beats pretty-and-generic in a room that has seen twelve pretty-and-generic decks.
Dead sponsor API: do not fight twelve endpoints. Use two so well that the sponsor's own VP understands their product for the first time. That is often the actual prize.
Pay the constraint
Every hour must pay the constraint. If the constraint is 'demo cannot fail', then a local video of the happy path is not a cop-out. It is the work. If the constraint is 'one nurse judge', then a handover tool with twelve features is theft of her patience.
Ask, hourly: does this hour make the constraint cheaper, or are we hiding from it.
Drill
Write three constraints on your current project. Circle the one that would still be true if you were twice as talented. That circled line is the brief. Put it at the top of the page.
Knowledge check