►
From YouTube: UX Showcase – Exploring the vision for navigation
Description
Previous UX Showcase - https://youtu.be/fcxejI2HmwU
Google slides - https://docs.google.com/presentation/d/1x97LeAM9uB62AIHZ5ohHyiD4YvO1ZykWi5MylBKtR8Q/edit?usp=sharing
Build a compelling vision as a north star for navigation (#365403) · Issues - https://gitlab.com/gitlab-org/gitlab/-/issues/365403
Figma - https://www.figma.com/file/PMIznpz7POtRKTiurKfZSF/Vision-for-Navigation?node-id=0%3A1
A
Hey
everyone:
my
name
is
austin,
I'm
a
senior
product
designer
here
at
gitlab,
working
on
the
foundations
team
today
for
media
showcase.
I
want
to
run
through
some
of
the
navigation
exploration
that
I've
been
doing
around
our
vision
and
how
we're
going
to
set
the
future
of
gitlab
and
the
architecture
for
that.
A
Just
yet,
but
nick
brant
is
helping,
carry
on
some
of
those
design
ideas
in
the
future,
but
for
now
that
leaves
us
with
15
2.
and
15
2.
We
are
focusing
on
specific
themes,
and
this
is
what
we
used
to
help
orient
the
designs
that
I
was
working
on
and
the
like
previous
milestone,
and
we
came
with
a
bunch
of
different
themes
as
a
team.
A
This
somewhat
fits
in
with
like
the
ux
roadmap
concept,
but
these
helped
us
better
understand
like
what
are
we
really
trying
to
address
in
terms
of
the
navigation
category
and
these
themes
stuck
out
to
us
in
terms
of
what
we
saw
in
sus,
but
also
just
verbatims?
We've
read
from
previous
ux
research
and
other
usability
studies
as
well.
So
we
want
to
address
these
feelings
of
being
overwhelmed,
helping
users
feel
oriented
and
helping
them
pick
up
where
they
left
off
and
in
terms
of
how
much
we
feel
confident
in
them.
A
It
correlates
a
little
bit
to
how
we
see
that
materialized
in
the
research
and
the
frequency
in
which
we
see
these
problems
occurring
so
fast-forwarding
to
15-2.
I
took
those
low-fat
concepts
and
just
started
a
lot
of
ideas
at
it,
adding
more
fidelity,
color,
visual
ideas
and
I'll
be
honest.
I
think
it
was
too
much.
I
was
taking
a
bunch
of
different
ideas,
pulling
them
all
together.
Thinking
about
all
the
different
micro
interactions.
A
It
was
helpful
for
exploring,
but
I
do
think
it
got
a
little
bit
too
in
the
weeds
so
just
to
stick
to
this
presentation.
I'm
only
going
to
be
presenting
this
this
one
basic
view
of
a
project
page
essentially-
and
this
is
where
we
are
going
to
start
a
lot
of
our
research
around,
because
we
feel
like
that
is
part
of
the
orientation
for
the
user
is
where
they're
coming
into
a
project
and
where
they're
trying
to
then
go
from
there.
A
So
each
of
these
explore
a
lot
of
different
problems
at
the
same
time,
and
that's
the
challenge
with
this
is
how
do
we
move
forward
with
that?
We're
tying
it
back
to
those
themes
and
from
there
we're
trying
to
then
better
understand
what
should
we
put
in
front
of
the
user
so
that
we
can
get
meaningful
insights
so,
first
of
all
too
much
visual
fidelity
here.
A
One
of
the
things
I
did
last
milestone
was
take
out
some
of
those
visual
fidelity
elements
back
to
its
core
components,
trying
to
create
more
of
a
baseline
around
each
of
the
design
languages
here
so
that
everything's
on
more
of
an
even
playing
field.
We
don't
want
to
like
over
rotate
towards
an
idea
just
because
it
had
more
visual
polish
than
another
or
had
used
perhaps
like
color,
in
a
way
that
draws
more
tension
so
to
try
and
create
a
more
equal
playing
field.
A
I
took
everything
out
and
then
from
there
started
to
choose
to
add
in
specific
elements
so
bringing
into
these
designs
what's
necessary
and
leaving
behind.
What's
not
so
these
things
might
be
like
adding
the
details
around
the
name
of
a
feature
or
page,
but
not
necessarily
highlighting
all
the
files
in
a
repository
and
just
replacing
that
with
a
placeholder,
with
the
background
of
like
a
skeleton
loader
there
just
to
help
give
context
of
what
is
on
the
page,
but
the
things
that
aren't
necessarily
important,
or
at
least
key
to
the
navigational
experience.
A
A
Do
those
pieces
still
make
sense,
and
from
here
I
started
to
notice
that
there's
a
bit
of
a
logical
grouping
here,
and
I
can
see
this
scale
over
time
or
the
scale
in
terms
of
how
familiar
an
idea
is
to
what
feels
more
unknown
to
a
existing
gitlab
user
today.
So
the
ideas
on
the
far
left
here
are
similar
in
the
fact
that
they're
trying
to
approach
the
same
problems
by
changing
more
of
my
new
details.
A
Ideas
in
the
middle
are
a
little
bit
different,
so
taking
away
that
global
header
tucking
it
into
the
left
sidebar
somehow,
so
you
only
have
one
left
sidebar
instead
of
having
a
global
and
a
left
sidebar
and
the
far
right
is
still
using
a
pure
left
sidebar.
But
it's
a
unique
perspective
because
it's
eliminating
the
concept
of
having
any
sort
of
like
tree
down
structure
where
you're
looking
at
things
by
groups
or
projects
you're.
Just
looking
at
get
lab
and
you're
looking
by
specific
features,
which
is
a
relatively
unknown
concept.
A
We
don't
really
do
it
all
that
much
the
places
that
you
get
that
top
down
view
that
bird's
eye
view
might
be
a
list
of
projects
or
issues
or
merge
requests.
But
you
don't
necessarily
get
that
when
you're
looking
for
all
the
wikis
that
exist
in
gitlab,
so
we're
just
trying
to
understand
on
that
gradient
scale.
Where
do
we
need
to
land?
A
What
we
want
to
avoid
is
too
many
small
changes,
and
this
is
a
hypothetical
definitely
not
our
road
map
or
what
we'll
be
planning
to
do,
but
just
an
example
of
what
we
don't
want
to
have
our
users
experience.
We
don't
want
to
work
on
a
bunch
of
small
changes
that
lead
to
bigger
navigational
impact
that
feels
like
the
platform
is
changing
from
beneath
the
user's
feed.
We
want
them
to
feel
like
they
have
a
consistent,
stable
experience
when
they
come
to
work
on
the
gitlab
product.
A
A
So
I
feel
less
confident
that
we're
going
to
move
towards
the
unknown,
but
by
using
some
of
our
user
research
testing
methods,
we
can
help
validate
or
invalidate
what's
necessary
here,
because
perhaps
somewhere
is
in
the
middle.
Perhaps
like
this
vertical
left.
Sidebar
is
more
useful
and
we
can
start
moving
away
from
our
existing
global
header
and
left
sidebar
to
something
like
this
instead
and
also
be
able
to
say
no
we're
not
moving
towards
this
unknown
concept
more
towards
the
right.
A
We're
really
trying
to
pinpoint
the
vision,
and
so
how
do
we
do
that?
Specifically
115.3
we're
still
refining
our
testing
plan,
so
I'm
still
trying
to
refine
those
designs
to
better
match
the
methodology
that
we're
going
to
employ
we're
looking
between
using
the
right
method
versus
comparative
testing.
But
ultimately,
what
we're
trying
to
do
is
validate
these
concepts.
A
We're
trying
to
take
these
concepts
and
put
them
through
a
testing
method
to
better
understand
which
direction
do
we
want
to
go
while
we
will
do
an
mvc
approach
into
these
visionary
ideas,
we're
just
trying
to
have
at
least
a
guiding
north
star
so
that
we
have
a
better
way
to
say
yes
to
specific
nvcs
and
no
to
others.
The
last
thing
we
want
to
do
is
iterate
into
an
experience.
That's
worse,
so
we
really
want
to
pay
attention
to
our
sus
feedback,
as
well
as
dog
food.
A
Any
changes
that
we
start
to
build
before
we
start
releasing
them
or
more
widely
or
publicly,
and
if
you're
interested
you're
all
welcome
to
follow
along
on
the
issue
that
I've
assigned
to
myself.
That
highlights
the
problem
that
we're
trying
to
solve
those
themes.
A
few
of
the
goals
that
I'd
like
to
see
both
myself
and
some
of
the
solutions
bring
in
the
tasks
of
dog
fooding
work
items
at
the
moment,
so
breaking
those
down
trying
to
road
map
out
how
I'm
like
working
on
this
vision.
A
But
overall,
hopefully,
we
can
find
a
meaningful
direction
for
our
navigation
soon
and
start
testing,
because
I
think
the
most
important
thing
here
as
I
want
to
get
to
a
feedback
loop
where
we're
getting
to
find
out
from
our
users.
Specifically
what
is
working
well,
what
is
not
I
do.
I
don't
want
to
subjectively
choose
which
direction
we
want
to
go.
I
want
to
use
some
of
our
research
insights
to
help
gleam
that
direction,
while
also
relying
on
our
understanding
gitlab
product,
for
what
makes
sense
for
where
we
want
to
take
it.