brainstorming

Structured brainstorming enforces one-question-at-a-time prompts to maintain focus, guiding teams through Understanding, Exploring Approaches, Presenting Design, and After Design phases to surface requirements and viable design options.

Facilitate architecture planning by articulating a clear problem statement, then guiding the process through four structured dialogue phases to surface intent, constraints, and 2-3 approaches with trade-offs before implementation.

Yes, structured ideation presents 2-3 design options with trade-offs and recommended paths during the Exploring Approaches phase, ensuring teams evaluate viable approaches before finalizing a validated design plan.

Document validated design plans by saving the output to docs/plans/YYYY-MM-DD-brainstorming-design.md, creating a suitable record of surfaced requirements, constraints, and recommended design directions for future reference.

You need structured ideation when brainstorming sessions stall or lack structure, leading to unclear requirements and design directions at project kickoff or review sessions before implementation begins.

Yes, structured brainstorming is applicable to cross-functional collaboration at project kickoff and review sessions, using one-question-at-a-time interactions to maintain focus and pace across team members.