►
Description
The System Usability Scale is a quarterly initiative that helps us understand the needs, challenges, and pain points of GitLab users.
In this series, Katherine Okpara (UX Researcher, Create) will discuss the top themes we’ve gathered from the SUS surveys conducted thus far and highlight opportunities for improvement.
Learn more about the insights and action items from the SUS here: https://gitlab.com/gitlab-org/gitlab/-/issues/227847
A
Hi,
I'm
catherine
akpara
ux
researcher,
for
the
create
stage
of
git
lab
today.
I'd
like
to
talk
to
you
about
the
feedback
we
receive
regarding
the
left
side,
navigation
in
our
quarterly
system
usability
scale
survey
as
the
product
continues
to
grow.
Users
can
become
overwhelmed
by
all
of
the
information
and
paths
they
encounter
in
gitlab.
A
This
is
especially
true
if
they
mean
if
they
mainly
use
a
certain
set
of
features
and
don't
explore
other
product
areas
very
well.
The
majority
of
pain
points
fall
into
two
buckets:
first,
understanding
where
you
are
in
gitlab.
So
how
can
we
help
users
maintain
context
and
stay
oriented,
while
switching
between
levels
of
navigation
and
features
in
different
product
stages
and
second
discovering
the
tools
you
need
to
improve
your
workflow?
A
A
I
observed
the
following
behavioral
patterns,
so
when
completing
tasks,
some
users
were
aware
of
the
concept
of
a
feature,
but
they
did
not
know
the
exact
name
of
it
in
gitlab,
for
example,
they
may
they
may
know
that
managing
the
progress
of
a
project
is
related
to
planning,
but
they
weren't
aware
of
the
milestone
feature.
For
example,
these
users
were
more
likely
to
identify
a
certain
section
related
to
the
concept
of
planning
for
in
this
instant
issues,
for
example,
even
if
they
couldn't
pinpoint
the
exact
level
of
navigation
needed
to
find
fine
milestones.
A
On
the
other
hand,
other
users
remembered
feature
names
very
well
from
hearing
about
them
in
sources
like
blog
posts,
videos
and
release
updates.
However,
they
weren't
sure
of
where
they
should
start
looking
to
actually
find
the
feature.
In
those
cases,
the
category
names
did
not
match
their
expectations.
A
A
A
Reassessing
these
proposals
and
identifying
whether
they
still
fit
into
the
scheme
of
gitlab
would
be
a
great
step
toward
improving
this
issue.
It's
important
to
note
that
time
has
passed
since
the
original
research
studies
we
conducted
related
to
this
categorization
we've
expanded
our
product
further,
and
we
need
to
consider
additional
categorization
users,
workflows
and
jobs
to
be
done.
A
However,
if
users
aren't
aware
of
this
distinction,
they
can
be
confused
when
they
are
not
able
to
find
the
item.
They
are
looking
for
so
an
open
issue
that
is
important
to
consider
for
helping
to
increase
awareness
of
these
different
levels
of
navigation
is
a
proposal
to
differentiate
the
icons
used
for
the
overview
pages
for
groups
subgroups
and
projects.
A
So
all
these
interactions
impact
the
user's
productivity
in
gitlab,
and
that
is
why
navigation
is
such
a
critical
area
of
usability
and
also
why
it
is
so
closely
tied
to
discoverability
navigation
is
now
by
the
growth
expansion
group.
They
will
conduct
a
series
of
research
studies
and
growth
experiments
to
identify
how
we
can
make
iterative
improvements
to
the
navigation.
A
So
here
we
have
a
look
at
an
epic
that
contains
some
of
the
initiatives
they
have
planned,
which
include
existing
proposed
improvements
to
navigation,
in
addition
to
research
efforts
that
are
planned
and
growth
experiments
that
will
be
upcoming.
So
that's
all
I
have
to
share
about
the
left
side.
Navigation.
Thank
you.
So
much
for
watching
this.
Video
and
I'll
see
you
in
the
next.