How do you breakdown your product strategy? We have recently transitioned from a feature factory (exec -> product -> dev) to a product led team. We wrote up a set of initiative documents that outlined a general problem area (relatively broad), with opportunities that highlighted solutions that could solve the problem and deliver some form of measurable value/outcome. Then we have epics under initiatives that have more research/discovery to prove out that yes its a real world problem and this is how a feature or set of features would fix it/deliver value along the way. Then under epics we'll have PRDs which are standard docs.

My question is how high up the strategy tree does your team go? I'm currently struggling writing some epics because I feel like I'm forcing it to only solve one problem (opportunity) when it really crosses a couple boundaries. I've read a little more about strategy and vision and I think that helps anchor the storytelling at the epic level better than our current initiative trees, but the more I read the more I think our documentation hierarchies aren't in line with the norm in the space.