Early in my delivery career I worked with a client who asked for everything twice and meant it kindly. Every meeting added scope. Every deadline moved earlier. I said yes to all of it, because yes felt professional and no felt like failure. The project nearly broke me, and it taught me the most valuable lesson of my career.
Saying no in project work means declining scope, timelines, or requests that would damage the project, early and clearly, before they become expensive. It is not rudeness. It is not negativity. It is the delivery lead doing the part of the job nobody else will do: protecting the work from the enthusiasm around it.
What was the client actually asking for?
More, constantly, and always with good reasons. A new audience segment that needed a variant. A stakeholder who wanted their idea included. A launch event that moved forward by two weeks. Each request was reasonable on its own. Together they were a different project wearing the original budget.
I kept a mental list of all the yeses and told myself I was being flexible. What I was actually doing was spending money nobody had approved: my evenings, the team's goodwill, and the quality of the final work. Flexibility without boundaries is just slow collapse.
Why was yes so tempting?
Because yes is rewarded in the moment and no is punished in the moment. The client smiled at yes. The team felt supported by yes. Saying no would have meant an awkward conversation, and I was young enough to believe awkward conversations were the enemy.
They are not. The awkward conversation in week three is cheap. The crisis in week ten is expensive. I was optimising for comfort in the meeting instead of success in the project, which is the exact inversion of the job. Nobody tells you this when you start. You learn it the way I did, by paying for the lesson.
What did the first real no sound like?
It sounded small and terrifying. The client asked for another round of concepts, on top of the two we had agreed, with the deadline unchanged. I said we could do the extra round or keep the date, but not both, and I said which one I recommended.
There was a pause. Then the client chose to keep the date, and the project got better, not worse, because the constraint forced a decision. That pause taught me something no training ever had: clients do not actually want unlimited yes. They want someone they can trust to tell them the truth about trade offs. This is the same honesty that keeps good marketing teams from missing deadlines.
What changed after I learned to say it?
Everything, but quietly. Projects stopped expanding mid flight. Timelines started holding. The strange part was that clients trusted me more, not less. The no had proved I was guarding their interests, not just pleasing them.
I also got better at the shape of no. Never a bare refusal. Always the trade off, stated plainly: we can do this or that, here is what each costs, here is my recommendation. Said early, said kindly, said once. That formula has protected every engagement since, and it is the backbone of what is brand delivery as I practise it.
What does a healthy no look like in practice?
It looks like the brief conversation, the scope conversation, and the timeline conversation, all held before the work starts rather than after it breaks. It looks like change requests priced openly instead of absorbed silently.
Most importantly, it looks routine. The teams I work with now hear no as a normal part of planning, not as a crisis. That normalisation is the real lesson the client taught me. Saying no is not an event. It is a habit, practised early and often, until protecting the project feels as natural as starting it.
Working with Avy
I say no for a living now, kindly and early, and my clients are grateful for it. If your projects keep growing past their budgets and timelines, you may not need more capacity. You may need someone willing to have the awkward conversation in week three.
If that sounds like your team, book a call. I will tell you where the yeses are costing you, and we will practise the no together.
Need someone to get your project over the line?
Project delivery support for brand, digital, and creative teams that need clearer direction and smoother progress.