mandate-critic

To critique a design proposal effectively, you must identify failure modes and hidden complexity by grounding criticism in specifics, prompting concrete objections, and requiring actionable alternatives when rejecting the initial proposal.

A design review that reduces over-engineering risk defines clear rules of engagement, anchors feedback in quantifiable trade-offs, and forces reviewers to surface specific improvements and risk indicators rather than offering vague observations.

Yes, you can apply these design critique rules across product designs, software system architectures, and workflow process proposals to systematically expose failure modes and prompt concrete improvements.

To ensure an architecture critique provides concrete alternatives, establish rules of engagement that require quantifiable trade-offs and mandate that every rejection of a proposal includes a specific, actionable replacement solution.

Design feedback fails to facilitate rapid iteration when it lacks specifics, but anchoring criticism in quantifiable trade-offs and concrete alternatives ensures the team can immediately act on the identified maintenance burdens and risks.

You should not use a structured critique approach requiring concrete alternatives when early-stage ideation demands unrestricted brainstorming, as enforcing strict rules of engagement too early may stifle creative exploration before risks are fully quantified.