►
From YouTube: Settings UX - UX Research
Description
As part of the overarching initiative to improve the GitLab Settings experience, we will collect existing user feedback and proposals in order to drive user experience and SUS score improvements for settings. This is a conversation with UX Research.
More on https://gitlab.com/groups/gitlab-org/-/epics/3535
A
B
A
That
was
that
was
it,
but
also
because
settings
up
up
until
this
point
or
there's
some
conversations
going
on,
but
up
to
this
point,
there's
no
real
honor.
So
it's
even
in
the
group
not
owned
differently
from
navigation
and
I'm
not
sure
which
one
was
the
other
one
that
was
assigned
to
a
stage
group
recently.
A
But
we
are
working
on
some
group
level
settings
in
release
management.
So
I
want
to
use
that
as
an
opportunity
to
work
on
settings
or
to
at
least
you
know
bring
some
direction,
but
I
think
that's.
I
think
you
will
agree
that
that's
a
bigger
problem
that
needs
you
know:
involvement
from
other
designers
and
from
research.
A
So
that's
why
I'm
having
these
conversations
with
different
designers
from
different
stage
groups,
so
that
I
can.
I
can
collect
information,
more
updated
information
on
what
their
vision
is
for
settings.
What
what
they
are
right
now,
what
their
previous
struggles
of
designers
working
with
settings
to
try
to
find
some
common
ground
there
and
then
I
hope
in
the
future.
We
can
assign
or
have
more
dear
eyes
for
that,
because
it's
a
big
thing
right
settings,
it's
it's
everywhere!
So
that's
pretty
much.
It.
B
A
Freeze
but
yeah
now
it
looks
stable
before
it
was
a
little
bit.
B
Okay
awesome.
Well,
I
personally
think
this
is
exciting
because
just
from
a
lot
of
the
work
with
the
system,
usability
scale
and
also
earlier
work
that
I
was
doing
with
git
lab,
that
has
become
what
not
unowned
now
yeah
navigation
settings.
Things
like
that
they've
been
kind
of
long
time
coming
issues,
and
so
there
are
a
lot
of
different
areas
and
I'm
not
sure
if
you
saw
the
issue
that
I
have
with
like
actionable
insights.
B
B
Basically
the
different
points
that
I
think
we
need
to
address
in
some
way,
and
so
things
like
the
information
architecture,
so
the
actual
naming
of
the
settings
and
how
we're
categorizing
them
can
still
be
improved,
but
also
the
layout
of
the
pages
we've
received
feedback
around
kind
of
like
the
padding
of
the
pages
or
how
certain
settings
aren't
visible
above
the
folds.
You
might
not
even
know
to
look
below
for
certain
things.
A
I'm
just
scanning
the
the
content.
I'm
excited
that
the
problems
are
so
similar
to
what
I've
been
listening
from.
Other
designers
excited
might
not.
A
Yeah
and
so
let's
just
jump
into
the
search,
because
I
see
that
you
have
like
some
two
issues
open
here
and
I
just
had
a
conversation
with
mike
nichols
from
create
and
we
were
discussing
sociable
settings
and
in
context
with
the
features
and
how
that
could
give
more
visibility
to
you
know
to
the
the
functionality.
A
You
can
even
show
me
some
examples.
But
what
can
you
share
about
settings
and
search
yeah.
B
So
I
would
say
what
I
can
share
is
that
the
feedback
that
I
was
seeing
in
the
system
usability
scale
in
a
previous
survey
was
that
for
the
left
side,
navigation
bar,
so
the
whole
thing
people
were
thinking.
I
have
so
many
items
everywhere
and
yes,
if
you
improve
the
organization
of
them,
it
will
make
it
easier
to
find
it,
but
sometimes
I
might
just
want
to
even
just
quickly
search
for
it
and
be
able
to
pull
it
out.
B
A
B
B
A
I
think
that
comes
in
a
very
good
moment,
because
I
know
soon
june
she's
from
ngo
and
she's
working
on
redesigning
this
global
search,
not
how
you
search
or
anything
like
that,
but
the
results
and
she,
let
me
see
if
I
can
find
this
issue.
B
B
I
think
I
saw
that
issue
come
through
and
the
global
search
is
interesting
because
when
you
you
can
get
to
that
page
that
she's
thinking
of
redesigning
or
if
you
look
for
something
like
a
project,
it
might
take
you
just
directly
to
the
project
like.
Sometimes
you
don't
see
that
page
yeah,
that's
interesting
to
me.
So
I'm
not
sure
if
you
would
have
a
list
of
settings
kind
of
added
to
that
page,
that's
filtered
by
issues,
merge,
requests
and
everything
or
if
you
would
just
take
someone
directly
to
the
setting
once
they
click
on
it.
B
A
Because
I
think
it's
a
little
bit
like
what
the
handbook
search
works
today
right
because
you,
if
you
just
hit
enter
you,
find
you
get
to
that
pop-up
with
all
the
results.
But
if
you.
B
B
A
If
you
look
at
the
this
issue,
it
is
the
destination
one.
If
you
go
to
the
application
issues
in
advanced
search
and
know
that
she's
working
only
on
ui
polish,
so
it's
really
like
you
know,
aligning
buttons
and
changing
the
font
sizes,
etc
to
make
it
look
a
little
bit
more
aligned
with
dramas
but
also
the
rest
of
the
product,
because
right
now
the
page
is
not
really
used
by
alert.
A
So
on
that
note,
I
was
wondering
if
you
got
any
feedback
from
people
saying
that
they
don't
use
our
search,
because
the
search
doesn't
give
them
some.
You
know
specific
abilities,
because
that's
what
I
heard
from
shinjun
that
a
lot
of
people
use
the
search
they
go
to
google
and
they
find
what
they
need
to
find
there.
So
do
you
hear
anything
in
that.
A
B
A
collection
of
docs
that
are
just
a
bunch
of
feedback
and
there's
a
doc
out
there
with
search
feedback
that
I'm
gonna
look
for
right
now,
but
yeah.
I've
heard
this
in
the
context
of
docs
and
in
the
product.
I
think
things
have
improved
over
time
for
global
search
in
get
lab.
A
B
That's
subjective,
but
I
I
think
it
has
improved
over
time,
but
that
was
a
common
thing.
What
people
were
saying
in
the
past-
and
I
know
I
got-
I
have
a
dot
there
somewhere
and
I'll,
find
it
and
link
it,
but
yeah,
so
that
used
to
be
kind
of
a
concern
where
it's
like
it's
difficult
to
navigate,
but
also
the
search
isn't
so
great.
So
then
it's
like,
I
guess
google
will
fill
in
the
gaps
for
me
for
some
things.
A
A
B
A
B
The
stock
yeah.
No,
so
this
stock
is
like
a
combination
of
like
feedback
from
different
sources.
So,
like
the
sus
interviews,
other
usability
tests,
it's
just
kind
of
like
all
of
it
all
in
one.
B
This
is
the
this
is
something
I
like
to
do.
I
don't
know
if
it's
something
other
people
like
to
do,
but
there's
a
lot
of
random
information
in
our
issue
tracker
and
our
different
studies
that
I'll
just
pull
into
a
dock
like
this,
and
I
think
it
could
be
helpful.
So,
if
you're
ever
collecting
things,
I
would
suggest
to
do
that.
A
Can
you
tell
me
a
little
bit
more
about
information
architecture
and
what
you've
heard
from
users
now
and
also
in
the
past,
because
we
did
conduct
some
some
research
writing
settings
or
was
that
just
a
request?
I'm
not
exactly
sure
but
anyways.
B
The
basic
the
main
concern.
There
was
understanding
how
to
present
how
to
present
the
content
on
the
pages,
because
we
had
lots
of
content
and
it's
like
do
we
do
we
expand
it
all.
Do
we
collapse
at
all?
Do
we
do
partial,
like
expand
the
most
important
things
at
the
top
and
collapse
everything
else?
That
was
like
the
the
premise
of
that
survey,
but
other
than
that?
I'm
not
sure
that
we
have
done
other
studies.
There's.
B
I
know
marcel
once
had
a
research
issue
open
around
the
placement
of
settings,
so
that
question
was
whether
settings
should
all
exist
under
that
you
know
that
little
nav
item
or
whether
they
should
be
more
out
in
context
more
often.
So
if
I'm
on
the
milestones
page-
and
I
need
to
do
something
that
I
need
to
change
something
about
milestones-
I
should
be-
should
I
be
able
to
access
that
setting
right
on
that
page
or
do
I
need
to
go
find
you
know
the
milestone
settings
and
the
whole
nav
item?
B
That
was
an
issue
that
marcel
had
opened
that
we
didn't
do,
I'm
not
sure
if
that's
the
one
you're
thinking
about-
and
I
know,
monitor,
I
think,
monitor
the
group-
monitor-
has
an
issue
around
improving
the
information
architecture
of
some
of
their
settings
or
something
like
that.
I
don't
think
we've
done
a
large,
coordinated
effort
for
settings.
We've
done
that
for
the
nav
bar
in
the
past,
but
I
mean
not
the
the
side
nav
in
the
past,
but
we
haven't
done
it
for
settings.
A
Then,
in
the
survey
that
you
that
you
worked
on
some
time
ago
to
understand
how
to
present
the
settings
in
the
ui
did
you
or
like
with
me
as
a
as
a
team
as
a
company,
we
actually
apply
some
of
these
insights
and
the
findings
back
into
the
product.
Where
do
we
see
those
reflected
today?
What
we
have.
B
Right,
so
I
do
think
this
one
this
one.
I
can't
remember,
I
can't
remember
if
it
was
implemented
and
then
the
survey
kind
of
was
to
confirm
or
if
it
influenced
but
one
way
or
another,
the
pattern
of
expanding
some
but
collapsing
all
but
collapsing
all
the
others.
I
guess
expanding
the
most
common
but
collapsing
the
least
important.
B
I
guess
that
concept
that
that
one,
I
can't
remember
if
it
resulted
from
the
survey
or
if
it
was
there
before,
but
that
one,
I
think,
was
the
one
that
people
were
supporting
the
most
that
option
of
kind
of
having
it
in
between,
because
if
it's
all
collapsed,
you're
kind
of
having
to
click
through
and
see
everything
if
the
descriptions
aren't
very
accurate.
B
But
if
it's
all
expanded,
then
everything
is
just
like
all
down
the
page
and
it's
extremely
long
yeah.
Actually,
I'm
not
sure
if
we
came
to
a
conclusion
there
and
I
would
have
to
read
it
again-
it
was
like
two
years
ago,
but
yeah.
There
were
basically
pros
and
cons
on
both
sides,
and
some
people
were
like
the
description
of
the
setting
is
even
more
important
there
too,
because
if
it's
all
collapsed
and
I
have
to
actually
go
into
it
to
see
what
I'd
find
in
there,
then
I'm
doing
even
more
processing.
B
A
From
mother
designers
that
of
course
search
would
help
would
make
you
know
everyone's
lives
easier.
If
you
could
just
quickly
go
to
the
global
search
and
say
I
don't
know
cicd
settings
or
variables,
and
then
you
get
variables
settings
as
an
option,
but
I've
been
here
from
other
designers
that
sometimes
the
copy
or
sometimes
what
we
put
out
there
in
the
settings,
don't
really
explain
what
you're
going
to
do
in
the
game.
A
There's
a
lot
of.
I
wouldn't
say
that
it's
a
lack
of
center,
but
sometimes
I
feel
like
the
the
way
we
communicate
is
too
technical
and
that
you
need
to
know
ahead
of
time
what
you're
going
to
do
with
that
option.
Right.
That's
my
personal
experience
with
some
some
settings
in
the
project.
A
B
So
I
don't
remember
anything
particular
for
those
things
it
might
have
been
in
there,
but
I
can't
think
of
anything
that
comes
to
mind.
B
I
don't
think
we
made
a
conclusion
in
terms
of
which
one
is
better
I'll,
expand
it
all
collapse,
but
the
leading
choice
in
that
survey
was
most
settings
collapsed,
but
the
frequently
used
ones
expanded,
and
so
I
believe
what
we
were
supposed
to
do
is
follow
up
by
testing
that
proposal
testing
a
design
with
the
proposal
to
expand
the
frequently
used
ones
and
collapse
the
rest
and
then
also
improve
the
or
create
the
filtering
for
settings
pages.
B
A
Happened:
the
opportunity
for
us
to
identify
these
jobs
to
be
done,
because
we
have
so
many
right
related
to
settings
and
then
kind
of
that's
why
I
did
this
in
release
management,
where
we
were
in
a
way
we
had
so
much
information
from
users
because
we
conducted
so
many
customer
interviews
that
doing
a
whole
round
of
validation
just
to
confirm
what
we
already
knew
was
kind
of.
Like
you
know
much.
A
Overworked
so
that's
one
of
the
things
I
was
thinking
today,
kind
of
trying
to
figure
out
or
find
this
insight
that
you
already
have,
that
marcel,
might
have
that
other
designers
found
in
different
or
related
research
to
kind
of
back
up
these
big
themes
that
we
have
around
settings
like
usability
replacement,
the
ability
to
search
the
information
architecture,
and
then,
from
that
see
where
we
move,
which
direction
we
will
move.
B
So
that's
most
of
the
information
that
I
have
to
go
on,
but
I
would
say
it's
consistent
with
a
lot
of
the
navigation
feedback,
so
there
is
a
lot
in
there
that
can
be
kind
of
worked
on
rather
than
starting
from
the
point
a
of
do.
We
have
an
issue
with
settings,
it's
more
like
we
have.
We
know
there
are
issues
with
settings.
Perhaps
it's
understanding
which
ones
are
most
severe
and
which
one
should
be
addressed
first
or
which
ones
would
have
the
most
impact,
but
yeah.
That's
how
I
see
it
at
this
stage.
A
It's
a
very
it's
very
good
to
hear
that
no
way,
because
now
that
I
have
access
to
rtc
pointing
me
to
these
issues,
I
can
go
ahead
and
try
to
maybe
relate
them
to
some
of
the
just
some
of
the
items,
because.
A
Requests
like
internal
feature,
requests
for
settings
and
I
think
a
lot
of
these
issues
they
would
be
solved
with.
I
don't
know,
improving
the
navigation,
and
then
you
know
having
a
conversation
about
settings
and
similar
to
what
we
did
for
the
ui
polish.
A
couple
of
months
ago,
we
had
that
opr
to
improve
the
overall
look
and
feel
of
the
product.
A
My
gut
feeling-
and
my
proposal
here
is
as
well
as
that
we
just
find,
which
are
these
ui
polish,
to
extend
just
the
you
know,
visual
enhancements
that
we
could
do
and
tackle
them,
because
I
think
there's
a
lot
that
we
can.
We
can
do
to
move
towards
this
direction
of
well
once
we
agree.
What
is
this
we
address?
First,
or
at
least
we
will
have
some
things
already.
B
Attacking
yeah
yeah,
I
agree
and
looking
through
some
of
the
settings
right
now,
because
I'm
trying
to
think
of
this
survey
and
how
it
landed,
because
I
know
we
didn't
decide
to
make
that
change,
and
so
I
was
looking
through
the
settings
and
yeah
general.
B
A
This
is
so
interesting
because
I
actually
have
a
bug.
I
found
a
bug
that
someone
says
that
there
is
a
bug
in
the
set
in
general,
it's
expended,
because
all
other
pages
should
be
yeah.
B
A
B
Yeah
and
it's
naming
topics
in
avatar,
so
this
is
another
thing.
The
compliance
framework
was
like
added
to
this.
I
think
at
some
point,
maybe
in
the
past
well
time
has
passed
by
really
fast.
It
might
be.
I
think
it
was
this
year
that
this
compliance
framework
part
was
added
to
general,
and
so
it's
just
like
a
really
big
expanded
setting.
A
B
B
B
It
kind
of
yeah
they're.
Have
you
been
able
to
find
the
the
settings
feedback
in
dovetails.
B
A
B
B
B
B
A
B
Yeah
and
feel
free
to
ask
any
questions
because
in
in
dovetail
it's
like
a
stream
of
consciousness
of
different
user
quotes,
but
the
survey,
the
project
admin
survey
is
more
structured
and
you'll
be
able
to
follow
a
story
more,
but
in
the
sus
it's
kind
of
like
random
feedback,
because
it's
just
we'll
get
pages
of
you
know
comments
from
people
and
then
pull
out
the
ones
that
are
related
to
settings.
But
the
other
one
is
more
structured
and
tells
a
story.
B
A
Adjusted
I
thought
that
this
is
under
enablement,
yeah.
B
A
I
mean
that
is
good,
because
we
are
fair
designers.