brainstorming

To turn a rough idea into a validated design specification, you clarify product goals and constraints through iterative, one-question-at-a-time dialogue before implementation begins. This process surfaces success criteria early to prevent building the wrong feature.

Evaluating alternative approaches during feature planning involves comparing 2-3 possible design paths with their respective trade-offs. This method recommends a clear path forward by contrasting architectural impacts and component behaviors before committing to implementation.

You scope a new product idea incrementally by reviewing the design in small, validated sections covering architecture, components, data flow, error handling, and testing. This incremental spec review reduces ambiguity and ensures all behavior changes are well-defined.

Yes, you can use this brainstorming process for changing existing software behavior. The guided creative planning and intent discovery steps apply directly to modifying existing features, ensuring the updated behavior changes are fully scoped and validated.

You need to define requirements and success criteria before building a feature whenever you have a rough product idea or component design. Defining these early through intent discovery surfaces constraints and avoids the cost of building the wrong functionality.