One of the important skills of a product manager is to be able to tell a story about how to get from today to the desired result, for example, in a year. Such a document should make the reader feel like “I understood everything and believe not only in the idea, but also in the plan.”
Despite the fact that the story can be written in different ways (hence the 100500 strategy templates), the main complex questions remain in place. Therefore, by the way, the template is applicable to projects of any size, it will just change the level of detail and the name of the document - and the “complex” questions will remain the same, and they can be asked for:
- Projects/company strategy (Project Review doc, Strategy doc)
- Services/team strategy (Product Review doc, Service scope doc)
- Features/team projects (Product Requirements doc, Stories Breakdown for backlog)
The template described above is a great start to strategic planning and is enough to communicate your plans to others. But don’t forget that everything said still needs to be built. Therefore, examining the system's technical state and limitations is often necessary to make the strategy more resistant to reality. You can look at the advanced Full Product Review template
here.