►
From YouTube: Growth Group Conversation (Public)
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
A
A
A
Every
name
is
a
growth
categories
to
give
it
a
little
bit
better
understanding
of
how
we're
breaking
down
the
growth
work
so
under
telemetry
and
fulfillment
groups.
Yes,
those
are
the
correct
categories
for
the
other
column,
the
activation
adoption
of
cell
retention
sections,
those
they're,
not
actually
official
categories
on
that
product,
page
they're,
just
kind
of
segregations
of
growth,
work
or
buckets
of
growth
work,
as
you
will,
and
so
I
can
make
sure
that
that
naming
is
more
consistency.
My
apologies
on
that.
B
Yeah
thanks
the
big
page
category
says
as
a
known
connotation
and
especially
since
this
really
deals
with
six
categories:
tamo
momentary,
fulfillment,
activation
reduction,
upsell
and
retention.
Now
it
since
that
seven
six
and
the
addiction
I
get
I
gave
is
that
I
think
that
analysis
system
it
might
be
very
confusing.
With
our
metrics
category
under
managed
at
which
I've
we
can
come
reading
it
into
an
analysis
that
maybe
not
I'm
cool
with
idea.
But
but
we
shouldn't
have
something
that
overlaps
licensing
and
transactions
I.
B
Think
it's
the
same
thing
so
I
think
it's
confusing
to
make
that
in
two
separate
boxes.
It
should
be
the
sole
problem.
We
want
it
to
be
one
integrated
process.
We
want
to
have
kind
of
cloud
fulfillment
of
everything,
so
I
think
by
separating
those
two
things,
I,
don't
think
we're
making
we're
selling
that
team
out
for
it
for
the
right
way
to
frame
that
work.
B
Okay,
I
think
there
might
be
a
stretch,
but
you
can
think
about
collection
and
amyloidosis.
That
way
too,
like
it's
the
same
thing,
if
you
want
to
know
something
you
set
up
action
of
that
yeah
well,
I
wouldn't
go
there
into
trucking
that,
because,
before
you
know
they
have
soccer
team
members
working
on
these
things.
B
B
B
Great
and
what's
the
timeline
beyond
that,
when,
when
I,
what's
gonna
be
gonna
xsplit,
are
you
gonna
split
one
team
up
to
four?
Are
you
gonna
do
one
team
up
to
two
but
I?
Don't
know
you
say
it.
Adoption
and
activation
will
be
1
and
epsilon
retention
will
be
1
and
then
possibilities
them
again,
2
months
later.
What
what
is
what's
your
thinking.
C
Initially,
it'll
depend
on
the
work
that
comes
through
they'll
be
low-hanging
fruit.
That
means
that
we
may
concentrate
on
a
specific
stage
and
then,
as
we
get
more
data
more
granularity
and
more
team
members,
then
we
can
split
them
out
into
equal
sized
groups.
My
understanding
is
that
for
the
next
quarter,
there'll
be
another
six
engineers
coming
on
board
cool.
B
C
B
Yeah
and
you
don't
need
any
data,
because
we
didn't
have
any
data
when
we
took
the
decision
either
so
your
home,
whether
you
want
to
go,
maybe
parts
full-stack
part
front
and
back-end
or
keep
doing
full
stack,
but
anyway,
that's
that's,
certainly,
certainly
not
something
you
have
to
prove
we'll
just
follow
your
leader.
Sure.
A
In
you
didn't
ask
us
it,
but
just
to
highlight
and
call
out
the
goal
was
for
a
product
manager
for
each
four
of
those
of
those
buckets
of
work,
so
adoption
upsell
retention
and
activation,
and
we
had
our
first
growth
PM
start
last
week
we
have
our
second
one
starting
next
week
and
in
the
the
previous
are
the
subsequent
two
starting
on
August
5th,
which
is
in
slide
2,
and
so
the
product
team
will
be
will
be
full
staffed
here
in
early
August,
which
is
really
exciting.
Yeah.
B
That
is
super
exciting,
and
it's
super
well
done.
That
was
not
a
easy,
easy
thing
to
hire
for
so
really
well
done,
and
I'm
really
excited.
I
I
think
we'll
have
a
lot
of
pressure
on
part
a
his
team
soon,
because
those
four
teams
are
gonna
have
a
lot
of
requests
so
well
that
will
almost
automatically
meet
us
to
to
hire
and
if
you're
watching
this
on
YouTube
we're
hiring
engineering
positions.
B
A
Is
gonna
be
a
fun
team
to
be
a
part
of
it,
because
you're
gonna
get
to
watch
some
some
really
important,
metrics
move
across
the
company.
You
know,
of
course,
there's
gonna
be
user
metrics,
but
there's
gonna
be
financial
metrics
that
are
going
to
be
directly
tied
to
this
group
and
I
just
want
to
echo
sits
comment.
This
is
gonna,
be
a
really
fun
and
exciting
team
to
be
a
part
of.
D
Yeah
good
morning,
happy
Monday
big
shout
out
to
bar
tech,
because
my
my
watch
is
what
I
am
and
Sydney
I'm
curious.
I
know
that
data
is
really
important
to
the
success
of
the
growth
groups,
but
also
these
other
groups,
but
it
looks
like
the
snowplow
em
are
around
getting
user
IDs
in
has
stalled.
I'm
curious.
How
you
see
that
being
or
the
way
I
see
is
that's
a
symptom
of
a
bigger
problem
of
we're
growing,
really
fast
and
I'm
worried
about
things
falling
or
do
you
have
an
idea?
Is
this
part
of
that?
C
I
can
answer
that
one
so
you're
right,
so
we
had
we've
gone
through
a
global,
optimization
exercise
to
by
individuals
within
the
company
that
can
assist
in
growth.
We've
had
one
engineer:
ash
McKenzie
who's
been
really
helpful
in
getting
us
through
some
initial
piers
of
work,
but
unfortunately
his
vacations
then
coincided
with
with
the
particular
merge
request
that
you're
referring
to
to
go
back
to
step,
though
we
do
have
new
engineers
coming
online,
as
I
mentioned
the
next
week
and
separately
with
what
you're
saying
around
the
importance
of
data.
E
A
A
So
that
includes
things
like
snow
pile,
which
is
primarily
used
to
gather
you
know:
user
metrics
and
product
data
inside
of
the
inside
of
the
application,
but
also
things
like
usage
ping,
which
sends
us
data
from
on-prem
self-managed
instances
and
we've
actually
broken
telemetry
out
into
into
its
own
group
to
provide
it
a
little
bit
more
focus,
and
so
you
know
Emily
to
kind
of
answer
your
question
a
bit
more
directly.
We
are
going
to
keep
moving
on
this
issue
in
this
mor
today.
A
Obviously,
the
MMR
is
not
incredibly
complicated
from
a
code
perspective,
but
it
does
have
some
legal
and
compliance
implications
and
it's
typically
on
product
to
drive
those
types
of
things
forward
and
to
make
sure
that
they
move
forward,
and
so
we'll
continue
to
do
that.
And
obviously
this
past
week
was
a
little
bit
challenging
with
respect
to
vacations
I
know:
I
was
personally
out,
so
I
wasn't
able
to
help
drive
a
lot
of
these,
and
but
the
fourth
of
July
was
a
short
week
for
many.
A
But
you
know
the
point
is
for
the
product
managers
in
each
of
these
areas
to
to
drive
these
things
and
make
sure
that
they
don't
stall
us
all
out,
as
you
mentioned,
and
with
respect
to
want
to
tell
make
sure
you
are
hiring
again
so
just
a
quick
plug
for
that
area.
It's
a
super,
exciting
area,
that'll
help
drive
a
data
foundation
and
framework
for
the
application
for
many
years
to
come.
So
you
know
just
a
quick
plug
if
you're
interested
in
that
or
if
you're
watching
on
YouTube.
A
B
I
see
that
issue
and
I
see
that
we're
looking
at
tracking
and
we're
checking
that
with
our
privacy
policy,
and
we
should
I
just
want
to
make
sure
that
we
understand
that
this
is
an
internal
system
like
we're
using
this
to
improve
our
product,
we're
not
sending
this
data
out
to
any
external
party
and
I
think
in
the
way
it
is
discussed
in
the
issue.
This
is
like
we're:
sending
data
to
pay
or
something
I
think
there's
an
enormous
difference
like.
B
B
Like
user
extent
why?
But
as
long
as
it's
in
our
data,
storing,
we
only
publish
aggregate
metrics
I'm,
not
sure
where
do
we
need
to
make
this
opt-in
I
think
we
can
turn
it
on
for
everyone
by
default,
but
I'm
not
sure.
So
we
should
check
that,
but
I
would
like
to
see
that
distinction
between,
like
tracking,
in
an
external,
a
sending
data
externally
and
attracting
people
into
an
internal
systems.
If.
D
I
could
tag
on
to
that
I
want
to
echo
CID
in
that
we
already
know
what
issues
you
create
on
get
Lancome.
We
already
know
what
labels
you
add.
We
already
know
what
words
requests
you
create.
We
already
know
when
they're
merged
this
tracking
is
just
going
to
give
us
the
how
of
your
of
what
you're
doing
and
so
I.
Don't
really
understand
the
the
compliance
blocker,
but
I'll
look
into
the
issue
more
to
understand.
They
see
where
the
discussions
couldn't
turn
out.
There
I
think.
E
A
And
to
answer
your
question
directly
said:
we
are
absolutely
differentiating
between
internal
and
external
systems.
In
fact,
this
was
the
impetus
behind
moving
our
snow
plow
collection
systems
off
of
third
party
infrastructure
into
in-house,
and
so
this
is,
as
Luca
mentioned,
just
the
final
making
sure
we
go
through
the
right
process
and
we're
updating
our
privacy
policy,
we're
making
sure
that
we're
transparent
to
the
community
and
in
doing
this,
the
right
way,
but
we
shouldn't
have
any
issue
of
getting
this
done.
B
A
So
if
you're
listening,
you
just
got
an
interview
tip,
but
the
onboarding
experience
is
is
not
very
good
right
now,
when
a
new
user
signs
in
there's,
basically
four
boxes,
you
can
click
on
to
take
various
actions,
and
you
know
we
assume
that
you
want
to
take
one
of
those
four,
but
we
know
nothing
about
you.
Your
role
may
be.
Maybe
one
of
those
four
things
is
not
what
you
should
be
doing,
and
so
we're
going
to
shift
the
new
onboarding
in
12.1
behind
a
feature
flag.
You
can
see
it
in
issue.
A
So
that's
the
first
thing.
The
second
thing
that
we're
going
to
work
on
is
the
signup
flow.
The
signup
flow
is
is
not
very
good.
It's
also
not
good
for
how
customers
can
purchase
plans
Luka.
Can
it
elaborate
on
this
a
little
bit,
but
the
the
the
experience
for
when
customers
sign
up
and
decided
they
actually
want
to
purchase,
get
lab
I
get
lab
license
is
actually
very
painful
right
now,
and
so
we're
going
to
to
fix
that
as
well
and
right
now
we're
working
on
the
plan
to
do
that.
E
Those
are
those
are
two
of
my
biggest
priorities
at
the
moment,
because
I
mean
trials
are
essentially
the
first,
that's
the
first
time
you
experience
working
with
get
lab
and
right
now
it
I
think
it's
equally
as
important
as
as
onboarding,
and
it's
sort
of
that
first
step
in
onboarding.
So
you
have
trials
as
step
number
one.
You
have
purchasing
as
step
number
two
and
then
you
have
all
morning
a
step
around
the
tree
and
I
think
it's
important
to
treat
those
all
as
a
as
a
similar
priority.
E
B
C
So
flipper
is
our
process
that
really
gem
that
we
use
for
feature
feature
toggling
and
we've
been
using
that
to
do
some
rudimentary
a
be
testing
so
turn
the
feature.
Rod
for
a
certain
amount
of
time
turn
it
off
to
be
able
to
test
two
different
things.
The
issue
that
we're
that
Eric
is
thinking
now
is
iterating
towards
a
better
solution
to
be
able
to
do
proper
AV
tests
and
that'll
be
one
of
the
first
pieces
of
work
along
with
other
parent
mentioned
earlier.
That
will
get
the
engineers
on
yeah.
B
C
B
Yeah,
but
now,
when
suppose
you're
using
your
lab
as
a
customer,
you
don't
you
wonderful
featured
solution
right,
you
get
live,
got
feature
flag,
so
it's
not
a.
We
need
to
have
a
very
compelling
reason
to
not
use
our
own
product
and
they
understand
feature
thanks.
Like
a
cart,
it's
gonna
be
hard,
but
now
we
brought
a
few
thought,
gives
lap
down
feature
flags
that
I
was
away
and
now
we're
not
using
that
lesson
to
kind
of
improve
the
product
for
our
customers.
C
F
I
think
this
is
great
and
I
think
I'm
next
question.
I
just
was
curious.
Lucca
I,
like
the
the
notion
of
thinking
of
the
different
stages
question,
would
it
be
at
all
make
it
any
easier
for
self-managed
customers
if
we
made
it
any
easier
for
them
to
deploy
or
do
a
trial,
for
example,
in
a
public
cloud
for
myself
managed
it?
Is
there
anything
there
that
we
can
at
the
Alliance
that
can
help
with,
but
just
curious?
If
that
ties
any
way
to
make
it
easier
and
faster
for
customers
from
what
you've
seen.
E
F
E
E
It's
a
good
idea,
I
think
it's
something
you
can
definitely
explore,
I'm,
not
sure
how
heavily
that
would
specifically
fall
under
fulfillment
right
now.
That
might
involve,
like
other
other
areas
of
product,
earn
chip
in
on
that,
but
I
think
it's
a
great
idea.
Anything
is
stuffing
something
we
can
talk
about.
Do.
F
E
It
hasn't
specifically
since
I
have
worked
in
product
when
I
was
in
working
in
customer
success.
This
the
reason
I
asked
specifically
about
whether
or
not
you
were
talking
about
a
managed
service
was
that
is
something
that
customers
have
spoken
about.
Specifically
goldman-sachs
have
brought
up
they've
just
they've
said
we
would
much
rather
not
have
to
deal
with
setting
this
all
up
ourselves
and
hosting
or
an
infrastructure,
but
they
also
don't
want
to
be
on
get
up
to
calm,
so
I'd
be
I'd,
be
curious
to
know.
E
F
A
You
know
just
one
quick
call
out
here:
we
have
made
this
a
little
bit
easier,
especially
for
for
ultimate
users
by
providing
the
AWS
marketplace
listing
recently.
That's
something
that's
like
literally
a
few
clicks
and
you
can
have
a
like
a
working.
Install
of
you
know
of
Iggy
write
your
fingertips
on
AWS,
but
that
doesn't
necessarily
incorporate
a
trial
process,
but
it
is
at
least
a
springboard
we
could
build
on
top
of.
If
we
wanted
to
consider
something
like
this
Brandon
yep.
F
E
I
think
it
depends
on
what
the
customer
wants
to
get
out
of
the
trial
right
like
what
is
it
specifically
they're
trying
to
trial
like
if
they
do
have
to
host
it
on
their
own
infrastructure?
Ultimately,
then,
maybe
that's
what
what
that's
what
they
want
to
trial
Biff?
It's
just
get
labs
of
the
product
like
the
front
end
of
it,
then
maybe
that's
something
that
would
be
really
beneficial
to
them.
You'd
have
to
do
some
research,
so
great
suggestion.
No
thank
you.
A
Other
thing,
too,
is
we
also
have
a
marketplace
listing
for
it.
Lab
seee,
which
obviously
would
be,
would
be
free
from
a
license
perspective.
It
would
cost
users
infrastructure
if
they
didn't
want
to
trial.
Obviously
on
github.com,
that
would
be
a
way
for
them
to.
You
know
cheaply,
evaluate
at
least
the
the
CEO
dish
and
on
it,
abuse
isn't.
F
B
A
A
Yeah,
let
me
just
clarify
real
quick
on
the
ADA
based
marketplace,
so
there's
actually
two
paths
for
kind
of
AWS
listings,
there's
just
general
community
am
eyes
Amazon,
machine
images
and
then
there's
the
curated
marketplace.
So,
on
the
as
AM
eyes,
we
have
Community
Edition
and
Enterprise
Edition,
which
comes
with
no
license,
so
customers
are
free
to
use
that
and
apply
their
own
license
that
they've
procured
from
us
outside
of
that
process.
A
The
curated
path
was
essentially
like
the
MVC
version
of
allowing
us
to
do
what
we
call
a
private
offer
through
AWS,
so
that
so
that
customers
could
basically
purchase
get
lab
licenses
with
their
AWS,
EVP
or
AWS
credits,
so
that
was
kind
of
the
path
that
we
took.
But
customers
do
have
that
option
today.
Sit
so
basically
do
like
a
one-click,
IE
install
and
then
apply
license.
B
But
I
think
that
the
confusion
here
a
bit
is
that
EE
would
necessarily
be
paid.
We
could
I
think
it's
a
great
thing
that
people
who
use
EE
without
pain,
so
I'm
not
even
sure
we're
maintaining
a
see
e
offering
because
it's
it
it
it
doesn't
need
like
99%
of
the
customers,
would
be
better
off.
Just
installing
the
song
yeah.
F
I'll
work
on
that
said:
I
think
there
was
some
historic
history
there
as
to
Amazon's
point
of
view,
which
I
believe
may
be
evolving,
so
I'll
work
I'll.
Take
that
since
I
brought
up
the
question
idea,
I
will
put
that
I've
I
put
it
to
Amazon
will
see
on
if
we
can
get
to
that,
because
I
think
you're
right
for
customers,
that's
a
better
that
that's
the
best
option,
if
that's
everywhere
for
them,
Thanks.