It took a good burning, as in attorney’s, legal fees, reimbursements and the like to convince me that when my gut says don’t do it, not to frickin’ do it. Sometimes the headache ain’t worth the quick buck.
Thankfully, since then I have learned to be more judicious in the acceptance, planning, plotting, logistics and execution of said web dev projects and their clients, so maybe it was a good thing that I learned from the not saying no fiasco.
To make a short answer long, if you don’t want to do something, saying yes won’t make the client/person like you any better or create good karma for you in the long run.
Say “no” and they could still come back for another job. But on your terms. It’s happened to me.
No.
Honestly, this is a lesson that I’ve had to learn the hard way. I started out my business hungry for work and I said “yes” to jobs that I shouldn’t have. Bad Idea.
I have very little problems in saying “No” to either a current client or a prospective client, mainly because I did pick up a bad job from simply saying yes before I had the full information and not listening to my gut feeling.
From now on I wait till I have had as complete a brief as possible on my desk for a day or two before making a decision on it.
Yes.
You sometimes have to say “No”. The only thing better than saying “No” to some clients is to fire them! Now that can feel good.
We’re just getting to the stage where we can say ‘no’ to projects that give you a bad feeling from the start. I still make mistakes judging them, but am now better with ensuring the project scope is locked up at the beginning so even a lack of ‘no’ doesn’t land us with too much headache, we just get the job done and move on.
7 responses to “No”
It took a good burning, as in attorney’s, legal fees, reimbursements and the like to convince me that when my gut says don’t do it, not to frickin’ do it. Sometimes the headache ain’t worth the quick buck.
Thankfully, since then I have learned to be more judicious in the acceptance, planning, plotting, logistics and execution of said web dev projects and their clients, so maybe it was a good thing that I learned from the not saying no fiasco.
To make a short answer long, if you don’t want to do something, saying yes won’t make the client/person like you any better or create good karma for you in the long run.
Say “no” and they could still come back for another job. But on your terms. It’s happened to me.
No.
Honestly, this is a lesson that I’ve had to learn the hard way. I started out my business hungry for work and I said “yes” to jobs that I shouldn’t have. Bad Idea.
I have very little problems in saying “No” to either a current client or a prospective client, mainly because I did pick up a bad job from simply saying yes before I had the full information and not listening to my gut feeling.
From now on I wait till I have had as complete a brief as possible on my desk for a day or two before making a decision on it.
Yes.
You sometimes have to say “No”. The only thing better than saying “No” to some clients is to fire them! Now that can feel good.
We’re just getting to the stage where we can say ‘no’ to projects that give you a bad feeling from the start. I still make mistakes judging them, but am now better with ensuring the project scope is locked up at the beginning so even a lack of ‘no’ doesn’t land us with too much headache, we just get the job done and move on.