►
From YouTube: UX Showcase: Asynchronous Design Reviews
Description
Sunjung Park talks about how she iterated on her design review process with her team.
A
A
A
Yeah
cool
so
good
morning,
good
afternoon
and
good
evening,
I'm
sanjong,
I'm
in
enablements
group
and
I'm
a
senior
product
designer
working
mostly
for
the
geo
and
the
distribution
team,
and
today
I
would
like
to
just
share
my
experience.
How
I
started
to
provide
and
getting
the
feedback
asynchronously
in
the
design
review.
A
I
mean
we
like
literally
okay,
asynchronously,
okay,
meaning
like
it's
not
synchronous
meeting,
and
my
immediate
reaction
was
like
okay.
Well,
this
is
my
day
one
and
it's
it's
harsh
okay,
so
I
just
google
it
and
then
now
I
understand.
Okay,
let
me
try
that
so
that
was
immediate
reaction
and
yeah.
That
was
not
professional,
but
I
was
really
got
shocked
at
first
time,
so
this
was
the
very
first
attempt
at
the
time
and
sorry
about
this
poor
design.
A
A
So
we
would
like
to
have
this,
but
I
think,
like
the
the
positioning
was
not
right,
so
I
found
some
from
front
and
back
so
like
okay,
this
could
be
the
proposed
design
and
I
would
like
to
change
this
design
and
I
think
it's
pretty
like
solid
solution
yeah.
Why
not?
Let's?
Let's
just
deliver
this
so
my
my
thought
process
was
like
this,
so
I
stopped
your
issues
because
it
was
just
mine
like
really
like
second
week
or
the
third
week.
I
was
still
like
overwhelmed
by
all
our
handbook
and
the
markdown.
A
A
Just
for
this
confirmation
model
and
the
ui
text
there
and
just
for
this
design,
I
had
to
had
a
two
times
a
synchronous,
not
asynchronous
meeting
but
a
meeting
with
the
product
manager
just
to
make
sure
like.
How
would
I
change
this
or
not?
How
would
I
change
the
ui
text
or
not?
So
I
was
like
that.
It
was
my
month
the
first
month
and
I
got
some
feedback.
I
got
some
like
direct
feedback
from
engineer
and
I
got
also
feedback
on
the
comments
section
that
okay
look
like
the
discus.
A
The
discussion
scope
is
getting
bigger
and
bigger,
and
the
first
screenshot
here
is
the
reaction
that
I
got
like:
here's
how
it
works
and
they
started
to
like
just
send
me
the
link
of
the
ruby
code.
Of
course,
I
have
no
idea
what
does
that
mean,
but
they
just
started
to
share
they're
like
actually.
This
is
how
this
works,
and
maybe
you
can
refer
to
this-
and
I
was
like
thank
you,
but
it
was
really
hard
to
follow
up
the
the
ruby
code
and
I
got
a
really
nice
constructive
feedback
from
others.
A
On
the
comment
section,
you
can
check
the
issue
link
down
down
there,
that
it's
not
easy
to
find
your
final
proposal,
and,
oh,
my
god,
I
felt
so
bad,
I'm
a
ux
designer
and
I
didn't
thought
about
our
team's
usability
and
ux.
Okay.
That
was
bad
and
I
think
this
is
the
main
question
for
the
engineers,
because
they
have
put
a
lot
of
knowledge
that
they
have
and
I'm
I
was
the
newbie
and
I
think
they
wanted
to
know
like
how
frequently
this
happens,
because
I
think
they
are
maybe
concerning
about
their
efforts
on
this.
A
Maybe
she'll
ping
every
design
issue
and
then
ask
us
maybe
very
basic
or
stupid
question.
I
think
maybe
they're
worried
about
that.
So
I
was
a
bit
like
thinking
face,
okay,
it
it
took
a
while.
Then
I
thought
and
okay.
This
is
now
my
life.
I
have
to
keep
everything
try
to
keep
everything
asynchronously,
okay,
it's
it's
tough
and
I
I
had
an
idea,
though,
that
okay,
maybe
it's
better
to
share
sorry.
A
I
think
it's
not
the
right
context
but
like
okay,
maybe
it's
better
to
share
my
thought
process,
how
I
put
this
design
and
how
I
work.
So
I
decided
to
create
this
not
the
pretty
illustration
but
the
the
first
images
that
I
put
at
the
time.
So
I
introduced
him
opening
an
issue.
Okay,
this
is
my
design
process
and
I
need
your
input
here
and
there
and
I
need
your
input
so
maybe
in
the
very
early
phase
I
missed.
A
A
So
I
think
that
was
the
reason
why
I
need
to
come
up
with
my
own
poor
illustration
flow
chart,
but
I
think
this
would
work
and
this-
and
I
I
hope-
and
I
I
hope
this
helps
engineer-
to
understand
that.
Okay,
maybe
I
can
put
this
amount
of
time
per
week
or
per
month
for
sanjiang
to
providing
design
feedback,
so
I
think
we
are
kind
of
slowly
on
the
same
phase.
A
So
this
was
my
second
attempt.
I
I
tried
to
just
google
a
lot
and
how
can
I
get
this
feedback
in
a
better
way,
and
I
I
think
so,
I'm
dealing
with
engineers.
So
there
are,
they
are
my
target
user
and
just
thinking
about
their
characteristic.
They
want
to
have
it
something
very
specific.
That's
my
understanding,
that's
my
understanding
from
my
partner,
who
is
a
software
engineer
and
just
based
on
my
observation.
Okay,
that's
the
thing,
so
I
think
the
discussion
goes
wider
and
wider.
A
A
A
A
So
I
had
to
change
the
design
like
three
times,
but
I
was
still
happy
because
I
could
see
the
progress
of
my
design
and
the
the
second
screenshot
is
the
final
design
at
that
time
before
delivery,
and
now
we
don't
have
to
use
this
big
comment
line,
because
now
we
have
the
design
tab.
So
it's
way
more
easier
than
before,
but
this
was
before
the
design
tab
release.
A
When,
when
do
you
prefer,
so
I
think
I
I
use
the
stigma
approach
when
I
come
up
with
a
very
initial
draft
for
the
global
search
team,
because
I
really
need
some
immediate
change
and
immediate
feedback
from
the
engineer,
because
it
it
looks
like
a
high
fidelity,
but
it's
like
a
really
low
fidelity
at
that
time,
because
this
is
one
of
the
high
ability
screen
at
the
time
and
it
has
a
really
long
user
flow.
So
I
prefer
to
use
speak
my
jet
tie,
but
there
are
some
cons
that
it's
quite
difficult
to
follow.
A
All
the
discussion-
and
I
think
mate
once
mentioned
that
it's
it's
kind
of
hard
once
it's
resolved.
We
need
to
double
check
our
email
inbox.
Maybe
someone
mentioned
me
or
not,
and
it's
not
easy
to
find
the
resolved
discussion
on
figma
and
a
lot
of
notification
that
I
got
in
email
inbox.
That
was
like
really
a
while
and
some
engineers
confused
because
of
they
have
a
lot
of
email
from
bitmap
because
of
my
notification.
A
I
sometimes
feel
sorry
about
that,
but
I
feel
like
it's
also
worse,
to
bring
them
in
in
a
very
early
phase
before
we
release
this
feature,
and
I
find
it
it's
also
very
worse-
to
involve
sales
counterparts
because
full
especially
for
the
geo
team.
They
need
to
know
this
like
what
is
happening
on
our
geo
world,
so
I
and
our
product
manager
think
it's
really
important
to
involve
them
also
in
our
design
review.
A
A
I
I
would
like
to
have
like
both
approach,
but
still
I
love
to
improve
my
design
like
process.
I
would
say
to
getting
more
feedback
from
the
engineering
and
product
team
and
also
from
you
that
it's
not
a
fixed
thing.
It
could
be
evolved
in
a
very
continuous
way.
So
thank
you
for
your
time
and
I
would
love
to
get
your
input
on
it.
B
Yeah
I
do
and
I'm
gonna
start
with
a
comment.
This
was
awesome.
I
enjoyed
it
so
much.
It
was
so
deeply
entertaining
the
oh,
my
god.
This
is
my
life.
Now
it
was
really
good.
So
thank
you.
This
is
very
well
done
are
other,
and
maybe
this
isn't
a
question
for
you
sanjiang.
Maybe
this
is
a
question
for
the
group.
Are
other
designers
doing
async
reviews
in
this
way.
C
We
want
people
to
give
us
feedback
on
exactly
what
we
need,
and
sometimes
things
are
out
of
scope
and
it's
difficult
to
put
all
of
that
in
one
single
comment.
So
I
can
definitely
relate
to
your
pains.
It's
something
I've
been
through
myself
and
and
it's
hard
because
it's
oh
we've
done
all
of
the
work,
the
design
work,
but
I
mean
it's
on
our
responsibility
as
designers
and
etc.
C
C
Okay,
now
I
have
to
think
and
work
how
I'm
going
to
prepare
my
message
and
my
request
for
feedback
in
a
way
that
is
most
efficient
and
most
helpful
and
useful,
and
also
pleasing
for
others
to
consume
and
interact
with,
and
it's
exhausting,
I
agree
with
you
yeah,
so
I
can
say
I
can
relate
to
a
lot
of
that
and
what
I
would
say
is,
I
think,
what
you
just
showed
is
like
breaking
up
the
the
request
for
feedback
like
how
what
did
you
like
here?
What
did
did
you
you
didn't
like?
C
What
do
you
think
are
the
technical
constraints,
so
all
of
those
questions
and
having
threats
for
that.
I
thought
that
was
amazing
and
something
that
sometimes
I
also
do
and
also
being
clear
about
who
you
want
feedback
from.
So
I
think
those
two
things
alone
go
a
long
way
in
in
streamlining
the
conversation.
B
B
A
You
and
one
last
comment
would
be-
I
think
it's
just
like
not
so
designers
work,
it's
not
the
sole
designer's
task
like
I
think
what
we
need
to
do
is
crafting
beautiful,
ui
and
ux,
of
course,
but
I
think
what
I
feel
like
is
the
really
team
effort.
I
got
support
from
the
pm
and
also
from
the
engineering
manager.
How
can
we
like
get?
A
It
was
the
whole
team's
effort
and
I
think
it
also
takes
some
time
and
it
would
be
more
like
practicing
and
maybe
we
can
have
some
like
maturity
level,
because
now
I
I
feel,
like
their
feedback,
is
really
great
and
it
really
changed
my
design
in
a
good
way.
So
I
like
to
share
my
experience
today.
Thank
you.
A
C
C
A
A
Maybe
we
can
add
that,
and
also
I'd
like
to
highlight
if
we
have
some
like
very
clear
question
sets.
I
think
it
depends
on
the
situation,
though,
but
if
we
have
a
really
clear
expectation
for
feedback,
then
I
think
that
it
reduced
the
the
time
that
we
get
feedback,
because
if
that's
the
clear
question
then
they
would
love
to
jump
in
and
yeah
it's
a
or
maybe
it's
b.
So
I
think
that
was
really
helpful,
for
my
experience.
C
B
Yeah
and
I'll
just
say
in
the
handbook,
there
is
a
section
that
talks
about
collaborating
with
pms
and
developers
and
soliciting
feedback.
So
but
but
I
love
the
idea
of
adding
the
specific
questions
to
it
because
it
makes
it
more
actionable.
So
my
request,
I
think
jackie
actually
wrote
that
contact
10,
so
she
can
work
with
you
to
help
fold
some
of
this
into
our
existing
content,
because
concrete's
really.