►
From YouTube: UX Showcase - Navigation, where do we even begin?
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
Today
I
just
wanted
to
share
a
little
perspective
with
you
on
my
journey
into
the
foundations
group,
but
also
what
I've
been
working
on
in
terms
of
the
navigation,
to
help
share
a
little
transparency
into
what
that
workflow
has
looked
like
so
just
jumping
into
it.
A
little
background
on
like
why
I
care
about
navigation.
A
lot.
I've
been
a
long
time
worker
of
both
the
discussion
and
research
around
the
topic.
A
Many
people
have
asked
me
like
why
I
switched
to
foundations.
It
was
one
of
the
things
that
I
was
most
excited
to
see
the
group
become
responsible
for
when
it
became
formally
a
team,
and
so
I
joined
officially
in
1410
and,
like
I
was
saying,
I
followed
a
lot
of
discussions
and
research
before
so.
A
What
I
wanted
to
start
with
was
just
an
open
retrospective
with
a
handful
of
the
designers
that
have
worked
in
this
area,
so
I've
tagged
a
few
designers
and
post
a
few
prompts
to
them
just
to
better
understand
like
what
were
some
of
the
challenges
that
they
were
facing
to
inform
things
that
I
would
probably
encounter
myself.
A
A
This
is
how
it
feels
to
think
about
navigation
problems.
Everything
is
connected
and
you
feel
like
you're,
losing
your
mind
when
you're
trying
to
account
for
all
of
those
things
so
getting
to
hear
from
all
their
different
perspectives
and
their
passions
really
got
me
energized
going
into
the
team,
and
so,
if
you
look
at
it,
if
you
consider
how
many
issues
we
have
opened
today,
there
are
currently
I'm
just
going
off
labels
here,
which
aren't
perfect,
but
there's
about
200
plus
issues
around
navigation.
A
Specifically,
if
we
cut
out
settings
and
just
focus
on
nav
items,
so
then
it
becomes
like
where
the
heck
do.
We
start
as
a
team
there's
so
much
history
here.
The
way
I've
described
this
to
a
few
is
it
feels
like
I
moved
into
a
house
like
a
fraternity
house
where
so
many
people
have
lived
before
things
are
in
a
little
bit
of
a
disarray.
There
are
some
really
great
ideas.
There
are
some
really
old,
lingering
ideas.
A
Many
are
conflicting
with
each
other,
and
so
what
that
has
looked
like
is
some
manual
triage
by
both
me
and
my
product
manager.
Each
milestone
just
kind
of
whittling
away,
trying
to
service
what's
been
relevant.
There
have
been
some
good
epics
created
from
past
product
managers
that
helped
highlight
some
key
themes,
some
areas
that
we
consider,
but
that
was
just
you
know
like
the
tip
of
the
iceberg.
We
can
only
see
you
know.
What's
on
the
surface
there
so,
like
I
was
saying,
I've
spent
a
lot
of
my
time
just
reading
previous
issues.
A
Threads
research
cat
had
done
a
ton
of
ux
research
last
year
in
terms
of
looking
at
the
information
architecture
of
the
pages
and
as
a
result,
there
was
a
lot
of
work
that
had
been
done
for
navigation.
Just
looking
back
to
those
past
decisions
was
really
helpful
for
me
just
catching
up
to
where
things
were,
it's
both
like
the
benefit
and
drawback
to
having
so
much
of
our
work
done
in
gitlab,
I
feel
like
I
could
never
actually
reach
the
end
of
all
the
content.
That's
there.
A
So
I
do
try
and
also
lean
on
those
people
that
are
still
around
that.
I
can
ask
more
questions
to
so
what
I've
learned
is.
You
know
there
are
some
great
designers,
as
well
as
product
managers,
engineers
that
have
all
worked
on
these
problems
at
some
point
and
if
I'm
having
a
thought,
it's
likely
that
one
of
them
have
also
had
that
thought.
A
So
there's
sometimes
a
lot
of
negativity
talked
about
navigation,
but
I
also
want
to
highlight
what
I
think
is
great,
so
just
comparing
to
some
of
the
like
neil's
norman
principles,
around
navigation,
some
things
that
stand
out
to
me
that
I
think
are
really
good.
Specifically,
I
think
the
scaffolding
that
we
use
to
architect
the
way
that
users
orient
themselves
in
our
product
is
good,
our
global
navigation.
So
that's
that
top
bar
is
stable,
I'll
ignore,
like
maybe,
when
you're
signed
in
signed
up
a
little
less
stable
in
that
sense.
A
But
for
the
most
part,
that's
not
gonna.
Really
change
when
you're
signed
into
the
product,
which
is
good
users,
can
trust
that
their
options
will
be
there
as
they're
progressing
through
different
areas,
and
then
we
even
use
the
left
sidebar
to
give
them
some
more
localized
information
about
the
thing
that
they're
working
on
and
from
there
they
can
use
that
to
become
familiarized
with
the
tree.
We
do
that
by
putting
things
into
sub-menus,
allowing
them
to
thumb
through
and
find
what
they're
looking
for.
A
We
don't
duplicate
things
necessarily
so
we're
not
just
putting
everything.
That's
in
the
left
sidebar
at
the
top,
we're
not
just
duplicating
a
bunch
of
words,
it's
more
specific
to
what
gitlab
teamers
are
used
to
in
terms
of
the
scope
of
things,
but
we're
working
looking
for
better
ways
to
inform
users
with
that,
but
we
also
avoid
doing
drop
down
with
another
drop
down
with
our
drop
down
or
maybe
rather
a
list
box
with
another
list
box
with
another
list
box.
We
only
keep
it
to
one.
A
So
the
farthest
ring
goes
one
here,
you
know
appear
you
can
go
into
one
as
well
and
that
just
helps
users
progress
a
little
bit
easier
when
they're
going
through
the
product.
Also
note
that
it's
very
fast
I
mean
these
sections
in
the
left
side,
sidebar
load
fast
same
with
the
menu
same
with
the
global
search.
A
These
things
are
very
quick,
so
the
responsiveness
is
definitely
a
good
appeal,
but
where
can
we
improve
so
an
area
that
I
feel
like
is
a
theme
is
navigating
around
gitlab
can
be
hard,
and
this
is
because
we
have
a
very
rich
product
that
we
continue
to
add
and
add
and
add
to
so
the
biggest
thing
that
I'm
seeing
is
an
increase
in
cognitive
load,
a
way
that
can
help
illustrate
this
is,
if
you
were
to
just
look
at
the
number
of
pages
that
we
list
in
our
navigation.
A
I'm
going
to
pick
on
one
page
in
particular
locked
files,
it's
a
essentially
just
a
sub
view
of
the
files
that
you've
locked
in
your
repository,
but
we
make
it
discoverable
from
within
the
left.
Sidebar
we've
just
added
to
the
cognitive
load
of
users
that
they
have
to
see
just
one
more
thing,
which
could
perhaps
be
more
contextually
placed
if
you're,
considering
a
user
workflow.
A
I
understand
this
feature,
I
don't
think
it's
been
touched
in
like
five
or
six
years.
If
I
was
looking
back
at
some
of
the
commit
history,
we
just
have
to
go.
Make
the
hard
decisions
to
fight
against.
You
know
this
resistance
to
change,
going
against
the
status
quo,
making
informed
decisions.
It's
challenging.
It's
scary,
like
I
said,
like
michael's
picture
from
it's
always
sunny,
there's
so
many
different
connection
points
it's
true,
but
if
we
just
lean
into
each
one
at
a
time
take
a
step
by
step,
we
can
make
some
meaningful
progress.
A
The
way
that
I'm
trying
to
make
my
next
revisions
and
trying
to
understand
where
we
want
to
go
with
navigation,
I
took
a
little
time
to
do
a
design
exercise.
I
don't
remember
where
I
read
about
this,
but
there's
this
concept
of
writing
down
the.
If
anybody
remembers
this,
when
you
buy
like
a
video
game
like
back
in
the
90s
on
the
back
of,
it
would
be
like
this
story
about
what
would
capture
your
attention
like.
Why
should
you
buy
this
game
when
you
walk
in
the
best
buy?
A
I
was
trying
to
think
of
that
in
terms
of
our
release
post.
So
if
I
were
to
fast
forward
into
version
16,
what
would
I
want
to
see
as
like
the
headliners
for
navigation?
So
before
I'm
even
like
thinking
about
specifically
in
the
ui?
What
are
some
of
the
greater
things
that
I
think
would
be
meaningful,
and
not
all
of
these
things
we're
going
to
do,
and
they
will
probably
look
a
lot
different
as
we're
going
into
each
milestone,
trying
to
decide
what
we
want
to
do
what's
working
well.
What's
not.
A
These
are
just
a
lot
of
the
themes
that
I've
picked
up
from
previous
designers.
A
lot
of
these
aren't
even
my
own
ideas.
I
mean
a
lot
of
these
have
come
from
just
long
outstanding
issues,
pain,
points
that
we
hear
users
reaffirming
over
and
over
and
over
again,
but
we
just
have
to
lean
to
the
hard
decisions
figure
out.
A
How
do
we
make
it
work,
so
that
was
helpful
for
me
to
collect
my
thoughts
share
that
with
my
product
manager,
so
we
could
start
discussing
more
of
a
vision,
a
road
map
of
where
we
could
think
about
tackling
each
milestone,
and
so
for
this
milestone,
what
I'm
focused
on
is
the
hamburger
menu,
so
that
is
in
the
global
navigation,
where
you
have
the
amber
hamburger
icon
that
says:
menu
we're
thinking
about
just
some
different
ways
that
we
could
help
reduce
the
confusion
around
here.
A
One
of
the
key
aspects
that
we
see
users
using
is
just
navigating
to
the
groups
and
projects
from
here.
The
rest
of
the
content
sometimes
is
ignored,
but
what's
most
important
to
them
is
switching
between
groups
and
projects.
So
what
we're
going
to
be
testing
is?
How
can
we
make
revisions
to
this
without
degrading
the
experience
to
the
point
where
they
can
no
longer
find
the
groups
and
projects?
If
we
can
find
some
meaningful
choices,
then
we
can
find
a
solution
that
we
can
build,
maybe
in
fifteen
two,
maybe
in
fifteen
three.
A
A
I've
got
another
design
for
potentially
using
it
as
a
well.
I
call
it
a
drop
down,
but
given
jeremy's
presentation,
I'm
not
going
to
call
a
drop
down
anymore.
Maybe
a
disclosure
would
be
a
better
way
to
describe
this
yeah,
just
trying
to
think
through
different
ways
that
users
could
progress
through
keeping
that
contextual
information
like
where
are
they
always
knowing
where
they
are
in
the
product
and
then.
A
Lastly,
I
haven't
quite
sat
with
this
one
long
enough,
but
a
context
switcher,
we
know
from
the
past
hasn't
tested
super
well,
so
I'm
apprehensive
to
follow
with
testing
on
this
one,
but
still
thinking
through
it.
If
you'd
like
to
know
more
about
those
ideas,
I
have
a
link
in
there
as
well
for
a
youtube
video
that
I
posted.
B
C
Or
I
can
do
that,
I
was
trying
to
figure
out
how
to
phrase
it,
but
I
just
really
appreciate
the
way
that
you
broke
this
down.
I
love
the
thoughts
of
you
know
the
example
that
you
gave
of
what
would
be
on
the
back
of
that
video
game.
C
C
A
Yeah
absolutely
yeah,
it
really
did
help
me
think
through
it
as
well.
Just
have
some
space
to
write
down
my
thoughts,
kind
of
shape
them
together
and
see
how
things
may
relate
to
one
another
or
not
I'm.
I
am
also
a
very
visual
person,
so
it's
hard
sometimes
to
make
me
write
things
down
just
words
alone,
but
it
does
help
abstract
concepts
a
bit
more.
C
Since
no
one
else
is
putting
anything
in
the
agenda,
oh
and
we
have
a
little
time
I'll,
ask
you
so
this
was
great
austin
you
and
I
have
been
really
closely
connected
on
this
entire
initiative,
I'm
so
pleased
with
the
work
that
you're
doing.
I
think
you've
got
great
rationale
for
starting
with
that
top
hamburger
menu.
That
makes
a
ton
of
sense.
Could
you
briefly
talk
about
you?
You
touched
on
the
left
nav.
We
know
the
left.
Nav
needs
changes.
We
also
know
that
the
left
nav
is
associated
with
that
top
navigation.
C
A
A
We
could
do
better
to
think
more
critically
about
what
we'd
choose
to
put
in
that
left.
Sidebar.
That's
one
way
that
we
could
reduce
the
number
of
items,
just
the
sheer
volume
of
them,
but
we
have
some
other
hypotheses
like
we
would
love
to
go
test
further,
like
reducing
the
number
of
parent
items
just
to
help
aggregate
together
things,
users
care
about,
I'm
interested
in
looking
at
even
making
that
list
smaller
based
off
of
some
of
the
usage
data
that
we're
seeing.
A
C
Yeah,
that's
great
for
anyone
who
doesn't
know
there's
a
lot
of
navigation
research
happening
right
now.
That'll
help
give
better
information
about
that
left.
Sidebar
in
the
way
that
I
understand
it,
austin
is
so
you're,
starting
with
this
top
hamburger
menu
you're.
C
Getting
this
into
validation,
you're,
going
to
come
away
from
that
with
a
direction
one
direction
you're
going
to
converge,
then
you're
gonna
start
looking
at
that
left,
nav
you're
gonna
have
multiple
options:
you're
gonna
diverge
there
you're
gonna
run
that
through
validation,
you're
gonna,
converge,
you're,
gonna,
think
about
those
two
things
together
and
we're
gonna
go
from
there.
So
implementation
will
happen
reasonably
quickly
after
that,
as
soon
as
we
start
to
feel
confident
that
we
understand
those
structures
need
to
be.
Did
I
get
that
right.
A
Yeah,
that's
true.
I
wouldn't
necessarily
like
definitively
say
like
yeah
like
the
left.
Sidebar
is
the
next
thing
on
the
docket.
I
think
we're
still
trying
to
figure
that
out
from
like
a
prioritization
matrix,
but
yes
we're
just
trying
to
find
ways
that
we
can
also
help
remove
some
content,
because
it
can
give
us
options
to
bring
in
more
useful
features
that
we
just
basically
don't
have
space
for
right
now,
like
I
would
say,
an
area
that
we
do
a
okay
job
at
is
helping
users
pick
up
where
they
left
off.
A
I
mean
the
thing
that
I
see
like
software
engineers
using
the
most
is
the
alert
they
get
to
create
a
merge
request
after
they
push
a
branch,
helping
users
pick
up
work
when
they
come
from
some
other
place,
I
think
is
really
important
and
something
I
personally
lose
context
of.
All
time
is
when
I
am
like
drafting
a
comment-
and
I
close
my
tab-
I
don't
know
if
I
ever
sent
that
one,
and
sometimes
I
find
that
I
didn't
so
being
able
to
help
users
jump
back
into
that
workflow.
A
D
B
B
Yeah
yeah,
I
can
vocalize,
so
I
appreciate
all
the
work
austin
that
you're
doing
in
this
space.
You
know
I'm
personally
excited
to
see
what
comes
out
of
the
work
that
you
talked
about
in
regards
to
the
hamburger
menu
for
15.1.
B
I've
been
doing
some
research
for
the
global
search
team
and
have
seen
you
know
firsthand
how
users
have
difficulty
knowing
when
to
use
that
hamburger
menu
versus
global
search
header,
it
seems
like
the
hamburger
menu,
is
a
little
bit
more
approachable
just
because
you
can
know
exactly
what
you're
searching
for
in
regards
to
either
a
group
or
a
project
while
global
search
is
a
little
bit,
maybe
too
broad
for
some
people.
So
I'm
glad
that
the
designs
that
you're
proposing
are
trying
to
tackle
that
problem
a
little
bit.
A
Yeah,
it's
it's
funny.
You
mentioned
that
will
I've
seen
firsthand
like
users
say
I
wish
I
could
search
for
projects
and
groups
in
the
same
place.
I'm
like
you
can,
but
I
do
think
this.
This
menu
item
has
a
strong
gravitational
pull,
and
so
then
they
feel
that
things
are.
A
B
D
Of
course,
I'm
right
at
the
very
end,
I'll
just
squeeze
in
my
two
comments.
They
date
me
as
a
designer,
but
I
love
the
thinking
here.
I
think
valerie
was
kind
of
pointed
out,
the
the
sort
of
back
of
the
the
game,
cartridge
sort
of
sale
thing,
but
I
was
thinking
like
the
the
press
release
like
thinking
of
it
in
the
future
like
when
we
announce
this.
D
What's
it
gonna
look
like
and
that
will
help
sort
of
drive
our
our
longer
term
vision,
that's
a
theme,
a
sort
of
a
trend
that
we
did
at
my
last
job
as
well
as
when
you
were
talking
about
just
the
like.
We
brought
up
the
picture
down
there
at
the
bottom
of
the
thumbnail,
where
nothing
is,
is
contextual.
D
We
just
sort
of
unload
everything
to
the
user
and
sort
of
how
we
could
sort
of
make
it
contextual,
and
even
though
those
are
really
tiny,
itty-bitty
little
things,
the
more
we
do
it
and
the
more
we
push
it
throughout
global.
It's
going
to
make
a
huge
impact
on
cognitive
loads
for
the
user.
It
reminded
me
of
the
first
time
I
heard
of
minified
css.
I
was
like
there's
no
way
getting
rid
of
spaces
and
stuff
is
going
to
do
anything
and
then
sure
enough.
D
I
think
it
was
facebook
in
particular
minifying
their
css
like
improved
their
performance
by
like
40.
It
was
insane.
So
it
sort
of
reminded
me
of
those
two
things
and
I
made
it.
B
Awesome
with
that,
thank
you
so
much
awesome.
This
is
a
great
presentation
appreciate
you
running
through
all
that.