It’s that time of the year where we are all jotting down (or reading) product strategy docs so I wanted to share what I’ve done in the past…
I’ve always done half-yearly planning and provide a product strategy doc with the assumptions, business context, strategy, objectives and key results documented. I then share this doc broadly with the product/EPD org and go over the OKRs all hands, etc. but what I’ve often found is that many folks don’t read this doc, primarily because they are all too busy with existing commitments. If teams don’t read the doc, internalize the strategy and explicitly commit, it’s harder for a strategy to stick so the question is, how to get the teams to read the strategy doc, ask clarifying questions and commit to it?
One thing I learned from mentors is the idea of doing roadshows with individual teams where the goal is to talk through the strategy, contextualize it for them, take their questions and clarify the strategy and ideally get them to give you the thumbs up. People tend to be more comfortable asking questions in smaller groups so you will uncover things you may not have thought about. It’s also a great opportunity for product leaders to engage directly with teams and get a better sense of what’s top of mind for them.
Any other suggestions to make the product strategy stick?