►
From YouTube: UX Research Q1 2022 SUS Interview Findings
Description
12 GitLab users were interviewed to understand their thoughts on how GitLab usability has changed over the past year.
A
Hi
everybody
I'm
adam
spalensky
and
I'm
here
to
just
try
to
briefly
walk
everybody
through
a
piece
of
research
that
I
conducted
around
interviewing
respondents
from
the
sus
survey
that
we
do
every
quarter
for
some
context.
Here
there
was
a
ux
key
review
meeting.
I
think
it
was
a
little
over
a
month
ago
and
during
that
eric
johnson
asked
the
question:
do
we
know
if
our
users
feel
if
usability
has
improved
over
the
past
year?
A
So
that's
what
this
particular
piece
of
research
set
out
to
find
out
and
the
way
that
this
was
done
was
a
set
of
interviews.
So
I
reached
out
to
people
that
had
filled
out
the
sus
survey
from
q1
and
there's
a
total
of
12
of
them,
so
mainly
to
really
understand
those
differences
in
perception
and
get
lab
usability
from
a
year
ago
till
now
and
see
what
the
difference
is
and
because
this
is
qualitative
research.
I
was
able
to
go
in
and
understand
the.
Why?
A
In
back
of
that,
so
I
got
a
lot
of
really
great
information
and
that's
what
I'm
going
to
just
walk
through
so
top
takeaways,
we'll
start
with
the
bad
right
away.
There
was
a
major
theme
that
was
surfacing
up
and
it
was
around
learnability
and
it
was
actually
the
most
common
reason
why
these
participants
felt
that
gitlab
was
not
easy
to
use.
It
was
hard
to
learn
and
I'll
talk
about
that
with
some
examples.
A
There
was
some
good,
though
so
on
average
over
the
past
year.
These
these
predict
these
participants
felt
that
there
was
a
very
slight
improvement.
That's
the
mean
average
to
usability
within
gitlab,
so
very
slight,
but
there
was
a
big
surprise
that
I
was
not
expecting
and
there's
a
main
reason
behind
their
ratings
and
I'll
talk
about
that.
But
essentially
it
was
whether
they
were
getting
used
to
gitlab
or
not.
So
that
was
a
shocking
surprise
to
me
and
I'll
I'll
go
into
detail
around
what
that
actually
means.
A
So
first
the
difference
is
between
a
year
ago
versus
today,
so
participants
were
asked
how
difficult
or
easy
it
is
to
use
gitlab
on
a
scale
of
one
to
seven.
They
were
asked
to
think
back
a
year.
There
are
some
challenges
with
that
and
I
outlined
that
later
on
in
the
deck.
If
you
want
to
read
that
and
then
I
asked
them
the
same
question
now
in
the
context
of
today,
and
we
can
see
the
differences
on
their
ratings
on
the
chart
on
the
right
there.
A
So
some
are
positive
and
some
are
no
change
at
all
and
some
are
negative,
so
half
felt
that
it's
easier
today,
3
out
of
12,
felt
there
was
no
change
from
a
year
ago
and
another
3
out
of
12
felt
that
it
was
more
difficult
today.
So
when
we
look
at
the
mean
across
these
there's
a
very
slight
positive.
A
Increase
from
a
year
ago
to
today,
so
we
might
think
okay,
that's
that's
promising
a
little
bit,
but
again
since
it's
qualitative,
we're
able
to
kind
of
go
in
and
understand
the.
Why?
So
what
I
did?
I
looked
at
the
positive
and
I
started
to
ask
okay
well.
Why?
Because
I
was,
I
was
personally
expecting
to
see
some
concrete
examples
around
usability
changes
that
may
have
been
made
that
these
participants
could
be
experiencing
instead.
A
The
main
the
main
reason
behind
these
scores
was
that
these
participants-
they
eventually
got
used
to
it,
so
let
that
sink
in
a
little
bit.
That
means
that
they
didn't
necessarily
all
see
usability
improvements,
but
they
got
used
to
the
experience
that
they
do
within
gate
lab,
so
shifting
gears
a
little
bit
to
the
participants
who
found
either
a
negative
change
over
the
past
year
or
no
change
at
all.
I
also
asked
why
and
the
main
reason
behind
their
ratings.
A
A
A
A
This
group
struggles
tremendously
for
them
gitlab
it's
difficult
to
learn
and
use.
These
are
people
that
might
be
product
managers
who
may
not
go
into
the
code
at
all
but
they're
using
it
for
issues.
Things
like
that
for
updates,
and
it's
hard
for
them
to
really
go
into
it
for
just
a
view
on
one
thing
that
might
be
an
update
within
an
issue
because
there's
everything
else
around
in
the
ui
that
doesn't
really
pertain
to
them,
but
it's
intimidating.
It's
overwhelming.
A
The
shocking
thing
that
I
found
also
was
that
it's
impacting
adoption
with
this
group
with
with
some
of
these
participants-
and
I
highlighted
those
quotes
in
yellow
here
for
everyone
to
see.
Interestingly
enough
too
technical
users
who
use
get
lab-
let's
say
engineers,
for
example-
they're
also
negatively
infect
negatively
affected
by
non-technical
users.
They
work
with
because
they're
the
ones
who
are
coming
to
the
technical
users
saying
hey.
I
need
your
help
with
this.
A
Can
you
help
me
understand
how
to
use
gitlab
with
what
we
need
to
do
so
it
takes
them
away
from
their
job.
So
that
was
surprising
to
me.
The
second
key
factor
was
the
fact
that
there's
a
learning
curve
and
it's
relatively
steep.
This
was
where
people
were
talking
about
getting
used
to
it.
They
flat
out
called
out
that
the
learning
curve
is
huge.
A
So
there
is
somewhat
of
a
correlation
as
to
whether
these
participants
did
or
didn't
get
used
to.
Gitlab
and
their
perception
of
how
usability
changed
over
the
last
year,
so
the
learning
curve
plays
a
factor
there
with
usability
the
last
two
key
areas
are
a
little
closely
related
navigation
and
discoverability,
just
at
a
high
level
navigation.
A
It's
viewed
as
difficult
to
learn
and
use.
It's
complex,
there's
a
lot
of
items
in
the
navigation.
I
know
that
we're
making
navigation
changes
as
I
speak,
so
I
think
we're
on
the
right
track.
There
there's
a
discoverability
piece
too,
and
this
is
a
little
closely
related
to
navigation,
but
essentially
it's
really
hard
for
some
of
these
users
to
find
and
learn
about
new
features
that
may
or
may
not
help
them.
A
Actually,
christie
asked
this
question
to
me
and
I
thought
it
was
worthy
enough
to
put
in
a
slide
in
case
others
start
to
think
about
this.
So
the
short
answer,
we
don't
know
this
research.
It
really
doesn't
answer
that
question.
As
a
reminder,
the
sus
is
built
out
of
ten
questions
total
and
this
research
happens
to
focus
on
just
one
of
those
questions,
so
we
can't
really
draw
a
direct
comparison
between
those
two
sets
of
scores.
A
A
A
There
was
also
another
angle
that
I
took
within
this
research
and
it's
really
just
kind
of
understand
how
they,
if
they
felt
that
usability,
has
changed
over
the
year,
which
is
a
little
bit
different
than
the
two
rating
questions
I
asked
earlier,
and
I'm
glad
that
I
asked
it
this
way,
because
I
was
able
to
see
a
slightly
different
view
on
things
about
half
roughly.
It
was
fairly
split
here,
whether
they
they
felt
that
it
changed
over
time.
A
So
I'll
just
point
out,
there
is
a
lot
of
bonus
content
that
I
also
got
that
I
wanted
to
also
share
feel
free
to
look
through
this
there's
a
full
slide
around
feedback
that
we
got
on
the
doc
site,
and
I
have
two
full
slides
around
mrs
just
feedback
around
that,
and
there
were
some
miscellaneous
pain
points
as
well,
and
if
anybody's
interested
in
learning
a
little
bit
more
about
our
participants,
I
threw
together
a
couple
slides
there.
I
think
I'll
call
out
just
two
things:
real,
quick
one.
A
A
So
there's
also
some
links
in
the
appendix
and
a
few
other
things,
but
I'll
stop
here
for
now.
If
anybody
has
any
questions
at
all
feel
free
to
reach
out
to
me,
I
love
talking
about
research
and
especially
this
study.
This
was
a
lot
of
fun
and
if
anybody
has
any
questions
I'll
be
happy
to
answer
them.
Thank.