1
00:00:00,494 --> 00:00:03,810
When requesting feedback timing is key.

2
00:00:03,810 --> 00:00:09,063
Getting feedback early and
often is more effective and less pressure.

3
00:00:09,063 --> 00:00:13,534
If you receive negative feedback on
something you've worked on for a month,

4
00:00:13,534 --> 00:00:16,370
it's gonna hurt more than if
you spend an hour on it.

5
00:00:16,370 --> 00:00:21,458
Additionally, you'll quickly validate if
you're heading in the right direction.

6
00:00:21,458 --> 00:00:25,129
So how do you know when to
start seeking feedback?

7
00:00:25,129 --> 00:00:28,027
Share as soon as your
concept is fleshed out, or

8
00:00:28,027 --> 00:00:31,147
your visual direction is
able to be communicated.

9
00:00:31,147 --> 00:00:35,621
As a tech degree student, slack is
a great way to get feedback on your work.

10
00:00:35,621 --> 00:00:40,508
We found that students who are active
in slack have better outcomes.

11
00:00:40,508 --> 00:00:44,496
Be sure to share your work in progress and
the review my project channel.

12
00:00:44,496 --> 00:00:48,591
While the slack audience already has
awareness of the tech degree projects,

13
00:00:48,591 --> 00:00:51,365
they may need a refresher
on their project details.

14
00:00:51,365 --> 00:00:56,353
When requesting feedback,
communicate clearly and provide context.

15
00:00:56,353 --> 00:01:01,113
If you were to simply show a mock up
to a person and say, what do you think?

16
00:01:01,113 --> 00:01:04,710
You'd receive a range of reactions
which are likely to miss the point.

17
00:01:04,710 --> 00:01:08,951
Without context they can't
adequately provide feedback.

18
00:01:08,951 --> 00:01:10,934
Here's how to present your design.

19
00:01:10,934 --> 00:01:15,873
Explain the product state and
where you're at in the design process.

20
00:01:15,873 --> 00:01:19,409
Is this design an early iteration?

21
00:01:19,409 --> 00:01:22,290
Designers often refer to
this as being wet paint,

22
00:01:22,290 --> 00:01:26,346
meaning it's an early stage idea
which can easily change direction.

23
00:01:26,346 --> 00:01:30,835
Alternatively, is this a design
under a tight deadline and

24
00:01:30,835 --> 00:01:33,451
is about to shift the production?

25
00:01:33,451 --> 00:01:36,526
Also, explain the goal
you're trying to achieve and

26
00:01:36,526 --> 00:01:38,652
how your design solves the problem.

27
00:01:38,652 --> 00:01:41,237
Consider sharing
alternatives you tried and

28
00:01:41,237 --> 00:01:43,554
why you decided to go in this direction.

29
00:01:43,554 --> 00:01:48,939
If there are any technical time, or
financial constraints, make those known.

30
00:01:48,939 --> 00:01:52,874
Lastly, explain what type of
critique you're looking for.

31
00:01:52,874 --> 00:01:56,471
You may ask for feedback on the big
picture ideas in your design.

32
00:01:56,471 --> 00:01:57,398
For example,

33
00:01:57,398 --> 00:02:02,273
here's a rough draft I quickly put
together to communicate this concept.

34
00:02:02,273 --> 00:02:06,643
I haven't refined the details yet
so disregard the lack of polish and

35
00:02:06,643 --> 00:02:08,160
critique the big idea.

36
00:02:08,160 --> 00:02:11,382
If you're further along
in the design process,

37
00:02:11,382 --> 00:02:16,578
you may want focused critique of the
visual design and interaction patterns.

38
00:02:16,578 --> 00:02:20,452
As a review, here are the elements you
should communicate when asking for

39
00:02:20,452 --> 00:02:21,087
feedback.

40
00:02:21,087 --> 00:02:22,444
Project state.

41
00:02:22,444 --> 00:02:23,283
Goals.

42
00:02:23,283 --> 00:02:27,469
Constraints, including technical,
time, and financial.

43
00:02:27,469 --> 00:02:31,457
Explanation of what you did and
why you did it.

44
00:02:31,457 --> 00:02:34,800
The goal is to do blank,
so I made this decision.

45
00:02:34,800 --> 00:02:37,570
Type of critique sought.

46
00:02:37,570 --> 00:02:42,374
It may feel daunting to share your work,
especially as a new designer.

47
00:02:42,374 --> 00:02:46,059
I recommend getting a quick review
from someone you trust first,

48
00:02:46,059 --> 00:02:48,409
before jumping into a big design review.

49
00:02:48,409 --> 00:02:51,126
It could be a fellow
designer on your team or

50
00:02:51,126 --> 00:02:56,419
a developer you're collaborating with,
a product manager or a user researcher.

51
00:02:56,419 --> 00:03:01,351
Showing your work to a colleague is
a lower stakes way of getting validation

52
00:03:01,351 --> 00:03:05,815
on your work, gaining fresh ideas and
catching unforeseen flaws,

53
00:03:05,815 --> 00:03:07,788
typos and grammar mistakes.

54
00:03:07,788 --> 00:03:12,324
This prepares you to go into big design
review meetings with more confidence and

55
00:03:12,324 --> 00:03:16,530
assurance, knowing that your ideas
are more polished than ever before.