►
From YouTube: UX Showcase Intro to User Experience Research
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
So
hi,
my
name
is
ben
leduc
mills,
I'm
a
senior
ux
researcher
with
the
create
stage,
and
we
are
going
to
talk
a
little
bit
about
ux
research
today.
A
This
presentation
is
born
out
of
kind
of
the
cumulative
questions
that
we've
received
over
the
past
six
months
to
a
year
and
just
kind
of
also
looking
towards
the
future
of
having
this
resource
available
for
folks,
who
are
a
little
bit
curious
about
what
we
do
and
who
we
are
and
how
to
get
involved.
A
So
we're
going
to
keep
this
relatively
high
level,
but
we'll
touch
on
a
few
things
like
what
ux
research
is.
Who
is
on
our
team?
What
exactly
we
do
when
we're
conducting
research
and
how
product
teams
in
particular,
can
get
involved
in
requesting
us
ux
research.
A
So
basically,
ux
research
is
the
practice
of
understanding
user
behaviors
needs
and
motivations
through
observation,
analysis
and
and
feedback,
and
we
do
this
in
a
variety
of
ways
which
we'll
get
to
later
on
in
the
presentation,
but
essentially
next
slide.
Please.
A
One
good
way
to
think
about
how
ux
research
can
be
involved
in
the
product
development
life
cycle
is
to
just
kind
of
break
it
down
into
a
double
diamond.
So
we
we
often
talk
about
problem,
validation,
research
and
solution,
validation,
research
and
the
way
we
do
it
here
at
get
lab
is
kind
of
very
interesting
where
designers,
for
the
most
part,
do
the
solution.
Validation.
B
B
Those
responsibilities
include
having
a
deep
understanding
of
our
users
working
within
the
product
teams
that
we
support
to
help
them
lead
research,
getting
buy-in
for
the
research
that
we
generate
and
then
prioritizing
different
research
requests
for
the
teams.
We
support
and
updating
documentation
and
processes,
like
our
gitlab
handbook,.
B
So,
at
a
high
level,
the
research
process
consists
of
five
main
steps.
As
you
can
see
in
this
graphic,
the
first
step
is
defining
the
goals
of
the
research.
So
what
do
we
want
to
learn?
What
do
we
want
to
know
and
what
will
new
research
add
to
our
existing
set
of
knowledge
in
step?
Two?
This
is
recruiting
the
desired
participants
so
that
we
can
get
user
feedback
on
questions
we
and
our
product
teams
have
about
people
and
their
engagement
with
our
product
and
step.
B
Three,
that's
collecting
data
from
our
participants,
whether
it's
in
the
form
of
qualitative
feedback
such
as
user
pain,
points
or
attitudes
about
the
product
or
things
like
quantitative
metrics,
like
completion
rate
or
time
on
task,
or
some
mixture
of
qualitative
and
quantitative
metrics
and
step
four.
It's
analyzing
data
to
identify
insights
that
connect
back
to
the
original
study
goals
and
help
answer
questions
about
our
users
and
then
in
step.
Five.
C
Yeah,
so
what
are
the
kinds
of
research
that
are
typically
conducted
and
how
do
they
fit
into
the
life
cycle?
I'll
be
explaining
a
little
bit
about
what
ben
touched
on
with
the
double
diamond.
So
this
is
just
a
little
bit
more
of
an
overview
of
the
double
diamond
design
process
and
how
research
fits
into
this.
So
the
process
typically
starts
out
with
some
catalyst
that
is
captured
in
a
problem
statement,
something
that
kind
of
describes
who
the
problem
impacts,
the
problem
and
the
goal,
and
sometimes
you
don't
have
that.
C
This
can
also
be
called
tactical
research,
evaluative
research
or
even
solution,
validation
and
some
common
methods
to
assess
this
would
include
usability,
testing
and
tree
testing
and
then
last
in
the
delivered
listening
phase,
you
decide
on
a
solution,
so
you
are
converging
and
you
hand
it
off
to
development,
and
at
this
point
you
want
to
listen
and
get
feedback
from
users.
So
listening
could
take
the
form
of
collecting
survey
feedback
like
in
a
sus
survey
or
even
doing
a
more
summative
usability
test
next
slide.
C
And
then
thinking
about
research,
you
can
also
break
it
into
quantitative
and
qualitative.
Both
are
very
important.
They
answer
different
kinds
of
questions
and
serve
different
purposes.
They
often
complement
each
other,
so
you
might
have
both
in
a
study
but
just
very
high
level.
Qualitative
research
is
focused
on
understanding
the.
C
Why
deeply
understanding,
maybe
even
a
smaller
subset
of
users,
where
as
quantitative
research,
is
aimed
at
understanding
the
what
and
useful
when
you
when
you
want
to
establish
benchmarks
or
understand
broader
usage,
and
you
can
see
more
examples
here,
of
methods
that
could
be
used
and
next
I
think
we
have
erica
to
go
more
into
how
product
teams
can
use
research.
D
Yes,
so
we
wanted
to
end
by
by
letting
you
know
how
to
work
with
us
next
slide
so
yeah.
This
process
is
specific
to
the
product
teams
that
we
support,
but
it's
also
helpful
for
you
to
know
just
how
we
work
so
step.
One
is
to
create
a
research
issue
and
that
issue
will
help
you
think
through
the
research
project
and
the
questions,
and
importantly,
it
also
communicates
the
need
to
our
team.
D
D
So
the
research
template
is
important
because
it
was
designed
to
scaffold
your
process.
So
it
will
ask
you
different
questions
that
you
should
be
asking
yourself,
as
you
think,
through
your
research
process,
so
there's
different
types
for
different
types
of
research
projects,
but
it
will
ask
you
for
things
like
what
you
want
to
know
and
when
you
need
to
know
it
by
so
you'll
see
the
prompts
and
the
templates.
So
I
won't
belabor
those
here
but
know
that
they
were
intentionally
created
to
help
you
think
through
the
process,
like
a
user
researcher,
would
next.
A
D
So
asking
yourself
and
your
stage
group
the
questions
that
we've
outlined.
There
is
really
helpful
and
then,
after
that,
you're
going
to
start
working
with
your
uxr
from
your
stage
group
on
the
research
process.
D
Next
slide
and
in
terms
of
the
research
process
just
wanted
to
spell
out
the
steps
that
you'll
see
us
going
through
on
the
right
there.
You
can
see
that
I'm
experimenting
with
having
different
comment,
archetypes
to
make
sure
that
teams
are
taking
these
different
steps
when
possible
in
the
issues,
and
that
makes
it
helpful
for
context
switching
for
researchers,
but
also
just
making
it
clear
that
we're
going
through
these
stages.
D
First,
refining,
your
goals
and
your
research
questions
and
from
there
comes
the
methodological,
consider
considerations
and
how
you'll
approach
the
project
and
then
we'll
think
also
about
timeline
and
how
we
can
do
do
the
mvr
minimum
viable
research
to
deliver
to
you
also
important
is
kind
of
clarifying
how
you'll
work
as
a
team
and
what
the
different
parts
that
team
members
will
will
do
and
then
last
kind
of
what
the
deliverables
will
look
like
next
slide.
D
D
So
basically
we
have
these
three
different
levels
of
support
that
we
offer
and
then
also
a
research
calculator
that
gets
filled
out
as
part
of
our
prioritization
process.
D
So
the
research
calculator
will
ask
questions
like
or
take
into
consideration
things
like
the
impact
of
the
project.
How
much
support
is
needed?
Whether
a
uxr
needs
to
be
involved
to
execute
if
there's
different
types
of
methods
involved
in
a
specific
project
and
things
like
that
and
then
from
that
we
will
then
assign
a
support
level.
D
So
you
can
see
here
that
there's
these
three
levels-
gold,
silver
and
bronze,
so
starting
on
the
bronze
part,
that's
more
of
a
light
touch
advisory
where
we'll
come
in
and
provide
some
feedback
on
some
suggestions,
ad
hoc,
as
available
kind
of
during
downtime
between
higher
tier
support
and
those
tasks
that
we
might
take
up.
There
would
take
around
three
to
five
hours,
then
leveling
up
to
silver,
the
dri
on
that
project.
D
So
not
the
uxr
will
drive
the
timeline
and
the
executables,
but
the
uxr
will
come
in
to
support
on
specific
tasks
or
stages
within
the
research
project,
but
will
generally
be
involved
for
less
than
a
few
days
for
each
of
those
tasks,
and
the
uxr
may
need
to
de-prioritize
that
work
if
higher
priority
projects
come
into
play
and
if
that
happens,
the
dri
on
the
project
will
kind
of
pick
up,
but
we
like
to
be
of
service.
D
So
hopefully
that
doesn't
happen,
but
in
the
end
we
need
to
also
be
focusing
on
the
gold
level
projects
which
are
kind
of
end
to
end
from
conceptualization
to
delivery.
The
uxr
is
working
on
all
those
components,
kind
of
being
the
project
manager
in
the
project
and
then
also
importantly,
team
members
are
there
to
provide
support
along
the
way,
because
research
is
a
group
effort.
D
After
we
set
up
a
research
project
and
we're
ready
to
go,
then
the
next
step
next
slide
is
to
file
a
recruitment
request,
which
is
important,
because
we
need
to
kind
of
track
all
of
our
efforts
along
these
different
stages,
especially
with
recruitment
and
there's
a
link
to
the
handbook
page
there,
where
you
can
get
involved
and
with
that
we'll
say
please
partner
with
us,
and
we
are
looking
forward
to
researching
with
you.
E
Awesome.
Thank
you
very
much.
If
anyone
has
any
questions,
please
feel
free
to
shout
them
out
and
I'll
take
notes
or
someone
will
take
notes.
E
I
did
have
a
question
off
the
top
of
my
mind
that
I
wanted
to
wait
to
see
if
it
was
covered
or
not
before
I
wrote
it
down,
but
basically
I'm
just
wondering
for
the
consultation
bronze
step
at
what
point
should
a
product
designer
reach
out
for
assistance
or
consultation.
D
So
we
have
this
right:
research,
prioritization
process,
that's
we're
starting
out
and
scaling
for
the
teams.
So
hopefully
we
will
have
those
projects
on
our
radar,
but
really
as
early
as
setting
up
the
research
issue
we
can
kind
of
come
in,
but
until
we
have
that
it's
hard
to
it,
it's
more
efficient.
If
we
have
that
in
place
to
partner
right.
D
I
think
that
the
the
research
issue
will
kind
of
work
through
that,
and
I
think
that,
as
we
kind
of
mentioned,
that's
a
stage
two
in
the
process,
so
getting
the
issue
there
and
then
we
can
talk
about
it
within
the
issue
and
work
on
developing
those
and,
if
needed,
have
a
sync
meeting
if
they
need
help.
We're
also
here
to
to
to
coach
and
mentor,
but
that
can
also
happen
async
in
the
issue,
and
that
can
be
helpful
too.
Okay,.
E
F
G
Hello,
can
you
hear
me
sorry,
I
wasn't.
I
wasn't
expecting
necessarily
to
voice.
I
just
wanted
to
say
on
your
last
thing:
justin
don't
be
afraid
to
create
an
issue.
Anybody
don't
be
afraid
to
create
a
research
issue.
If
you
don't
have
all
of
the
details,
yeah
as
erico
is
saying
we
can
help
with
that.
So,
if
you
add
us,
even
if
it's
like
us,
mostly
blink
issue,
we
can
help
fill
everything
out
as
needed
and
then
determine
exactly
what
more
we
should
do
later.
So
we
can.