Wireframe Feedback & Critique

Overview

Creating and analyzing are different processes — never do both at once (Corita Kent's rule 8). Critique is structured analysis: evaluate the design against defined criteria, gather enough actionable information to fuel the next creative pass, then stop. The goal is a better design for the user, not consensus, approval, or defense of the current version. You are not your design.

When to Use

• Requesting feedback at any wireframe stage — early concepts through near-final detail
• Facilitating a team critique, stakeholder review, or async comment round
• Translating vague or solution-shaped feedback into usable problems
• Triaging a pile of post-review comments into a plan
• NOT for: usability testing — critique is expert/team analysis; user evidence needs real users on real tasks
• NOT for: sign-off meetings — critique improves the design; approval is a separate decision forum with different stakes

Asking for Feedback