►
Description
Katherine provides context to Michael on existing research around navigation and settings. Highlights gaps between current product and existing research.
A
A
So
here
is
where
I
try
to
gather
context,
and
you
can
see
a
little
bit
of
this
in
that
article.
I
sent
you,
but
so
basically,
if
you
look
at
original-
and
this
is
as
original
as
it
gets,
because
I
can't
keep
track
of
all
the
versions
like
as
accurate,
but
this
is
somewhere
before
2016
from
my
knowledge,
so
it's
pretty
close
to
the
original
structure
and
if
you
look
at
it,
basically
it
was
kind
of
flipped.
A
A
A
B
B
A
A
A
So
the
problem
with
this
is
that
this
is
where
we
left
off
before
we
have
reached
that
20
20
like
level
so
basically
it
it
doesn't
fully
it
kind
of
applies,
but
it
doesn't
fully
apply
we're
in
this
awkward
situation,
where
we're
probably
going
to
need
to
just
do
another
round
of
research
on
this
structure,
because
it's
kind
of
like
doubled
in
size
and
there's
a
difference
in
like
the
cognitive
load.
You
know
of
searching
for
something
in
this
menu
versus.
A
A
Yeah,
I
know
it's
it's
it's
pretty
crazy.
How
much
has
changed
since
then
and
in
that
study
that
we
did,
we
were
able
to
do.
We
did
a
project
and
group
level
like
thing
together,
but
if
you
go
to
what
we'd
be
testing
in
2020,
I
did
like
a
new
and
removed,
so
you
can
see
what's
different
about
the
structure.
A
A
B
A
And
and
for
example,
some
things
might
still
apply
like
one
of
the
recommendations
from
back
then,
was
to
add
a
planning
category
at
the
group
level,
and
we
might
still
need
a
planning
category.
But,
for
example,
statistics
might
not
be
relevant
anymore
because
we
have
a
whole
analytics
section
that
has
kind
of
grabbed
some
of
the
things
that
were
supposed
to
be
under
statistics.
B
A
We
kind
of
have
to
tease
this
apart
a
little
bit
more
before
making
improvements
to
the
left.
Sidebar,
that's
one
thing
I'll
pause
here
hopefully
is
this:
is
this
useful
information?
Is
this
in
this
yeah,
so
in
the
in
the
sus?
I
love
that
little
thing.
It
always
interrupts
you
and
you
like.
I
get
why
it
does
it,
but
you
can't
just
smoothly.
A
A
A
B
B
A
B
A
Smaller,
but
it
still,
it
has
more
items
than
before.
So
that's
the
main,
the
main
thing,
but
that's
something
we
want
to
work
out
as
well,
is
having
better
differentiation
between
those
two
levels
and
so
basically
back
to
that
customization
problem.
We
actually
have
a
setting
in
settings.
General
visibility,
project,
features
and
permissions
where
you
can
disable
certain
items
from
this
left
sidebar.
A
So
that's
one
problem,
that's
described
in
this
issue,
but
another
problem
is
that
this
list
of
features
is
not
fully
updated
and
from
what
my
sleuthing
has
shown
me
is
that
I
think
this
stops
being
updated
around,
perhaps
like
2018
or
something
because
it
kind
of
correlates
to
that.
You
can't
really.
You
can't
turn
off
security
operations
and,
like
certain
like
analytics
certain
new
things
that
were
added.
B
A
A
B
A
A
B
A
A
B
A
A
So
that's
another
another
challenge
that
we
want
to
figure
out
as
well
this
how
to
better,
I
guess
utilize,
the
space
here
and
it's
like
is
it?
Is
it
supposed
to
be
something
someone
can
pin
to
make
it
more
relevant
to
their
needs?
Or
is
it
just
global
what's
going
on
up
here?
Basically,
because
these
are
like
very
user-centric,
and
these
are
kind
of
like
anybody.
A
A
Me
navigating
throughout
gitlab
to
show
you
our
navigation
is
an
interesting
concept
and
then
wayfinding.
So
then
our
next
thing
is
kind
of
around
all
right.
So
how
do
I
know
where
I
am
in
gitlab
and
how
do
I
know
how
to
get
back
to
things,
because
another
thing
that
comes
up
often
is
I
lose
everything
if
I
don't
bookmark
it
in
my
browser,
or
I
have
to
use,
rely
on
the
browser
navigation
to
kind
of
get.
A
So
this
is
another
topic
that
I
guess
is
under
here.
I'm
not
sure
that
these
are
the
right
steps
per
se,
but,
for
example,
when
you've
just
gone
to
somewhere
frequently
visited
is
not
always
the
most
reliable
like
I
haven't
clicked
on
this
one
in
a
very
long
time
and
the
ones
I
have
clicked
on,
don't
always
show
up
and
there's
like
something
with
the
local
storage
or.
A
That,
but
it's
a
similar
thing
here,
I
think
I
think,
in
the
search
you're
also
able
to
see
recent
things
now.
This
is
a
new
development,
so
that
used
to
be
a
problem,
though
it
was
like
hard
to
find
your
recent
issues
and
like
where
you
even
have
gone
throughout
gitlab,
without
relying
on
your
browser
and
like
bookmarks
or
sometimes
using
the
to-do
list
to
kind
of
store
things
and
keep
track
of
things
to
get
back
to
them.
Like
little
workarounds
like
that,.
B
A
A
A
B
A
Get
lab
and
things
like
that,
but
so
far
those
are
the
main
things.
So
I've
created
two
ux
research
ethics.
I
don't
know
how
big
they'll
get
with
the
left
side,
navigation.
What
we're!
What
we're
thinking
to
do
is
to
do
a
top
level
tree
test
for
project
and
group
level.
So
that's
just
like
findability
tasks
for
the
whole
thing.
B
A
A
B
B
A
B
A
B
A
You
didn't
know
you
see,
nobody
else
does
either
because
they're
all
they're
all
this
preferences,
one
right
here.
This
is
where
so
many
of
the
things
live.
The
themes
where
you
can
set
your
homepage
content
project
overview
content.
Things
like
that
live
under
preferences,
hidden
away
in
user
settings.
A
A
B
A
A
I
believe
there's
only
maybe
two
groups
that
have
settings
somewhere
else-
or
maybe
three
like
I
think
geo-
might
have
settings
like
on
a
page
somewhere
and
I
think
configure
and
security
are
potentially
considering
like
having
settings
somewhere
on
the
dashboard
or
something
like
that.
But
for
the
most
part
they
live
in
here,
but
we're
also
considering
where
they
actually
should
be
placed
like.
A
B
There's
not
a
bad
way
to
kind
of
approach
this
and
like
even
the
way
you
were
describing
some
of
this
stuff,
for
example
like
delegating
certain
card
sorts
to
certain
groups,
because
it's
more
specific
to
them
and
their
users,
so
you
know
pushing
that
off
and
then
kind
of
having
the
rough
areas
for
them.
So
it's
not
a
bad
way
to
kind
of
think
about
this
yeah.