brainstorming

Brainstorming refines rough ideas into fully-formed designs through structured questioning, alternative exploration, and incremental validation. It guides you through phases of understanding requirements, proposing 2-3 approaches with trade-offs, validating designs in sections, and documenting the outcome—preventing premature coding and ensuring alignment.

Structured brainstorming proposes 2-3 architectural approaches with explicit trade-offs, letting you compare options before committing to one. This alternative exploration fosters informed decision-making and surfaces constraints and dependencies early, reducing rework and costly pivots later.

Use Socratic questioning to systematically gather purpose, constraints, and success criteria from stakeholders. This ensures all angles are covered upfront, prevents misalignment, and creates a shared understanding of what success looks like before design or implementation begins.

Use brainstorming before writing any code on new features, products, or architectural changes. It applies to early-stage ideation across product design, software architecture, and documentation, preventing wasted effort on solutions that don't meet unstated requirements or constraints.

Incremental design validation presents your design in sections and gathers feedback after each, allowing flexible progression and early course correction. This staged approach catches misalignments before implementation and reduces the risk of building the wrong solution.

Brainstorming generates design artifacts and setup instructions written to documentation files, creating a handoff for implementation. This ensures the design rationale, decisions, and next steps are recorded and accessible to anyone executing the work.