How to politely tell coworkers that their input is unnecessary or unneeded?

Question

I am a manager at a company which has struggled the past 2 years with the changing market and due to this has had several budget constraints. Just recently I finally got a budget to redesign one of our web products that actually will be considered that products EOL (end of life) update. After that the product will have no future updates released. The main reason is a pivot in the core of our business to another market segment.

Now that I have a budget, have outsourced the work (all planning and decisions completed for deliverables), and actually have started to execute on the project I received an email from another managers that wants to include their opinions with screenshots of what the update should look like (that boat has sailed already). I worked with one of our business development members for high level input on design but ultimately I am the decision maker.

Our office culture is one that is open to opinions and feedback but in this case I do not want this project to distract our new direction, nor do I want to have it get off the rails with features that simply don't matter. My fear about the latter is that we have an owner who has at times had "knee-jerk" responses to managers feedback that have blown out the budget and scope of projects.

Question: How can you tell coworkers that their input is unnecessary or unneeded, not only because the plan is already being executed on, but to be honest this is not their project to worry about in a polite and constructive way since our culture is one generally open to opinions? In this case it is a manager who also happened to CC about 4 or 5 other managers/personnel on the communication with their opinion. How can I nip this in the bud so this project stays on focus?

Answer 1

So in summary it sounds like you guys normally all work well together, are open and share ideas, but in this one case that process was not followed for what appears to be a very good reason: expediting this last update to an effectively dead system.

How about replying with something like this:

Thank you for your helpful suggestions. Just so everyone is aware, this update to Application "X" is the final update as Application "X" has been scheduled to be sunsetted in the near future.

That means we are keeping the scope very rigid and the budget tight. As usual, I'm always open to suggestions and ideas but in this case I won't have much wiggle room as I need to ensure that we keep to the scope and budget. Please don't be disappointed if that means that I cannot implement additional ideas.

As we pivot to the new market segment, I'll be pinging you for suggestions on how to best do that and look forward to your suggestions in that area.

Answer 2

Just say "thanks for your input" and leave it at that. Said input may in fact be useful for understanding longer-term priorities even if you can't or don't intend to act on it now.

Chad wants me to explicitly say why: Because this answer acknowledges that the suggestion was probably well intended, acknowledges that it has been heard, and politely sets it aside without any confrontation. I don't know a better way to "nip it in the bud" than to simply not stress about it.

Answer 3

Don't just close the door in their face even though that's what you really want to do. Explain the current status of the project and that new suggestions at this time cannot be implemented. Suggest you will either hold on to their suggestions and possibly ask for their feedback if you get another budget to redo the sight.

If you're not careful, they could take these suggestions and go over your head. You could be blamed for not taking their suggestions if something goes wrong or the people don't like the site. Try to keep them from getting too involved by having them get involved at a more appropriate time.

Answer 4

You don't tell them :-)

You say that your company's office culture is to be open to discussions, so that makes it really hard to tell him that you don't want his comments. On the other hand, there are times (like right now) where you have no interest whatsoever to consider his comments. But don't tell him that. People like to be involved, like to have an opinion, so try to let him have his opinion but without wasting your time.

I'd tell him truthfully that the whole project is on a very, very tight budget, both money wise and time wise, and that unfortunately, even though his ideas are truly excellent (Ok, that may be a lie), any delay right now even in the planning stage means you will go over that budget. You wish you had thought of A, B and C which he suggested, but unfortunately the train has left the station, and there is absolutely nothing you can do to change things anymore at this change.

Answer 5

Senior Management Problem

Given these three facts described in the Question:

• This project is a large one, a significant one.
• This project is part of a larger change in strategy for the company.
• Other managers, that is, your peers not just your own subordinates are the ones offering input.

…this sounds like a senior management problem.

The senior managers have not clearly explained the new strategy being undertaken by the company. They have not made the product plan well-understood. Perhaps they have not made clear the end-of-life nature of the OP’s project’s products; certainly not its timeline as you say the design decision deadlines are in the past. And certainly they have not made clear the need to focus on the future products on which the company is betting heavily.

I suggest you go to your boss or the senior managers, very soon. Rely the fact of your getting these offers of input. Explain your concern that this may mean the teams are not in focus with the new company agenda. Ask them to make clear the bigger picture in general, and ask them to make clear in particular that your project no longer needs/deserves their attention.

If those three conditions listed above were not true, if this were a more minor project, I would agree with some of the other Answers posted here. But in this case the Question’s problem is more of a symptom of a bigger problem.

Answer 6

Be transparant. When an EOL is already agreed on there is no point in letting other managers believe they can provide feedback. I think you could avoid the situation.

Answer 7

If you can not hide your project and you can not forbid people from meddling, you next option is distraction.

Report about your project and ask for feedback, but explicitly ask about those aspects which don't really matter to you at all and which can be changed with very little work. The more trivial the aspect the better, because that way you ensure that everyone can form an opinion about it. You might also consider placing a duck in your project description: An idea which is completely absurd and out of place, so people have something they can shoot down.

While people keep arguing about whether the font should be Helvetica or Arial, you can keep developing those parts which actually matter. In the end they will all feel like they did their important contribution and had the share of influence they deserve, even though they actually didn't.