Sassy Miriam writes: "I am about to turn down ANOTHER project, this one a long-time client. I want to say “yes” but I know if I do I will be thoroughly overwhelmed and unbalanced and unhappy. I will, of course, refer another writer, but it feels awful to say “no.” I can barely bring myself to type it. No. (Eewww). No. (Ack!) No. (Sigh.)
The Spock in me says this: You’re turning down this work because you have so much other work. And the work you’re doing is as satisfying (if not more so) and as lucrative as what you’re losing. And by saying “no” you’re giving another writer work that he or she may really need. And it’s time for change: I’m getting new experiences and my (former) client will get a writer with a fresh perspective.
The human in me responds: You’re crazy to pass up work. What if you’re looking for work next year but they don’t need you because they have a new writer (who you recommended)?
I hate arguing. Especially with myself.
Here’s to such a good problem to have ..."
Question of the day: Have you ever said "NO!" to client work before? Post your response below.
Subscribe to:
Post Comments (Atom)
1 comment:
Miriam, Good for you! It IS hard to say "no". I have been referring smaller projects to a good resource at Precision and everyone benefits in the end.
Don't think of what you're giving up. What goes around comes around. Down the road, the other writer just might refer projects to you that you wouldn't have had the chance to work on.
Another good reason to turn down work is when the proverbial red flag runs up the pole - by something the potential client does or says that turns you off. I once told a client, "We are just not a good fit for what you are looking for." when accepting the job didn't make me feel happy.
When your business can get to the stage when you can refuse work, you should pat yourself on the back. That is a good feeling indeed.
Post a Comment