I read a good article by Peter Bregman about how to say 'No'.
This is a very under-rated skill to have. Saying 'No' is vital to keeping work and customer expectations at manageable levels.Failing to say ‘No’ when we instinctively know that we may not be able to deliver is a bad move that can come back to bite us over and over. What ensues is usually a lengthy and awkward process of realigning customer expectations and eventually telling them ‘No’. In the meantime, you probably have damaged customer relationships, frustrated staff and wasted time figuring out how to limit the damage.
This happens quite a bit in software start-ups that code their own product. Feature creep can set in and it’s easy to say ‘Yes’ to an important client when they inevitably ask for a function or change request. At start-up phase pretty much any client is an important client.However, you will find yourself making promises you can’t keep, burning the candle at both ends (working late / weekends) to come good on commitments when you should have said ‘No’. That leads to endless firefighting where you neglect the basics of making sure your strategic business systems are running properly (sales pipeline, support documentation, credit control, cost benefit analysis of activity).
Key staff will get demotivated at constantly working under pressure or jumping from one ‘priority’ to another and probably leave (if you have more than three priorities, you don't have any). You will more than likely rehire in a hurry because you need someone straight away. Because you have taken your eye off the ball on the fundamentals of the business you may neglect your sales process, prospect call backs etc, so the clients that made the initial request now become even more important (as other sales haven't grown as planned ). It then gets even harder to say 'No' to their next change request. On and on it goes.
If you are a start-up company in firefighting mode or constantly find yourself avoiding calls from clients, end up working weekends, late at night, ask yourself how often you have said ‘No’ to a request in the last week. Chances are it’s not very often. There is nothing wrong with being busy and firefighting, just so long as it’s for a strategic or commercially sound reason. If it’s purely because you could not say ‘No’, then it’s a problem.
As someone once said, 'The road to hell is paved with good intentions', failing to say 'No' might be just laying another stone on that road for your projects or organisation.
This is a very under-rated skill to have. Saying 'No' is vital to keeping work and customer expectations at manageable levels.Failing to say ‘No’ when we instinctively know that we may not be able to deliver is a bad move that can come back to bite us over and over. What ensues is usually a lengthy and awkward process of realigning customer expectations and eventually telling them ‘No’. In the meantime, you probably have damaged customer relationships, frustrated staff and wasted time figuring out how to limit the damage.
This happens quite a bit in software start-ups that code their own product. Feature creep can set in and it’s easy to say ‘Yes’ to an important client when they inevitably ask for a function or change request. At start-up phase pretty much any client is an important client.However, you will find yourself making promises you can’t keep, burning the candle at both ends (working late / weekends) to come good on commitments when you should have said ‘No’. That leads to endless firefighting where you neglect the basics of making sure your strategic business systems are running properly (sales pipeline, support documentation, credit control, cost benefit analysis of activity).
Key staff will get demotivated at constantly working under pressure or jumping from one ‘priority’ to another and probably leave (if you have more than three priorities, you don't have any). You will more than likely rehire in a hurry because you need someone straight away. Because you have taken your eye off the ball on the fundamentals of the business you may neglect your sales process, prospect call backs etc, so the clients that made the initial request now become even more important (as other sales haven't grown as planned ). It then gets even harder to say 'No' to their next change request. On and on it goes.
If you are a start-up company in firefighting mode or constantly find yourself avoiding calls from clients, end up working weekends, late at night, ask yourself how often you have said ‘No’ to a request in the last week. Chances are it’s not very often. There is nothing wrong with being busy and firefighting, just so long as it’s for a strategic or commercially sound reason. If it’s purely because you could not say ‘No’, then it’s a problem.
As someone once said, 'The road to hell is paved with good intentions', failing to say 'No' might be just laying another stone on that road for your projects or organisation.
No comments:
Post a Comment