brainstorming

Brainstorming transforms vague concepts into fully-formed designs through iterative questioning about purpose, constraints, and success criteria. It presents designs in 200-300 word sections with 2-3 alternative approaches and trade-offs, creating a validated foundation ready for development or detailed planning.

Brainstorming proposes 2-3 different approaches for each design challenge, explicitly outlining trade-offs so you can make informed choices. This comparative exploration happens during ideation, before committing resources to a single path.

Brainstorming presents designs in small, digestible sections using one-question-at-a-time prompts, validating each part before proceeding. This incremental approach catches misalignments early and ensures a solid foundation for downstream work.

Yes. Brainstorming generates design documentation that integrates with version control and plan-writing workflows, making design rationale and alternative considerations visible and shareable across your team.

Use brainstorming during early ideation and design phases for software, product, and process initiatives—before writing code or detailed plans. It's most effective when you have a concept that needs clarity, foresight, and structured exploration.

Rough ideas often lack clarity, foresight, and alternative considerations, leading to poorly designed solutions and wasted effort if implemented prematurely. Brainstorming applies disciplined questioning and validation to prevent these costly mistakes.