I love how Marty Cagan emphasizes giving product teams "hard problems to solve, and then giving them the space to solve them" - it's all about trust and autonomy in product development.
https://www.svpg.com/product-strategy-overview/
I've seen this approach work well in agile environments, but how do you ensure that 'hard problems' align with overall business objectives and don't lead to scope creep?
I've seen that approach work well in our org, but what about when teams are still learning the product domain - do you think they need more guidance then?