Requesting Feedback3:16 with Hope Armstrong
Learn how to effectively ask for feedback using a structured approach that helps guide constructive criticism of your work.
Here are the elements you should communicate when asking for feedback:
- Project state
- Constraints (technical, time, financial)
- Explanation of what you did and why you did it. For example, "The goal is to do [ BLANK ], so I made [ this decision ]"
- Type of critique sought
When requesting feedback timing is key. 0:00 Getting feedback early and often is more effective and less pressure. 0:03 If you receive negative feedback on something you've worked on for a month, 0:09 is gonna hurt more than if you spend an hour on it. 0:13 Additionally, you'll quickly validate if you're heading in the right direction. 0:16 So how do you know when to start seeking feedback? 0:21 Share as soon as your concept is fleshed out, or 0:25 your visual direction is able to be communicated. 0:28 As a tech degree student, slack is a great way to get feedback on your work. 0:31 We found that students who are active in slack have better outcomes. 0:35 Be sure to share your work in progress and the review my project channel. 0:40 While the slack audience already has awareness of the tech degree projects, 0:44 they may need a refresher on their project details. 0:48 When requesting feedback, communicate clearly and provide context. 0:51 If you were to simply show a mock up to a person and say, what do you think? 0:56 You'd receive a range of reactions which are likely to miss the point. 1:01 Without context they can't adequately provide feedback. 1:04 Here's how to present your design. 1:08 Explain the product state and where you're at in the design process. 1:10 Is this design an early iteration? 1:15 Designers often refer to this as being wet paint, 1:19 meaning it's an early stage idea which can easily change direction. 1:22 Alternatively, is this a design under a tight deadline and 1:26 is about to shift the production? 1:30 Also, explain the goal you're trying to achieve and 1:33 how your design solves the problem. 1:36 Consider sharing alternatives you tried and 1:38 why you decided to go in this direction. 1:41 If there are any technical time, or financial constraints, make those known. 1:43 Lastly, explain what type of critique you're looking for. 1:48 You may ask for feedback on the big picture ideas in your design. 1:52 For example, 1:56 here's a rough draft I quickly put together to communicate this concept. 1:57 I haven't refined the details yet so disregard the lack of polish and 2:02 critique the big idea. 2:06 If you're further along in the design process, 2:08 you may want focused critique of the visual design and interaction patterns. 2:11 As a review, here are the elements you should communicate when asking for 2:16 feedback. 2:20 Project state. 2:21 Goals. 2:22 Constraints, including technical, time, and financial. 2:23 Explanation of what you did and why you did it. 2:27 The goal is to do blank, so I made this decision. 2:31 Type of critique sought. 2:34 It may feel daunting to share your work, especially as a new designer. 2:37 I recommend getting a quick review from someone you trust first, 2:42 before jumping into a big design review. 2:46 It could be a fellow designer on your team or 2:48 a developer you're collaborating with, a product manager or a user researcher. 2:51 Showing your work to a colleague is a lower stakes way of getting validation 2:56 on your work, gaining fresh ideas and catching unforeseen flaws, 3:01 typos and grammar mistakes. 3:05 This prepares you to go into big design review meetings with more confidence and 3:07 assurance, knowing that your ideas are more polished than ever before. 3:12
You need to sign up for Treehouse in order to download course files.Sign up