Requirements-driven product definition is a sure-fire way to get 100% of the wrong product launched. The assumptions that requirements are based on are usually not accurate enough to determine the exact solution those requirements dictate. Instead, teams should focus on creating a series of hypotheses that define potential solutions to their business problem business problem and then work together to learn which of these hypotheses are keepers and which ideas to kill.