Get 1-1 interview coaching and land a PM job at Google. Browse our coaches or take our Google PM course: igotanoffer.com/en/interview-coaching/type/tech-interview?RUclips&
Thanks for another great video and all the content you create on this channel. I have an additional perspective to conflict resolution question. Referring directly to an escalation in interview response is little risky. Depending on the personality of the interviewer, an approach of escalation can be negatively viewed as "this candidate doesn't have a back, and would like to pass on the problems to higher-ups". So a a little more safer approach to answer this question could be, Step 1: Detailing out a framework one would use to negotiate with all relevant parties (example; using a RICE framework to stack rank all requirements), Step 2: Stack ranking eliminates most conflicts as requirements are being measured basis clear outcomes, and the outcomes which are aligned with org. goals for the year. Technically in companies like FAANG one has to respect data driven approaches, so post this process very few conflicts would remain to debate. Step 3: For the reminder of conflicts, one could explore alternates like, scope rationalisation across quarters , doing scrappy in this quarter and a platform approach in subsequent qtr etc Step 4: If conflicts still exist, invite conflicting parties (+ respective seniors) for a conversation over a meeting, and then summarise pros and cons for each of the conflicting requirement. A meeting helps view the situation as collaborative exercise vs a email as pure escalation. At the end of the day, human sensitivities play a very major role in handling a conflict scenario via escalation approach.
I feel this is not a very strong answer though it had clear structure. First step should be to try and resolve the issue with peer product manager and discussing the trade off and the stage of the product and what problem is higher priority etc. If that doesn't work it can be escalated but escalation is generally not seen as a positive thing to do in most companies and can create some friction among the colleagues.
Not true at all, and depends on the org! One can attempt to build consensus through influence, but if the teams are federated and speed to market is your goal, escalation is the optimal path forward. It has such a negative connotation but should really be viewed as a tool to help hasten decision-making when there isn't a clear win-win available for all parties
Get 1-1 interview coaching and land a PM job at Google. Browse our coaches or take our Google PM course: igotanoffer.com/en/interview-coaching/type/tech-interview?RUclips&
Thanks for another great video and all the content you create on this channel.
I have an additional perspective to conflict resolution question.
Referring directly to an escalation in interview response is little risky. Depending on the personality of the interviewer, an approach of escalation can be negatively viewed as "this candidate doesn't have a back, and would like to pass on the problems to higher-ups".
So a a little more safer approach to answer this question could be,
Step 1: Detailing out a framework one would use to negotiate with all relevant parties (example; using a RICE framework to stack rank all requirements),
Step 2: Stack ranking eliminates most conflicts as requirements are being measured basis clear outcomes, and the outcomes which are aligned with org. goals for the year. Technically in companies like FAANG one has to respect data driven approaches, so post this process very few conflicts would remain to debate.
Step 3: For the reminder of conflicts, one could explore alternates like, scope rationalisation across quarters , doing scrappy in this quarter and a platform approach in subsequent qtr etc
Step 4: If conflicts still exist, invite conflicting parties (+ respective seniors) for a conversation over a meeting, and then summarise pros and cons for each of the conflicting requirement. A meeting helps view the situation as collaborative exercise vs a email as pure escalation.
At the end of the day, human sensitivities play a very major role in handling a conflict scenario via escalation approach.
Great contribution, thanks Vivek.
I feel this is not a very strong answer though it had clear structure. First step should be to try and resolve the issue with peer product manager and discussing the trade off and the stage of the product and what problem is higher priority etc. If that doesn't work it can be escalated but escalation is generally not seen as a positive thing to do in most companies and can create some friction among the colleagues.
good job guys
Great!
Solve conflict through escalation ? That's just passing the buck !!
Not true at all, and depends on the org! One can attempt to build consensus through influence, but if the teams are federated and speed to market is your goal, escalation is the optimal path forward. It has such a negative connotation but should really be viewed as a tool to help hasten decision-making when there isn't a clear win-win available for all parties
Agreed, this is most unprofessional way to solve a conflict.
usually the people higher up , generally have more context about the larger picture and they can help decide
Good answers. But the Ums are sooo distracting!