►
From YouTube: PI Think Big May 2022
Description
Problem to solve: Existing events instrumentation are not easily discoverable.
JTBD: "As a product manager and engineer, I need to identify existing metrics instrumentation so I do not waste time reinstrumenting metrics which already exist.
Issue: https://gitlab.com/gitlab-org/gitlab/-/issues/363417
Epic which explains the process further and to see past examples: https://gitlab.com/groups/gitlab-org/-/epics/7823
A
Hey
team,
I'm
amanda
morita
and
I'm
the
product
manager
for
product
intelligence.
I
want
to
walk
you
through
what
you
can
expect
for
the
may
2022
think
big
session.
So
let's
go
ahead
and
dive
in.
I
didn't
create
a
slide
deck
this
time,
because
those
are
boring.
So,
let's
just
like
walk
through
some
live
materials
here,
so
we
have
an
issue
created
for
the
think
big
session
for
this
month.
The
problem
that
we
are
trying
to
solve
is
existing
events.
A
Instrumentation
are
not
easily
discoverable
and
the
jobs
to
be
done
kind
of
expanding
on
this.
This
problem
is
as
a
product
manager
or
an
engineer.
I
need
to
identify
existing
metrics
instrumentation,
so
I
do
not
waste
time
reinstrumenting
metrics,
which
already
exists
okay,
so
this
might
sound
familiar
to
you.
If
you
watch
the
customer
interview,
video
or
read
any
of
the
materials
that
came
out
of
the
customer
interviews,
because
this
was,
I
think,
maybe
the
number
three
problems
are
solved
as
scoped
by
the
rice
core.
A
A
What
we
end
up
coming
up
with
might
also
work
first
for
service
being,
but
let's
just
focus
on
snowplow
for
now.
Okay,
so
I'd
like
to
walk
you
through
a
use
case,
so
consider
this
example
and
I'll
just
pull
this
up
for
you
here.
It
is
where
a
product
leader
six
months
ago,
this
was
mid-november,
created
a
an
issue
for
her
dev
team,
because
she
wanted
to
know
how
many
custom
value
streams
were
created
when
she
created
the
issue.
She
tagged
her
engineering
manager
and
said
she
needed
some
help.
A
The
product
manager
came
back
and
said
that
looks
good,
and
so
the
engineering
manager
created
another
issue
to
for
that
actual
work,
and
then,
a
month
later,
in
discussions
in
slack,
coincidentally
with
me,
or
we
discovered
that
this
metric
was
already
instrumental,
and
so
the
engineering
manager
was
able
to
close
that
instrumentation
issue
and
the
rest
of
this
issue.
They
just
went
into
sci-sense
to
create
a
dashboard,
and
so
this
is
a
very
small
example
and
really
what
was
what
was
expended
here.
A
A
B
Discoverable
to
your
events,
now
we
have
these
nice
metrics
dictionary
but
in
short,
it's
very
difficult
for
a
pm
to
say:
hey,
I
have
a
new
event
or
shall
I
go
and
get
it
here
on
the
metrics
list
or
size
sense
how
to
make
sense
of
all
that
now
I
have
a
question.
That's
also
a
challenge.
I'd
be.
I
think
the
answer
is
not
easy.
So
how
can
you
know
that
your
what
you
are
looking
for
is
already
instrumented
or
can
be
derived
from
or
available
data.
A
Okay,
thank
you
albert
all,
right,
so
that
kind
of
with
the
example,
as
well
as
el
elper's
summarization
of
the
problem
that
pretty
much
drives
it
home.
But
I
want
to
do
one
last
thing
and
that
is
I
want
to
put
on
my
my
product
hat
and
walk
through
the
problem
live
okay.
So
let's
say
that
I
am
the
product
manager
for
epic
boards.
A
Okay,
the
the
team
that
owns
epic
fort
and
let's
say
I
want
to
know
how
many
times
people
change
the
show
labels
control
here
and
what
are
they
doing
before
and
after
that
right.
So
let's
say
I
already
do
know
about
the
metrics
dictionary,
because
I
think
that
that's
the
first
step
of
the
problem.
But
let's
say
I
know
about.
A
I
know
that
I
need
to
come
to
snowplow
because
I'm
talking
about
events
and
let's
say
well,
I'm
just
gonna
search
to
see
if
it's
been
instrumented
because
I'm
brand
new
today's
day-
one.
I
don't
know
what
this
team
has
done
before.
So
if
I
come
here-
and
I
say
epics
because
I'm
at
an
epic
board,
only
one
value
comes
up
with
epics
and
it
is
click
load,
more
epics.
But
that's
not
what
I
want.
Maybe
it's
not
fun.
Okay,
let's
see
click
epics
board,
switcher.
Okay,
that's
weird!
Okay!
A
A
Click
edit
drag
issue
toggle
labels
on
board.
I
think
that
that's
the
one
that
I
was
looking
for
right.
So,
let's
take
a
look
again
show
labels.
Well,
that
might
be
it.
Toggle
labels
show
labels
on
off.
So
I
might
make
an
assumption
that
it
already
exists
based
on
this,
but
it's
not
a
direct
match,
because
this
says
show
labels
and
the
value
on
the
ui
is
oh,
it
is
shown
it's
perfect.
I
thought
it
was
something
else.
A
Okay,
so
now
I
think
that
this
is
it,
but
what
if
I
didn't
get
the
idea
to
search
blackboard
or
what,
if
the
value
that
I
used
was
so
big
returned,
so
many
results
like
create,
for
example,
shows
29
results.
Am
I
really
going
to
toggle
through
all
of
those,
so
discoverability
is
tricky
because
you
have
to
know
the
terminology.
That's
been
used
for
the
dictionary
or
you
have
to
go
to
a
developer,
to
ask
them
to
look
in
the
code
to
see
if
it's
already
been
instrumented
and
do
developers
struggle
with
this.
A
I'm
not
sure.
So
that
is
just
an
illustration
of
the
problem
that
we
are
trying
to
solve.
Now.
The
opportunities
that
we
brainstorm
don't
have
to
be
technical
opportunities,
they
can
be
enablement
opportunities,
but
I
would
love
to
see
ways
that
we
can
make
this
make
this
information
more
discoverable
for
all
personas
that
might
care
about.
So
next
steps,
please,
if
you
plan
on
not
attending
the
session,
but
you
want
to
contribute.
Please
go
ahead
and
add
comments
to
this
async
ideas
thread
in
the
think.
A
If
you
plan
on
attending
the
session,
you
can
also
collaborate
ahead
of
time
just
to
get
some
ideas
out.
If
you
don't
have
time
to
collaborate
before
the
session
and
you're
not
attending,
don't
worry
we're
going
to
have
this
feedback
and
ac
collaboration
thread
open
for
a
week
after
the
session
as
well.
So
you
can
always
collaborate
in
that
way.