What I've Learned About Saying No

There was a time I'd say yes to anything that sounded like opportunity. If a client wanted it, I'd make it happen. Even when it didn't feel right. Even when I knew it didn't belong in the world I wanted to help build.

That's the thing about creative work. It's easy to convince yourself you're just executing. You tell yourself it's their vision, their money, their problem. You detach a little, just enough to quiet that small voice that whispers, this isn't you.

But over time, you realize every piece of work you put out there shapes your reflection. The things you design, write, build, or ship. They don't just live on your client's site or app. They live in you. They shape your taste, your integrity, your future opportunities.

I've learned the hard way that if you keep saying yes to things you don't believe in, you eventually start losing the ability to tell what you do. The line between your work and your values starts to blur. You start mistaking approval for alignment.

So now I try to hold one rule. Never pitch something I wouldn't want to see in the world.

Not because it's strategic, but because it's honest. If I can't stand behind it, if it doesn't make sense in my bones, if it feels like noise instead of signal, I'd rather walk away.

That doesn't make me stubborn. It just means I care. About what gets built, about who it serves, about what message it sends. Because design isn't neutral. Every decision has a ripple. Through users, through brands, through people who'll never even know my name but will still feel the impact of what I helped create.

The more I grow, the more I realize my job isn't to please. It's to protect the work from becoming meaningless. It's to make sure what I make adds clarity, not clutter.

I'd rather lose a project than lose my voice. I'd rather build something small that feels true than something loud that feels empty.

Because the work outlasts the meeting. And I have to live with what I choose to put into the world.