design-review

Review a design document for rigor by evaluating problem statements, decision matrices, and scope documents to ensure they are root-cause focused, evidence-based, and clearly scoped. This prevents flawed solutions and wasted development effort.

Solution contamination in a problem statement occurs when the proposed solution dictates the problem definition rather than remaining solution-agnostic. Check for it by analyzing artifacts to ensure the root cause is clear and independent of specific implementation choices.

Evaluate a decision matrix by analyzing it for specificity, evidence quality, and constraint realism. This ensures the matrix adheres to established design principles and provides structured feedback to identify critical findings before development starts.

Yes, the design review process specifically analyzes scope documents and problem statements for completeness and adherence to best practices. It identifies critical findings and provides structured feedback to ensure design quality before implementation.

The best way to ensure design artifacts are ready is to critically evaluate them for root cause clarity, specificity, evidence quality, and constraint realism. This structured feedback prevents costly rework by aligning designs with best practices.

A scope document lacks rigor when it fails to be specific, evidence-based, or clearly scoped. Improve its quality by using structured feedback from an artifact analysis that checks for constraint realism and adherence to established design principles.