brainstorm

To brainstorm feature design options, you provide a feature idea and request multiple approaches. The process enforces a hard gate on implementation until a design is approved, ensuring alignment before coding begins.

Divergent design exploration frames the design space before committing to a spec. You need this process for non-trivial features where early design decisions matter across product, engineering, and UX contexts to prevent misaligned expectations.

A pre-mortem risk analysis anticipates failures for each design approach generated during brainstorming. You run it after creating two to three design options with trade-offs to evaluate potential risks before selecting a recommended path.

Yes, clarifying questions refine requirements one at a time during design exploration. This guided context reading ensures stakeholder alignment before generating design options and prevents premature narrowing of the solution space.

Yes, the design-thinking process enforces a hard gate on implementation until a design is approved. This prevents premature narrowing and ensures stakeholder alignment before any coding begins on the feature.

Brainstorming design options is limited to non-trivial features and problems where early design decisions matter. It requires stakeholder alignment and guided context reading, making it less suited for simple, straightforward implementation tasks.