I used to think saying “no” was negative.
Now I think it’s basically kindness in a hard hat.
Because without clear “no’s”, everything becomes “maybe”…
…and “maybe” becomes rework.
“No” gives your team a boundary to build against.
No = tempo.
Tempo = momentum.
Momentum = fewer late nights staring at Figma like it owes
you money.
If your projects keep wobbling, try writing down three “no’s” for the next month.
You’ll be amazed how many “feedback” conversations disappear when the boundaries are real.
Written by Ryan Taylor