►
From YouTube: State of the docs 2020 - GitLab UX research
Description
Deck: https://docs.google.com/presentation/d/1h-rISbpsl1D73Or6dVJm6Do7gP7oXlAdURODMQ18GLg/edit#slide=id.g97dadc2709_1_93
Join our research program! cxr.gitlab.com
A
Hi,
I'm
emily,
I'm
on
the
ux
research
team
at
kit
lab-
and
I
recently
did
some
research
on
doc
succulent.com,
which
turned
into
this
project
that
we're
calling
state
of
the
ducks
2020.
So
that's
all
I'll
be
chatting
about
today
and
I
hope
you
check
out
the
accompanying
deck.
There's
a
lot
more
information
here,
but
for
now
I'm
just
going
to
zip
through
some
context
and
the
key
takeaways
of
the
research.
A
But
when
we
started
this,
we
didn't
really
know
very
much
about
who
visits
the
doc
site
and
why
and
whether
they
find
what
they
need,
and
it's
really
important
that
we
understand
more
about
our
users
and
what
they're
looking
for
so
that
we
can
make
sure
the
docs
are
an
effective
guide
for
them
and
the
results
that
you'll
see
here
are
from
a
mixed
method.
Study
that
started
with
qualitative
interviews
of
visitors
to
the
doc
site
and
a
quantitative
survey
of
500
visitors
to
the
site
over
a
period
of
time.
This
past
august.
A
And
finally,
we
also
roped
in
the
results
some
relevant
results
from
our
quarterly
system
usability
scale
survey,
which
is
run
by
another
researcher,
on
the
team,
catherine
and
for
our
top
takeaways.
I
will
start
with
the
bad
news,
which
is
that
almost
25,
almost
a
quarter
of
visitors
to
the
doc
site,
fail
to
find
what
they're
looking
for
the
flip
side
of
that
is
that
most
people
do
find
what
they're
looking
for
and
most
of
those
96
of
those
say.
A
First
people
told
us
that
it
was
difficult
to
find
information
we
heard
over
and
over
again
in
interviews,
people
say
something
like
yeah.
I
found
what
I'm
looking
for,
but
it
took
some
doing.
I
had
to
visit
multiple
pages.
I
had
to
read
for
a
while
get
like
somewhat
far
down
a
path
before
ascertaining.
Is
this
really
what
I'm
looking
for?
Is
it
not,
and
so
one
recommendation
here
is
to
clarify
section
headings
and
organize
content
a
little
better
to
make
it
easier
to
scan.
A
Next,
the
different,
the
information
about
different
versions
of
gitlab
that
appear
sometimes
close
together
in
the
documentation,
is
confusing
for
people
in
this
example
right
up
top
there's
something
about
gitlab,
11.11
and
then
further
down.
There's
something
about
gitlab
13.4
and
later,
and
people
told
us
they
would
have
expected
to
see
the
most
recent
version
of
top,
and
especially
for
newer
users
who
we
found
are
less
likely
to
know
which
version
they're
on
it
can
be
really
difficult
to
know
which
set
of
instructions
applies
to
them.
A
A
But
what
we
found
from
speaking
to
some
of
those
users
is
that
they
were
familiar
with
doc
secondlab.com,
like
they've,
used
it
on
other
devices
or
in
other
settings,
and
so
every
time
they
clicked
on
help
or
some
docs
link
in
their
instance.
It
took
them
a
slash.
Help
and
they
were
confused
about
the
differences
that
they
noticed.
There's
some
navigation,
that's
lacking
on
slash
help.
The
content
is
slightly
different,
they're,
not
sure.
If
it's
up
to
date,
they
wondered
if
they're
missing.
A
Something
is
there
a
reason
that
this
is
here
that
I
should
be
consulting
this
this
more
often,
and
so
a
recommendation
is
to
make
docs.getlab.com
available
to
all
users,
including
those
in
offline
environments,
and,
I
believe,
the
static
site.
Editor
team
is
already
working
on
something
along
those
lines.
A
Troubleshooting
content
is
the
most
difficult
for
users
to
find.
We
came
up
with
some
categories
that
represent
kind
of
the
main
reasons.
Why
that
we
thought
people
would
visit
the
docs,
and
you
can
see
these
on
this
slide
and
the
success
rate
for
people
finding
what
they
needed,
who
were
looking
for.
Troubleshooting
content
was
by
far
the
lowest
of
all
the
categories,
so
a
recommendation
is
to
make
troubleshooting
content
easier,
to
find
and
to
visually
distinguish
it
from
the
surrounding
content.
A
And
finally,
users
want
more
contextual.
Why
information
they
need
a
little
bit
of
help,
sometimes
understanding
why
this
set
of
instructions
or
that
set
of
instructions,
this
option
versus
that
option
would
be
best
for
them.
What
person
in
what
situations
would
choose
x
over
y?
They
want
to
limit
the
decisions
they
have
to
make
with
limited
information
before
they
invest
in
in
any
given
path.
So
I
think
in
our
docs
we
often
jump
right
into
exactly
how
to
do
how
to
set
something
up,
how
to
complete
a
process
they
want
to
hear
they
want.
A
A
A
A
lot
of
people,
70
of
people
visit
the
docs
once
a
week
or
more
so
the
docs
are
a
trustee,
companion,
they're
doing
a
lot
of
things
really
well
users,
especially
like
that
detailed
documentation
is
available
on
release
day
and
they
especially
love
the
code
samples
they
love
when
they
can
just
copy
and
paste
something,
and
it
works
of
course-
and
I
hope
you
take
a
spin
through
the
rest
of
the
deck
looking
forward
to
any
questions
that
come
up
thanks.
So
much.