►
From YouTube: Op Section PI Review September - Pre-Recording
A
A
Before
we
start,
I
want
to
remind
everybody
about
the
intent
here.
We
as
a
product
team
really
want
to
focus
on
singular
product
performance
indicators,
make
sure
we're
focused
on
the
art
of
the
possible
and
what
we
can
do
next,
as
opposed
to
product
performance
indicators
that
might
be
outside
of
the
capabilities
of
our
telemetry
system.
Focus
on
business
metrics,
so
metrics
that
tie
back
to
smau
and
users.
Kind
of
userfied.
A
The
other
thing
I
want
to
remind
the
products
team
specifically
is
that
instrumentation
is
not
the
end.
We
instrument
we
hypothesize
about
the
funnel.
We
seek
to
improve
that.
We
develop
new
instrumentation
that
helps
us
understand
things
further
up.
The
funnel
and
kind
of
will
help
us
target
the
most
effective
use
of
our
r
d
investment
time
to
drive
our
metric
most
successfully.
A
So
with
that,
I
want
to
go
over
the
overview.
Real
quick.
This
new
overview
page
is
limited
to
just
the
s
mao
and
gmail
and
ops,
section
smile
for
the
ops
section
and
gives
an
overview
of
the
health
as
well
as
the
kind
of
instrumentation
or
pi
workflow
status.
We
have
two
primary
groups
in
instrument
or
three
groups
in
still
instrumenting
verify.
Testing
package
is
instrumenting,
both
their
their
gmail
and
small
are
similar
and
monitor.
Health
is
instrumenting
in
usage
ping.
A
A
The
review
will
go
through
each
one
of
these
individual
groups,
but
I
did
want
to
highlight
the
overall
performance
indicator
for
the
ops
section.
We
had
a
target
of
466
000
total
smiles.
That's
the
smell
of
the
groups
that
our
reporting's
now
added
together,
there's
a
obvious
reporting
anomaly
that
is
causing
us
to
have
exceeded
that,
where
the
monitor
proxy
smile
of
users
associated
with
projects
where
there
is
prometheus
integration
enabled
skyrocketed
to
where
it's
almost
on
par.
A
With
the
number
of
users
we
have
in
ci,
which
we
don't
think
is
appropriate,
but
we
have
an
ongoing
investigation
issue
linked
here
to
investigate
that
sudden
spike
things
we're
doing.
Overall,
though,
to
improve
our
ops
section
smile
include
a
heavy
focus
on
ci
adoption,
we've
seen
ci
adoption
continue
to
ramp
significantly
and
actually,
we've
also
seen
great
growth
in
the
release
stage.
Adoption.
A
But
really
we
consider
ci
adoption
to
be
this
kind
of
core
part
of
our
user
adoption
journey
and
so
a
focus
on
that
in
terms
of
our
research
into
what
it
takes
to
adopt.
What
what
pain
points
there
are
in
adopting,
as
well
as
we
created
a
new
group
in
the
last
month
for
ci
authoring
that
is
really
focused
on
that
getting
to
your
first
green
pipeline
user
journey
for
our
users.
A
As
I
mentioned,
lots
of
great
other
updates,
I'm
excited
about
smell,
getting
measured
for
package
and
the
work
that
the
teams
are
doing
to
instrument
new
metrics
we've
also
seen
great
improvements,
as
I
mentioned
in
package,
hitting
their
non-smau
target
for
on
track
for
the
non-smart
target
for
their
quarter,
as
well
as
the
release
stage
surpassing
100
000
smile
users,
which
is
awesome,
so
lots
of
growth
and
good
improvements
in
the
configure
stage.
A
We
have
also
had
a
number
of
new
initiatives
that
are
shipping
with
instrumentation,
which
is
great
to
see
that
focus
on
instrumentation
up
front,
so
we
have
both
infrastructure
as
code
feature
ads
and
our
kubernetes
management
feature
ads
that
are
starting
with
instrumentation.
At
this
point,
we're
kind
of
just
waiting
for
metrics
to
come
back.
So
I
encourage
you
to
take
a
look
through
this
entire
page
and
ask
great
questions
during
our
review.
A
As
always,
the
product
team
is
using
this
content
to
not
just
measure
ourselves,
but
also
provide
guidance
and
support
so
that
other
team
members
can
come
up
with
great
ideas
that
will
help
us
drive
our
smile.
So
if,
in
looking
at
our
metrics
and
small
in
particular,
you
think
oh
there's
some
some
other
things
that
we
can
be
doing
within
our
product
group
to
drive
these
indicators.
Please
do
not
hesitate
to
reach
out
to
your
product
manager
and
make
those
suggestions
thanks
a.