How to say "no, thanks"
Last week's Quick Tip from Marketing Mentor generated lots of comments and questions. In the tip, I revealed three reasons to say "no" to certain work that will cause you more misery than anything else (read that here.)
Here's a comment I got from David Bresler, Vice President of Breakfast Network:
I would add this: An offer of a lucrative project that is different from anything you have done in the past or a mismatch for your skill set. Even if you believe that you can do it, you are bound to make mistakes this first time around and thus both damage your reputation and not make the kind of return you are used to (or even lose money). It is tempting to go to school on somebody else’s nickel, but, in the end it is usually a bad policy.
Andrea Robinson, of AT Design and Illustration (and a Marketing Mentor client) agreed that it's important to say no and has struggled with the issue of how to say no. In fact, she wonders about the best way to graciously and tactfully decline a request from a non-profit agency who also happens to be a client. They want her to serve on their board of directors.
My answer is this: Let them know you have too many existing commitments to do them justice right now, but ask if there's a way you can participate more peripherally. I don't know all the details but it sounds like too good an opportunity to pass up, especially if you're interested in nurturing this relationship.
Andrea is also involved in CreateAthon, a 24-hour, work-around the clock creative blitz during which local advertising agencies generate advertising services for local nonprofits that have little or no marketing budget. So now, when someone asks her to do pro bono work, her first response is to ask these non profit prospects to submit an application for CreateAthon, which, she says, "helps tremendously take care of the requests, efficiency of the process of doing "pro bono" and giving back to the community."
Andrea also passed along these ideas from marketing coach, Susan DePue:
7 Ways to say NO!
- Just “NO” - “Thanks, but Ill have to pass on that”. – then say no more.
- The Gracious “NO” - “I really appreciate you asking me, but my time is already committed.”
- The “I’m Sorry” NO - “I wish I could, but it’s just not convenient.”
- The “It’s Someone Else’s Decision” NO - “I promised my coach, I wouldn’t take on any more projects without discussing them with her first.” – or the board, or your partner, etc..
- The “My Family is the Reason “ NO - “Thank you very much for the invitation. That’s the day of my son’s soccer game, and I never miss those.” Other great reasons: birthdays, anniversaries, high school graduations – just make sure it’s the TRUTH!
- The “I Know Someone Else” NO - “I just don’t have the time to help you, but let me recommend someone else I know.”
- The “I am Already Booked” NO - “I appreciate you thinking of me, but I’m afraid I’m already booked that day.” – Use this one even if this is the time you booked for yourself. Remember that you will have nothing to offer unless you take the time to replenish your spirit.
Any others you can think of?

I usually just like to say: "I'm just getting that it isn't really the right project for me now." And, if possible, I also like to make a referral to them.
When I read David Bresler's comment: "...It is tempting to go to school on somebody else’s nickel, but, in the end it is usually a bad policy." I had to disagree.
I think if a project is a total mismatch and it's outside your passion or interests, then of course let it go. But, if it's an area you've been wanting to reach into, and it's new, I think it's perfectly acceptable to learn on someone else's dime as long as:
1. You're not making extravagant promises you can't deliver on.
2. You're prepared to take a financial loss as part of the learning process (meaning you might not get paid your usual rate, given the extra hours of learning or fixing mistakes.)
3. You're willing to be honest and call in other resources or people for help, even to hand the project off, if your learning curve is putting the client at risk.
In effect, that's how the Sistine Chapel got painted- Michelangelo had no previous experience with painting frescoes, and very little with painting at all- he was known as a sculptor. And yet, the Pope hired him. Although it took him four years to do it while he got up to speed with fresco painting, it seems like he handled the job okay, eh?
Posted by: Mark Silver | September 10, 2007 at 08:59 AM
I try to do the "yes no yes" sandwich method: sliding the no between two positives.
As in, "I'm so glad you'd like my input on this (yes!). However I have a lot on my plate right now and won't be able give it the attention it deserves (no!). I believe so and so might be a good match for you (yes!)"
Posted by: Havi Brooks | September 11, 2007 at 05:13 PM
We are quite selective about the clients that we take on. If a client or a project is not a good fit for us, we are very honest and tell them... "You know this isn't a fit for us right now because (and give an honest and kind reason)."
I will almost always suggest a freelancer or a different firm who I know is a good fit for their project. I keep a list of recommended resources and then it is a win-win-win for all three entities.
The other thing that happens is that ultimately, the freelancers will usually send a great client our way because it is too big for them to take on.
Posted by: Wendy Maynard | September 19, 2007 at 06:45 PM