►
From YouTube: UX Research Group Conversation (Public Livestream)
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
Hi,
my
name
is
Jeff
Crowe
I
am
a
member
of
the
research
team
here
at
get
lab.
I
work
on
the
gross
section
and
with
me
today
are
some
other
members
of
the
UX
research
team
and
we're
looking
forward
to
answering
your
questions
about
you,
extry
search,
agate
lab
and
some
of
the
work
that
we've
been
doing
over
the
last
few
months.
A
B
If
you
Thanks,
have
you
looked
at
like
the
the
initial
user
experience
of
like
using
get
lab
like
the
signup
flow,
but
also
like
the
downloading
flow?
If
I
look
at
our
install
page,
it's
not
getting
regular
updates
and
I
figured
that
that's
that's
a
point
where
users
determine
hey
and
we're
gonna
use
this
product
that
those
ten
minutes
out
of
the
box
is
super
important.
Yeah.
A
So
yeah
that
is
super
important.
It's
something
I
as
someone
on
the
growth
team
is
very
interested
in.
We
have
looked
at
some
aspects
of
sort
of
the
new
user
experience
or
the
signup
flow.
We've
looked
at
the
pricing
page
looked
at
some
of
the
signup
flows
in
terms
of
a
moral
holistic.
Understanding
of
you
know,
starting
at
with
git
lab
or
the
new
user
experience.
We
haven't
done
that
or
also
the
another
area
is
like
downloading
and
installing
self-managed,
and
getting
that
up
and
running.
A
That's
something
we
want
to
do
a
struggle
we
have
in
regard
to
that
type
of
research.
Right
now
is
our
ability
to
effectively
recruit
those
users.
Obviously,
when
you're
trying
to
recruit
someone
who's
two
days
into
gitlab
or
a
very
near
term
in
terms
of
being
a
git
lab
user
right
now,
our
recruiting
processes
don't
really
have
that
ability.
A
So
we've
been
working
with
data
to
be
able
to
leverage
user
data
in
a
more
efficient
and
quick
manner
so
that
we
can
find
people
who
have
signed
up
for
a
trial,
in
the
last
say
48
hours
or
our
new
get
lab
comm
users
in
the
last.
You
know
a
few
days
or
a
week
so
that
we
can
get
that
new
user
experience.
A
B
So
dot-com
is
super
important
in
this
go
got
two
times
the
rate
of
her
self
managed
installations.
However,
right
now
still
like
ninety
percent
of
our
revenues
coming
from
self-managed,
it's
super
important
and
we
see
kind
of
the
new
installations.
Flatlining
I
think
none
of
the
things
you
indicated
will
get
you
a
user
to
go
to
the
initial
download,
get
lab
and
install
it
experience.
Is
it
an
option
to
you
send
out
a
tweet
or
something
like
that?
I'd
be
happy
to
tweet
or
retweet,
something
that
is
hey?
A
A
So
I
don't
see
any
new
questions
so
for
the
time
being,
I
just
wanted
to
talk
a
little
bit
about
some
of
the
recent
work
that
we've
done
so
last
quarter.
We
had
an
OK
R
to
build
out
our
UX
research
training
materials
to
benefit
our
product
designers
and
product
managers
and
allow
them
to
do
their
own
research
and
a
more
self-sufficient
manner.
A
So
we
hit
a
hundred
percent
on
that
ok,
R,
which
we're
quite
proud
of,
and
if
you
go
and
look
in
the
handbook
at
our
UX
research,
training,
materials
they're,
just
in
a
much
better
place
than
they
were
just
a
quarter
ago
and
we've
really
flushed
them
out.
We've
really
given
people
the
material
and
the
guidance
they
need
to
be
able
to
go
and
conduct
their
own
research
largely
independently.
We,
of
course,
as
a
team,
are
still
available
to
offer
guidance
and
support
as
needed,
but
I
think
right.
A
Looking
forward
to
this
quarter,
we
have
an
OK
R
to
standardize
the
process
for
what
we
were
calling
UX
scorecards
now
UX
scorecards
are
still
a
thing,
but
we've
created
a
sort
of
a
new
version
of
a
UX
scorecard
that
we're
calling
a
category
maturity
scorecard
with
the
goal
of
allowing
cut
the
category
maturity
process
to
be
driven
by
user
feedback
and
user
evaluation
and
not
purely
a
heuristic
process,
and
so
we've
created
these
category.
Maturity
scorecard
validations
to
include
user
input
into
that
category,
maturity,
determination,
and
so
you
can
go
see.
A
We
have
a
merge
request
right
now
and
process.
The
team
has
been
giving
feedback
on
and
should
be
finalized
in
the
next
couple
days
to
create
an
initial
process
for
how
we
go
about
doing
these
category
maturity,
evaluations
with
actual
users
of
kit
lab
and
those
evaluations
will
then
feed
into
the
ultimate
category
of
maturity,
determination.
A
C
Do
you
want
questions
opposed
to
you
as
you
go
through?
Would
you
prefer
to
finish
and
then
have
questions
back
in
the
afterwards
feel
free
to
put
the
questions
in
the
dark,
and
then
you
can
just
vocalize
them?
Okay,
so
I've
just
put
one
in
there
actually
two
things:
one
I
managed
to
capture
Sid's
comments,
but
I
didn't
manage
to
capture
your
response
on
the
previous
discussion
points.
When
you
get
a
second,
could
you
update
the
doc
yeah.
B
C
A
By
the
definition
of
okay,
ours,
I
guess
it
wasn't.
You
know
this
is
the
first
time
that
we've
said
an
OK
are
like
this.
So
I
think
there
was
a
bit
of
calibration
that
was
necessary.
I
think
it
was
a
relatively
ambitious
okay,
our
I
mean
we
built
out
I,
think
seven
different
areas
of
documentation
within
our
training
materials.
Basically,
each
researcher
handled
an
area
of
need
for
our
training,
materials
and,
and
some
of
those
were
quite
extensive
and
so
yeah.
In
retrospect,
we
probably
could
have
set
something
a
bit
more
ambitious
but
I.
A
Think
if
you
go
and
look
at
kind
of
the
difference
between
where
we
were
and
where
we
are
now,
it
is
quite
a
change
and
so
yeah
as
we
think
about
evolving
our
training
materials
moving
forward.
I
think
we
recognized
that
we
do
have
the
ability
to
you
know,
progress
them
quite
a
bit
and
I
think
if
we
set
subsequent
okay,
ours
or
own
training
materials,
we
will
know
that
we
can.
A
A
There
is
no
overarching
framework
that
we
can
rely
on
for
this,
so
we're
having
to
really
invent
it
ourselves,
and
so,
while
the
do
you
know,
devising
of
the
process
is
one
part
of
the
okay
are
making
sure
that
product
designers
understand
the
process,
can
execute
the
process
successfully
and
then
actually
incorporating
whatever
feedback
or
changes
are
necessary.
You
know
that's
all
wrapped
into
that
is
because
there's
sort
of
so
many
moving
parts
to
that,
or
so
many
different
groups
within
the
company
that
you
know
or
we're
having
to
rely
on
to
make
that
happen.
A
A
This
is
not
something
we've
done
before
and
as
research
I
think
it's
a
little
bit
different
than
a
lot
of
people
are
used
to
you
know
it's
meant
to
be
reproducible
and
standardized
and
and
with
a
goal
of
trying
to
get
a
more
objective
understanding
with
with
the
understanding
that
research
is
inherently
subjective,
but
with
the
goal
of
introducing
some
amount
of
objectivity
to
the
process,
so
that
we
can
feel
confident
when
we
reduce
the
you
know
those
sessions
down
to
a
score
or
a
letter
grade.
In
this
case,
cool.
A
A
B
Even
if
it's
finished
it's
it's
more
fun
for
people
watching
to
YouTube,
people
might
say
more
than
you
expected
and
there's
a
cognitive
process
that
happens
in
the
other
participants
of
the
call
so
like
so
there's
are
all
good
reasons
to
to
never
like
say
someone
else's
question.
That's
not
why
you
write
them
down
fair.
D
It
I
I
will
just
verbalize
my
question
and
finish
typing.
It
I
think
I
already
know
that
answer
to
this
first
I'm
gonna
say
it's
all
sorry,
Church
I
think
is
awesome
like
empower
everyone
who
feels
they
need
to
or
wanted
to
do,
that
I
think
is
great
I
just
and
it
and
again
I
think
I
already
know
the
answer
to
this,
but
for
the
kind
of
everyone
else
on
the
call
I.
D
Could
you
speak
a
little
bit
about
how
you
see
the
research
UX
research,
team,
kind
of
I
guess
going
in
direction
and
purpose?
Because,
obviously
you
know
we
were
kind
of
used
to
this
thing
where
the
UX
research
team
might
have
done
all
the
research
right
and
then
taking
that
on
so
I
wonder
if
you
can
just
speak
a
little
bit
about
how
you
see
the
direction
of
the
team
going
and
the
kind
of
the
purpose
for
the
team.
A
So
I'll
give
kind
of
my
thoughts
on
what
I
feel
that
purpose
of
the
team
is
in
the
direction
of
team
and
then
I'll,
let
Sara
way
and
if
there's
anything,
I've
missed
or
anything
that
she
wants
to
clarify
Sara
the
the
UX
research
manager.
So,
yes,
research
is
becoming
more
self-service
and
is
being
driven
more
by
product
designers
and
product
managers,
and
the
researchers
are
acting
more
and
more
as
guidance
or
support.
So
solution
validation
is
now
being
handled
by
product
designers
exclusively,
researchers
are
still
taking
the
lead
with
problem
validations.
A
Sometimes
that's
in
collaboration
or
in
consultation
with
product
designers
and
the
product
designers
may
lead
it.
It
depends
sort
of
on
the
situation
and
the
group
and
the
specific
research
problems
that
are
being
addressed.
The
goal
is
that,
as
we
scale,
we
want
to,
you
know
just
allow
product
designers
to
be
able
to
do
their
own
solution.
Validation
because
we
believe
that's
sort
of
the
most
efficient
way
forward.
Given
the
resources
that
we
have
and
the
amount
of
research
that
we
want
to
conduct.
A
E
A
great
answer
and
I
know
that
Christy's
typing
out
some
of
the
points
as
well
in
my
mind,
is
the
fact
that
when
we
were
a
smaller
research
team
and
we
were
being
inundated
with
requests-
and
we
didn't
want
to
become
a
block
of
product
managers
and
product
designers
to
be
able
to
go
out
there
and
do
research,
you
know
they
obviously
all
see
the
value
in
it.
And
we
don't
want
to
be
the
main
stuck
in
point
and
so,
as
we've
kind
of
scaled.
E
The
research
team
we've
trained
for
product
managers
and
product
designers
to
be
able
to
do
research
and
the
solution.
Validation
side,
like
Geoff
studies,
mainly
now
being
handled
by
product
designers
and
they
escalate
inquiries
first
to
their
design
managers.
And
then
we
step
in
if
there's
still
any
kind
of
confusion
there
and
any
kind
of
help
with
methodology,
perhaps
unchecking
scripts
and
things
like
that
and
then
on.
E
The
other
end
of
that
is
the
problem,
validation
efforts,
which
are
more
kind
of
larger
strategic
kind
of
initiatives
which
a
better
place
for
researchers
to
actually
kind
of
work
on
and
there's
something
that
you
know
like
a
lot
of
research.
Is
they
go
to
school
for
this
or
they've
studied
kind
of
working
on
these
projects
for
a
couple
of
years?
It's
like
a
kind
of
specialist
skill.
E
At
the
same
time,
we're
trying
to
bring
product
managers
I
want
for
the
ride
and
the
the
great
thing
about
having
product
managers
involved
at
kind
of
every
stage
of
the
research
is
that
they
understand
it
better.
The
internalize
it
better
and
it's
so
much
easier
than
kind
of
you
know
just
explained,
and
they
see
someone
as
opposed
them
actually
come
in
and
speaking
to
users
themselves
and
also
gaining
confidence
to
feel
like
they
may
be
able
to
run
some
sessions
and
things
like
that.
E
F
I
will
vocalize
a
question
that
I
have
so
I
know
that
we
are
really
working
hard
to
scale
participant
recruitment
for
UX
research,
and
it's
been
a
real
challenge
for
everyone
involved.
We
need
a
lot
of
participation
for
very
specific
personas
that
can
be
very
difficult
to
recruit.
So
I'd
love
to
hear
your
team
talk
about
what
we're
doing
to
to
move
that
forward,
but
then
also
how
the
broader
gitlab
team
can
help
with
that
yeah.
A
So
I
think
we
have
a
few
different
efforts
underway
to
improve
that.
So
the
first
thing
is
first
look
or
use
a
research
panel
that
has
been
around
for
a
while.
First
look
is
great,
because
people
have
opted
into
that
and
they're
very
open
to
participating
in
research
and
we're
still
growing
that,
where
we
can,
we've
had
researchers
going
to
commit
and
soliciting
people
to
join.
First,
look
and
that's
been
very
successful.
A
We're
looking
for
other
ways
where
both
the
research
team,
but
also
other
get
lab
employees
can
help
us
sort
people
for
the
first
panel.
But
the
first
look
panel
is
never
going
to
keep
pace
with
our
user
base
as
a
whole
and,
as
you
kind
of
alluded
to
there
are
certain
criteria
or
specialized
people
who
are
gonna
always
be
tricky
to
get
via.
First
look
so
we're
also
working
with
the
data
team
to
increase
our
capabilities
around
recruiting
gitlab
users
based
on
who
they
are
or
maybe
what
they
do.
A
And
so
we've
been
working
with
the
data
team
to
be
able
to
do
that
and
be
able
to,
for
instance,
pipe
information
into
Qualtrics,
which
is
the
platform
that
we
use
to
send
invitations
for
research
interviews
or
usability
studies,
things
like
that
and
invite
users
or
have
them
fill
out
surveys
or
whatever.
That
may
be
so
that
work
is
underway
right
now,
I'm,
actually
working
with
the
data
team
to
create
some
of
that
new
infrastructure.
I
was
actually
looking
at
some
issues
earlier
today
around
some
new
API,
that's
being
built
out.
A
So
hopefully
we
can
start
doing
more
of
that,
and
we
can
start
better,
allowing
researchers
and
and
product
designers
and
product
managers
to
be
able
to
find
people
based
more
on
who
they
are.
And
so
this
allows
us
to
say:
I
have
this
criteria
that
I
need
to
satisfy
for
my
research
I
need
to
find
people
that
meet
that
criteria.
A
Historically,
that's
been
challenging
for
us,
and
so
hopefully
we
can
get
a
lot
better
at
that
over
the
coming
months
and
that
will
also
make
hopefully
recruiting
much
more
efficient.
Sometimes
when
we're
recruiting
via
first
look
or
just
via
social
media,
that
can
be
a
long
process.
You
can
wait
sometimes
upwards
of
a
month
to
find
a
sufficient
number
of
users
for
your
study
a
month
is
a
long
time.
A
month
is
a
milestone,
and
so
we
want
to
try
to
shorten
that
process.
If
we
can
get.
A
A
Thinking
about
that,
because
I
think
recruiting
is
one
of
our
main
challenges
we
have,
especially
as
we
scale
you
know,
we
need
a
sufficient
volume
of
users
to
be
able
to
meet
all
of
these
research
requests
that
we
have,
and
so
we
need
ways
to
to
find
them
effectively,
and
so
that's
something
we
continue
to
think
about
as
a
team
as
well.
Yeah.
F
A
So
we've
been
talking
with
them,
as
well
as
on
growth.
We've
been
talking
with
them
and
ways
to
users
that
kind
of
do
certain
things
we're
interested
in
talking
to
as
a
result
of
whatever
that
action
may
be.
Examples
are
like
users
that
have
churned
recently
or
upgraded
recently
or
gone
through
a
renewal
recently
we're
interested,
often
in
talking
to
those
users,
because
those
are
things
that
you
know
we
have
entire
teams
devoted
to,
and
so
we
want
to
understand
certain
aspects
of
those
processes.
A
So
right
now,
we've
done
it
kind
of
on
a
more
informal
ad-hoc
basis.
For
instance,
I
have
a
recurring
meeting
with
the
retention
PM,
where
we
go
and
identify
recently
churned
users,
and
we
say:
do
we
want
to
reach
out
to
these
folks
and
better
understand
their
experience?
We
have
a
similar
thought
with
upgrades
as
well
talking
with
people
who's
recently
upgraded
their
subscription
and.
A
A
In
the
coming
months,
we've
been
working
a
lot
with
support
around
just
sort
of
data
and
how
their
data
is
flowing
and
how
we
can
better
understand
the
data
that
they
have,
whether
that's
via
Salesforce
or
via
the
data
warehouse
and
I,
know
they're
interested
as
well
in
increasing
some
of
their
own
survey,
capabilities
of
based
on
certain
actions
that
may
occur.
Maybe
that's
a
support
interaction.
A
Maybe
that's
an
upcoming
renewal
or
a
recently
completed
renewal,
or
what
have
you
they
want
to
have
sort
of
recurring
survey,
capabilities
to
better
understand
how
those
interactions
or
experiences
are
going
and
so
I
think
it
kind
of
works
in
both
directions.
But
no
I
think
support
is,
is
a
very
valuable
resource
for
us
just
given
the
sheer
volume
of
people
that
they
they
speak
to
on
a
given
day
versus
the
number
of
people
that
we
as
a
team
can
speak
to.
E
Just
to
kind
of
answer,
Geoff's
comments
and
on
slide
11
of
the
deck.
There
is
a
link
to
get
my
first
lock
to
kind
of
join,
there's.
Also,
a
research
studies
like
channel,
which
is
a
very
like
internal
and
team
members
to
join
and-
and
we
do
research
with
internal
team
members
as
well
and
for
two
purposes,
one
to
kind
of
test
scripts
and
things
like
that.
E
But
also
the
second
thing
is
to
correlate
what
we
think
and
how
we
use
get
well
with
our
kind
of
external
users
as
well,
and
the
other
thing
that
I've
just
added
to
the
group
conversation
document
is
Emily's.
Research,
coordination,
but
so
Emily,
John
Hoffman
is
our
research
coordinator
and
she
tracks
all
and
working
progress
on
this
board.
So
if
anyone
is
interested
in
helping
us
out,
then
please
check
out
that
board.
Look
at
the
issues
that
are
within
there
and
you
can
see
the
kind
of
things
that
were
recruiting
for
at
the
moment.
G
I'll
just
quickly
add
a
comment
in
there
too.
I
was
not
aware
initially
of
first
look
and
I'm
just
wondering
if
we
could
add
that
on
our
community
contribution
page,
because
that
one
sort
of
summarizes
all
the
ways
you
can
contribute
to
good
luck
get
lab.
So
it
might
be
cool
to
have
a
call
out
there
if
you're,
a
user,
whatever
the
whatever
you
guys,
use
to
filter
candidates,
but
just
some
kind
of
a
link
over
the
first
look
from
that
page
would
be
awesome.