►
From YouTube: Settings UX - Growth
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 Growth.
https://gitlab.com/groups/gitlab-org/-/epics/3535
A
Awesome
thanks
again
for
joining
and,
as
I
said,
I'm
gonna
jump
right
in
I
gave.
I
think
a
brief
overview
yesterday
during
the
ux
call
didn't
have
a
lot
of
time
to
chat
about
how
these
plans
and
what
we're
doing
for
settings.
But
I
think
it's
awesome
that
I
have
the
opportunity
to
talk
to
you,
because
growth
took
over
navigation
right
as
well
as
part
of
the
yeah,
the
not
owned
functionalities
and
for
settings.
I
think
kind
of
trying
to
do
the
same
thing.
It's
still
or
it's
debatable.
A
I
think
that's
going
to
change,
but
still
labeled
as
a
group
not
owned
and
nadia,
and
I
started
with
this
initiative
to
look
into
the
existing
issues
and
ux
proposals,
research,
everything
for
navigation,
sorry
for
settings
and
that's
what
you
can
find
in
the
epic
and
then
pretty
much
during
these
calls.
A
As
you
see
in
the
agenda
doc,
I
just
want
to
talk
to
you
a
little
bit,
so
we
can
maybe
gather
more
information
on
what's
the
state
of
settings
right
now
in
different
stage
groups
and
then
validate
together
with
katherine's
research.
Let's
say
the
main
topics,
or
what's
hot
right
now
in
settings,
so
we
have
a
lot
of
discussions
about
information,
architecture
or
just
visibility
of
settings,
inconsistencies
in
the
ui
and
then
rediscover.
I
just
wanted
to
talk
to
you
a
little
bit
about
yeah.
B
I'll
start,
since
I've
got
the
first
thing
in
the
agenda,
so
I
did
some
work
so
for
context.
I
did
some
work
for
retention
and
growth
around
increasing
engagement
with
our
features,
especially
after
a
new
release,
and
this
culminated
in
some
thinking
around
a
what's
new
project
and
so
I've
kind
of
linked,
the
ui
design
and
plus
the
settings
issue,
and
I
think
to
answer
the
question
in
the
dock
around
what
challenges
did
I
have
with
the
settings?
B
Really,
there
wasn't
a
a
place
to
or
an
ideal
place,
to
put
a
particular
setting.
We
wanted
to
give
people
the
ability,
on
a
on
a
self-managed
instance,
to
be
able
to
turn
off
the
ability
to
show
this
to
particular
users,
mainly
because
of
security
reasons,
especially
if
you
have
an
external
person,
that's
using
the
instance,
and
they
know
what
version
of
the
platform
that
you're
running
and
it
could.
B
You
know,
lend
some
security
problems
and
then
also
because
you-
maybe
you
just
don't-
want
your
users
to
know
that
you're
not
upselling
and
you're,
not
getting
the
the
most.
So
there
are
legitimate
reasons
why
people
wanted
to
turn
this
off
and
we
ended
up
placing
it
in
the
admin
general
settings
page,
and
I
actually
need
to
refresh
my
memory
because
I
can't
remember
where
it
lived.
B
B
B
So
that
was
a
big
challenge.
I
really
wanted
to
maybe
create
another
compartment
or
category
and
and
maybe
fix
up
some
of
the
the
hierarchy.
But,
as
you
know,
the
way
we
work
with
mvc
that
just
wasn't
going
to
be
possible
in
a
time
frame
that
we
had.
B
That
would
have
been
like
a
much
longer
in-depth
look
what
you're
doing
now.
So
I'm
happy
very
happy
that
you're
working
on
this,
so
just
to
sum
up
the
issues
I
had
was
just
a
no
idea
really
where
to
place.
It
wasn't
really
a
framework
of
understanding
on
where
to
place
the
the
settings
and
then
also
the
hierarchy
of
when
I
actually
got
in
there
and
found
the
place
to
put
it.
It's
just
a
bit
overwhelming,
and
I
know
that
users
are
probably
going
to
find
that
overwhelming
as
well.
So.
A
And
then
team,
where
did
you
go
to
get
help
or
to
try
to
understand
how
settings
work,
given
the
yeah
the
current
status
of
it
across
the
product?
What
was
your
source
of
truth
for
that.
B
Was
really
engineers
because
it
wasn't
like
you're
saying
it
wasn't
really
an
owned
thing
and
a
couple
of
pms?
Actually
I
reached
out
to
so
jeremy
on
manage,
I
believe-
and
I
forget
who
else,
but
it
was
mainly
growth,
engineers,
so
jeremy,
joe
another
jeremy,
on
the
cross
team
and
jay.
They
were
really
helpful.
B
They
they
gave
some
kind
of
insights,
and
so
because
these
settings,
I
think,
do
you
know
what
they
do,
what
they
were
for,
and
so
it
was
good
to
get
some
context
around
what
was
actually
happening
on
the
page,
but
in
general
it
was
mainly
the
engineers
who
were
the
driving
force
for
the
kind
of
source
of
truth
in
settings.
A
And
other
than
the
the
framework
for
how
settings
work,
what
do
you
think
that
might
have
might
have
helped
you
during
this
the
design
process,
because
we
talked
about
it
about
with
other
designers
on
you
know,
having
pajamas
assets
or
having
some
sort
of
guidelines
on
they're
a
bit
more,
not
so
much
a
component
centered,
but
how
this
works
in
context
with
a
page,
you
know.
B
Yeah
yeah,
I
I
totally
hear
you're
coming
from
and
I
think
what
would
have
helped
would
have
been
maybe
to
have
more
of
this
documented.
B
B
So
there
was
more
documentation
and
maybe
a
framework
around
how
settings
should
be
grouped,
and
maybe
some
rules
in
terms
of
you
know,
once
you
get
to
a
certain
level
or
a
certain
amount
of
settings
inside
them,
I'm
just
using
the
the
admin
page
as
an
example
inside
of
one
of
those
expand
collapse
modules.
B
Maybe
once
you
get
beyond
a
certain
point,
it
needs
to
be
reorganized.
If
that
was
a
rule,
we
could
have
baked
it
into
our
kind
of
engineering
and
design
process,
and
it
would
have
been
something
that
we
would
have
spent
allocated
or
allocated
time
towards
and
really
kind
of,
honing
in
and
crafting
the
experience
a
little
better
for
users.
So.
C
Yeah,
so
I
did
some
stuff
for
settings
redesign
and
trying
to
improve
settings
in
general.
Back
when
I
was
on
manage
right,
andreas
was
actually
the
product
manager
back
then
still
and
what
we
were
trying
to
do
is
we
started
with
projects
and
group
settings
just
trying
to
make
them
more
usable,
because
when
I
joined
those
sections
that
tim
just
mentioned
right,
if
you
go
to
settings,
you
have
a
couple
of
those
expandable
sections
they
weren't
even
properly
labeled.
C
So
if
you're
searching
for
something
specific,
you
basically
have
no
idea
where
to
find
it,
even
just
by
going
through
the
page,
either
scanning
it
or
even
reading
it,
because
it
wasn't,
it
wasn't
mentioned
some
things.
Weren't
mentioned
that
they
were
actually
in
that
settings
section
right.
C
C
So
here
you
will
find
this
this
this
and
that
right
without
here,
you
will
find,
of
course,
and
then
we
also
updated
the
descriptions,
because
each
of
those
sections
also
has
a
short
description.
C
C
So
I
think
this
would
be
a
really
good
opportunity
with
the
newfound
focus
on
these
settings
in
general
right.
So
this
is
what
we
did
back.
Then
settings
are
your
most
proud
of
so
yeah,
that's,
basically
it
we
were
actually
able
to
improve
slightly
improve.
I
should
say
some
of
these
pages.
I
can
try
to
dig
these
issues
up.
I
saw
you
you
pasted
a
couple
already,
and
maybe
that's
actually
those
issues
we
we
made
them
more
usable.
C
A
C
Click
on
an
actual
expand
button,
which
was
quite
annoying.
Those
were
like
these
small
improvements
which
you
know
it
improved
the
settings
page.
But
not
that's
enough.
If
you
ask
me
and
if
you
go
to
the
admin
page,
that's
the
tricky
one
right.
That's
the
huge
settings
page
that
I
I
would
assume
nobody
looked
at
in
ages
and
probably
no
one
from
ux.
B
C
Yeah
exactly,
I
recently
took
a
quick
look
at
the
admin
overview
page
where
you
have
the
information
about
how
many
users
you
have
there,
how
many
projects,
what
features
you
have
enabled
and
those
things
it's
not
even
optimized,
so
that
sections
would
be
nicely
scaled
on
on
a
mobile
screen.
They
just
get
squeezed
right
and
I
would
assume
no
ux
person
was
ever
involved
in
doing
anything
on
that
screen.
C
For
example,
it's
so
poorly
designed
right,
but
this
this
might
actually
be
something
that
the
growth
expansion
team
might
start
looking
at
in
in
terms
of
improving
navigation,
and
we
also
have
an
interest
on
improving
and
improving
that
page,
because
we
want
to
drive
more
upgrades
to
higher
plans
right
and
at
the
moment,
you
can't
find
the
information
on
how
to
upgrade
to
a
higher
plan
for
self-hosted
instance
from
inside
the
application.
There's
no
link
that
will
tell
you
here
you
can
read
how
you
can
do
that,
not
even
to
documentation
right.
C
So
we
we
added
that
recently.
I
think
it
should
be
implemented
soon
if
it
wasn't
already,
but
then
the
next
steps
will
be
to
add
a
button,
and
it
takes
you
to
a
form
where
you
can
contact,
say
our
sales
department,
for
example,
for
stuff
like
that
right
and
with
with
looking
at
that
admin
overview
page
just
because
of
these
small
things.
I
just
couldn't
help
myself
to
try
to.
C
You
know
just
make
an
improvement
here
or
there
and
slightly
change
the
the
visual
look
of
it,
because
it's
so
dated
right
and
it
doesn't
scale
on
mobile
devices
as
well.
There's
so
much
we
can
improve
there.
It's
just
kind
of
waiting
there
for
one
ux
person
to
to
pick
it
up
and
start
working
on
it.
Basically,
so
we
might
actually
take
a
look
at
that
in
the
future.
I
think
I
even
mentioned
that
yeah
in
in
the
section
below
where
you
are
asking
about
the
upcoming
direction
and
priorities.
C
So
another
thing
that
I
know
we.
I
started
this
discussion.
It
was
the
members
management
right,
so
you
need
to
go
in
the
past.
You
needed
to
go
to
settings
and
members.
I
think
it
was
like
that
in
project
projects
you
need
to
go.
You
need
to
go
to
settings
members
to
manage
members
of
that
project.
C
C
A
Yeah-
and
I
heard
last
week
last
friday,
I
had
a
chat
with
mike
nichols
and
he
actually
mentioned
this
part
that
the
the
member
settings
that,
when
you're,
for
example,
setting
up
permissions,
for
I
don't
know
as
a
pipeline
or
for
a
project
or
group.
A
A
There
isn't
some
issue
and
some
feedback
related
to
that,
and
that's
another
point
that
I'm
hearing
a
lot
during
this
calls
is
that
we
are
not
really
good
at
cross-linking
or
at
least
letting
users
know
that
hey
once
you
set
up
something
here
on
members,
for
example,
your
next
step
is
to
go
to
your
group
page
or
to
your
project
page
settings
and
then
define
permissions
there
right.
A
So
there
is
also
some
comments
on
that
other,
and
I
think
it
relates
to
a
little
bit
these
general
patterns
that
we
could
implement
or
that
we
could
recommend
so
that
when
you
create
a
new
page,
you
know
make
sure
that
you
connect
the
flow
with
a
different
part
of
the
product.
C
Yeah-
and
I
think
that's
that's
a
good
thing
to
recognize,
because
this
is
something
that
we
start
noticing
a
lot
on
growth,
because
we
work
across
different
features,
different
areas
of
the
of
the
application,
and
we
just
noticed
how
things
aren't
connected
at
all,
and
I
guess
it
comes
naturally
from
you
know
one
group
of
people
working
on
this
feature.
Then
another
group
of
people
working
on
another
feature.
The
two
are
kind
of
related
in
some
cases
in
some
scenarios
and
the
flow
should
be.
C
C
A
So
it
I
feel,
like
my
experience,
that
this
type
of
enhancements
they're
always
sent
to
the
backlog,
and
then
you
pay
the
price
with
the
overall
use.
Experience.
A
No,
so
in
the
in
the
main,
epic
actually
linked
here,
I
sent
you
the
incorrect
link
before,
but
I
think
this
main
yeah
these
big
items
that
we
talked
about
search
and
just
the
overall
discoverability
of
settings
and
connecting
things
to
different
places.
I
grouped
them
in
the
settings-
ux
re-architecture,
epic.
I
had
to
call
re-architecture
because
redesign
was
a
bit
a
bit
too
strong,
and
then
I
think
here
I've
seen
a
lot
of
issues
that
you
created
in
the
past
day,
like
yeah.
A
And
catherine
also
shared,
I'm
not
sure
if
you
did
the
research
together
with
cat
right
now,
for
it
was
from
like
your
legacy,
but
there
are
a
lot
of
things
that
still
relate
to
what
you
say
and
then
indeed,
there's
no
clear
ownership
for
it
right
now.
So
I
think
my
plan,
what
I'm,
what
I'm
starting
to
figure
out
during
this
call
is
that
I
want
to
just
gather
this
feedback
and
the
issues
where
we
say.
Okay.
A
This
is
my
next
step
for
settings
in
growth
or
my
next
app
for
settings
in
release
management
and
try
to
combine
it
so
that
maybe
we
can
connect
first
step.
We
can
connect-
and
you
know
if
you're
implementing
specific
patterns
or
changing
things,
make
sure
that
we
are
following.
A
I
don't
know
one
standard,
or
at
least
not
changing
things
too
much
in
different
stage
groups,
but
also
when
we
talk
about
the
themes
for
settings
which
we
we
pointed
it
as
discoverability
of
settings,
the
global
settings
versus
project
settings
or
like
feature
settings
mix,
the
switch
of
the
flow.
The
options
overload,
the
inconsistencies
that
we
have
in
the
ui.
Those
are
like.
A
The
four
five
main
topics:
what
I'm
thinking
right
now
is
that
we're
gonna
just
try
to
group
our
ideas
and
our
feedbacks
in
our
previous
challenges
into
these
buckets
so
that
we
can,
together
with
the
leadership,
try
to
look
into
the
what's
next
because
indeed
like
search.
It's
such
a
big
thing,
but
I
think
if
we
commit
to
delivering
search
for
settings,
it
might
not
be
the
one
thing.
You
know
that
that
can
help
us
across
the
product.
B
But
yeah
ask
when
you
say:
search:
do
you
mean
searches
in
and
I
don't
mean
to
get
into
the
weeds,
but
searches
in
a
a
user
initiated
enter?
For
instance,
you
have
to
interact
or
a
filtering
system
like
what
we
have
for
groups
and
projects.
A
Yeah
we
have
two
types
of
issues
or
proposals
open
enablement.
I
think
xinjiang
shared
this
in
the
you
actual
case
last
week,
where
there's
a
proposal
to
improve
the
global
search
on
the
top
navigation,
where
you
can
also
search
for
settings
things
there.
So
if
I
type
the
icd
of
variables
the
results
are
going
to
show,
you
know
a
highlight
in
the
settings
page,
that's
one
and
then
the
other
one
is
like
what
mate
say
that
in
the
settings
page,
you
can
search
for
things
there.
A
B
Okay,
the
reason
when
I
say
filtering
I
don't
mean,
like
I
mean,
maybe
like
tagging
or
anything
like
that,
but
have
you
you
know
how,
if
you
go
on
to
like
the
groups
or
projects
page
in
the
right-hand
corner,
I
believe,
and
I
think
I
need
to
refresh
my
own
memory,
but
it's
not
the
group,
it's
the
the
overview
page,
sorry,
not
not
inside
of
a
group,
but
just
the
overall
very
little
overall
page
in
the
right
hand
corner
you
have
the
ability
to
type
in
the
name,
and
it
would
definitely
kind
of
find
what
you're
looking
for
in
line
rather
than
having
to
search
search
rather
and
refresh
the
page,
and
then
it
shows
you
your
results.
A
Sorry,
I'm
muted,
where
you
have
a
I'm
on
the
group
page
and
then
has
a
subgroup
and
project,
and
then
I
have
a
list
and
there's
a
search
bar
right
in
the
on
page.
B
The
understanding
that
the
engineers
had
was
that
it
was
gonna
you
type
in
say
I
don't
know
a
project's
called
analyst
and
you
type
in
analyst
and
then
you
have
to
hit
enter
or
interact
with
a
a
go
button
or
submit
button
before
we
can
draw
those
results,
and
I
think
it's
a
much
more
seamless
experience
happened
in
line,
so
there
isn't
a
browser
refresh
there
isn't
any
kind
of
server-side
refreshing
it
just
happens,
live
on
the
page,
almost
like
a
you
know
like
an
app
format.
C
A
For
sure,
and
my
experience
with
the
search,
the
gitlab
search
is
that
it's
not
there.
I
think
it's
not
google
right.
So
if
I
want
to
find
something
on
gitlab
I'll,
just
google
it
and
then
I'll
go
back
to
gitlab
and
mike
nichols
also
shared
some
insights
on
having
this
contextual
search.
That,
indeed,
would
just
you
know,
work
almost
like
an
autocomplete,
and
then
you
could
see
in
the
in
the
global
search
the
the
the
result
page.
That
syndrome
is
working.
A
Then
you
have
like
a
sidebar
saying
if
you
type,
for
example,
variables
and
then
you
have,
the
results
appear
on
ci
cd
variables.
You
know
project
variables,
admin
variables
and
then
like
having
a
sidebar.
A
Then
you
select
in
context
I'll
find
that
with
that
proposal
cool
well,
it's
actually
here,
let
me
but
then
again
I
feel
like
it's
a
very
big
thing
to
implement,
and
I
really
wonder
like
now
without
looking
at
without
having
a
clear
vision
for
it
as
a
designer.
I
wonder
if
this
is
our
low
hanging
fruit.
If
search
for
settings,
is
I
my
experience
as
a
user
as
a
gitlab
user?
A
I
think
the
information
architecture
of
settings-
and
you
know
this
connectivity
with
other
parts
in
the
product
yeah-
would
solve
maybe
more
problems
than
than
search,
but
I
see
I
definitely
see
the
value
it's
here.
Let
me
add
to
the
chat,
I
think
it
it
clicks
so
mike
shared.
I
think
this
is
a
yabia's
code
and
he
say
that
you
have
this.
You
know
super
powerful
way.
B
Yeah
yeah,
that's
literally
the
I
would
say
the
the
best
case
scenario
and
I
would
have
felt
totally
more
comfortable
when
I
was
working
on
the
previous
project
with
the
what's
new
component.
If
that
was
indeed,
there
was
a
way
to
search
easily.
That
would
have
kind
of
mitigated
some
of
the
fears
I
had
with
people
kind
of
discovering
it
and
being
able
to
use
it.
B
C
Yeah,
because
the
two
of
you
talked
about
search
versus
filters,
so
we
actually
use
both
at
gitlab
and
I
actually
wrote
these
guidelines
and
it
was
one
of
the
trickiest
guidelines
that
I
had
to
write.
So
we
have
we
differentiate
them
by
how
users
interact
with
them.
You
could
call
them
search
and
filter.
We
just
call
them
search
by
type
or
search
by
what
is
it
confirmation
or
something
like
that?
C
So
the
confirmation
is
where
you
need
to
press
a
button
to
actually
trigger
the
search
right,
yeah
confirmation,
so
we
use
both,
but
we
use
them
very
inconsistently
and
we
haven't
replaced
existing
search
boxes
with
the
actual
ones
right,
because
the
search
by
confirmation
has
a
button,
the
other
one
doesn't
so
that
alone
should
kind
of
indicate.
C
If
the
button
is
present,
you
need
to
press
it.
If
it's
not
present,
it
will
filter
as
you
type
right,
but
we
need
we
need
to.
As
we
do
now
have
this
epic
for
button
migration.
At
some
point,
you
will
need
to
replace
all
these
search
boxes
so
that
they
actually
use
the
component
that
we
built
right.
A
Yeah,
that's
a
good
point.
Does
the
same:
it's
not
just
the
the
interaction
but
also
the
placement
in
the
page,
or
you
know
like
what
you're
saying
it
has
a
trigger
yes
or
no,
and
I
think
I
saw
an
issue
that
you
opened
also
a
couple
of
maybe
a
year
ago
that
was
about
replacing
or
improving
the
positioning
of
buttons
like
the
submit
button
in
settings.
That's
another
thing
that
I've.
C
A
A
I
have
yes
here.
I
have
an
epic
for
bugs
I'm
gonna
drop
here
in
the
agenda
and
also
in
the
in
the
chat
this
epic
here
that
lists
all
the
existing
and
the
bugs
ux
dev
to
ipolish
anyways
things
that
need
visual
improvement.
That
will
improve
the
user
experience
and
don't
necessarily
need
a
designer
to
sign
off
so
they're,
mostly
yeah
buttons
misaligned,
you
know
copy
is
unclear.
A
So
if
you
have
anything
that
is
in
your
stage,
group
that
you
think
would
fit
here
for
settings
now
feel
free
to
add
to
this
to
this
bucket,
but
also,
if
you
think
that,
with
your
next
work
on
settings,
you
can
pick
up
some
of
these
issues
and
make
improvements
and
yeah
just
have
a
conversation
with
your
pms.
I
think
that
would
also
help
a
lot
because,
similar
to
the
migration
and
the
ui
polish
efforts
these
are
here.
A
B
A
Yeah
all
right,
I
gotta,
drop
guys.
I
have
so
many
questions,
but
if
you
can
find
any
other
issues
or
if
you
think
of
anything
else,
that
will
be
valuable
here,
please
either
add
to
the
agenda
doc
or
to
the
main
epic,
so
that
other
people
can
see
as
well
and
then
end
of
this
week,
I'll
try
to
put
together
some
thoughts
and
cross-reference.
Some
of
these.