Design Critique Notes: Project / screen name
Crit notes – severity-tagged feedback
Mode d'emploi: Crit sessions. Feedback as observation + question, severity-tagged – not taste verdicts.
Aperçu
Design Critique Notes: Project / screen name
Date: YYYY-MM-DD · Presenter: @designer · Reviewers: @a, @b
What was presented
Which flow/screen/prototype, and the stage (concept, wireframe, high-fidelity, implementation).
Goals stated by designer
The problem the design is solving – critique against this, not taste.
Feedback
| Area | Comment | Severity | Owner |
|---|---|---|---|
| Layout | Feedback phrased as observation + question | blocker / suggestion / nit | @name |
| Interaction | ... | ||
| Copy | ... | ||
| Accessibility | contrast, focus, labels |
Strengths to keep
- What is working – protect it in revision
Open questions
- Question needing product/engineering input
Decisions
- What was agreed in the room
Next iteration
- Revision item one – owner – due
- Re-review date