►
Description
This is a brief research readout to share what we learned about how Parkers navigate within GitLab and why.
A
A
This
particular
research
project
focuses
primarily
on
one
thing:
learning
how
parkers
navigate
within
gitlab.
A
A
I
want
to
briefly
talk
a
little
bit
about
how
the
research
project
was
structured,
because,
I
think
that's
important
to
know
there
were
three
components.
The
first
was
a
set
of
interviews
to
really
learn
more
about
our
participants,
how
they
use
git
lab,
why
their
top
three
tasks.
Things
like
that.
A
Okay
I'll,
be
skipping
several
slides
just
to
try
to
keep
this
short
so
jumping
in
to
the
top
takeaway.
So
we
learned
that
parkers,
first
and
foremost,
they
really
need
to
know
what's
going
on
within
the
projects
that
they
are
responsible
for
sometimes
that
means
that
they
have
to
go
across
multiple
projects
because
they're
responsible
for
more
than
one.
A
So
keep
that
in
mind.
The
second
big
thing
was
getting
to
their
projects,
obviously,
is
a
critical
first
step,
the
way
they
do
this,
they
have
browser
bookmarks
that
they
save
and
they
can
jump
that
way.
Another
way,
some
of
them
use
the
gitlab
company
home
page
and
they
can
search
or
scroll
down
and
click
on
the
project
that
they
need
to
jump
to
from
that
list.
A
A
third
way
was
using
the
top
menu
in
the
top
left.
Some
people
use
that,
so
we
learned
how
they
get
to
those
projects
once
they're
in
a
project
they
navigate
to
issues
to
milestones
and
to
boards
and
the
main
reason.
Why
is
because
that's
where
the
information
is
that
they
need
and
I'll
talk
a
little
bit
about
what
that
is,
so
the
primary
tasks
for
parker
they
were,
they
kind
of
fell
into
these
three
buckets.
A
A
A
A
A
A
A
So
what
are
the
workflows
on
how
they
get
how
they
do
those
things
they
were
pretty
similar,
but
the
starting
points
vary
a
little
bit,
so
a
high-level
workflow
this
table
summarizes
it
very
clearly
getting
to
a
project.
The
starting
points
were
bookmarking.
Like
I
mentioned
earlier,
the
company
get
lab
home
page
and
that
top
menu-
some
of
these
were
efficient.
A
Some
were
convenient
and
the
next
high-level
workflow
viewing
boards
or
milestones
starting
points
same
as
above,
but
this
could
be
improved
a
little
bit
because
the
way
they
have
to
do
this
is
navigate
to
another
project
via
those
other
ways
that
are
listed
above
think
about
parker,
if
they're
responsible
for
two
or
more
projects-
and
they
need
to
see
what's
going
on-
certainly
boards
and
milestones,
and
even
some
issues
they
need
to
back
out
and
go
back
in
so
that
could
be
improved
getting
to
an
issue.
A
They
use
links
from
email
alerts,
links
from
other
applications
like
jira,
etc.
So
those
are
viewed
as
efficient,
because
it's
essentially
one
link
you're
right
where
you
need
to
be
the
workflows
for
parker,
is
fairly
interesting,
because
they're
quick
to
complete
they're
shallow
one
to
three
clicks
and
they're.
There
they're
also
very
well
established
so
their
pathways,
they
felt
were
fairly
efficient
thanks
to
bookmarking
and
they're
really
and
those
links
that
they
get
from
email
alerts
like
take
them
right
there.
So
they
were
pretty
satisfied
in
that
regard.
A
I'm
going
to
jump
to
this
mural.
I
recommend
anyone
who's
watching
this
to
look
at
this
mural
in
mural.
There's
a
link
here.
This
really
documents
it
all
so
there's.
This
is
almost
like
a
visual
heat
map
where
you
can
see
how
they're
coming
in
they're
clicking
on
issues
they're
going
in
there
they're
going
in
boards
and
milestones
and
a
few
other
spots
too.
So
this
checks
out
completely
with
what
they
were
telling
me
earlier
in
their
interviews.
A
This
is
where
exactly
where
they're
clicking
and
also
just
as
importantly,
it
also
gives
us
some
indication
on
where
they're
not
clicking
too
so
something
to
consider
so
pain
points.
What
navigating
there
were
some
pain
points,
but
there
weren't
really
major
ones
experienced
with
their
top
workflows
because
they
were
fairly
established
already,
but
to
talk
about
some
pain
points
that
were
experienced
outside
of
those
there's
a
lack
of
personalized
view.
A
So
that's
probably
the
biggest
one
imagine
having
to
navigate
in
and
out
of
projects,
and
you
need
to
go
to
places
to
see
what
you
care
about
and
they
all
happen
to
kind
of
be
the
same
thing
which
might
be
a
board
or
an
issue,
but
in
different
projects.
It's
a
lot
of
jumping
around.
So
what
this
is
is
essentially
a
desire
to
create
a
customizable
place
to
put
the
things
that
they
care
about
in
one
area,
so
they
don't
have
to
go
in
and
out
of
other
projects.
A
A
few
other
things
that
were
called
out
as
pain
points
hard
to
learn.
So
that's
not
necessarily
gitlab
as
a
tool,
but
the
navigation
as
well,
because
some
of
those
things
are
just
hard
to
understand
suggestion
there
was
providing
learning
material
catered
to
parker's.
A
Another
is
search
the
works
as
designed,
but
still
too
many
results,
some
weren't
that
relevant
either.
So
the
current
work
around
with
that
is
that
people
may
avoid
using
it.
That's
what
we
saw
here
a
little
bit.
A
There
is
a
recommendation
to
just
align,
search
behavior
to
mental
models,
also
there's
something
about
nomenclature
which
is
very
relevant
to
the
left
nav.
So
the
naming
of
elements
wasn't
clear
or
intuitive
for
some
of
these
partners
so
again,
something
to
consider
as
well
lots
of
quotes
here
suggestions.
So
this
was
a
great
conversation
across
all
participants
and
definitely
saw
some
themes
here
and
it's
really.
These
two
big
themes
came
up
a
lot.
A
A
The
thinking
here
was
to
allow
some
type
of
customization
that
could
be
done
several
ways.
One
way
might
be
allowing
the
the
user
to
pick
and
choose
what
they
want.
Another
might
be
as
you're
creating
your
gitlab
account.
You
want
to
select
from
a
number
of
profiles,
one
of
which
might
be
product
manager
and
by
default
you're,
given
fewer
left-hand
navigation
elements
to
choose
from
another
might
be
just
clumping
them
together
in
groups
where
we're
kind
of
helping
them
out
a
little
bit.
A
A
So
next
steps,
obviously
there's
this-
will
be
fed
into
some
of
the
design
work,
that's
currently
being
worked
on
by
the
foundations
team.
So,
lastly,
there's
an
appendix
that
goes
into
more
detail
around
who
some
of
these
participants
are,
and
also
lots
of
links
to
the
resources,
including
that
mural
mapping
overlay
so
strongly
suggest.