►
From YouTube: Settings UX - Enablement
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 Enablement.
More on https://gitlab.com/groups/gitlab-org/-/epics/3535
A
C
B
It's
cool
awesome
so
today
we're
here
to
talk
about
previously
settings
this.
B
I
think
we
touched
based
on
this
topic
a
couple
of
times
right,
but
then
I
told
you
that
I
wanted
to
be
more
formal
just
in
a
way
that
the
topics
I
have
in
the
agenda
and
also
see
where
your
feedback
for
enablement
aligns
with
what
other
designers
already
said
from
different
stage
groups-
and
you
know
there
is
this
epic
for
settings
that
so
far
doesn't
really
belong
to
any
stage
groups,
and
I
created
this
proposal
to
go
over
existing
setting
issues
and
also
look
at
previous
research
preview,
easier
insights
and
feature
requests
that.
C
B
But
also
try
to
get
an
understanding
from
different
stage
groups.
Where
are
they
right
now
and
when
it
comes
to
settings
and
what
are
the
the
future
enhancements
that
different
things
are
planning
so
that
we
can
align
here,
and
I
saw
that
you
already
added
some
things
in
the
agenda.
So
yeah
we're
going
to
talk
about
the
previous
work
by
by
enablement.
C
A
So
I
think
enablement
we
have
several
several
different
groups,
but
what
I
can
talk
about
today
is
the
geo
distribution
and
search
which
includes
some
of
the
ui
and
the
others.
I
cannot
tell
you
that
much
so
thanks,
please
geo
team.
We
we
have
already
some
chances
to
revisit
this
page.
So
if
you
see
the
feedback
page
here,
do
you
want
me
to
share
the
screen
and
then
walk
through
this
okay.
A
So
if
you
see
the
geo
settings
page,
we
we
don't
have
that
much
in
on
the
ui,
because
the
other
behavior
could
be
done
in
the
terminal.
For
now,
and
we
already
revisit
this
page
and
then
now.
Everything
here
is
from
the
latest
pajama
and
then
I
also
check
with
the
behavior
on
the
pajama
document.
So
I
think
it's
it's
done,
but
of
course,
if
you
have
any
feedback,
I
can
also
add
a
new
issue
and
adding
to
the
epic.
A
A
A
So-
and
this
is
the
distribution
teams
related
setting
page,
which
is
the
just
the
default
page
of
the
admin
area.
I
chose
this
page
because
I
think
this
is
the
only
page
about
setting
related
to
distribution,
because
distribution
take
care
of
the
installation
of
the
cell
phone
set
and
also
some
upgrading
version.
A
So
I
think
there
are
some
room
for
improvement
regarding
the
upgrading
journey
from
this
page.
It's
it's
not
that
clear.
So
what
our
user
currently
doing
for
this
is
just
open,
a
new
tab
and
google
like
upgrade
the
left
version
ubuntu,
and
then
they
found
the
right
document.
So
there's
no
link
in
between
those
pages.
A
And
maybe
there
could
be
some
other
pages
could
be
part
of
the
distribution
setting
the
wax.
But
I
went
through
the
document
that
maybe
it's
under
the
gross
team
or
the
distribution
team,
so
I
think
in
general,
like
we
need
to
revisit
the
general
admin
settings
area
because
we
have
everything
there
and
it's
not
easy
like
to
imagine
that.
Okay,
it's
under
the
general
settings.
B
I
mean
I
work,
I
don't
think
I
work
at
all
with
the
admin
area,
but
then,
when
I
go
into
the
that
environment
that
you
gave
me
and
I
play
around
with
it-
I
wonder
if
what
you
have
now
in
the
admin
area,
it's
it
just
replicates
the
patterns
that
we
have
in.
You
know
the
regular
product
project.
B
A
Not
here
so
this
is
what
I
could
see
part
of
the
distribution
team's
work
and
I
realized
there
is
some
more
setting.
Ux
part
could
be
involved
in
the
global
search
team,
because
this
is
what
I
have
like
missed.
Actually,
so
I
went
through
this
page,
so
as
a
system
administrator,
they
need
to
enable
elastic
search
for
their
non-admin
user
on
this
page.
So
they
also
need
to
start
from
this
page.
B
A
B
A
A
A
Okay,
so
I,
but
thanks
to
this
spanner,
I
could
follow
it
and
then
this
is
some
part
of
it's.
Not
all.
Sorry,
I
think
I
tried
to
make
the
screenshot,
but
this
is
not
all
we
have
some
more
in
between
these
two
images
and
what
I
heard
from
the
team
is,
we
will
have
more,
and
this
long
list
is
part
of
the
general
settings
journal
and
if
user
expanded
and
they'll
see
this
page,
so
as
you
can
see,
I
think
designers
should
revisit
this
page
in
the
line
with
the
pajama
design
system.
A
And
also
so
sorry,
I'm
not
gonna,
say
anything,
oh
okay,
so
and
also
like,
I
think
some
components
is
like
could
be
replaced
by
something
else
like
because
like
as
far
as
I
know,
there
is
no
design
team
involved.
When
we
come
up
with
this
design,
it
was
coming
from
the
engineering
team.
A
Then,
if
I'm
wondering
if
it
is
the
really
right
place
to
stay
here,
it's
still
under
the
settings
general
and
I'm
just
questioning
like.
Maybe
we
need
to
rethink
about
this
information
architecture.
First,
it's
hard
to
find
for
the
first
time
user.
Second,
it's
it's
a
lot.
There's
a
lot
of
things
ongoing
here.
B
A
Yeah,
so
I
think
not
this
one.
So
when
I
did
the
setting
ux
for
the
geo
I
I
was
a
bit
confused
because
I
think
I
mentioned
it,
like.
I
told
you
before
on
our
101
that,
like
we,
our
form
has
some
different
types
like
we
sometimes
use
accordion
to
just
click,
expand
and
collapse,
or
sometimes
we
use
totally
different
layout,
not
like
this
geo
settings
view.
I
think
it's
like
left
hand
side
like
30
percent
of
the
way
we
used
to
as
a
title
area
and
the
other
70
percent.
A
A
B
Because
I'm
not
sure
if
I
mentioned
this
before,
but
we
during
this
conversation
with
designers.
This
is
a
topic
that
comes
up
quite
often
as
in
we
have
components,
guidelines
and
we
have
you
know
the
ui
the
look
and
feel
of
the
components
in
isolation.
B
But
then
there
is
this,
because
there
is
so
much
inconsistency
across
the
product
there.
It
will
be
helpful
to
have
you
know:
pajamas
guiding
the
settings
ux
or
the
you
know
the
general
guidelines
for
how
we
should
design
this
yeah.
A
That'll
be
really
helpful
because
key
lab
is
a
complicated
product
and
then
I
do
think
like
every
single
stage
group.
They
have
on
their
settings
area
and
they
look
different,
sometimes
and
as
a
designer.
That
is
confusing.
And
if
I
imagine
that,
maybe
for
the
user
and
if
they
are
not
familiar
with
our
product
and
things.
C
B
That's
a
very
good
point
because
we
try
to
like
myself
when
I'm
trying
to
design
something
for
settings,
then
I
look
at
the
product
I'm
constantly
like.
Oh,
my
god,
is
this
this
source
of
truth.
Do
people
actually
use
this
right
and
we
do
have
research
and
actually
the
the
recent
research
and
the
the
conversations
and
the
interviews
around
navigation
they
touch
base
on
settings
as
well.
I.
B
Katrine-
and
I
think
you
saw
those
insights-
I'm
gonna-
add
here
in
the
chat
about
the
system
usability
for
settings.
B
And
then
we
have
the
big
themes
that
were
identified.
You
know
when
I
created
this.
The
settings
ux
epic,
so.
B
I
think
we
already
touched
on
that
the
change
of
context
so
in
in
the
project
in
the
group
settings
we
have
this
switch
between
contextual
settings
and
general
settings,
and
I
think
you
also
mentioned
this
right
in
the
general
and
the
areas
yeah
we'll
try
to
I'm
trying
to
think
and
placements
of
features.
B
Let
me
see
you
have
so
many
issues
here
and
options
overload
the
switch
to
the
flow.
Those
were
like
the
main
things:
discoverability
global
versus
contextual
settings.
The
switch
the
flow
options
overload.
Any
consistency.
B
A
I
think
the
discoverability
in
general
is
a
bit
problematic.
I
know
that
it's
not
like
easy
as
the
product
team,
because
we
have
so
many
things
to
be
shown
there
and
then,
of
course,
we
we
like
to
show
everything
at
once,
but
it's
it's
not
like
that,
and
it's
not
how
user
perceive
the
ui
when
they're
using.
A
B
B
And
this
nick.
B
It's
a
settings
ux
and
re-architecture.
That's
how
we're
calling
it
and
we
do
have
a
bunch
of
voltage
requests,
but
also
our
existing
insights
and
research
that
we
started
but
never
finished.
Around
settings.
Ux,
node,
settings
search.
B
I
remember
that
we
talked
about
when,
when
you
were
showing
your
prototypes
on
how
you
wanted
to
improve
the
search
layout
and
everything,
did
you
consider
expanding
the
options
that
the
users
will
be
able
to
search
for
in
the
global
search?
For
example,
you
can
search
for
settings
you
can
search
for.
B
A
So
when
I,
when
I
tried
to
think
about
so
redesigning
the
search
result
page,
I
didn't
think
about
like
adding
new
features,
because
I
only
have
like
one
milestone
to
be
delivered
and
I
just
deliver.
So
I
think
the
new
designer
nick
he
will
join
from
13.5
for
this
global
search
team,
and
I
think
you
have
more
time
to
investigate
those
and
also
what
josh
mentioned,
and
then
I
also
found
something
similar
idea
like
like
some.
A
I
don't
know,
keyboard
shortcut
or
maybe
using
the
top
navigation
search
bar
by
typing
some
specific
term
that
they
can
like
go
through
some
setting
option
if
they're,
what
does
that
mean?
Or
maybe
if
they
have
accessibility
to
see
those
settings
page?
I
think
it's
a
nice
idea,
because
it'll
reduce
the
number
of
clicks
at
least
or
it
will
increase
the
discoverability.
A
C
A
B
I
have
this
tendency
of
asking
one
thing
and
then
I
get
too
excited
no,
it
was
about
extra
features
and
also
about
existing
research.
When
you
were
doing
the
redesign
of
settings
jesus
christ
of
search.
A
So
I
have
found
something
it,
but
it's
not
really
directly
about
the
global
search.
It
is
about
some
filtering
option
in
the
issue
list
or
the
mr
list
that
we
have
and
then
I
have
seen
those
research
document
and
the
result-
and
I
that
I
could
refer
to,
but
it's
not
exactly
the
same.
So
what
I'm
currently
conducting
is
it's
not
about
just
setting
thing.
It's
more
about
just
searching
result.
B
Itself
now
that's
that's
all
right.
I
just
want
to
touch
base
with
I
think
and
team,
and
then
we
talked
we'll
have
a
video
on
future.
If
you're,
curious
and
also
the
milks
here
as
well,
it
was
my
favorite.
My
last
call
where
they
talk
about
that's
one
of
the
main
things
for
for
growth
is
really
that
we
make
easier
to
find
things
in
settings.
B
One
already
sent
you
that's
the
big
epic
and
again
yeah
mate
had
some
some
interesting
things
to
share,
but
it
was
never
prioritized.
So
if
you're
curious
or
if
you
ever
feel
like
you
need
to
go
there,
there's
there's
some
issues
that
a
lot
of
this
information
life.
B
A
A
I
don't
know,
manage
the
version
or
just
provide
at
least
a
link
to
the
documentation
when
they
upgrade
the
self-managed
version,
because
that
is
part
of
settings
and
administrative
work
that
they
need
to
maintain
the
right
version
for
using
some
managed
gitlab
and
for
nick.
I
think
he
will
have
plenty
of
things
to
do
and
I'm
not
so
sure
about
like
when
the
setting
ux
will
be
prioritized
on
the
top
level,
but
maybe
not
for
now.