►
From YouTube: Ops Section PM Meeting - Europe Friendly - 2020-05-19
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
The
customer
success
organization,
as
well
as
I
think,
there's
going
to
be
more
collaboration
with
docs
around
these
use
case.
Use
cases
which
are
kind
of
you
can
think
of
it.
As
a
more
customer
focused
go
to
market
motion
that
is
also
really
aligned
with
our
desire
to
expand
span
for
users.
It's
part
of
like
driving
the
user
adoption
journey,
and
so
the
customer
success
organization
is
kind
of
measured
on
increasing
span
within
their
accounts
and
they're
kind
of
pushing
the
pmm
for
more
documentation
about
how
to
do
that.
A
What
the
process
is,
how
do
we
sell
a
customer
on,
in
this
case
the
icd,
and
so
I'm
really
I've
been
really
hardened
to
see
that
I'll.
Put
that
little
note
that
we
also
have
to
be
careful
to
not
replicate
our
docs
and
jason's
been
doing
a
great
job
with
the
verify
one
of
making
sure
we
don't
do
that.
A
C
Sorry,
I'm
late
so
in
13.1
we're
taking
some
time
to
invest
in
our
technical
improvements,
so
like
graphql
implementation,
we're
also
fixing
a
couple
of
the
performance
issues
that
we
noticed
inside
of
our
pages
implementation,
with
some
tests
and
then,
of
course,
in
13.0
we
shipped
our
api
for
deploy
phrases
which
is
really
good
and
our
edit
milestones
in
ui.
I'm
also
super
excited
because
darren
is
going
to
help
me
with
my
secrets,
management
vision,
which
is
great,
very
excited
about
that.
That's
it.
A
On
your,
I,
I
saw
your
kickoff
video
and
I
think
I
gave
you
some
feedback
about
framing,
but
are
you
maybe
just
for
everyone's
benefit
as
you're
taking
some
time
to
clean
up?
Is
that
slowing
down
to
speed
up
in
the
future
or
because
you're
working
on
a
bunch
of
high
impact
problem
validations
that
you
want
to
make
sure
you
get
right
before
you
would
have
the
team
start
working
on
them?
Oh.
C
No
that's
kind
of
like
a
the
second
one's
a
byproduct.
The
first
one
is
to
slow
down
to
speed
up,
so
graphql
will
allow
our
front-end
team
to
enable
some
endpoints
from
the
front
end
so
that
they
can
work
on
some
features
on
the
releases
page
as
we
begin
to
expand
it,
which
will
be
an
increase
in
our
velocity.
C
We
also
have
tests
for
the
disk
serving
on
pages,
which
will
allow
us
to
actually
be
able
to
fine-tune
and
see
how
our
object
storage
is
benefiting
our
serving
of
files,
which
is
great,
because
I
want
to
understand
whether
or
not
we
should
stop
investing
in
that
project
or
continue
investing
in
that
project.
If
there's
no
benefit
in
performance,
and
we
have
to
really
be
mindful
of
the
time
we're
spending
on
it.
So
it's
definitely
the
the
second
one.
Okay,.
D
I
had
a
couple
ideas
from
engineering
and
from
ux
for
that
dimitri
told
me:
he
started
a
ux
research
project.
Maybe
we
can
recruit
through
our
first
look
program
and
maybe
that'll
give
incentive
for
folks
to
con.
I
think
there's
a
lot
of
interest,
but
I
think
people
are
also
very
busy
with
their
own.
D
You
know,
so
we
don't
have
a
lot
of
participation
yet
and
then
another
idea
engineering
gave
me
is:
maybe
we
put
up
a
web
page
that
will
come
up
on
a
search
engine
that
will
point
them
to
the
jenkins
rap
republic
issue.
Another
thing
I
was
not
finished
typing
yet
is
the
ci
team
is
we've?
We've
had
a
lot
of
changes
on
the
team
and
we're
just
now
really
starting
to
get
gelled
as
a
team,
and
you
know
in
how
we
work
and
the
iterations
and
the
planning
and
stuff.
D
D
The
way
we
want
to
work
with
our
new
process,
but
I
think
in
1392,
what's
going
to
be
exciting,
is
I'm
going
to
focus
just
on
one
area
of
functionality
that
we
haven't
made
progress
on
and
it
either
be
throwing
all
of
our
effort
into
the
many
sub
the
issues
under
the
epic
for
parent
child
pipeline
or
all
of
it
under
the
rules?
Syntax,
so
that
we
can
try
to
see
if
we
make
more
projects?
I
also
listened
to
the
peanut
butter
and
long
tails
video,
so
that
kind
of
inspired
me
cool
yeah.
D
A
E
Yeah
something
exciting:
I
think
that
ux
teams
in
creating
very
fine,
secure
and
actually
even
beyond
that
are
joining
to
help
to
improve
their
experience
on
the
merger
quest
widgets.
The
issue
that
myself
have
triggered
has
triggered
and
started.
So
I
included
the
issue
in
the
video,
but
now
also
later,
I've
seen
that
actually
that's
one
of
the
key
oops,
it's
not
okay.
It's
key
results.
Yeah,
so
would
really
appreciate
help
from
the
product
management
to
paradise.
E
Some
of
those
improvements
that
we're
gonna
be
pushing
to
propose
your
way
because
yeah
there
was
a
pretty
interesting
video
for
those
who
haven't
seen
that
definitely
advised
to
do
that.
There
is
some
eye-opening
information
for,
and
it's
really
cross
functional
cross-stage
cross
across
the
platform.
B
F
A
Cool
victor,
I
think
I
posted
the
link
to
the
video
in
the
product
channel
friday
or
saturday,
but
that
video
that
you
did
where
I
think
probably
maria,
had
created
the
storyboard
and
then
you
walked
through
the
storyboard
with
a
user
was
super
cool
to
see
I
mean
not
for
everyone
on
this
call
in
terms
of
the
specific
kubernetes
agent
flow,
but
just
seeing
you
walk
through
a
user
who
was
unaccustomed
walk
them
through
that
storyboard
was
pretty
cool.
So
if
you
could
share
that
I'd
appreciate
it.
E
A
Group
is
victor
frozen.
That
was
the
first
one
that
I've
seen
done
here
at
gitlab.
To
be
honest,
I
think
there
was
a
time,
maybe
a
year
ago
where
we
said
we
were
going
to
do
a
handful
of
small,
isolated
ones
and
they
didn't
that
were
actually
run
by
google
ventures.
I
mean
they
weren't
super
successful.
If
I
recall
correctly,.
E
F
G
Yeah
so,
first
of
all,
I'm
really
happy
with
the
amount
of
deliverables
that
we
are
able
to
ship
in
this
situation,
13
specifically
around
the
variables
on
dashboard.
This
is
something
that
is
really
like.
I
I
I'm
biased,
but
I
think
it's
really
like
an
awesome
feature
that
we're
an
enhancement
to
our
to
our
dashboard
and,
generally
speaking,
the
amount
of
features
that
we
added
to
the
metric
dashboard
is
is
really
cool.
I
probably
should
start
drafting
a
blog
on
all
the
new
cool
features
that
we
release,
so
our
users
will
be
able
to.
G
A
Awesome
yeah
totally
agree.
I
know,
there's
a
what
we
call
simulation
day,
where
we're
going
to
attempt
to
use
all
of
our
get
lab,
monitor
tools
and
replace
of
the
existing
tools
in
late
june,
but
yeah
the
progress
has
been
pretty
astounding,
so
yeah
congrats,
okay,
so
we
have
okrs
and
then
active
discussions.
A
I
do
want
to
darren
I'm
going
to
apologize,
I'm
going
to
take
a
little
bit
of
like
leadership,
liberty
and
bump
up
jackie's
discussion,
because
I
do
think
it's
specifically
about
our
okrs
and
it's
our
first
time
discussing
since
we've
had
the
okrs,
and
I
want
to
make
sure
we
get
to
this
topic,
which
is
a
focus
on
span
so
jackie.
Why
don't
you
kick
it
off?
You
had
had
the
question
and
some
comments
about
what
you're
working
on.
C
Yeah
for
sure,
so
I
orie-
and
I
have
this
release,
epic,
where
we've
landed
cross-stage
issues
just
as
something
that
we're
tracking
together
as
an
initiative.
I've
listed
some
of
the
issues
that
are
contained
within
that
epic
below,
but
I
wanted
to
see
are
we
is
anyone
else
tracking
things
like
this
and
is
there
a
more
global
way
that
we
should
be
updating
these
or
tracking
these,
and
should
we
consider
a
handbook
page
that
highlights
these
different
features
wanted
to
get
your
your
thoughts
on
that.
F
F
So
we
just
realized
this
series
last
week
and
we
are
trying
to
come
up
with
ideas
how
to
fix
it,
and
we
have
that.
We
have
only
that
one
issue
that
I
learned
there
there's
only
one
idea
in
it
and
my
product
designer
would
like
to
to
look
at
several
ideas
before
we
we
develop
anything,
but
this
specific
idea
might
be
might
influence
actually
others
as
well.
A
Cool
yeah,
I
you
can
see
if
you
look
at
the.
Let
me
just
type
this
out
dog
in
the
okr
issue.
I
I
think
that
the
magnitude
of
this
okr
improvement
is
large,
so
large
that
if
we
were
to
say
we
are
all
like
working
towards
improving
this
shipping,
a
handful
of
features
that
provide
better
interconnectedness
between
stages
is
not
going
to
move
the
needle
within
a
quarter
of
this
type
of
span
increase.
A
I
had
a
dialogue
on
that
issue
about,
if
that's
the
case,
if
we
want
it
to
be
large,
we
could
think
of
this
as
an
opportunity
to
kind
of
like
inject
a
more
growth-binded
mindset
into
each
product
group,
but
I
feel
like
we're
a
little
bit
ahead
of
the
game,
because
we're
still
adopting
northstar
metrics,
the
idea
would
be
let's
get
northstar
metrics
under
our
belt
understand
our
funnel.
Then
we
can
start
saying
well,
is
to
get
to
victor's.
Point
he's
realized
that
adoption
is
the
the.
What
do
you
call
it.
A
The
like
squeeze
point
of
in
his
funnel
there's
a
word
for
that
that
I'm
forgetting
right
now,
and
so
we
would
so
he
would
target
improvements
that
might
not
be
product
features.
They
might
be
just
awareness
type
features,
and
those
are,
I
think
it's
some
teams
might
not
be
ready
for
that.
I
guess
let
me
describe
that
some
people
might
not
have
a
good
enough
understanding
of
their
funnel
to
do
that.
But
if
you
are,
I
think
now
is
an
opportunity
to
begin
prioritizing.
A
Those
kind
of
pure
awareness
and
adoption
type
features.
A
great
example
that
I've
seen
recently
was
ori
is
has
planned
this
improvement
to
the
user
flow
when
adding
aws
variables
to
also
show
them.
Oh
here's,
some
templates,
you
could
use
for
your
ci
if
you're,
adding
an
aws
variable
so
helping
that
adoption
journey
for
users.
A
So
I
guess
when
I
think
about
how
to
increase
span.
I
wouldn't
I
don't
want
it
to
just
be
well.
You
know
we
are
already
doing
some
other
activities
that
help
the
interconnectedness
between
our
stages.
So
that's
what's
helping
span.
We
should
really
think
about
it
in
terms
of
how
can
we
move
the
needle
directly
and
if
you're
prepared-
and
you
have
good
data
that
says,
hey
the
the
pain
point
isn't
I
need
new
features
to
attract
users
to
this
stage?
It's
actually,
I
need
awareness
or
to
improve
the
adoption
journey.
A
Let's
focus
on
those
things.
Instead,
what
I'm
cognizant
of
is
that
some
of
us,
some
groups,
don't
even
have
north
star
metrics
being
measured,
yet
that
would
all
be
just
their
presumption,
and
so
I
want
to
make
sure
we're
following
the
actual
growth
process
and
not
kind
of
skipping.
The
line
does
that
make.
D
D
Yeah
it
as
far
as
increasing
adoption
across
stage
is
that
also
something
the
growth
team
is
focusing
on
like,
for
example,
I
had
a.
I
had
a
coffee
chat,
maybe
two
months
ago
with
tim
haye,
and
he
was
telling
me
that
they
were
going
to
have
some
almost
wizard-like
guide
to
the
user.
To
say:
hey,
we
see
that
you're
using
source
code
management,
but
you
have
no
pipeline
in
two
minutes.
You
can
set
up
your
pipeline
to
increase
the
use
of
users
in
that
name
space
to
another
stage
I
mean.
C
D
G
A
Adoption
so
the
one
for
verified
that
might
be
the
one
that
they
are
working
on,
but
in
any
other
case,
I'm
fairly
certain
that
this
is
not
in
their
top
priority
and
they're.
Relatively
small
teams.
Keep
in
mind
like
I
think
each
growth
team
is
two
to
three
full
stack
developers
so
they're
not
making
major
improvements.
A
I
think
it's
they
should
be
an
enabler
and
one
thing
that
if
you
feel
like
you've,
got
good
metrics
and
know
that
maybe
awareness
and
adoption
are
your
pain,
points
meeting
with
a
growth
pm
and
getting
an
understanding
of
what
types
of
experimentation
you
could
do
or
what
ideas
they
might
have
might
be
useful.
But
I
think
it's
going
to
be
incumbent
on
your
teams
to
ship
the
improvements.
C
A
If
to
victor's
point
awareness
is
a
bigger
problem
than
having
a
new
feature
right,
and
so
I
think
it's
really
great
to
start
thinking.
I
guess
my
tldr
is.
I
really
want
us
to
start
thinking
about
span.
Our
long-term
plan
is
to
make
sure
that
each
product
group
is
growth-minded
and
thinks
about
their
funnel
and
targets,
improvements
that
aren't
necessarily
just
attracting
new
users
with
features,
but
also
that,
like
awareness
and
adoption
journey-
and
I
just
am
a
little
bit
concerned-
that
the
more
important
goal
is
to
make
sure
we
have
north
star
metrics.
A
A
Yeah,
a
new
proposed
in
that
issue,
the
okr
issue
that
we
start
adding
that
just
like
here's
things
that
we
are
already
working
on
yeah.
I
think
I
already
said.
I
think
that
that
just
feels
like
us
writing
down
work
we're
already
planning
on
doing,
but
I
do
want
to
make
sure
that
there
are
opportunities
for
us
to
be
growth-minded
and
make
sure
we're
focused
on
most
important
part
of
our
funnel.
But
let's
make
sure
we
have
our
funnel
first.
A
So
the
answer
is
there
probably
will
be
a
place
that
I'll
ask
you
to
write
down
those
issues,
but
I
want
to
make
sure
we're
not
muddling
that
like
this
is
by
just
writing
down
our
issues
that
are
features
that
connect
between
stages,
that
that
is
the
best
way
for
us
to
improve
span
and
that
I
expect
in
maybe
future
quarters.
As
we
have
north
star
metrics
in
place,
we
we
will
come
back
and
have
more
data-driven
focus
on
activities
that
would
drive
span.
A
Correct
yeah,
okay,
I'm
not
saying
you
can
you
can
follow
that
dialogue
in
the
issue.
Anub
is
you'll.
You'll
hear
this
from
me
a
lot
I
do
think
as
we
are
like
there's
a
certain
cadence
or
sequence
by
which
we're
maturing
our
organization
and
adding
our
new
kind
of
like
product
capabilities.
I
guess
you
call
them
product
management
capabilities.
A
First
was
we
had
problem
validation
and
we're
growing
our
kind
of
customer
intimacy?
Now
we're
trying
to
become
data
driven
and
have
norstar
metrics
and
understand
our
customers
journey
and
kind
of
funnel,
then
I
think
we
can
talk
about
being
very
growth
focused
and
moving
growth.
Metrics
like
span
in
a
quarter,
I'm
a
little
bit
hesitant
to
suggest
that
we
can
do
that
and
to
jackie's
point.
The
natural
response
today
is
going
to
be,
let's
add,
all
the
existing
stuff
we're
doing
that
drive
that
has
interconnectedness.
A
But
that's
not.
We
should
be
honest
with
ourselves
that
that's
not
realistically
going
to
move
the
needle
from
1.4
to
1.7
in
the
course
of
the
next
two
months,
and
that's
what
I'm
concerned
about
is
that
I
don't
want
you
all
to
to
come
away
with
the
conclusion
that
that's
the
type
of
activity
that
moves
span
rapidly,
but
we
need
to
make
sure
we
understand
our
funnels.
Then
we
can
have
activities
and
jackie.
A
I
know
that
you
are
very
aware
of
your
funnel
and
if
those
truly
are
the
things
that
you
consider
to
be
most
capable
of
moving
your
span,
that's
great.
I
don't
want
to
discount
that
I'm
just
saying
I
know
a
number
of
teams
don't
even
have
instrumented
north
star
metrics
yet
so
it
would
be
hard
to
suggest
that
any
activities
we
propose
would
be
the
ones
that
drive
span
most
efficiently.
D
D
D
You
know
like
we
can't
I'm
not
saying
you
say,
ignore
the
span
stuff,
you're
saying
you
know,
we
really
need
to
that's
something
that
we
need
to
at
least
get
our
north
star
metrics
solid
before
we,
but
still
being
in
the
okay,
both
of
them
being
okrs
in
the
same
quarter.
I'm
just
trying
to
think
of
how
I'm
going
to
achieve
whatever
is
is
expected
under
each,
but
but
there's,
there's
stuff
that
I'm
I
haven't
read
through
on
that
discussion
in
the
span
once
so
I'll
go
catch
up
there.
A
Okay,
yeah,
I
think
the
part
of
the
intention
was
that
the
growth
team
would
be
very
focused
on
that
span,
one,
but
we're
now
kind
of
asking
the
product
organization
to
list
off
or
the
what's
called
the
devops
product
groups
to
list
off
their
items.
And
what
I'm
worried
about
is
that
we
walk
away
from
that
saying.
Let's
say
next
quarter,
we
had
another
span,
increase
okr
that
we
would
think
that's
the
primary
way
you
increase
spam
span.