I used to dream about the day I’d be so busy with work, I’d be able to turn down projects. Not because I wanted a client to feel bad, but because it would signify to me that I had reached a certain level of success.
As I’ve gone along and built my business, that dream isn’t so important. I try not to turn down projects and I’m certainly not to a point where I’m turning down a project every day.
But I have said no a few times and thought I’d share some of the reasons why so you can be prepared for it when it happens to you, or at least give you some things to think about for the future.
1. The project is offensive in some way. Actually, this is one that hasn’t happened to me yet, but it will happen to every designer or writer at some point. Whether it’s for political, moral or religious reasons, there are projects that just don’t match with your own views. Sometimes it’s tempting to take the money and do the project anyway. For me, if in doubt, I try to picture showing the project to someone at church. If that thought makes me uncomfortable, that helps to tell me that perhaps the project isn’t a good match.
2. The project is not one where I feel I have the skills or desire. I’ve said before that I don’t care to do logos. Of course, as soon as I said that, I started getting requests for logos. I’ve done one since it was just a variation of a prior logo a company used, but other than that, I’ve said no. The reason? I simply don’t think I’m that good at it.
While it would be nice to think I can do every type of project, the reality is that it would take a lifetime to become an expert in every aspect of design. Instead, I like to focus on the things that I enjoy and think I’m good at, then slowly build up new skills in different areas as time allows.
There’s a temptation to say yes to everything so you’re not leaving money on the table or so you can stretch yourself. But there’s no shame in admitting that, for some projects, you’re not going to be the best match with the client, whether it’s due to skill level or a lack of passion for the type of project.
3. The project requires an on-going commitment. About a year or so ago, I bid on a project to do the layout for a monthly newsletter. It would take about a week out of each month dedicated just to that project. Thankfully, I didn’t get the job. As I think back on it, I should have never bid on it to begin with.
I enjoy the freedom of not being tied down to ongoing projects. I have no problem with projects that last weeks or months, but that’s different. With projects that are, for example, every second week of the month, you start losing the freedom to do things like schedule time off for family vacations when it’s best for your whole family. Plus, all other projects then need to be planned around that one regular job and, for me, that’s not something I care to do. (I do have one project that is monthly, but it only takes me a day or two to do it, so that one is ok in my book.)
4. The client isn’t being fair to another designer. About two years ago, a client was impressed with something I said on some marketing forum. She said that she had just given a project to another designer, but would pull it from him and give it to me if I could beat his price by a few dollars. (Literally!) There were probably a number of reasons to turn this one down, but the reason that I felt strongest about was that the other designer, who had already landed the job, had apparently done nothing wrong to lose that job. I saw no reason to rob another designer of a job simply because I could beat his price by a few dollars. (If he and I had been bidding on the same project, that’s different…may the best designer win.)
5. The project doesn’t pay enough. In the beginning, I was ready to take any project at any price just to build my business. While I’m not always totally busy now, I’m not concerned about losing a job because my price isn’t low enough, if I feel my price is fair. You’re not going to see the income you want until you’re being very realistic about the rates you charge and walking away from projects that don’t pay what the job is really worth.
Obviously there are more than 5 reasons to turn down work, but these are the ones that stand out most for me. Freelancing should be fun, so doing projects that aren’t enjoyable or a good fit for some reason or another reminds me too much of working for some company, Monday through Friday, 9-5 and that’s no longer for me.
