problem-exploration

To explore design options before committing, run a structured brainstorming workflow that defines the problem, lists viable solutions exhaustively, and analyzes trade-offs. This prevents teams from leaping to the first plausible path during complex product development.

A structured problem definition workflow formally identifies the problem space, enforces exhaustive option generation, and documents decision rationale. It ensures teams evaluate trade-offs and identify unresolved gaps before implementation begins.

To analyze trade-offs for multiple solution paths, evaluate explicit pros and cons while assessing risks for each viable option. This formal analysis justifies the chosen approach and identifies unresolved gaps before implementation.

Use a formal brainstorming workflow for decision-making when facing complex technical problems with multiple plausible paths and uncertain requirements. It forces structured problem exploration to prevent committing prematurely to an approach.

To document validation criteria and gaps after choosing a technical approach, record the decision justification alongside identified unresolved gaps. This guides implementation by defining exactly how the chosen path will be validated.