On Saying No to a Project

Early on, I said yes to almost everything. I suspect most people starting a studio do. There is a particular fear in those first years that any project turned away might be the last one offered, so you say yes and figure out the fit afterward. I do not work that way anymore, and I think the business, and the work itself, is better for it.

A project that is wrong from the start rarely becomes right through effort. Sometimes it is a mismatch of vision - a client wanting something loud and trend-driven when everything about how I work leans toward restraint and story. Sometimes it is simpler than that: a timeline that does not allow for the groundwork good design actually needs, or a budget that would force corners to be cut in ways that would show, eventually, no matter how carefully we tried to hide them. None of these are anyone's fault. They are simply signs that this particular project and this particular studio are not meant to work together.

Saying no to that used to feel like a risk. Now I think of it as a kind of protection, not just for me, but for the client too. A designer who takes on work that does not fit them well cannot do their best for anyone, and everyone ends up a little disappointed by a version of the work that was never going to be their strongest. Turning a project away, kindly and honestly, is often the more generous thing to do.

It also protects something less obvious: the quality of everything I do say yes to. Every hour I am not spending on a project that was never quite right is an hour I can give fully to one that is. Saying no, in that sense, is not the opposite of saying yes to good work. It is what makes saying yes to good work possible in the first place.