Everyone looks for simple tricks in product management. I usually say Good PMng is not about tricks, but frameworks and mental models. But today I am sharing a trick.
I call it the โDouble Jabโ. ๐ ๐
Most stakeholders live in the solution-space: โ๐ ๐ธ๐ข๐ฏ๐ต ๐โ. โ๐๐บ ๐ต๐ฆ๐ข๐ฎ ๐ฏ๐ฆ๐ฆ๐ฅ๐ด ๐๐ฆ๐ข๐ต๐ถ๐ณ๐ฆ ๐ โ. โ๐๐ตโ๐ด ๐ฐ๐ฃ๐ท๐ช๐ฐ๐ถ๐ด ๐ธ๐ฆ ๐ด๐ฉ๐ฐ๐ถ๐ญ๐ฅ ๐ฃ๐ถ๐ช๐ญ๐ฅ ๐กโ. Even though every PM would love their stakeholders to live in the problem-space, generally you donโt have time to educate, you just need to be effective, cut through the solution cloud and prioritize correctly.
To do this, you ask the typical โWhy?โ. Now your stakeholder will have the answer ready and prepared.ย
๐๐ง๐๐ฑ๐ฉ๐๐ซ๐ข๐๐ง๐๐๐ ๐๐๐ฌ will take it and carry on, building whatever they are asked.ย
๐๐ฑ๐ฉ๐๐ซ๐ข๐๐ง๐๐๐ ๐๐๐ฌ double jab, punching a second โBut why?โ.ย
Stakeholders are usually not ready for the second โWhy?โ. They never thought about diving deep into the rationale of the first answer. They are caught off guard. It often leads them to retreating, and say โlet me get back to youโ. More times than not, they donโt come back. This means there was a lack of critical thinking, and maybe that need wasnโt as important. ๐๐จ๐ฎ ๐ฃ๐ฎ๐ฌ๐ญ ๐ฌ๐๐ฏ๐๐ ๐ฒ๐จ๐ฎ๐ซ๐ฌ๐๐ฅ๐ ๐ญ๐ข๐ฆ๐ ๐๐ง๐ ๐ซ๐๐ฌ๐จ๐ฎ๐ซ๐๐๐ฌ.
If they do answer the second Why, then you might have a winning argument. There was a thought process that overcomes an easy layer of reasoning, and it might deserve prioritisation discussion.
Bad ideas, unprepared requests, and proxy requirements rarely survive the double jab.
Discussion about this post
No posts