Return to Video

03-06 I Do What I Love (Even When I Shouldn't)

  • 0:00 - 0:02
    The other type of bias that we have to
  • 0:02 - 0:04
    be careful about is called the, we call it the
  • 0:04 - 0:07
    approach bias and this bias often shows itself in the
  • 0:07 - 0:10
    beginning of a project or the way we approach something.
  • 0:10 - 0:12
    >> Yeah, we see this all the time when we've run UXD
  • 0:12 - 0:18
    workshops at IO, and a variety of other venues before, and almost
  • 0:18 - 0:21
    9 times out of 10 every developer when, when asked to build
  • 0:21 - 0:23
    a pizza ordering application. Thinks about
  • 0:23 - 0:26
    a photo realistic pizza ordering widget
  • 0:26 - 0:29
    that uses some really nifty graphics API said
  • 0:29 - 0:31
    they want to go and build right now.
  • 0:31 - 0:32
    >> Gosh and I was the one getting hungry.
  • 0:32 - 0:35
    But why do you think developers approach it this way?
  • 0:35 - 0:40
    >> Well, developers love to code. And when asked to design a pizza
  • 0:40 - 0:42
    ordering application, the first thing to think
  • 0:42 - 0:44
    about is what graphics API, APIs are
  • 0:44 - 0:48
    available on Android. And what other pinch to zoom and 3D, 4D realistic
  • 0:48 - 0:51
    things they can implement right now. And they want to get to it right now.
  • 0:51 - 0:54
    And honestly, as a developer even when I'm
  • 0:54 - 0:55
    designing things, in the back of my head.
  • 0:55 - 0:55
    >> Yep.
  • 0:55 - 0:58
    >> I'm always thinking, how do I build this thing? How would you approach it?
  • 0:58 - 1:01
    >> Well, as a designer, the way I would approach it is this. I would try to
  • 1:01 - 1:04
    imagine a user who's sitting there using their phone
  • 1:04 - 1:06
    and they're hungry for pizza. And they pull up
  • 1:06 - 1:09
    an application, and they want to go from being hungry
  • 1:09 - 1:12
    to being satisfied. And I think about, what is
  • 1:12 - 1:14
    the flow I could create in an application that
  • 1:14 - 1:17
    would let them go from being hungry to satisfied
  • 1:17 - 1:20
    as quickly as possible, with as little friction as possible, and
  • 1:20 - 1:23
    make them happy. So that's kind of the pure designer approach.
  • 1:23 - 1:26
    But the way that we really want to go about this
  • 1:26 - 1:28
    is not exactly the developer approach or the designer approach. We want
  • 1:28 - 1:31
    to do something that kind of meets in the middle. So,
  • 1:31 - 1:35
    as a development minded designer, I think what you would want to
  • 1:35 - 1:39
    do is design something really great, empathize with your user, but
  • 1:39 - 1:42
    keep constraints in mind and keep the question of whether you can
  • 1:42 - 1:43
    really build this in mind.
  • 1:44 - 1:46
    >> You know, exactly. And another thing is
  • 1:46 - 1:48
    you and I are very familiar with software. And
  • 1:48 - 1:51
    the way we think about interaction design patterns
  • 1:51 - 1:54
    and libraries are not the same as a user.
  • 1:54 - 1:55
    >> Exactly.
  • 1:55 - 1:57
    >> When we're building things, we have a certain bias, because
  • 1:57 - 2:00
    we're so familiar with these tool kits and platforms that we end
  • 2:00 - 2:03
    up having assumptions about how somebody will actually use a particular
  • 2:03 - 2:07
    widget or a control. And that's not exactly how a [INAUDIBLE] user
  • 2:07 - 2:07
    might do it.
  • 2:07 - 2:10
    >> Now that we've discussed approach bias, think about the
  • 2:10 - 2:13
    most recent project that you've worked on. Think about what you
  • 2:13 - 2:16
    did on day one or how you first approached this
  • 2:16 - 2:20
    project. Did any of your approaches actually bias the final product?
Title:
03-06 I Do What I Love (Even When I Shouldn't)
Description:

03-06 I Do What I Love (Even When I Shouldn't)

more » « less
Video Language:
English
Team:
Udacity
Project:
UD849 - UX Design
Duration:
02:21

English subtitles

Revisions Compare revisions