brainstorming

Brainstorming refines rough ideas into fully-formed designs through structured dialogue. It asks focused questions one at a time, explores 2-3 alternative approaches with trade-offs, validates designs incrementally, and produces documentation and implementation steps ready for development.

Collaborative brainstorming presents multiple design approaches with clear trade-offs, validates each section before moving forward, and captures reasoning in documented specifications. This prevents costly rework by aligning on architecture and implementation strategy before coding begins.

Design validation through brainstorming breaks specifications into small sections, confirms understanding after each part, and surfaces competing approaches so teams align on trade-offs. This incremental validation catches misalignment early in the design phase.

Use brainstorming during early feature planning and architectural decisions when ideas are still rough and assumptions unclear. It's most valuable before development work begins, when stakeholders need to align on direction and the cost of rework is highest.

Yes. Brainstorming applies to any design phase—technical architecture, feature specification, and system planning. Its structured questioning and alternative-exploration workflow works across design domains requiring collaborative refinement before implementation.