Summary: Discussing Design (Book)

in Papers

I really like the book Discussing Design. Here is an AI generated summary of what is in it. The authors give away the first chapter. This summary can help you decide if you want to read more than that.

I asked Claude to summarize the book considering what students in my class might get out of it. In the past, I asked students in my class to read the first chapter of the book. Now, I require students to read Tutorial 4: Critique and make the first chapter optional.

Chapter-by-chapter notes on Connor & Irizarry, “Discussing Design: Improving Communication and Collaboration Through Critique” (O’Reilly, 2015). Read against two framing messages for CS765: critique as a way to learn and critique as a general skill, not just something designers do. The book’s own audience is designers working in organizations — these notes filter for what transfers to a student learning visualization, and flag what doesn’t. Page numbers are book pages.

The book’s structure in one line: Ch1 defines critique, Ch2 covers the two roles (giving/receiving), Ch3 covers the conditions that make critique possible, Ch4–5 cover process and facilitation mechanics, Ch6 handles pathologies, Ch7 recaps, and Appendix A is the whole book compressed into ten bad habits.

Chapter 1: Understanding Critique (pp. 1–19)

The foundational chapter, and the one that carries almost the entire message a vis student needs — which is why it worked as the standalone assigned reading, and why its key ideas are now folded into VisSnacks Tutorial 4. It diagnoses why asking for “feedback” produces junk (feedback is just any response), separates three forms — reaction, direction, critique — and defines critique as analysis: critical thinking about whether design choices serve the design’s objectives. The three-element formula (aspect, objective, how/why) lives here, as does the two-part framing (critique = critical thinking + delivery).

For students, the quietly important sections are the ones easy to skim past: Critiquing Solo (p. 11) — the creative/analytical toggle — legitimizes critique as a private learning practice rather than a social event, which is exactly the “critique as a way to learn” message. And Why Critique Is So Important (pp. 11–15) gives the group-level payoff: shared vocabulary, objective-grounded consensus, directed iteration.

  • Feedback has three forms: reaction (gut, including polite “looks great!” praise), direction (prescriptions), critique (analysis). Only the third tells you whether the design works. (pp. 5–10)
  • Good critique = specific aspect + related objective/best practice + how/why it supports or doesn’t. (p. 9)
  • Objectives come in kinds: utility, measurable, experiential. (p. 10)
  • Critique alone: toggle deliberately between creating and analyzing your own work. (p. 11) The learning-skill framing in one section.
  • Critique builds shared vocabulary — for a class, this is the pedagogy itself. (pp. 11–13)
  • Critique = critical thinking + delivery; anything constructed against an objective can be critiqued, not just pictures. (pp. 17–18) The “beyond designers” message.

Chapter 2: What Critique Looks Like (pp. 21–45)

The practice chapter: two roles (giver, recipient), with intent as the hinge — the giver’s proper intent is helping the designer understand the effects of their choices; the recipient’s is understanding whether the design serves its objectives (not defending it). Bad critique is characterized (selfish, untimely, incomplete, preferential), then best practices for giving (lead with questions, use a filter, don’t assume, don’t invite yourself, talk about strengths, think about perspective) and receiving (the anti-patterns: asking without listening, asking for praise/validation, not asking at all; then: listen fully → ask clarifying questions, relate stray feedback back to objectives, and participate in critiquing your own work).

For students this is the most directly actionable chapter after ch1, because 765 students occupy both roles twice per module (S4 draft critiques, peer video feedback). The receiving side is material the course has never assigned (it was outside the free chapter) — the biggest untapped vein in the book.

  • Intent separates useful critique from performance, on both sides. (pp. 21–22)
  • Bad-critique characteristics: selfish, untimely, incomplete, preferential — recognizable instantly in peer-feedback settings. (pp. 22–28)
  • Giving: lead with questions; talk about strengths (analysis of what to keep, not politeness); don’t assume the designer didn’t consider your idea. (pp. 28–36)
  • Receiving: you asked for analysis, not applause — listen to understand, ask clarifying questions, don’t defend. (pp. 36–41)
  • When feedback seems off-track, return to the objectives — either it connects, or you’ve discovered the group disagrees about objectives (also worth knowing). (pp. 41–42)
  • Critique your own work in front of others: it normalizes analysis, models the form, and takes the sting out. (pp. 42–43)

