Get to the bottom of the strategy with this question-based approach and avoid all other frameworks. Strategy is about understanding where you're headed, why it matters and how to get there.
My best learning for strategy came from when I was working in the automotive domain. Those guys are super clear about what it takes to make a product succeed and crisp directional docs was one such tool. At the early stage, built a ‘concept note’ which was a sharp doc which clearly explained what, why and the how we’ll succeed with the next car we’ll build. It was one coherent document where multiple aspects worked together like music. Making that doc was the single most high leverage task I did early on in my career.
And the industry continues to inform my thinking even as I’ve transitioned to the software side.
A couple of years ago, I worked with a client where we shared different interpretations of 'strategy' and it led to consistent problems in the entire project. I suspect just getting better at sharing common definitions will hep most people along the journey. Some of the questions remind me of my university days studying marketing strategy. Proof that many concepts are timeless.
Thank you Bandan, solid framework. For the sake of making it explicit I’d add between 4. and 5. « What are our current weaknesses / gaps in adopting this strategy ? ». The solution to these will show up among other things in your 5. But taking the time to call out the weaknesses (and strengths in 4.) adds up to a diagnosis : to me that’s what most companies fail doing in many cases …
Great article. Thanks for writing this.
Would you be able to share an example strategy doc condensed from this framework?
Hi Bandan, this post really helped me understand the difference between tactic and strategy. Keep the great work up :)
Really good and simple post about strategy.
My best learning for strategy came from when I was working in the automotive domain. Those guys are super clear about what it takes to make a product succeed and crisp directional docs was one such tool. At the early stage, built a ‘concept note’ which was a sharp doc which clearly explained what, why and the how we’ll succeed with the next car we’ll build. It was one coherent document where multiple aspects worked together like music. Making that doc was the single most high leverage task I did early on in my career.
And the industry continues to inform my thinking even as I’ve transitioned to the software side.
Insightful read. I like how you highlighted the importance of reassessing the strategy regularly to avoid rigidity and stagnation.
When so you see the product strategy document being implemented in the case of a startup. At what stage does it become mandatory?
This post is worth reading.
A couple of years ago, I worked with a client where we shared different interpretations of 'strategy' and it led to consistent problems in the entire project. I suspect just getting better at sharing common definitions will hep most people along the journey. Some of the questions remind me of my university days studying marketing strategy. Proof that many concepts are timeless.
Thank you Bandan, solid framework. For the sake of making it explicit I’d add between 4. and 5. « What are our current weaknesses / gaps in adopting this strategy ? ». The solution to these will show up among other things in your 5. But taking the time to call out the weaknesses (and strengths in 4.) adds up to a diagnosis : to me that’s what most companies fail doing in many cases …