 When to say not work is an important skill to learn, as is how to say not work. And if you don't say not work then firstly you're going to be overworked, stressed and unhappy. Secondly you'll have colleagues dumping their work on you. Third you'll let others down again and again. And fourth you simply will not be able to do a good job. You'll have too much work to do and will be trying to do acceptable quality work rather than good or great work. And of course this has bad implications for your career. And your problems will multiply if you go into the management ranks struggling to say no. Learning to say no at work is absolutely essential. To start with most people worry about offending the other person, feel guilty or uncomfortable saying no. I certainly did. Saying no is a very small let down compared to not delivering a work or not doing your job well enough. Learn to say no quickly. When to say no at work is important and I'm taking you through five different scenarios when you should say no at work. And then I'll be taking you through how to say no at work, whether it's to your manager, peers or other stakeholders asking things of you. There are five examples of how to say no at work towards the end of the video. My name is Jess Coles and I've had a 25 year management career in corporate and household names through to SMEs. Learning how to say no well is vital for you and for a successful career as a manager. Those individuals that struggle to say no will struggle to progress their careers. And if you're new to this channel enhance.training shares business and people management expertise to help you improve your performance and that of your team and business. And if you like this video please give a thumbs up and subscribe. Most managers expect their staff to say no at times. This is absolutely fine. When you do say no at work be clear on your reasons and explain these reasons. Nine times out of ten the other person will respect you for saying no and will not think negatively about the situation. So the first reason for when to say no at work is when you're maxed out. Whenever someone asks you to do a task or project think through what you currently have to do. When you expect you'll be able to deliver on each of the tasks and projects and then estimate if you have any spec capacity. Always give yourself some extra spare capacity because urgent tasks do routinely come up and you need to take these into account. If you're maxed out if you have no or next to no ability to take on the new work and complete it successfully in the time frames required while still delivering on everything you currently have to do you must say no to the additional task or project. But what if the new task is deemed more important you might ask. You may have to negotiate with the person asking and those that you've already said yes to. Set out your position by saying no and then negotiate. If you manage a team then apply the same thought process of mentally planning out what needs to be done. You have to consider everyone in the team and the team as a whole rather than just you which of course makes it a little bit more challenging. The second reason for when to say no at work is when you're not the right person. You have been asked to do a task or project and you're not the right person to do the work. There could be lots of reasons for this. You know you don't have the right skills or experience to do a good enough job or to do the task quickly enough. Secondly you're being asked to do someone else's work because they find it easier to ask you or because they're being lazy for instance. Third you know a colleague or another team that is in a much better place to do the work instead of you. There are lots of reasons. If you're not the right person to do the work then say so. The third reason for when to say no at work is when doing the work will stop you delivering your own work objectives or goals. We all have priorities. Our work priorities are usually set out formally as objectives to be achieved in a specific time frame. You have been set the objectives and goals because they are the most important projects or tasks to achieve for the team and the business. Always keep these in mind and prioritise them. And you may well have personal aspirations tied into completing your official objectives. You know such as gaining certain experience that will help you progress your career. If the task or project doesn't align with your objectives and goals or worse conflicts with those objectives or prevents you from completing your official objectives say no to the additional project or get your official objectives changed to reflect the new project if this is an option you are happy with. Taking this approach will also stop you getting pulled from pillar to post. The fourth reason of when to say no at work is when you can't deliver what is required. We all like to succeed at what we do at work. This helps our confidence and helps the team around us. When asked to do something new think carefully if you can deliver what is required. What level of support and help will you need and will this be available? Everyone has their own risk, appetite and desire to learn. If you are not say 70% plus sure that you can deliver then I would suggest you say no. You may not be able to deliver work even if you've done it before many times. There are a whole host of reasons for this. If for example any of the other reasons that we're covering today. If you have significant doubts it is better to say no than to say yes. And if you take the fake it until you make it approach then manage expectations carefully and set out what support you'll need and when to help you overcome uncertainties. Stack the odds in your favour so you can consistently deliver what you agree to. The fifth reason for when to say no at work is when there is a big conflict with your values. Our values on a personal level and a business level are really important guardrails for our choices and actions. Our values are steady, constant, changing slowly over time if at all. They make great and important reference points for us all. Know what values are important to you. If you're asked to do a project or task that is in strong conflict to important values for you or your team then say no. You'll of course have to weigh up your personal comfort and happiness with the potential negative impacts on your job. So now we have gone through five common reasons for when to say no at work. Let's talk about how to say no at work which is equally important. Whenever you say no at work to a request irrespective of who you're saying no to make the time to explain why you're saying no. If you just say no with no explanation you'll quickly be perceived as a difficult, awkward person to deal with. As in a clear, reasonable explanation of why you're saying no transforms the perception of you and the other person's eyes to a considerate sensible colleague. I mean if you say yes and then can't deliver the other person can't make alternative arrangements ahead of their deadlines. Do this more than a few times and it won't be long before you develop an unreliable reputation. You are saying no because you can't deliver or are maxed out etc. which allows the other person to make different arrangements that will see the task or project completed as needed. This helps a team. Saying no is useful and needed for good teamwork. Go a step further than just saying no by helping them find a different person to do the actual work. People will love working with you if you do these sorts of steps. And as promised some examples of how to say no at work. Firstly, I'm very sorry I can't take this project on because I have another three projects I haven't completed yet and I'm maxed out until the 23rd of the month. Secondly, I don't think I'm the best person to help you with Project X because I don't have much experience with Facebook advertising campaigns. Can I suggest you speak to Jill who is much better placed to help you. Third, the project you're outlining is not where I want to take my career. I have another two project offers which are much more aligned and I only have capacity to do one of these projects over the next month. Fourth, I am worried that I have too little experience to have a realistic chance of delivering this project. I think you'd be better off asking someone with more experience in this area. If you have a strong support program in place then I would love to go through that with you before deciding. Fifth, I feel very strongly about the sustainability impact this project seems to have. Are you considering improving this area? If not, I would not be happy leading the project and several other managers would be a better choice. All of these examples are saying no diplomatically and providing an explanation of why you are saying no without beating around the bush. Work out how you will say no clearly and definitely without offending the other person. Knowing when to say no at work improves with practice and experience. Some battles are well worth fighting, others much less so. Learn when to say no at work. And when you do decide to say no at work then how you say no becomes important. Always explain why you're saying no. Be considerate of the other person's situation and feelings without being wishy-washy on your decision. Working out your style of saying no at work is a must otherwise you will continually let others down and yourself down at work. Continuing letting others down at work is a bad place to be, avoid it. To quickly recap, when to say no at work includes when you're maxed out, when you're not the right person. When doing the work will stop you delivering your own work objectives or goals. Fourth, when you can't deliver what is required and fifth when there's a big conflict with your values. If you have any questions please leave them in the comments section below and I'll get back to you. Thanks very much for watching and I look forward to speaking to you again soon.