Chapter 3: Culture and Critique (pp. 47–75)

The conditions chapter. Mostly organizational (politics, territorialism, remote teams), but three ideas transfer cleanly. First, the incremental vs. iterative distinction (pp. 50–55): incremental processes add pieces without revisiting; iterative processes rework. Critique only pays off in an iterative process — feedback you can’t act on is decoration. Second, the foundation (pp. 56–65): critique requires mutually understood objectives (the book’s versions: goals, personas, scenarios, principles), or every participant steers by private preference. Third, practice: “Critique is a skill. It must be practiced. Don’t expect it to be perfect the first time” (p. 70) — the book’s own version of the course’s stance.

For a student: the incremental/iterative distinction explains why the course keeps making you revise things (drafts, do-overs) — critique and iteration are two halves of one mechanism. The remote-critique section (pp. 71–75) is unexpectedly relevant: “collaboration is a mindset, not a result of co-location” applies directly to critiquing recorded video walkthroughs.

  • No iteration, no point: critique presumes willingness to rework, not just add. (pp. 50–55) This is the intellectual justification for drafts and do-overs.
  • Shared objectives are the foundation; without them critique degenerates into preference-swapping. (pp. 56–65) In class, the formula’s “if the objective is…” clause carries this.
  • Personal barriers are real (fear, history, culture); safety is a precondition, and it is built, not assumed. (pp. 66–70)
  • Critique is a skill built by repetition — expect to be bad at it first. (p. 70)
  • Remote/asynchronous critique works if the mindset is right. (pp. 71–75) Direct support for video-based peer feedback.

Chapter 4: Making Critique a Part of Your Process (pp. 77–108)

The process chapter: standalone critiques (formal and informal, with Pixar’s dailies as the flagship example), critique inside collaborative activities (divergent idea generation → critique as the convergence mechanism), and design reviews (which the book firmly says are not critique — they’re approval gates).

The jewel for the course is When Should You Critique? (pp. 84 ff): a design is critiqueable when two conditions hold — the idea is developed enough to communicate, and there is still time to use the feedback. Too early and nobody can respond to a lump; too late and the analysis is a post-mortem. This is precisely the logic of the draft checkpoint before S4, stated better than we’ve stated it.

  • Critique when the idea is communicable AND there’s still time to iterate — the “bakedness” window. (pp. 84–88) Quote this when explaining why drafts are due before the critique session.
  • Small groups, intentional participants; listen and think before speaking. (pp. 77–79)
  • Informal critique (“grab the person next to you”) counts, and is the habit worth building — critique isn’t a meeting type, it’s a way of talking. (pp. 79–84)
  • In group ideation, critique is how you converge honestly — analysis against objectives, instead of voting or volume. (pp. 92–104) Useful frame for group ICEs.
  • Reviews ≠ critique: approval and analysis are different activities. Critique before the review. (pp. 104–108) The student version: grading isn’t critique; the critique already happened, in class, where you could act on it.

Chapter 5: Facilitating Critique (pp. 109–141)

The facilitation chapter — written for whoever runs the session, which in 765’s format is sometimes the instructor, sometimes a TA, and (in small groups) rotating students. The four rules (pp. 111–116) are the distilled classroom-usable core: everyone is equal (no rank in the room), everyone is a critic (participation isn’t optional, and non-designers’ analysis counts), avoid problem solving (analysis first; solutions are a different meeting — the hardest rule, since solving is instinctive), don’t rush decisions (the output of critique is understanding, not a to-do list). Plus the optional “no ‘I like/don’t like’” rule — phrased in the book as a trainable constraint, matching the tutorial’s “own your opinions.”

