As a PM, we are trained to say "No" to deflect requests that don't align with the product vision.
However, there are 2 ways to say "No" & both are equally important to learn.
1) When someone comes with a zany idea with little validation & apparent value. (e.g. "hey, can we make the chatbot do a little dance while the user waits for an agent?")
In such cases, it's not worth spending too much effort to explain why it's a bad idea. A respectful "No" along with a request for a stronger case is sufficient.
2) When someone brings an idea with more weight & backing.
For such requests, it's best to share your rationale before declining it.
A framework that works well is to run through order of consequences. Simulate the best & worst case scenarios.
For example,
Idea: "I have a top brand who is willing to pay big dough for our tech conference provided all their competitors are blocked out."
Order of Consequences:
1) We bring the brand aboard & get great money.
2) Several opposing brands approach us, we tell them no & dent those relations.
3) They see who we preferred, get negative PR & look like sell-outs.
Now, discuss the probability of each case & the impact of that risk.
Not only does it close the loop, it also gives you & them clarity of thought.
As a Product Manager, you might be asked a lot of questions during an interview. One of them includes technical questions. Here are 4 types of technical questions that you might come across.