I've seen too many product managers offload their decision-making to the leadership team, then complain that the leadership team decided. And, yes, obviously, I've done it myself before, too. Article 👇 oneknightinproduct.substack.com/p/is-that-yo...
I've seen too many product managers offload their decision-making to the leadership team, then complain that the leadership team decided. And, yes, obviously, I've done it myself before, too. Article 👇 oneknightinproduct.substack.com/p/is-that-yo...
What about tactical misdirection? E.g. you present A, B, and C, but on the choice you want (B) you leave some details "blank". The meeting descends into working on those details, hence sanctioning your pick on the important choice - while also leaving leadership with a sense of ownership.
My experience here is the opposite - the more you leave blank, the less likely the execs are to engage with it. So beware, YMMV with such an approach.
Leaving blank goes one of a few ways 1) You spend thoughtful time working on it together 2) You spend way too long getting into the weeds 3) You get shouted at for bringing incomplete information / not doing your homework 4) You just get told "LGTM" and made to do it
I generally advise not looking like you've not done your homework. It's fair enough to canvass leaders beforehand, but you still need to show you've done your part IMO
Great article. Many years ago, my Director of Product shared with me that for Executive level meetings I should always come in with a viewpoint or a position. Rather than an opinion, a fact-based viewpoint has always been beneficial. And, appreciated.