The presenting-side prep is also useful for students: describe the objectives first, present the work quickly, be careful with constraints. And the collect-and-follow-up section (share notes, record open questions) maps to capturing ICE artifacts.

  • The four rules — post them in the room. (pp. 111–116) Candidate for a one-slide “rules of our critique circles.”
  • “Everyone is a critic” directly answers the student worry “I’m not qualified to critique yet.” Analysis against objectives requires no design credentials. (p. 112)
  • Problem-solving during critique derails analysis — park solutions for after. (p. 113)
  • Critique output = observations and understanding, not a change list; the designer still owns decisions. (pp. 113–116)
  • Presenting for critique: state objectives first, present quickly and efficiently. (pp. 117–125) This is the skeleton of the 2-minute video walkthrough.
  • Facilitation moves: define scope and goals, active listening, direct inquiry, note-taking. (pp. 126–136)

Chapter 6: Critiquing with Difficult People and Challenging Situations (pp. 143–167)

The pathology chapter. Much of it is office politics (executives, clients, saboteurs) and can be skipped by students — but two techniques and one principle transfer. Laddering (pp. 152 ff): repeatedly asking “why?” to unpack vague or preference-based feedback until it either connects to an objective or reveals itself as taste. The universal de-escalator: when a conversation goes sideways, return to the shared objectives — refocusing on the product, not the people. And setting expectations up front (rules, structure, focus) prevents most difficulties before they occur — the argument for teaching the critique format explicitly in M0 rather than letting norms emerge.

  • Laddering / 5-whys: a learnable move for turning “I don’t like it” (yours or a peer’s) into analysis. (pp. 152–156)
  • When critique drifts or heats up, return to objectives — it’s the reset button. (pp. 148–152)
  • State the rules and scope at the start; most difficulty is misaligned expectations. (pp. 144–148)
  • Quiet participants often have the most useful unspoken analysis; structure (small groups, written-first artifacts) gets it out. (pp. 150–152) Supports the prep-artifact → small-group design.

Chapter 7: Summary (pp. 169–173)

A recap chapter; nothing new. Skippable for students. Its one-line takeaway is the book’s thesis: critique is not a meeting type or a deliverable — it’s a change in how you talk about the things you make.

Appendix A: The 10 Bad Habits That Hurt Critique (pp. 175–179)

The whole book as a checklist, and honestly the best five minutes a student can spend with it: reacting (verbalizing before analyzing), being selfish (feedback about you, not the work), getting defensive (“explain your work, do not defend it”), starting from disparate foundations (no shared objectives), lacking focus, focusing only on what isn’t working (strengths are analysis too), lack of discussion (a to-do list over email isn’t critique), avoiding participation (critique your own work alongside others), problem solving (mid-critique), confusing critique with review (approval ≠ analysis).

  • This appendix could serve as the one assigned excerpt beyond the tutorial: short, self-contained, and both course messages are implicit in it.
  • “Explain your work, do not defend it” (p. 176) is the single most quotable line in the book for students presenting drafts.

Where this feeds the course (quick map)

  • Tutorial 4 already absorbed ch1’s five key ideas. The next-highest-value absorption is ch2’s receiving side (a “when you’re the recipient” section) — currently nowhere in the course.
  • Critique-circle rules (S3/S4 sessions): ch5’s four rules + appendix habits → a one-page handout / M0 slide.
  • Draft-checkpoint rationale: ch4’s bakedness window — quote it on the DE pages.
  • Video walkthrough skeleton: ch5’s presenting guidance (objectives first, quick presentation).
  • Peer-feedback training: laddering (ch6) + “everyone is a critic” (ch5) answer the two standard student objections (“their feedback is vague,” “I’m not qualified”).
  • Assignable excerpt candidates, given only ch1 is public: nothing else can be assigned as-is — so the ch2/ch5 material worth student eyes must be paraphrased into VisSnacks (with attribution), or covered in class. Appendix A is short enough that its ten habit names + one-line glosses fit in a tutorial box without reproducing the text.

GenAI Disclosure:

Claude wrote the summary.