A blank canvas is not freedom. It is paralysis wearing a nicer name.
The projects I have been most proud of started with a constraint I didn’t choose. A budget that ruled out the obvious solution. A timeline that killed the clever one. A technical limitation that forced a different question entirely.
Constraints do something counterintuitive: they make the design space smaller, and that makes it navigable. When anything is possible, nothing has weight. When something is ruled out, the remaining options feel concrete enough to actually evaluate.
There is a version of this that’s just cope — telling yourself the limitation was a gift when it was just a limitation. I am not making that argument. Some constraints are bad and should be fought. But the interesting question isn’t whether constraints are good or bad. It’s what you do with them once they’re real.
The best answer I’ve found: treat them as material. Not as a wall to work around, but as something to build with. The constraint that ruled out animation led to a typographic solution that was sharper than anything moving would have been. The timeline that killed the full flow forced a prioritization conversation that revealed the feature nobody actually needed.
The constraint you didn’t want often points toward the decision you were avoiding.
None of this is advice about embracing restriction for its own sake. It’s about noticing that the shape of a problem is part of the problem — and that a well-understood constraint is closer to a solution than a wide-open brief.