brainstorming

Software architecture design uses Socratic questioning to uncover requirements and constraints, ensuring implementation begins only after a formal design document is explicitly approved.

You explore different software architecture approaches by evaluating 2-3 distinct implementation options, analyzing their trade-offs and potential failure points, and documenting the chosen design before coding begins.

You should use a structured design process for product development before starting any new feature, ensuring creative implementation begins only with an explicitly approved design to mitigate building the wrong thing.

You prevent project scope escalation during requirements gathering by using a structured design process that includes explicit checks for scope creep and mandates technical feasibility research before finalizing the agreed-upon design.

Yes, you can use Socratic questioning to collaboratively define problems and explore solutions like API design or data models, ensuring all implementation approaches are explicitly approved before development starts.

Yes, you need technical feasibility checks before finalizing a software architecture design, as the structured design process mandates using tech-feasibility and critical-research for technical decisions to prevent wasted effort.