►
From YouTube: UX Research Group Conversation 2019-10-18
Description
Learn more about us at https://about.gitlab.com
A
A
B
C
B
It's
question
and
it's
actually
the
same
thing
and
so
William
you're,
probably
aware
of
my
background
before
anyone
who's
not
on
the
call
and
I
was
getting
life's
first
and
only
you
actual
researcher
and
I
drink
it
like
a
little
over
three
years
ago.
Now
and
in
that
time,
as
you
can
sleep
from
the
second
slide
we
have
grown
massively.
Is
that
a
you,
much
research
team
and
that's
been
very
excited
that
has
been
great
and
one
of
the
things
that
we've
been
doing
as
a
team?
B
A
lot
recently
training
product
designers
and
product
managers
to
be
able
to
do
some
forms
of
UX
research.
So,
for
example,
we've
supported
and
product
managers
enable
to
do
like
qualitative
interviews
and
to
start
doing
some
kind
of
discovery.
Research
and
we've
also
worked
with
designers
in
terms
of
doing
evaluative
forms
of
research
of
things
like
usability,
testing
and
design
preference
tests.
So
researchers
are
kind
of
half
doing
their
own
research,
but
there
are
also
very
much
facilitators
and
trainers
as
well,
and
that
comes
with
challenges.
B
Obviously-
and
we
are
trying
to
balance
that
workload
at
the
moment
in
the
team-
and
so
one
of
the
things
that
we've
been
working
towards
is
producing
training
content,
which
will
take
some
of
the
pressure
away
from
researchers
when
they
can
I
get
the
same
common
questions
called
time
and
time
again.
It's
just
trying
to
find
the
balance
to
be
able
to
do
that.
So
one
thing
that
we're
pushing
for
in
quarter
four
is
to
be
able
to
actually
produce
more
of
this
training.
It's
a
and
then
we'll
add
that
to
the
handbook
and.
D
C
B
There
is
some
of
that
content
in
the
handbook.
Let
me
just
try
and
see
if
I
can
find
a
link
to
it.
I
am
going
to
admit
that
the
UX
research
pages
at
the
home
book
do
indeed
even
update
and
again
this
is
on
the
struggles
of
growing
as
a
team.
My
processes
change
as
well,
and
we
need
to
make
sure
that
they
are
documented
in
there.
B
Another
question:
can
you
explain
a
high-level
overview?
The
workflow
and
research
in
a
new
feature,
suggestion
yeah
and
definitely
so
what
tends
to
happen?
Is
we,
while
researchers
try
and
sit
in
as
many
kind
of
planning
meetings
as
they
can
do
with
product
managers
and
designers?
It's
a
little
bit
different
for
researchers
because
they
tend
to
work
at
section
level,
we're
not
quite
enough
researchers
per
section
at
the
moment.
So
we
don't.
We
don't
have
necessarily
the
capacity
as
to
attend
every
kind
of
stage.
B
B
We
like
product
managers
and
designers
to
come
and
be
involved
with
that
research.
So
if
we're
doing
something
like
user
interviews,
then
we'd
love
you
to
come
and
sit
in
the
calls
and
then
afterwards
again
we'll
try
and
kind
of
affinities
that
together
and
if
not,
then
the
researcher
will
normally
take
the
lead
on
that.
And
then
we
have
kind
of
a
short
meetings
as
well,
where
we
have
synchronous
calls
where
we
go
through
the
research
findings
and
discuss
what
needs
to
happen.
Next
fancy
question:
yes,
it
did
things.
There
are
right.
B
The
other
thing
that
we
also
hire,
we
also
have
them
like
a
UX
research,
insight
repository
as
well
I'm
hoping
if
one
of
the
UX
research
is
on
the
cloud.
Please
could
they
like
to
say,
identified
the
link
to
Matt's
bar,
but
basically
we
have
an
insight
repository,
which
is
where
all
our
research
ends,
or
so
other
researchers
and
try
and
break
down
the
research
that
they
find
out.
They
break
it
and
so
kind
of
these
like
little
nuggets,
and
then
they
put
it
into
the
insight
repository
and
they
label
it
up.
B
F
Yeah
and
so
I'm
super
excited
to
have
Emily
join
our
team
as
our
first
research
coordinator.
It's
a
new
role
for
the
company,
so
I
would
love
to
hear
you
talk
about
what
that
role
means
why
we
thought
it
was
important
and
what
we
we
think
we'll
get
from
that
over
the
next
shortest
period
of
time.
Yes,.
B
B
So
for
this
role
and
the
main
reason
why
we
we
kind
of
got
those
persons,
because
as
more
product
designers
and
product
managers
of
start
doing
research
that
we've
had
this
demand
for
recruitment
of
users.
So
we
have
get
well
first,
look
which
is
our
research
program
and
that's
currently
got
about
2,000
users
on
there.
But
obviously
we
don't
want
to
keep
bombarding
users
with
research
studies,
and
we
also
don't
want
to
keep
hearing
from
the
same
voices
over
and
over
again.
B
It's
important
that
you
know
get
like
has
millions
of
users
we
want
to
hear
from
all
of
them,
so
part
of
Emily's
role
be
brewing.
Get
my
first
look
a
research
program
and
encouraging
more
of
our
users
to
sign
up
to
that
and
non-users
as
well
and
and
then
the
other
thing
is
around
our
recruitment
processes.
B
As
well-
and
we
would
like
a
point
of
contact
within
the
UX
research
team
of
somebody
who
can
work
and
both
with
researchers
and
product
designers
and
product
managers
to
help
them
with
their
recruiting
needs,
so
someone
who
is
could
understand
in
and
how
to
kind
of
write,
screeners
and
flushing
out
those
requirements
for
users
and
then
to
be
able
to
actively
then
recruit
them
for
studies,
and
sometimes
that
may
mean
that
we
don't
always
have
like
the
users
that
we
need.
I'll
get
my
first
look.
B
It
might
be
that
they're
particularly
hard
to
reach,
as
we
found
with
some
of
like
studies
in
secure
and
in
ops
as
well.
So
the
technologies
are
newer,
they're
people,
insecure
and
less
likely
to
want
to
share
with
us
their
experiences
because
of
the
nature
of
the
we're
discussing
with
them.
So
we
need
someone
who
can
kind
of
go
out
there
and
really
find
these
users,
and
that
takes
some
of
the
pressure
then
of
researchers
as
well.
So
it
leaves
them
to
concentrate
I'm
doing
the
day-to-day
stuff.
H
Sarah
trust
from
the
customer
success
team.
My
question
has
had
to
do
with.
Has
any
research
been
done
to
explore
the
gitlab
onboarding
experience
for
Windows
development
teams
versus
non
Windows
team
I'm
asking
that
is
because
I've
been
working
with
more
customers
that
tend
to
develop
with
windows.net
more
recently,
I'm.
B
Personally,
not
aware
of
any
and
research
as
I've
been
done
in
this
area,
but
I
know
that
we
have
done
a
lot
of
research
into
the
onboarding
experience
and
I,
something
that
we're
constantly
trying
to
improve,
and
it's
something
that
we
get
a
lot
of
feedback
on
as
researchers
I,
don't
think,
we've
done
a
split
of
Windows.
Their
teams
to
non-windows
dev
teams.
Katherine
would
be
the
research
for
that
and,
unfortunately,
she's
not
on
the
call
today.
C
I
Sure
so,
we've
been
focusing
on
trying
to
evaluate
the
experience
of
setting
up
security
checks
and
we
tested
the
current
situation
and
we
found
out
that
it
could
be
improved.
Specifically.
What
we
found
was
that
people's
expectations
around
how
to
enable
security
checks
aren't
really
matching
what
we
currently
offer.
So,
if
you
want
to
enable
security
checks
these
days,
you
will
have
to
do
that
through
the
github
CI
mo
file,
or
you
would
enable
auto
dev
ops.
I
But
when
we
asked
people
to
go
ahead,
please
and
user
interface
to
enable
SAS,
for
example,
which
is
one
security
check.
We
saw
that
they
were
all
I,
think
all
of
them
headed
straight
to
the
main
nav,
and
they
looked
for
a
way
to
do
that
from
the
UI
itself.
They
wanted
something,
that's
very
simple,
something
that's
very.
I
That
would
be
like
toggling
a
switch
or
clicking
on
a
button
not
really
manually
configuring,
stuff
and
so
based
on
that
our
designer
for
secured
picked
up
on
that
created
a
new
flow
created,
a
configuration
page
which
has
those
will
not
Tuggle
but
checkboxes
for
enabling
security
checks,
and
so
we
just
now
recently
tested
that,
and
so
that
saw
a
huge
improvement.
So
this
is
I
think
the
latest
research
that
we've
done
for
secure
and
I
think
that
next
milestone
will
bring
new
research
into
security
gates
and
possibly
other
areas
as
well.
I
Tell
about
you
again,
so
what
we
wanted
is
to
evaluate
how
Auto
DevOps
as
a
term
is
doing
and
whether
we
should
change
it
to
something
else,
and
so
the
team
brought
up
a
few
terms,
a
few
suggestions,
no
ops,
Auto
pipelines
and
auto
configure
I.
Think,
and
so
we
put
out
a
survey
where
we
ask
people
a
few
questions,
but
the
most
important
ones
were:
let's
say
that
you're
now
being
offered
by
get
lab
to
use
a
product
service
called
no
ops.
For
example.
What
do
you
think
that
entails?
I
And
then
that
was
a
way
for
us
to
see
whether
the
term
would
allow
you
to
predict
what
the
feature
set
is
about,
and
then
our
other
question
was
okay.
The
reason
why
we
asked
you
about
this
is
because
we're
considering
it
as
a
name
for,
and
we
gave
the
definition
of
out
of
DevOps
does
that
feel
right,
and
so
after
surveying
nearly
200
people,
we
saw
that
the
terms
that
performed
best
on
both
fronts,
allowing
you
to
predict
what
the
term
was
about.
I
C
So
Talia,
if
I
could,
if
I
can
interject
on
your
call,
auto
pipelines
was
my
suggestion,
and
this
was
a
debate
for
a
long
time
almost
a
year
and
a
half
and
this
research
settled
that
very,
very,
very
long
debate.
So
I
was
pretty
I'm
asking
for
the
question,
because
I
was
so
excited
about
it
and
massive
props
to
you
and
the
whole
team
really
really
cool
research.
There.
J
By
the
way,
I
love
that
auto
develop
survey
and
I
thought
those
suggestions
were
good.
On
the
on
the
series,
I'd
say
date:
they
should
have
won,
but
I'm
I'm
glad
we
don't
have
to
rename
it
because
that's
a
that's
a
big
effort
so
but
very
cool,
very
good.
Other
suggestions.
I
love,
the
no
config
as
well.
B
J
Yeah,
to
give
a
bit
of
context
like
I,
think
anytime,
we
can
publish
it
to
unfiltered
I
think
it's
gonna
have
way
more
people
viewing
the
end
results,
so
you
just
have
way
more
leverage
and
I
think
we're
doing
awesome
work,
but
it's
it's
not
just
doing
the
great
work.
It's
also
like
making
sure
everyone's
aware
and
I
think
that
making
things
easy
to
reach
I
can
we
can
help
a
lot
of
thing.
Yeah.
B
J
For
sure
yeah
that's
another
thing:
it
helps
attract
great
people
to
our
UX
team.
It
helps
people
bring
it
up
in
issues
two
years
from
now,
reference
renfa
references
back
to
it
all
kinds
of
like
things
we
didn't
expect,
but
but
it
also
helps
me
to,
and
so
this
is
to
view
in
the
morning
in
the
gym,
because
I
can
download
it
to
my
ipad
and
put
it
on
my
playlist.
J
J
I'll
give
two
examples
so,
for
example,
out-of-the-box
get
lab
currently
doesn't
set
up
the
container
registry,
even
though
it
could,
and
because
of
that
auto
develops
doesn't
work.
So
we
say:
hey
get,
get
lab,
get
all
the
DevOps
and
out-of-the-box.
If
you
follow
installation
instructions,
other
DevOps
is
broken
because
the
docker
registry
doesn't
run
another
example.
Is
we
had
there's
a
there's,
a
checkbox?
J
You
can
click
when
you
merge
your
branch
and
it's
to
delete
the
feature
branch
that
caused
it,
and
that
is
what
you
probably
want
to
do,
95
to
99
percent
of
the
time.
So
we
made
that
the
default.
Then
all
kinds
of
people
were
like.
Oh,
we
just
deleted
our
long-running
branch
and
we
didn't
intend
to
do
that.
Oops
data
deletion-
that's
not
good!
So
now
we're
making
that
a
project
setting
which
I
think
is
amazing.
J
But
then
the
question
is
what
should
be
the
default
of
that
project
set
and
I
think
the
default
should
be
what
99%
of
the
people
should
do,
namely
delete
a
feature
branch.
So
you
don't
have
a
lot
of
branches
left
over.
For
example,
on
our
handbook
we
now
have
4800
branches,
if
that's
not
that
default.
But
the
conservative
thing
to
do
is
just
say:
are
we
introducing
this
new
feature?
B
This
is
where
usability
testing
is
really
useful,
so
we
see
how
users
behave
when
they
interact
would
get
webs
interface,
so
it
can
be.
You
know
we
can
be
focused
on
it,
any
part
of
kind
of
get
when
we're
doing
usability
testing
and
if,
like
users
like,
perhaps
make
a
mistake
and
like
that
you
just
might
mention
with
the
branches
or
they
go.
Oh
I'm
I'm
not
expecting
that
and
that's
the
key
for
us
to
say
hey.
We
need
to
do
something
about
this
and
we
normally
would
do
usability
testing
with
five
users.
B
J
So
you
might
find
this
when
kind
of
doing
install
from
scratch
without
my
work,
but
I
think
that
the
full
branch
thing
that's,
it
might
not
come
up
in
usability
testing.
It's
just
one
extra
click.
If
you
go
to
our
workflow
did
or
do
you
think
it's
like?
Oh
that's,
an
extra
click
and
we're
we're
focused
on
that
we're
like
are.
Why
isn't
this
dutiful?
How
do
you
think
that
go.
B
D
J
J
B
K
I
think
for
something
like
you're
talking
about
Sid,
where
what
are
some
sort
of
common
actions
that
users
are
taking,
often
that
we
can
potentially
make
default
or
that
we
can
alter
to
make
slightly
easier
or
less
work-intensive
I.
Think
now
that
we're
starting
to
roll
out
pendo
and
we're
starting
to
get
some
of
that
data,
we
can
look
at
okay.
You
know
what
users
doing
you
know
very
often,
because
I
think
it's
it's
very
telling
if
Oh
after
a
user,
starts
a
project
or
does
some
action,
you
know
75%
of
them,
take
this
action.
K
K
How
representative
is
that
person
or
those
five
people,
or
what
is
the
minority
case
like
you're,
describing
almost
everyone
wants
to
delete
the
branch
after
merge,
but
for
some
people,
that's
a
very
major
issue
and
they
actually
don't
want
to
and
that's
going
to
be
a
massive
deal
for
them.
So
trying
to
understand
the
you
know,
pros
and
cons,
for
you
know,
segments
at
a
larger
level.
D
To
the
other
issue
that
was
mentioned
about
the
defaults
not
being
there
for
our
DevOps
I
know
a
lot
of
times
in
the
past
and
using
the
product.
It
would
be
helpful
if
the
product
was
smart
enough
to
at
least
kick
out
something
that
says:
hey,
you're
missing
these
requirements.
Please
talk
to
an
admin
or
send
send
the
admin.
This
email,
then
that
way,
it's
a
lot
easier
to
figure
out.
B
B
Don't
think
there
was
anything
but
was
on
her,
certainly
not
from
my
natales
point
of
view.
I
don't
know
if
Laurie
and
Christy
felt
differently
for
from
me
entirely.
That
we'd
heard
these
kind
of
things
before
and
we
were
able
to
correlate
the
data
that
we
got
from
commits
and
with
Laurie's
data
and
that
she
collected
from
commit
New,
York
and
and
also
the
insights
that
we
already
have
within
that
repository
and
so
play
out
their
key
themes
but
of
reoccurring.
Themes
that
keep
coming
up.