Poor requirements definition are a common point of conflict between product managers and engineers, and between stakeholders and product. Product blames engineering for a perceived lack of delivery. Engineering blames product for prioritizing overly prescriptive, low-impact initiatives which may later be de-scoped. Priorities lacking in clear business purpose may even be overruled by stakeholders. Turn the paradigm around. Use contextually-rich, hypothesis-led, outcome-driven opportunity frameworks to create clarity of the focus problem to be solved and empower a motivated team to unleash their creativity on a solution.