FADA1010 Chap.5 Critique, Feedback and Collaboration
Critique, Feedback and Collaboration
Design critique is a collaborative conversation intended to improve the work, not judge the person. This chapter builds feedback from specific observation through clarifying question to a testable suggestion, then returns responsibility to the designer.
It also shows how to record accepted and declined comments so collaboration becomes visible evidence of development without confusing peer support with shared authorship.
What this chapter covers
- 01
Presenting intent and uncertainty
- 02
Specific observation before judgement
- 03
Clarifying questions and actionable suggestions
- 04
Receiving feedback without defensiveness
- 05
Interpreting contradictory comments
- 06
Recording collaboration and individual decisions
Worked example · free
Rewrite vague praise as a test
- 1Identify a visible feature and the effect it currently creates.
- 1Ask whether that effect matches the designer's intended experience.
- 1Propose a small comparison test without taking ownership of the project.
Key terms
- Design Critique
- A structured conversation that analyses a design and offers perspectives or suggestions for improvement.
- Feedback
- Information about how work is perceived or performs that can guide evaluation and revision.
- Collaboration
- A process in which people contribute perspectives and support while responsibilities and authorship remain clear.
- Actionable Suggestion
- A specific proposal small enough to test in the next design iteration.
Critique, Feedback and Collaboration FAQ
How is critique different from judgement?
Critique focuses on the work, its stated intention and observable effects. It asks questions and proposes tests. Judgement often stops at liking, disliking or ranking, which gives the designer little evidence about what to change or investigate.
Should every suggestion be applied?
No. Record comments, compare them with the core concept and project constraints, then select the most important uncertainty to test. Explain why a suggestion was accepted, transformed or declined so the journal shows responsible individual decision making.
What if feedback conflicts?
Ask what each person observed beneath the proposed change. Contradiction may indicate an unclear cue, different audience needs or an unresolved tradeoff. Create a small comparison that tests the underlying issue rather than choosing the most popular suggestion automatically.
Assessment move
Prepare for critique by stating the core concept, what the current version is testing and one focused uncertainty. During the conversation, write observations before defending the work. Ask for clarification and the reason beneath each suggestion. Afterward, sort comments into concept, communication, interaction, form, material and execution. Identify the issue that blocks progress and design a manageable test.
Paste or transcribe key feedback beside the affected iteration, then show the response and result. If you decline advice, record the concept, evidence or constraint behind the decision. Practise giving feedback with an observation, a question and a possible experiment. Avoid vague praise, personal judgement and instructions that redesign the project for someone else.
This method turns peer support into traceable development while preserving individual authorship. Design the critique setup so the work can be read before it is explained. Display the current artefact, relevant prior version, core-concept sentence and test question together. Ask peers first to describe what they notice and infer. Their language reveals which cues are legible without prompting.
Only then add context, because a long introduction can train the group to repeat your preferred interpretation. Give responders a structure: point to a feature, describe its effect, connect it to the stated intention, ask a genuine question and propose an experiment when useful. A suggestion without the observation behind it is hard to evaluate. The designer should listen for patterns while resisting the urge to tally votes.
Three similar comments may identify a communication issue, but one dissenting observation can expose an audience or context the group overlooked. Record exact phrases beside photographs rather than reducing everything to positive or negative. After the session, translate comments into testable hypotheses. If peers call a form confusing, specify which relationship they misread and create two controlled alternatives.
If they request more colour, determine whether hierarchy, mood or visibility is the actual concern. Rank actions by their influence on concept and use, the uncertainty they can resolve and the time required. Cosmetic adjustments should not displace a test that could change the whole direction. Collaboration also requires accountable authorship.
Attribute a peer's insight when it materially redirects the work, but show the judgment and making through which you transformed it. Declining a recommendation is legitimate when the journal records a defensible reason. For group exercises, note your role, the shared outcome and the contribution that informed your individual process.
End each critique cycle with a response sheet containing selected action, responsible maker, evidence to collect and review date. At the next meeting, present the before-and-after comparison and explain what the test established. This closed loop prevents feedback from becoming a ceremonial list and demonstrates that conversation altered design practice in observable ways.
