You have Already Succeeded: Design Critique Guidelines make Feedback Easier
summary
Claim: asking for feedback already counts as success and a short set of design critique guidelines makes critique actionable. Steps: write a scope/skill statement that lists goals and what feedback is wanted or not, identify stakeholders, collect focused feedback via thinking caps sessions, stickers, wikis or quick scheduled reviews, always start with positives, pose critiques as questions, tie every suggestion to project goals, own and triage feedback afterward, follow up and accept that iterative changes—not unanimous approval—measure success.
AI-written summary · about
chapters (5)
- 0:00Start
- 3:12What do you need?
- 5:43How do you start?
- 7:00How do you get people involved?
- 11:37How do you give feedback?
related talks
29mFrameworks for Feedback
30mCode Reviews Using Art Critique Principles
33mFinding your edge through a culture of feedback
29mDriving clarity in ambiguous projects
30mCode Reviews Using Art Critique Principles
35mFeedback: You don't have to be bad to get better
12mEffective communication: Mastering growth-oriented feedback
31mDesign FAQs from 5 Years of Coaching FOSS Projects