Anti-goals (aka NOKRs) explicitly state what you aren't trying to do. They help set expectations and clarify your strategy. A good exercise for setting anti-goals is to ask, "What might someone reasonably assume might happen because of our work that will likely NOT happen?"
These all seem familiar but genericized. It looks something like vision > strategy > (N)OKRs > KPIs > “product principles” — but probably got the order wrong.
@john why share it that way vs a relational model at different altitudes? Want to make sure I understand the lesson here
Well, you're absolutely right, as a PM and strategist I do. And I'm also naturally curious and motivated to read and learn and apply different models and frameworks on all product related topics in my day to day work.
However, One of my challenges is to NOT overwhelm my co-workers (devs, designers, even management) with this 'deep level, deep thinking' stuff. Any tips? Maybe you've written on this topic before?
Thanks btw for all the work you're doing in our messy space and keep up the good work!
These all seem familiar but genericized. It looks something like vision > strategy > (N)OKRs > KPIs > “product principles” — but probably got the order wrong.
@john why share it that way vs a relational model at different altitudes? Want to make sure I understand the lesson here
John... I'm trying to keep things simple over here...😅
It is simple. You probably use all of these goal types in your day to day work naturally.
Well, you're absolutely right, as a PM and strategist I do. And I'm also naturally curious and motivated to read and learn and apply different models and frameworks on all product related topics in my day to day work.
However, One of my challenges is to NOT overwhelm my co-workers (devs, designers, even management) with this 'deep level, deep thinking' stuff. Any tips? Maybe you've written on this topic before?
Thanks btw for all the work you're doing in our messy space and keep up the good work!