{"id":5268,"date":"2016-06-02T05:00:32","date_gmt":"2016-06-02T05:00:32","guid":{"rendered":"http:\/\/elireview.com\/?p=5268"},"modified":"2016-05-26T16:33:12","modified_gmt":"2016-05-26T16:33:12","slug":"feedback-triage","status":"publish","type":"post","link":"https:\/\/elireview.com\/2016\/06\/02\/feedback-triage\/","title":{"rendered":"Around the web: triaging feedback"},"content":{"rendered":"

Getting helpful feedback on writing isn’t enough; as we argue in our student module Rethinking and Revising Using Feedback to Improve Our Writing<\/a>,\u00a0selecting<\/em> from the feedback you receive is also important.<\/p>\n

Clark Wimberly<\/a>, writing for The Next Web<\/a>, describes a similar process when giving advice for how designers can handle feedback they receive during critiques. He describes a face-to-face\u00a0feedback process, where “you\u2019re deep into the review session and feedback is flying … before you start writing everything down, remember that it\u2019s possible to have too much of a good thing.”<\/p>\n

He describes his process for triaging the feedback he receives from his colleagues:<\/p>\n

I usually file my feedback into three\u00a0main buckets:<\/p>\n

    \n
  1. \n

    Low hanging fruit we can knock out right now<\/p>\n<\/li>\n

  2. \n

    Important things to get done by launch<\/p>\n<\/li>\n

  3. \n

    Other things to tackle sometime after launch<\/p>\n<\/li>\n<\/ol>\n

    Good ideas are capable of landing in any bucket\u2014it all just depends on timelines, goals, and available team power.<\/p><\/blockquote>\n

    He further adds:<\/p>\n

    With a daunting, updated to-do list in front of you, keep your sanity by figuring out what can be fixed in your current design space. Find the tweaks and changes that have the biggest impact with the smallest amount of rework. Tackle those first.<\/p><\/blockquote>\n

    Clark is, essentially, building a revision plan<\/a> by sorting through feedback, prioritizing, and then using the plan to act. But in his case, as in the case we lay out in our revision module<\/a>, you have to triage (or select) before you act.<\/p>\n

    \n

    Source<\/strong>:\u00a0How to handle a design critique<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

    Getting helpful feedback on writing isn’t enough; as we argue in our student module Rethinking and Revising Using Feedback to Improve Our Writing,\u00a0selecting from the feedback you receive is also […]<\/p>\n","protected":false},"author":17,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[34],"tags":[],"_links":{"self":[{"href":"https:\/\/elireview.com\/wp-json\/wp\/v2\/posts\/5268"}],"collection":[{"href":"https:\/\/elireview.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/elireview.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/elireview.com\/wp-json\/wp\/v2\/users\/17"}],"replies":[{"embeddable":true,"href":"https:\/\/elireview.com\/wp-json\/wp\/v2\/comments?post=5268"}],"version-history":[{"count":0,"href":"https:\/\/elireview.com\/wp-json\/wp\/v2\/posts\/5268\/revisions"}],"wp:attachment":[{"href":"https:\/\/elireview.com\/wp-json\/wp\/v2\/media?parent=5268"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/elireview.com\/wp-json\/wp\/v2\/categories?post=5268"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/elireview.com\/wp-json\/wp\/v2\/tags?post=5268"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}