►
Description
Will Leidheiser (Senior UX Researcher) and Daniel Fosco (Senior Product Designer) review insights from recent survey on the GitLab environments page.
See issue: https://gitlab.com/gitlab-org/ux-research/-/issues/1512
A
A
A
A
A
B
Yeah
that
that
matches
our
expectations
as
to
what
we,
what
we
think
is
most
used
and
most
successed
on
the
page,
but
it
is
notable
to
see
deployment
information
and
commit
information
at
the
very
top,
because
that's
the
core
of
what
the
page
is.
But
at
the
same
time
I
don't
think
we
do
the
best
job
of
properly
conveying
information
around
the
deployment
and
around
the
commits
in
the
environments
page.
So
so
it's
it's
pointing
in
in
a
good
direction
for
us.
I
think.
A
Awesome
next
stadium,
moving
on
to
the
next
question,
this
was
something
that
we
had
talked
about
a
little
bit
offline
and
did
a
follow-up
analysis
on.
So
one
of
the
questions
that
you
had
had
was
you
know,
looking
at
those
different
types
of
things,
elements
and
actions
that
they
could
complete
and
have
have
done
on
the
environments
page
like.
Is
there
a
breakdown
or
a
difference
between
larger
and
smaller
organizations
across
those
different
actions
and
elements?
So
we
ran
that
analysis.
This
is
showing
a
good
chunk
of
that
here.
A
And
basically
the
the
orange
and
blue
bars
represent.
You
know
small
and
large
organizations
across
these
different
types
of
actions.
So
in
this
case
it's
commit
information,
in
this
case
it's
deploying
to
a
different
environment
and
so
on.
So
the
only
one
that
we
actually
observed
is
significant.
Statistical
difference
for
was
opening
a
large
environment,
so
small
organizations
according
to
the
data,
are
opening
live
environments
about
twice
as
much
as
large
organizations
and
we
kind
of
categorized
those
groupings
here.
B
B
A
A
A
The
first
one
was
around.
You
know:
what's
the
main
reason
that
you're
visiting
the
environments
page
today,
and
so
we
got
a
number
of
responses
to
that-
this
was
an
open-ended
question,
so
they
could
provide
you
know
as
little
or
as
much
information
as
they
wanted
to,
and
then
I
went
through
this
after
the
survey
data
was
collected
and
closed
and
started
grouping
that
information
together
to
identify
specific
themes.
A
So
I
think
probably
the
least
surprising
thing
is
environments
and
deployments
came
up
as
much
as
it
did.
I
think
that's
a
very
common
thing
to
talk
about
in
the
context
of
just
environments
in
general
and
then
outside
of
that
we
found
particular
types
of
actions
that
people
were
performing,
so
people
are
trying
to
check
the
status
of
that
environment,
so
they're
actively
trying
to
figure
out
what's
going
on
with
something
in
the
moment.
A
A
We
also
heard
about
help
documentation
so
wanting
to
learn.
How
do
I
do
something?
So
people
might
be
not
as
familiar
about
how
to
complete
something
in
the
context
of
the
environment,
page
or
work.
Learn
wanting
to
learn
through
some
of
the
documentation
that
either
they
or
others
have
put
into
gitlab.com.
A
A
B
A
Yeah,
so
that's
a
great
question.
I
believe
it
was
around
like
wanting
to
check
the
version
of
something
so
I've
got
the
qualtrics
data
pulled
up.
So,
let's
see
for
version,
if
we
select
that
if
I
scroll
down,
we
can
see
like
what
particular
things
were
grouped
into
version.
So
I
want
to
check
the
version
running
on
a
specific
environment
deployment
status.
Ideally
version
for
qa.
B
Yeah
that
makes
sense
yeah.
I
would
say
this
team
wouldn't
be
the
same,
but
it's
really
close
to
to
the
second
one.
I
think
the
third
one
checking
status,
but
actually
the
status
of
the
environment
being
if
there
is
an
employment
that
is
currently
being
deployed
into
that
environment,
and
when
that
deployment
is
finished,
there
is
a
certain
version
that
is
live
from
that
environment.
B
A
Yeah,
I
think
that's
a
good
point
that
you
brought
up
that
you
know
these
two
number
three
and
number
10
are
quite
related,
as
I
was
going
through.
The
data
context
and
background
information
also
kind
of
falls
into
that.
So
I
think
there's
a
lot
of
situations
where
people
are
just
looking
for,
like
very
specific
information
that
they're
trying
to
reference.
A
A
B
Now
it's
super
interesting
to
see
this.
This
result
coming
so
so
high
up.
I
think
there
are
two
big
opportunities
here
for
improving
help
and
learning
documentation.
The
first
is
empty
states
right
when
the
users
first
get
to
the
environments,
page
and
they're.
First
setting
up
how
we
can
embed
in
the
ui
the
links
to
the
documentation,
the
guidance
and
really
the
handholding
that
they
need
in
order
to
successfully
set
up
their
first
environments,
and
the
second
case
is
for
these
customers
or
customers
that
already
have
their
environment
set
up.