►
From YouTube: Settings & Navigation Sync Up 2021-02-16
Description
Katherine and Michael discuss GitLab's leftnav from the perspective of UX research and design respectively
A
A
B
Things
are
potential
explorations,
and
some
of
these
things
are
things
that
are
recommended
based
off
of
the
research.
So
basically,
what
I
started
with
is
some
of
the
findings
that
came
out
of
the
study
that
was
specific
to
operations,
navigation
items,
and
so
this
is
just
where
I'm
collecting
all
the
the
different
points
that
were
made.
B
B
B
This
is
not
the
full
list,
it's
so
tricky,
sometimes
because
it
all
depends
on
what
you
have
enabled
in
your
project
anyway.
But
if
you
look
at
some
of
the
items
included
under
operations,
if
we
move
out
the
things
like
terraform,
kubernetes
environments,
feature
flags,
etc,
you'll
be
left
with
the
things
that
are
mainly
related
to
monitoring
and
observability.
B
B
B
A
B
A
A
B
A
And
when
I
was
trying
to
like
figure
out
where,
like
just
the
placement
of
it
on
this,
on
my
on
the
left
now
from
a
visual
interaction
standpoint,
I
was
just
curious.
Like
it's
not
really
issues,
it's
not
a
really
thing,
and
I
was
curious
why
you
were
thinking
and
putting
that,
under
the
overview
level.
B
Yeah,
so
that's
that's
another
thing
as
it
currently
stands.
We
don't
have
a
broad
planning
category,
there's
just
issues,
and
so
it
wouldn't
be
something
you
would
group
together
with
issues,
but
it
is
also
something
that
people
were
tying
into
general
project
information,
overview
of
information,
customer
information,
these
sort
of
things
in
the
card
sort.
So
one
idea
is
to
potentially
move
it
to
the
under
the
just
general
project
overview
section,
since
there
may
not
be
a
strong
case
for
it
being
its
own
top
level
item
at
the
moment.
A
B
And
so,
if
you
see
a
case
where
performance
is
better
or
kind
of
consistent,
then
I
would
feel
confident
with
moving
forward
with
some
of
these
proposed
changes.
But
if
we
saw
that
it
was
worse,
then
we
wouldn't
want
to
move
to
a
worse
situation.
So
then
we
would
kind
of
throw
out
some
of
these
proposals.
B
A
B
B
A
A
We
won't
have
like
hundreds
of
things
on
the
left,
nav,
or
at
least
I
hope
we
don't
because
then
that's
just
wild
so
that
that
being
said,
I
think
there
is
a
another
issue
around
like
starring
pages
within
gitlab,
and
things
like
that.
So
maybe
it
goes
hand
in
hand
and
then
there's
like
a
menu
item
on
the
left
side.
That's
like
a
start.
So
these,
like
your
start
pages
and
then
that
kind
of
lists
your
star
pages
but
yeah,
I
think
rearranging
the
left.
Nav
could
just
come
from
another
issue.
A
That
works
like
that.
We
created
a
few
months
ago
around
what
the
team
is
focused
on
around
enabling
features,
but
potentially
separating
enabling
features
with
hiding
visibility
of
the
left,
nav
items
in
the
left,
nav
versus
turning
off
the
feature
completely
so
like
right
now,
they're
kind
of
co-mingled
into
like
one
one
checkbox
and
that
causes
some
issues
on
you
know
what's
happening
with
her
in
gitlab
instance
is
not
running
properly
or
I
can't
see
something
that
I
need,
because
we
disable
the
features
to
hide
the
feature.
B
Yeah
yeah,
that's
a
good
point,
because
I
was
also
wondering
that
as
well,
because
those
comments
are
coming
from
our
existing
state.
Where,
aside
from,
I
think
the
things
you
were
able
to
disable
before
we
added
more
of
the
security
and
operations
and
analytics
things,
you
can't
take
them
away.
So
it
would
make
sense
why
people
are
kind
of
like
I
need
to.
I
want
there's
something
I
always
go
back
to,
and
I
just
want
to
quickly
go
to
that
thing.
B
B
C
B
A
A
B
This
ties
in
more
to
my
second
point
on
the
agenda
where
I
was
starting
to
do
a
audit
of
the
content.
That's
in
the
left,
sidebar
and
I
basically
have
found
we
have
like
an
abundance
of
list
views
list
pages
and
things
like
that,
even
beyond
the
one
that
we
explicitly
call
list
so,
for
example,
with
files.
A
B
Then
it
shows
up
here,
so
I
don't
know
what
the
solution
is,
but
it
just
seems
like
with
something
like
this
and
that's
why
I
want
to
investigate
the
usage
data.
I'm
not
sure
if
this
is
the
most
important
item
that
could
live
here,
for
example,
because
you
can
access
this
information
in
the
files
view
as
well,
but
I
just
wanted
your
thought
on
that.
A
B
C
B
A
B
B
Yeah
yeah,
it's
just
this
interesting
thing
with
the
locked
files
type
of
list,
I'm
not
sure
what
word
I
want
to
call
it
and
a
similar
thing
with
tags.
You
could
probably
filter
the
tags,
but
then
there
are
some
things
like
in
settings.
For
example,
in
settings
you'll
have
some
of
these
list
views
as
well,
where
you've
kind
of
interacted
with
something
in
some
way,
and
then
you
just
see
the
list
of
all
those
changes
like.
Let
me
find
an
example
sure
not
necessarily
inter
integrations,
but
kind
of
something
like
this.
A
B
B
C
B
A
B
B
You
have
a
similar
thing
where
there's
an
action
to
take,
but
there's
also
kind
of
like
the
states
and
everything
they're,
not
necessarily
they're,
not
the
same
content,
but
I'm
wondering
if
they
can
somehow
interact
in
a
way
where
they
don't
necessarily
have
to
be
entirely
separate
list
views
because
that's
we
have
a
bunch
of
them.
Basically,.
A
B
So
I
would
say
the
goal
is
to
basically
evaluate
the
usefulness
of
some
of
the
things
in
the
left,
sidebar
or
the
frequency
of
use
of
them,
and
if
they're
not
the
most
frequently
needed,
you
might
swap
in
something
else,
or
you
might
just
keep
it
simple
and
reduce
items,
it
could
be
either
way
but
yeah.
This
is
more
of
an
interesting
thing
that
came
to
mind
as
I
started
to
click
through
all
the
different
types
of
content
that
we
have
in
here.
A
B
A
B
Yeah,
so
basically
the
first
three,
I
don't
know
the
first
two
already
have
issues
associated
with
them,
and
so
the
next
steps
will
be
for
me
to
create
issues
for
the
rest
of
them
and
then
to
loop
in
the
relevant
groups
to
kind
of
discuss
why
the
change
is
being
proposed
and
then
kind
of
have
them
discuss
that
as
well.
And
then
I
think
we
probably
have
an
epic
that
just
contains
all
these
proposed
changes
to
the
left
side
bar
and
then
we'll.
A
A
Sounds
good
all
right,
so
I'll
jump
into
my
my
world.
So
at
the
moment
our
group
was
so.
I
was
responsible
for
filling
out
the
epic
around
consolidating
the
top
menu.
So
that's
this
menu
here
now
the
grooves
projects,
more
kind
of
combining
that
into
one
one
thing
that
was
brought
up
long
time
ago
by
other
designers
was
hey
michael.
What
does
this
look
like
on
mobile
and
I
said
yeah-
that's
easy
I'll
solve
that
later,
but
it's
never
easy
as
it
seems.
So.
A
A
A
We
have
them
as
drop
down
menus
like
this,
and
the
challenging
part
with
this
is
that
what
we're
introducing
with
the
flyout
menus
like
we
have
essentially
two
lists
like
a
primary
list
of
these
high-level
objects
and
potentially
recently
visited
links
on
the
side.
So
imagine
combining
this
list
with
this
list
together
on
one
and
on
mobile.
A
A
A
I'm
just
gonna
go
to
figma,
so,
instead
of
having
a
search
box
at
the
top,
this
is
a
concept
where
you
click
on
the
search
and
that
will
take
you
to
search
and
that
kind
of
sets
up
the
foundation
to
say
you
know
if
we
do
want
to
introduce
inline
search
on
the
page
itself,
that
we
could
introduce
it.
Something
like
this
and
then
one
of
the
comments
from
someone
else's.
A
So
would
it
be
useful
to
show
notifications
at
the
headers
all
the
time
for
a
mobile
view,
so
you
open
up
gitlab.
You
will
see
these
things
at
the
top
rather
than
having
it
nested
inside
this
menu
here.
So
then
that
cleans
up
this
menu
to
be
more
like
a
pure
menu
and
having
the
notifications
at
the
top
and.
A
So
how
that
all
could
potentially
look
like
is
something
like
this,
where
at
the
moment
the
user
menu
would
be
like
a
file.
Another
menu
austin
suggested,
perhaps
keeping
a
similar
pattern
or
listing
all
the
items
there.
So
what
that
could
look
like?
Is
you
have
your
user
stuff
down
here
clicking
on
that
would
open
up
a
another
panel
here
that
slides
in
the
note
just
like
these
panels
here.
So
this
is
where
I'm
at
with
the
mobile
menu.
B
Yeah,
I
think
I
would
see
this
more
of
it
as
an
opportunity
to
establish
those
things
because,
historically
from
what
I
know,
we
we
haven't
done
much
research
for
mobile
in
general
and
I'm
not.
I
don't
even
know
how.
Often
we
do
we
design
specifically
for
mobile
or
I
don't
really
know
the
flow
for
that.
But.
A
B
A
B
Were
like
the
top
three
things
that
people
were
mentioning
in
the
cess
survey?
So
what
comes
to
mind
immediately
is
that
I
like
this
idea
of
reviewing
the
icons
and
notifications
and
making
them
present
without
having
to
go
to
the
second
level,
because
these
are
things
that
at
least
from
the
survey
that
people
were
saying
they
wanted
to
do
on
mobile.
So
things.
B
We
also
have
a
survey,
an
overall
navigation
success,
survey
that
we
are
starting
to
run
as
of
last
quarter.
We
kicked
it
off
and
so
we'll
be
doing
that
quarterly.
So
we
might
also
add
some
questions
about
mobile
to
that
survey,
just
to
see
how
the
responses
start
to
evolve
over
time
like
before
this
is
implemented
and
in
the
following
quarters.
So
that's
also
an
option,
the
overall
approach
and
then
the
more
specific
approach
where
you're
testing-
I
don't
know
some
some
main
some
main
there
is
a
lot
changing.
B
B
A
B
A
A
Yeah,
because
at
the
moment,
like
part
of
me,
feels
like
I'm
pretty
confident
about
these
changes
if
it
was
like
yeah,
this
is
one
of
those
moments
like
I'll.
Be
surprised
if
this
difficulties
versus
like
where
someone
prefers
the
old
one
over
this
one
but
yeah.
I
think
that's
why
we
should
do
those
tests,
because
there
might
be
some
things,
I'm
not
saying,
but.
B
A
A
B
B
A
People
want
somewhere
in
here
to
jump
to
issues,
even
though
issues
is
here,
but
somewhere
here
or
somewhere
is
something
to
consider,
because
competitor
products
would
have
a
link
to
issues
really
prominent
on
the
page.
But
maybe
this
is
not
prominent
enough,
but
other
ideas
is
like
reorganizing
this,
so
that
you
know
issues
that
are
assigned
to
me
or
something,
because
this
is
the
overview
page.
A
It
should
help
this,
I
think,
would
be
a
good
area
to
introduce
workflow
based
links
on
the
page,
because
it's
essentially
an
overview
with
like
the
same
view.
As
you
know,
the
files
down
here
so
there's
an
opportunity
to
think
about
workflow
navigation
once
you
land
on
the
project
overview.
So
I
don't
think
it's
jumping
to
the
main
issues,
but
potentially
like
issues
assigned
to
me
or
issues.
A
A
C
B
A
Okay,
so
jumping
away
from
mobile
and
jumping
back
into
the
left
nav
world.
So
one
of
the
things
that
one
of
the
issues
that
is
in
my
radar
is
this
interaction
pattern
that
we
have
around
clicking
on
the
first
item.
You
know
whether
that
takes
you
to
a
landing
page
or
it
is
itself
its
landing
page.
So,
for
example,
here
what
I'm
talking
about
is
clicking
on
issues
actually
takes
you
or.
C
A
Like
issues
with
this,
when
there's
like,
when
it's
collapsed
in
the
sense
that
this
is
clickable-
and
this
is
clickable,
so
both
of
these
are
clickable,
so
it's
like
choose
one
like
make
a
choice
like,
but
but
we
don't
do
that
and
we
allow
people
to
click
both
because
there's
no
separation
really
between
the
two,
so
essentially
there's
three
ways
to
click
there.
Project
overview
is
another
one.
So
if
you
click
on
details,
it's
the
same
thing
as
clicking
on
an
overview
simply
as
clicking
on
the
homepage.
A
B
B
A
A
A
A
A
But
looking
at
the
two,
I
feel
that
this
one
has
more
focus
because
at
the
moment
you're
in
operation,
so
you
have
everything
related
to
operations.
You
don't
have
words
like
repository
and
issues
kind
of
like
cluttering,
your
space,
and
it
holds
up
when
you're
like
looking
across,
so
whether
we
have
another
kind
of
area
or
longer
areas
or
shorter
areas.
You
can
still
surface
a
lot
of
information
here
without
changing
the
view
on
this
side.
A
So
if
you
click
on
issues
that
pushes
everything
down
at
the
moment,
so
I
feel
like
there's
a
consistency
around
this
kind
of
layout
and
yeah
like.
Why
do
you?
Why
do
I
need
to
see
all
these
other
things?
I
think
it's
helpful
for
first-time
users
to
understand,
like
all
these
repositories,
issues
merge
requests
because
icon
association
is
potentially
yeah.
These
are
the
most
obvious
icons
for
newbies,
but
like
once
you
get
familiar
the
hypothesis
like
yeah,
you
know.
What's
going
on
or
on
the
hover
state,
you
can
see
yeah.
A
A
A
So
if
I
remove
that
we
get
into
this
kind
of
state
where
we
have
home
at
the
top,
which
is
makes
sense-
and
we
have
one
click
to
get
to
whatever
the
project
overview
might
be,
and
that
leaves
like
this
thing
so
breadcrumbs
and
like
project
switching
and
then
what's
this
oh
yeah
in
previous
explorations,
we
were
like
toying
with
like
showing
the
project
name
up
here.
If
you
selected
a
specific
project,
but
we
found
out
that
this
doesn't
hold
up
very
well.
A
A
B
B
A
B
B
A
You
see
two,
then
that's
a
that's
a
project
but
yeah.
If
you're
in
a
rush-
or
you
know
how
do
you
know
you
just
don't
know.
So,
that's
why
I
thought
about
signposting
as
a
way
to
like,
whatever
area
of
the
product
that
you're
selected
you're
selected
up
here
and
potentially
combining
the
idea
of
a
project
drop
down
with
breadcrumbs
together
and.
B
A
This
way
you
still
have
that
way
to
navigate,
but
then
here
you
can
switch
your
projects
at
this
level
to
switch
to
view
like
merge,
requests
of
a
different
project
as
well
execution,
wise
and
like
it
feels
okay
to
me
and
this-
and
this
is
probably
something
that
I'm
going
to
get
more
feedback
on.
But
I
try
to
see
other
pages
to
see
if
this
pattern
holds
up
and
if
you
look
at
side
by
side.
A
B
A
B
Yeah,
I
was
thinking
the
same
thing
about
the
the
top
breadcrumb
area,
that
that
might
be
the
one
that
at
least
that
one's
the
part
that's
a
little
bit
weird
for
me
right
now,
but
I
probably
would
get
used
to
it.
But
this
sidebar
thing
I
just
realized
what
it
reminds
me
of
a
little
bit
slightly
reminds
me
of
the
web
ide
kind
of
kind.
A
Like
pages
like
milestones,
this
is
where
this
time
posting
comes
in
handy,
because
if
you
were
on
the
milestone
page,
it
would
look
like
this.
There
is
no
left
now
for
a
milestone
page
but
clicking
into
a
milestone.
It
actually
doesn't
stay
in
the
world
of
milestones.
It
takes
you
actually
select
groups
and
specifically
milestones
within
issues
in
groups
at
a
group
object
level.
A
A
B
A
C
A
C
B
A
A
B
B
B
B
C
B
A
A
B
A
C
A
Longer
this
yeah,
it's
going
to
wrap
so
packaging
registries
would
also
kind
of
be
like
security
and
compliance
where
you
would
have
to
wrap
because
you
have
less
space,
then
you
can't
do
this
and
because
you'll
probably
get
too
close
to
the
sides
with
like
margins
and
stuff,
to
give
it
some
space.
But.
B
B
A
B
B
B
Nav
item
becomes
even
weirder
here,
but
I
see
that
you're
thinking
to
fill
it
up
with
some
of
the
and
the
settings,
but
but
yeah
it's
like
it
would
just
be
empty.
Otherwise,
because
right
now
it
doesn't
even
have
like
a
list
item
or
anything.
That's
so
that's
interesting
and
I
guess
the
same
would
be
well
if
we
don't
move
requirements
because
it
was.
A
A
Is
interesting
because
wiki
could,
like
there's
different
things
that
you
could
surface
there
like
the
menu
on
the
side?
Maybe
goes
on
the
left
hand.
Side
like
these
are
just
kind
of
crazy
ideas,
but
they're
thinking
on
the
spot,
but
yeah.
This
had
page
like
requirements
that
yeah
that's
like
that's
just
the
single
thing,
so
that
could
just
operate
like
unless
I
think
so.
A
B
A
Milestones
where
it
has
like
one
of
these
headings
at
the
top,
because
it's
only
the
one
thing
but
yeah.
Let
me
play
around
with
that
and
create
a
clickable
prototype
so
that
we
can
kick
the
tires
and
see
how
this
feels
for
those
for
those
pages
in
context
of
areas
with
long
mess
and
seeing
that's
distracting
or
it's
fine.
B
A
So
what
I'm
thinking
with
this
is
that
this
is
actually
like
a
combination
of
all
the
latest
solution,
validations
that
I've
done
so
far
like
the
top
nav,
the
navigating
to
like
merge
quest
settings
and
switching
between
projects
and
issues
that
this
could
use
the
same
task
as
the
past.
But
in
this
new
context
and
seeing
how
how
users
deal
with
that.
So
that's
that's!
What
I'm
thinking
of
to
validate
or
to
sense
check
this
stuff.