10 Interesting Ways To Say No To Stakeholders – Business Analyst Guide

There would be many instances in your business analyst career where you will be overwhelmed with unwanted requests, changes in existing requirements, unrealistic features, and many more. Sometimes, it is just possible to fulfill business stakeholders’ all the requirements and it becomes critical to say NO. However, saying NO to stakeholders is not easy as you say to your friend.

Ways To Say No To Stakeholders

Saying NO to your stakeholders can lead to bigger issues in your project’s success. Managing stakeholder relationships is one of the key responsibilities of a business analyst. Therefore, to maintain a positive relationship with the key business stakeholders, many times you have to fulfill their ad-hoc requests. You can continue to if the requests are small and doable within the project scope but how would you deal with the requirements that have a potential impact on the project scope?

Read Also… 7 Essential Roles and Responsibilities of a Business Analyst

Every project has a deadline to meet and it is calculated based on the initial business requirement. Therefore, whether you are a product owner or business analyst, you have to say NO to some of the requirements to avoid any issues. However, you might not want to upset your stakeholders. How will you say NO to them?

Saying no without having to use the word “NO”

Yes! you heard it right. You should build skills to avoid or indirectly say no without using the direct word “NO”. In this article, we will see the top 10 interesting ways to say No to stakeholders without using the word “NO”.

10 Interesting Ways To Say No To Stakeholders

1. Acknowledge and discuss the requirements

First thing first, you should acknowledge the business request and give your time for discussing the same with the stakeholders. If they have come up with additional requirements or any change in existing functionality then definitely they are interested in the system. It will create a positive atmosphere for further discussion.

Jumping onto the conclusion without listening to your stakeholder’s requirements may sound rude. Therefore, you should give some time in understanding what exactly is the requirements before saying “No! we cannot accept or implement this requirement.”

Having a detailed requirement can open other doors for you to manage critical situations. You might find a way to implement or fulfill the request or convince the stakeholders on why his or her requirements cannot be delivered.

2. Prepare yourself with supporting data/statistics

I am sure, you have some solid reason behind saying NO or rejecting business requirements. But how will you justify it? Well, the simplest way is to present the supporting data or statistics. A business analyst supposes to have an analytic mindset therefore, it shouldn’t be difficult for them to manage data or statistics to build their case stronger.

This data could be anything, it could be your current workload, business risk of implementing the requirements, etc. No stakeholder will argue more if you present the valid data. Don’t forget to be transparent and honest with the stakeholders.

3. Is it NO Forever or NO “For Now”?

Sometimes, you just can’t accept any new changes or additional requirements in the current project scope. However, there is an opportunity to accepted the same in the next phase of the project. There are many other ways to accept and deliver new requirements or changes like through a change request.

If you focus and allot some time in discussing the business requirements, you can understand the urgency or importance of it. You can convince the stakeholder to park the requirement for the next phase or post-go-live plan.

Make them understand that, the requirements are not being rejected rather it is being added to other releases. If possible, share the tentative timeline line. Business stakeholders will not feel being ignored and you will manage to avoid the requirement for now. This will become a win-win situation.

4. Highlight the impact of saying “YES”

Do you see any impact of implementing the requirements? It would be wise to highlight if there could be any impact of saying YES to what clients are asking you to do. No one would like to mess with the business therefore, it would become easy for you to decline the requirements.

But, how would you highlight the impact of saying “YES”?

For this, you need to do some homework and put some additional efforts in collecting some supporting documents. You might want to refer to similar events that might have happened in the past. You can have a meeting with impacted module or department owners and explain the situation and its impact.

Having visibility to the impact of implementing the requirements, stakeholders will be in a better position to decide whether the requirements or changes are genuinely required? This could simplify your job and you don’t need to give any other reason for declining their requests.

5. Offer alternative solutions

It is always better to offer alternative solutions than simply declining the requirements. You can do some research before meeting business users or stakeholders. Business users will approach you for additional requirements if they want to achieve something from the system. They might not be aware of any other way to get their work done.

Therefore, an alternative solution can close the topic in the meeting itself. The stakeholder will walk out with a smile if they get at least an alternative solution to their problem.

