sp-brainstorming

To clarify user goals and design requirements before implementation, use a guided brainstorming process that asks one question at a time, proposes concrete design directions, and formally documents specifications to prevent rework.

Achieving design consensus during early UX planning requires presenting 1-2 feasible design directions with evaluated pros and cons, allowing stakeholders to align on key features and design rules before any building starts.

One-question-at-a-time ideation for system design works by sequentially confirming user intent and background, ensuring deep understanding of requirements before proposing concrete solutions and documenting final specifications.

Yes, you can use this brainstorming approach for product discovery and requirements gathering to deeply understand user backgrounds, evaluate design options, and formalize rules and key features for downstream implementation.

You should not use guided brainstorming for ideation when implementation has already begun or when the requirements are already fully specified, as this process focuses exclusively on pre-implementation discovery and consensus.