Every brief arrives with the same hidden request underneath it: make it feel effortless. What nobody says out loud is that effortlessness is rarely the product of freedom. It is the product of a boundary drawn early and then defended for months.
The blank canvas is a trap
Give a team unlimited options and they will spend the first three weeks arguing about which options to remove. Give them one typeface, four spacing values and a single accent colour, and they will spend those same three weeks on the thing that actually matters: whether the screen makes sense to somebody who has never seen it before.
Constraints do not shrink the design space. They point at the part of it worth exploring.
What a useful constraint looks like
A useful constraint is specific, testable, and slightly uncomfortable.
- One accent colour, reserved for the primary action on a screen.
- No more than two type sizes above 20 pixels on any page.
- Every list works at 320 pixels wide before it is allowed to work at 1440.
- No new component until an existing one has genuinely been ruled out.
None of those are matters of taste. You can hold a screen against them and get a yes or a no. Vague principles like "keep it clean" cannot be enforced, which is why they quietly stop existing about six weeks into a project.
The constraints you write down are the only ones that survive contact with a deadline.
Defending the boundary
Choosing constraints is the easy part. The hard part is month four, when someone asks for a second accent colour for one campaign and the only reason to say no is the reason you wrote down in week one.
Keep the list short enough that everyone remembers it without looking. Three to five rules is plenty. A constraint that has to be looked up is a constraint that will be broken.
