nw-diverge

A structured divergence workflow transforms a validated problem into 3-5 design directions by enforcing a four-phase process: JTBD analysis, competitive research, brainstorming, and taste evaluation. This ensures solution paths are systematically explored rather than guessed.

Structured divergence is a four-phase process used when a problem is validated but no solution path is chosen. You should use it for new products, brownfield features, or pivot redesigns to systematically explore diverse design options before committing to a direction.

JTBD analysis helps with brainstorming product features by extracting core jobs and ODI outcome statements from your validated problem. This frames the subsequent brainstorming phase to ensure generated design directions directly address actual user needs and desired outcomes.

Yes, you can use this divergence workflow for brownfield feature redesigns. It is explicitly designed to handle new products, brownfield features, and pivot redesigns whenever a problem is validated but a specific solution path has not yet been chosen.

You evaluate and rank competing design directions using a taste evaluation phase that scores brainstormed options using fixed weights. This structured ranking process gates quality and outputs the final prioritized design directions to your feature-level artifacts.

A limitation of this structured divergence workflow is that it requires a validated problem as input; it cannot generate design directions for unvalidated or poorly defined product issues. Additionally, its taste evaluation phase relies on fixed weights, which may not suit highly dynamic market contexts.