How would you find an alternative solution to the stakeholder’s problem?

  • First, understand the problem
  • Explore the system for a workaround or alternative solution
  • Discuss with your development team
  • Sometimes, a minor tweak can solve the whole problem.

Read Also… 23 Essential Business Analyst Skills That Are High In Demand

6. Explain the priority tasks and backlog

You have access to the requests received from all the departments. There would be many requests that are highly critical and will be having an impact on the company’s business. If you are overwhelmed with additional requirements then you should consider explaining the situation to the business stakeholders.

Result could be any of following out of this activity;

  • Cancel the requests
  • Put the requirements on hold for the time being
  • Plan the requirements for the future releases

A detailed list of work backlog and priority tasks will give visibility to stakeholders why the new requirements can be canceled or could be put on hold. There would be fewer chances of conflict with business users.

7. It’s not you who is saying “NO”

If you had to say NO to the stakeholder’s requirement then remember, it is not you who is saying NO, it’s because of management, business impact, or due to any other factors. You want to maintain your relationship with the stakeholders therefore, it would be wise to put real factors on the table that are not allowing to accept the new requirements or change.

Avoid saying “I” while rejecting any requirements.

The stakeholder shouldn’t think that it’s you who doesn’t want to accept the requirements. Make it clear that, you are not the decision-maker here. You might face a hard time in the future while getting your work done with the same stakeholders if you don’t maintain a good relationship. Your interpersonal skills are utilized in such scenarios.

8. Express your empathy to stakeholders

You are about to reject requirements of a stakeholder that might be very important for his or her. Therefore, it is very critical to manage such scenarios to extra care. You should show your empathy to stakeholders.

Always appreciate their initiatives and acknowledge them before commenting on anything. You should talk to them and explain the key reason behind saying NO to their requests. It should be clear to them that there is no other option than saying “NO”. Also, you should convey that, you both have the same goal to be achieved.

Be sincere with stakeholders while communicating a message

Having a fake concern can be frustrating for the business users or stakeholders, therefore you should be sincere with them. Keep them interested in the project because trust me, you want them in the future.

9. Do something nice while saying “NO”?

Passing bad news is something that you never want to do but, at some level, you have to do. However, you can make it less difficult by doing something good for the stakeholders. But, how will you do it?

Well, you can explain how you have accepted other requests in the past that have made their work very easy. In short, remind them of their past issues that you solved quickly by proactively working on it.

Another cool way could be to invite for a coffee or by offering some homemade snacks. This will make your conversation more casual and it will be very easy for the stakeholders to follow them.

10. Don’t take it personal

I often see people hesitate to say NO, however it shouldn’t be the case. If something cannot be delivered due to some serious reasons, it should be conveyed to the stakeholders. It would be more dangerous if you keep it to yourself and don’t deliver.

Business Analysts hesitate to pass negative messages or fear to say “NO” because they take this personal. They fear to lose a good reputation with stakeholders whereas it could be made simple as explained in above 9 points.

Yes! you might end up with bitter or grumpy internal stakeholders. You should be ready to hear an earful of complaints, protests, and occasional shouts. But, you shouldn’t take it personally because it might affect your work. Be sincere with your work and do whatever you think is right. In the end, you and your stakeholders have the same goal as the company. 🙂

Read Also…

Conclusion

It will never be easy to say NO to the business stakeholder’s requests, however, the above 10 ways to say no to stakeholders will help you in managing such critical scenarios.

No matter, how hard you will try, there would be many stakeholders that would be upset and walk away with sad faces. But, if you use above-highlighted tricks to say NO, they’re much less likely also to walk away angry.

A business analyst should be sincere, honest, and be willing to lend a hand (or ear) when possible. You shouldn’t take your experiences with stakeholders personally.

Now, you know the top 10 ways to say NO to the stakeholders as business analysts. Remember, these ways are not limited to the business analysts. You will come to a point in your profession where you have to say NO to the business requests therefore, you should be knowing all the mentioned ways.

I hope you enjoyed reading this article. Please consider sharing this article with your friends and colleagues who should learn saying NO. You can also subscribe to the BABeginners mailing list for getting the latest post directly in your mailbox.

Leave a Reply

Top 6 Best Business Analyst Certifications Top 7 Most Wanted Career Paths For The Business Analysts How to become a business analyst without experience