►
From YouTube: Growing Analytics Usage, Part 1
A
A
Our
customers
care
a
great
deal
about
analytics,
and
that
was
really
evident
and
an
exercise
that
we
did
at
a
customer
advisory
board.
Meeting
back
in
november
of
2019.,
we
had
17
different
enterprise
customers
represented,
and
we
conducted
a
little
exercise
where
each
was
given
a
fictional
hundred
dollars
to
spend
across
19
different
product
areas
of
investment.
A
A
A
Merge
requests
are
the
single
most
used
feature
across
of
the
sessions
that
we
counted.
Signing
in
was
only
second
place
to
that
with
issues
coming
in.
Third,
if
we
come
down
here
to
the
left-hand
side,
we'll
see
analytics
and
analytics
kind
of
got
an
unfair
bump
to
our
advantage
here
and
that,
while
all
of
these
other
categories,
oops
was
counting
a
single
url
or
page,
we
combined
nine
different
features
into
our
one
bar
and
got
to
11
000
sessions.
So
where
should
we
be?
A
A
I
would
like
to
see
that
be
where
boards
is
perhaps
even
a
little
better
than
that
as
adoption
of
issues
grows,
so
we
won't
use
this
as
a
benchmark.
We've
got
another
instrumentation
thanks
to
magda,
that's
about
ready
to
show
up,
but
I
just
wanted
to
give
you
an
idea
of
what
a
big
hill
we
have
to
climb
here,
we're
not
talking
about
trying
to
improve
by
five
or
ten
percent,
but
by
three
four
five
x.
A
What
we're
doing
today
over
the
next
18
months
or
so,
and
so
how
do
we
do
that?
Well,
in
my
conversations
with
customers
with
sellers
with
internal
users,
and
so
on,
one
thing
that
stands
out
pretty
clearly
to
me
is
that
the
user
journey
is
a
problem.
Customers
find
it
difficult
to
find
and
consume
analytics
features
that
might
be
counter-intuitive.
A
A
So
I
was
talking
to
an
internal
user
who's
very
motivated
to
use
git
lab
wherever
possible,
and
this
person's
whole
job
is
about
getting
building.
Metrics
from
get
lab
data-
and
I
asked
about
what
sorts
of
metrics
this
person
needed
and
used
on
a
regular
basis,
and
many
of
them
were
metrics
that
we
have
features
for
and
so
on.
Then
I
asked
about
usage
of
gitlab's
features
and
the
person
was
familiar
with
the
analytic
sidebar
and
the
features
that
were
there.
A
But
when
asked
about
actually
using
those
capabilities,
they
said
you
know,
I
just
find
it
very
hard
to
match
the
problem.
I
have
to
the
right
tool
and
analytics
to
solve
that
problem,
and
I've
spent
some
time
playing
with
it,
and
I
can't
seem
to
figure
it
out
and
of
course
this
is
a
user
whose
motivated
who's.
A
You
know
their
whole
job
function
is
related
to
this
and
who
has
great
access
to
people
who
can
help
them.
So
if
an
internal
user
is
struggling
like
that,
what's
actually
happening
in
the
field.
Well,
I
think
our
numbers
tell
us
about
that,
and
I
have
similar
kinds
of
feedback
that
we're
getting
from
sellers
at
the
same
time.
A
A
A
A
We
looked
at
that
other
chart,
there's
some
obvious
places
and
we
need
to
sprinkle
in
analytics
that
are
truly
useful
and
interesting
to
customers
and
make
those
a
natural
part
of
their
existing
workflows
and
and
then,
when
they
click
into
that
particular
metric
and
and
want
to
learn
more,
we
have
to
bring
them
to
a
very
targeted
data
exploration
experience
that
solves
that
particular
problem.
That
answers
that
question
and
that's
really
what
our
report
pages
journey
is
about.
A
Remixable
kind
of
solution-
that's
more
flexible
and
our
competitors
have
this.
It's
table
stakes,
customers
expect
it.
We
don't
have
to
be
the
best
in
the
market,
but
we
do
have
to
meet
that
need
number
four
is
about
making
sure
that
when
we
invest
on
the
really
important
things,
the
things
that
make
gitlab
special
and
sets
us
apart,
things
that
isn't
just
a
commodity
experience,
but
but
one
that
we're
really
investing
and
delighting
customers.
A
We
want
to
make
sure
that
we're
focusing
that
energy
on
things
that
generate
daily
or
weekly
use
and
one
particular
trap-
that's
easy
to
fall
into
is
for
us
to
spend
too
much
time
satisfying
the
needs
of
the
people
that
we
have
best
access
to
and
like
any
enterprise
tool.
That's
usually
the
sponsor
or
administrator
of
the
tool
that
those
are
the
people
that
come
to
our
cab
meetings,
they're,
really
special
important
people,
because
their
whole
job
is
about
making
gitlab
successful
in
their
organization.
A
We
want
them
to
be
successful
and
there
are
tools
that
they
need
in
order
to
justify
further
expansion.
We
want
to
give
them
so
we
do
need
to
meet
those
needs,
but
we
have
to
be
and
they
can
have
a
big
impact,
but
they
won't
have
impact
on
usage,
because
there
are
small
numbers
of
users
and
very
occasional
use.
A
So
we
have
to
be
careful
when
we're
picking
what
work
to
do
we're,
picking
things
that
have
broad
user
base
at
a
broad
user
base
and
and
is
something
that's
likely
to
be
used
on
a
very
regular
basis.
That's
what
will
move
those
numbers
and
then,
in
order
to
take
us
where
we
want
to
go
with
value
stream
and
agile
planning
and
so
on.
There
are
data
structures
and
apis
that
we
need
in
the
product
that
we
don't
have
today.