pm-product-brainstorming

To stress-test product ideas before writing specs, you can run a structured brainstorming session that explores the problem space, generates divergent solution paths, and challenges underlying assumptions using frameworks like HMW and JTBD. This prevents premature convergence on unvalidated directions.

Assumption testing in product discovery is the process of identifying the riskiest beliefs underlying a product idea and proposing the cheapest tests to validate them. It works by applying devil's-advocate pressure to decompose what must be true for a strategy to succeed, mapping options across time horizons.

Yes, you can use ideation frameworks like OODA and JTBD for problem exploration to distinguish symptoms from root causes. Framework-guided reasoning helps surface adjacent problems and clarifies what must be true for the core problem to exist, ensuring you solve the right issue.

To validate product strategy and avoid premature convergence in fast-moving environments, apply a structured session flow of frame, diverge, provoke, and converge. This method rigorously critiques multiple solution options, including inversion and constraint-removal paths, before settling on a direction.

The best way to rethink a stuck product roadmap is to conduct a strategy exploration session that identifies root-cause clarity and generates divergent solution paths. By challenging underlying assumptions and mapping strategic options across time horizons, you can uncover new product directions.

You should not use a structured product brainstorming approach when you need immediate tactical execution rather than strategic discovery, or when the problem space is already thoroughly defined and validated. This approach targets avoiding premature convergence by investing time in rigorous assumption testing.