►
From YouTube: Reasons for Cross Stage Adoption
A
Hi,
my
name
is
jackie
porter
and
I
am
a
group
manager
over
in
the
verify
stage.
I'm
heading
up
a
cross
stage,
research
program
where
we
research
how
users
are
flowing
through
our
get
lab
adoption
and
utilizing
multiple
stages
in
q2
we
took
on
a
research
project
for
what
makes
organizations
more
likely
to
use
more
stages.
A
In
this
question,
we
were
able
to
introspect
on
organizations
that
were
considered
highly
adopted
or
utilizing
three
or
more
stages
at
large
organizations.
We
learned
that
there
were
about
four
underlying
reasons
for
this
and
out
of
this
research,
we
identified
a
few
recommendations
to
improve
the
adoption
journey
for
all
of
our
users.
A
In
the
interviews
we
interviewed
about
10
candidates
across
several
different
organizations
in
four
main
verticals,
including
manufacturing,
medical
telecom
and
technology.
The
company's
sizes
ranged
up
to
over
a
hundred
thousand
employees,
and
we
also
had
a
great
spread
in
personas,
mostly
concentrated
in
devon
and
sasha
the
engineering
space,
but
we
also
had
several
leaders,
including
application
directors
and
team
leads.
A
A
A
The
second
reason
that
we
found
was
that
the
same
8
out
of
10
teams
ended
up
building
tailored
documentation
that
connected
git
lab
documentation
to
business
documentation,
so
they
had
an
internet
that
had
this
is
the
business
value
and
the
roi
that
we're
getting
from
using
git
lab
and
had
an
immense
amount
of
content
that
was
built
just
around
how
to
use
gitlab.
Some
of
these
documentations
included
video
content
or
tailored
tutorials
on
how
to
use
git
lab
based
on
how
they
configured
the
document
how
they
configured
the
tool.
A
The
third
reason
that
we
found
organizations
were
highly
adopted
is
that
the
participants
cited
their
leadership
chose,
get
lab
as
the
universal
tool
for
devops
technology.
So
this
was
a
top-down
business-aligned
decision
that
gitlab
was
going
to
be
their
tool
of
choice
for
end-to-end
devops
technology.
A
The
fourth
reason
is
that
there
was
a
process
or
a
change
management
way
of
evaluating
and
adopting
new
features
as
they
were
released
by
git
lab.
This
change
management
process
included
a
regular
cadence
by
which
the
adoption
team
would
review,
release,
notes
and
consume
that
information
and
then
release
that
back
out
to
the
team.
A
Another
interesting
point
is
that,
as
you
start
to
think
about
the
adoption
journey,
these
implementation
teams
are
evaluating
release,
notes
and
they're,
making
a
choice
on
whether
or
not
to
implement
a
feature
based
off
of
the
documentation
and
what
they're
reading
and
there's
instance
in
the
research
that
we
learned
that
sometimes
they
will
make
a
choice
based
off
of
if
it's
conceptually
easy
or
to
implement
one
feature
over
another.
So
tailoring
release
notes
to
the
implementation,
persona
or
team
so
that
this
is
accurately
represented.
A
So
if
it
really
is
an
easy
to
implement
feature,
make
sure
that
that's
represented
accurately,
when
we
start
to
think
about
improvements
that
we
can
make
to
the
product,
considering
the
ease
of
use
of
group
features
being
easily
accessible
down
to
the
project
level.
When
we
look
at
administrators
people
that
are
supporting
multiple
teams,
it's
very
important
that
they
have
that
fluency
again
from
grouped
project
level.
A
All
of
the
teams
that
were
using
jira,
which
was
about
eight
of
the
ten
teams
that
we
interviewed,
expressed
improving
the
jira
to
get
lab
issue
integration,
would
support
their
use
of
gitlab
better
and
then.
Lastly,
the
more
interesting
issue
that
we
that
was
brought
up
in
one
of
our
interviews
was
creating
a
sort
of
graduated
experience
for
new
users
that
they
onboard
into
git
lab.
A
So
one
of
the
team
leads
expressed
that
new
users
are
often
overwhelmed
by
the
user
interface
in
gitlab,
because
there's
so
much
to
take
on
and
to
do
in
there.
So
for
the
first
90
days
they
could
have
a
simplified
user
interface
and
then,
as
they
start
to
get
more
experience
with
gitlab
getting
new
or
more
features
in
their
journey
altogether,
issues
we
can
consider
to
to
schedule
to
help
bridge.
Some
of
these
gaps
are
from
the
q1
research.
A
We
do
have
a
follow-up
video
that
we're
going
to
be
scheduling
with
the
growth
team
to
kind
of
dive
into
some
of
the
recommendations.
A
little
bit
more
around
onboarding
so
definitely
stay
tuned
for
that
follow-up
video.
Lastly,
I'm
hoping
to
carry
on
this
research
next
quarter
as
a
part
of
the
cross
stage,
research
program.