►
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
Hey
y'all,
okay,
I'm
really
excited
we're
almost
there
for
our
beta
launch
of
the
new
navigation.
Oh,
my
goodness,
we've
had
a
ton
of
internal
usage
which
has
been
really
hopeful.
One
of
the
things
I
think
we
realized
is
that
we
haven't
communicated
much
about
how
we
got
to
where
we
did
with
the
information
architecture
of
the
new
navigation.
So
I
wanted
to
chat
about
that
briefly,
so
I
want
to
start
with
I
believe
this
is
all
rooted
in
user
research.
B
Yeah
a
lot
so
I'll
first
say
that
working
around
the
topic
of
navigation
is
hard
from
a
research
perspective
and
from
a
design
perspective
too.
It
is
incredibly
hard.
There's
lots
of
strong
opinions
out
there
internally
externally,
too,
there's
lots
of
personas,
so
many
different
types
of
people
use
our
product
only
certain
areas
of
it
too.
B
So
there's
a
tremendous
amount
of
information
that
researchers
need
to
really
look
at
and
we
have
Ashley
here
who
conducted
a
lot
of
that
research
and
we
went
as
far
back
I
think
started
this
effort
a
year
plus
ago
lots
of
different
studies.
So
actually,
since
you're
here,
I'd
like
to
hand
it
over
to
you
to
just
talk
us
through
what
research
was
done
with
navigation,
what
we
learned
and
yeah
take
it
away.
Please.
C
Definitely
so
yeah
thanks
for
having
me
to
kind
of
go
through
this,
but
yeah
I'd
just
like
to
start
from
kind
of
the
beginning
when
I
onboarded
early
last
year
and
everything
that's
been
done
up
to
this
point,
just
to
give
a
little
background.
So
over
time,
even
before
I
joined,
we
had
learned
from
various
sources
like
sus,
that
current
navigation
was
a
confusing
and
overwhelming
for
users
and
looking
at
previous
research
that
had
been
conducted,
a
lot
of
it
was
more
tactical
in
nature
and
really
focused
on
what
was
happening
with
less
focus
on.
C
Why
so,
for
example,
rearranging
left
sidebar
items
and
seeing
how
it
performed?
So
we
learned
what
happened
but
didn't
have
as
much
understanding
as
to
why
it
was
happening.
So
to
fill
this
knowledge
Gap,
we
developed
a
research
program
to
better
understand
our
users
more
deeply
and
their
mental
models
for
navigating
a
gitlab
and
since,
like
Adam
had
mentioned,
navigation
affects
all
get
lab
users,
but
we
can't
necessarily
study
all
personas
at
once.
C
Our
team
decided
to
focus
on
four
key
personas
for
these
research
efforts
and
up
in
hopes
to
gain
a
holistic
point
of
view
from
different
kinds
of
users.
So
the
four
we
focused
on
were
software
Engineers
product
managers,
Security
Professionals
and
operations
professionals.
So,
in
the
spring
of
last
year,
we
started
off
with
diary
studies
to
really
understand
the
primary
tasks
that
different
personas
were
doing,
how
they
were
doing
it,
how
they
navigated
to
complete
those
tasks.
What
was
working
well,
what
wasn't
working
well
and
at
a
very,
very
high
level.
C
C
So
the
study
revealed
that
enabling
some
sort
of
customization
to
the
left
sidebar
would
be
beneficial
to
make
things
that
are
important
to
them
more
easily
accessible
and
also
reduce
the
amount
of
items
in
the
left
sidebar
that
they
kind
of
have
to
sift
through,
which
is
overwhelming.
Other
things
that
would
have
been
helpful
from
their
perspective
is
easier
access
to
relevant
projects
that
don't
rely
on
time,
because
time
can
go
away
if
they
go
on
vacation
or
something
like
that.
C
So
these
insights,
along
with
other
data
sources
like
sus,
helped
inform
our
navigation
themes
that
influenced
our
North
Star
work.
So
one
of
those
seams
was
minimize
feeling
overwhelmed.
So,
based
on
this
Concepts,
were
developed
and
assessed
to
see
whether
or
not
they
were
going
to
address
those
navigation
challenges.
C
So
the
team
did
a
second
round
of
testing
to
focus
on
those
to
validate
them
further
and
increase
confidence
and
decide
designed
directions.
The
current
design
ultimately
was
preferred
because
it
helped
users
navigate
between
projects
without
losing
context,
and
it
supported
both
mature
and
new
users
with
their
more
common
workflows.
C
We
also
saw
trends
of
users
creating
new
groups
for
items
that
they
didn't
feel
like
fit
into
categories
that
we
had
proposed
things
like
Wiki
and
members,
and
things
like
that.
Those
were
oftentimes
categories
that
they
created
that
they
thought
were
more
of
like
knowledge,
sharing
or
relevant
to
the
entire
team.
So
that
was
really
interesting
to
learn.
We
also
learned
that
some
things
did
align
with
user
expectations.
Things
like
product
management,
related
items,
security,
related
items,
as
opposed
to
like
the
operations
items.
That
was
less
clear.
C
We
also
learned
that
users
wanted
quick
access
to
things
that
were
relevant
more
specifically
to
their
role,
like
Ops
professionals,
wanted
more
easy
access
to
pipelines.
For
example.
These
findings
also
provided
confidence
to
things
that
we
were
already
working
on,
so
things
like
pinned
items
that
enables
customization
to
the
left
sidebar
and
for
this
whole
reclassification
effort,
the
team
did
consider
all
of
this
research
and
this
card
sort.
As
one
data
point,
we
also
looked
at
other
proposals
and
analytics
data
to
see
ultimately
where
things
should
go.
C
So
a
couple
examples
are
from
the
card
sort.
A
new
collection
was
added
for
more
generic
type
items
and
that
was
called
manage.
Some
items
that
were
thought
to
overlap
between
CI,
CD
and
operations
have
been
moved
under
CDI
CD
in
the
current
proposal,
which
is
build,
and
also
it
reinforced
other
decisions
like
keeping
analytics
items
together,
which
the
research
showed.
B
B
I
think
that
is
incredibly
important
to
call
out,
because
we
see,
through
our
other
data
sources
like
sus,
how
do
users
and
learnability
that
it's
hard
to
learn
gitlab
and
that
navigation
anything
we
can
do
there
to
help
is
going
to
be
great,
so
great
work,
everybody
David
I
think
you
probably
wanted
to
talk
a
little
bit
about
some
other
data
sources.
That
work
were
considered
too.
D
You
know
with
doing
planning
and
you're
going
to
code
you're
going
to
build
the
application
you're
going
to
secure
it
you're
going
to
deploy
it
and
operate
it.
You
want
a
moderate
production.
All
those
things
help
users
understand
how
I
get
through
my
journey
and
get
loud
and
I'll.
Tell
you
if
you
want
to
get
any
senses
to
whether
or
not
we're
touching
on
the
right
things.
People
are
copying
us
already
and
we're
only
still
in
our
beta,
so
we're
hitting
on
things
that
are
helping.
Others
see
that
they
also
have
navigation
problems.
D
I'll
I'll
end
with
this
comment.
I
know:
change
is
hard
I'm.
Also,
someone
who
sometimes
struggles
with
change
I
will
say
what
we're
really
seeing
is
the
ability
to
meet
our
users
where
they
are,
whether
they're
experts
or
whether
they're
new
to
gitlab
and
I
myself
I've
been
here
three
and
a
half
years
before
I've
used
get
live
for
several
years.
I
still
would
occasionally
not
be
able
to
find
something,
and
in
the
time
that
I've
just
been
playing
with
the
Alpha
and
the
beta
navigation
I've
been
able
to
find
things
a
lot
faster.
D
Those
are
my
customer
demos
and
just
my
day-to-day
usage
of
our
products.
So
a
big
shout
out
to
the
foundations,
team,
ux
research
team,
everyone
across
the
company
who's,
contributed
both
code
and
comments
and
I'll
say
give
the
team
Grace.
If
you
hate
something
it's
okay
to
hate,
it
just
provide
constructive
feedback.
So
we
can
try
to
address
that,
and
I
will
state
that
sometimes
and
I
I.
Don't
remember,
which
celebrity
said
this
or
a
person
said
if
it's
like
sometimes
compromise
these
everyone
loses.
D
I
kind
of
look
at
his
coverage
means
that
everyone's
going
to
win,
and
so
please
have
that
insight.
As
you
talk
with
the
team
about
it
and
kind
of
talk
about
like
what's
next
and
what
we're
going
to
be
doing,
I
want
to
head
over
to
Kristen
and
Tori
to
talk
a
little
bit
about
today
and
Beyond.
So
Kristen
you
wanna.
Take
that
away.
E
It
has
been
incredible
to
kind
of
watch.
It
go
over
the
last
nine
to
ten
months
of
all
of
this
work.
To
get
to
the
point
where
now
we
have
something
that
we're
really
proud
of,
and
it
feels
good
I
said,
I
wanted
to
also
just
touch
on
like
as
we
move
into
the
generally
available
for
all
of
our
customers.
We
do
still
want
your
feedback,
we're
going
to
be
putting
up
some
blogs
that
also
encourage
the
feedback
and
talk
about
a
lot
of
the
vision
here
and
how
we
got
to
this.
E
E
F
Of
issues
for
that
we're
working
through
for
General
availability,
a
number
of
additional
issues
for
when
we
just
turn
on
the
navigation
for
everyone
and
don't
look
back
so
we
are
keeping
in
mind
all
of
the
feedback
making
sure
we
incorporate
it.
And
then,
as
Ashley
mentioned,
we
have
the
longitudinal
study
as
well
as
additional
touch
points
throughout
time,
so
that
we
can
continue
to
iterate,
as
we
always
do
at
gitlab.