►
From YouTube: Growth Group Conversation (Public Livestream)
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
For
the
growth
org
is
also
joining
us
from
Australia,
okay,
everyone,
it's
ready
to
slay
and
I,
just
want
to
lead
off
by
thanking
Bartek,
Eric,
Jeremy
and
Luca
for
their
efforts
to
incubate.
This
growth
team
bar
Tech's
had
to
hire
a
ton
of
people.
Eric
was
interim
director
of
growth
for
a
good
while
Jeremy
was
the
interim
PM
on
growth
for
a
while.
Luke
has
been
the
interim
PM
on
telemetry.
In
addition
to
her
day
job
on
fulfillment.
A
B
A
Is
Jeremy
there?
Jeremy
is
the
main
consumer
for
this
one
or
Tim
hey
if
you've
spent
any
time
on
this,
yet
I
can
give
you
the
genesis
for
it
for
each
stage.
We
want
to
have
a
dashboard
which
helps
the
p.m.
and
also
the
adoption
growth
p.m.
who's.
Tim,
hey,
get
a
sense
for
usage
within
a
stage,
and
so
this
was
built
of
among
the
requirements.
If
you
scroll
to
the
right
there's
an
issue
in
there
which
describes
how
Jeremy
envisioned
usage
being
being
pictured
on
on
a
periscope
dashboard.
A
C
A
D
D
D
D
Basically,
at
what
I'm
trying
to
do
is
just
is
discover
uncom.
How
well
are
we
performing
in
each
product?
Category
I
think
we've
been
looking
at
it
by
M
R
R,
which
is
great,
and
we
can
see
that
view
here.
We
can
see
a
trend
line
of
gold
growth
increasing
over
time
and
silver
decreasing,
and
this
is
month
over
month
growth.
So
this
is
like
growth
from
one
month
to
the
next
same
thing
with
bronze.
The
MRI
growth
is
decreasing.
D
Let
me
try
to
highlight
that,
so
this
would
be
the
bronze
trend
line
here
and
it's
a
little
bit
hard
to
see.
But
this
is
the
best
you
can
do
with
periscope,
so
the
bronze
trend
line
is
decreasing
at
a
lower
rate,
but
that's
normal,
because
a
gold
customers
are
there
aren't
as
many
gold
customers.
So
you
might
see
that
growth
trend
line
decrease
a
little
faster
and
just
saw
just
one
last
one
last
item:
it
kind
of
gets
at
the
heart
of
what
this
dashboard
is
really
trying
to
say
you
can
see.
D
B
D
That
was
one
of
the
first
questions
that
I
asked,
but
all
of
our
other,
so
this
was
this-
was
really
enough.
I
started
out
by
just
wanting
to
look
at
the
numbers
that
I
would
want
to
see
for
the
growth
data
meeting.
All
of
those
previous
numbers
were
broken
out
by
Mr
R,
so
I
just
continued
with
that
trend,
thinking
that
that's
kind
of
what
the
company
wanted,
but
it's
just
a
RR
divided
by
12,
can.
B
B
E
E
Yes
yeah,
so
we
wanted
to
look
into
a
couple
of
other
options
that
might
provide
a
better
check
out
from
billing
experience,
so
the
stripe
offers
a
really
cool
feature
which
is
an
embedded
checkout.
So
we
wanted
to
look
at
things
like
that
to
see
if
it
could
help.
Maybe
expedite
some
of
the
larger
initiatives
we've
gotta
get
to
in
in
fulfilment
like
the
the
payment
and
purchase
process.
Right
now
is
is
not
anywhere
near
industry
standard
and
we
have
a
lot
of
work
to
do
so.
E
We
already
use
stripe
for
credit
card
payments
so
that
it's
just
a
case
of
adding
on
a
little
bit
of
extra
functionality
and
I.
Think
it's
from
our
conversation.
So
far,
some
of
the
stuff
that
we've
actually
been
looking
at
would
already
be
included
in
what
we're
already
paying
for
so
it
wouldn't
cost
us
much
more
if
anything
more
than
what
we're
currently
on,
but
I,
don't
I
can't
just
yet
it's
still
in
very
early
conversations
with
them.
E
B
E
We
actually
have
a
call
later
today
to
get
some
further
clarity
around
that
the
other
tool
that
we
looked
at
with
something
called
kee
Lite,
which
is
a
little
I,
think
it's
a
little
spin-off,
consulting
company
that
the
the
folks
used
to
consult
for
Xero,
specifically
but
they're,
very
immature
in
comparison
to
strike
from
why
I've
seen
they're
a
good
little
company
got
a
little
tool,
but
the
API
isn't
finished.
Yet
they
don't
have
things
like
and
embedded
checkout.
They
don't
there's
a
couple
of
other
features
that
we're
missing.
G
A
Understanding
is
nothing
for
placing
it
at
this
time.
We
are.
We
are
updating
it
to
get
better
data
from
it,
so
that
we
can
have
staged
monthly,
active
user
data
off
of
on-prem.
That
looks
like
what
we're
able
to
get
on
comm,
and
so
the
first
phase
is
to
bolster
the
usage
ping
to
give
us
what
we
need
in
the
short
term.
Think
in
the
medium
to
long
term,
there's
a
potential
project
to
move
to
leverage
snowplow
to
collect
and
harvest
on
Prem
data.
F
Yeah
so
I
look
I'll
jump
in.
We
have
three
areas
of
telemetry
that
we're
focusing
on
usage
ping,
which
Scott
said
we're
providing
stage
monthly,
active
users
and
I'll
add
a
link
to
that
issue
in
the
in
a
document
also
snowplow,
which
is
early
days
starting
to
get
more
useful
to
laboratory
and
then
pendo,
which
was
starting
an
implementation
of
which
will
accelerate
some
of
the
data
that
we
can
collect.
To
answer
your
specific
question.
B
May
be
disambiguate
a
bit,
there's
no
version
think
there's
version
check
and
uses
pink
and
they're
different
things.
I
was
assuming
this
was
usage
ping
as
I
clicked
on.
Yes,
you
should
yeah,
so
that
makes
sense,
but
I
think
we
get
a.
But
we
have
four
things:
four
ways
we
will
collect
data
so
I
think
we
need
to
at
least
from
the
growth
team.
We
need
to
make
sure
that
that
we're
sure
about
during.
G
Defining
servers
out
there
that
that
aren't
licensed
at
certain
companies
and
and
and
using
that
to
drive
sales
further
and
I
know.
There's
problems
with
the
server
version,
get
lab
comm,
it's
not
reliable.
We
don't
always
get
the
right
data,
so
we're
just
curious
and
sit
in
the
sales
department,
at
least
as
to
what
the
future
for
for
the
usage
ping
data
and
and
the
version
docket
lab
comm
server
is.
G
E
E
We
already
have
snow,
plow
setup
and
to
start
collecting
certain
types,
definite
like
page
views,
page
beings
link
clicks
at
such
roads,
so
we're
looking
at
researching
how
we
might
replicate
the
the
kind
of
functionality
that
we
get
from
use
of
ping
and,
if
that's
as
we're
discussing,
if
we
find
out,
if
that's
fairly
straightforward
to
do,
then
it
might
make
more
sense
to
start
trying
to
get
the
data
that
we
get
from
you
staying
in
these
snowpacks.
Do
it!
So
that's
that's!
E
What
we're
currently
out
with
snowplow
just
provide
a
little
bit
of
extra
context
on
that
there
are
some
issues
open,
there's
actually
an
effect
around
there's
some
other
improvements
we
can
make
to
usage
pain
and
the
burden.
But
at
the
moment
we
have
a
prioritize
that,
because
we're
still
looking
at
what
we
don't
want
to
kind
of
duplicate,
work
and
effort,
basically
like
we
can,
we
can
do
the
work
faster
and
more
efficiently
with
Winston.
E
E
H
A
A
This
is
a
new
way
of
working.
This
team
is
going
to
be
driving
experiments
and
we've
given
a
lot
of
a
be
testing.
It's
just
a
different
mindset.
How
do
you
set
an
experiment
up?
How
do
you
know
whether
it
worked
or
not?
There's
a
lot
of
methodology
behind
it
that
we
have
it?
We
don't
have
established
elsewhere,
so
it
gives
us
a
chance
to
define
how
we're
gonna
work
and
practice
a
bit
in
person.
A
I
think
that
will
help
a
ton
get
this
team
on
the
same
page
on
the
second
bullet,
around
data
collection
and
privacy.
This
is
a
hot
topic.
There's
an
issue
open
we're
getting
input
from
compliance,
legal
security.
We
need
to
and
we're
gonna
discuss
at
this
week's
Egret
meeting
to
come
up
with,
hopefully
make
a
decision
on
our
posture
around
this
kind
of
data,
and
you
know,
for
example,
was
it
should
be
opt-in,
opt-out,
etc.
A
F
So
that
the
version
the
coastal
reporter
that
we
use
is
behind
basically
our
front
end
technology,
so
we
need
to.
We
want
to
get
that
up
into
being
a
Best
of
Breed
system
using
the
pajama
design
system,
getting
it
up
to
being
a
fully
functional
view.
Jas
application,
it's
one
of
the
earliest
touch
points
we
have
with
our
customers.
So
we
want
to
really
focus
on
the
UX.
B
Bit
more
of
an
observation
but
I
think
it's
interesting,
like
our
sales,
people
are
using
Fusion
toget
lab
become
and
they
want
more
functionality
out
of
it.
We're
talking
about
doing
experiments
so
I
think,
although
we're
gonna
do
experience
to
like
if
our
sales
people
are
using
something
and
they
need
that
better.
That
might
be
a
good
iteration
to
focus
on
first
yeah.
A
I
should
clarify
the
experimentation.
Stuff
will
be
heavy
in
the
for
growth,
metric
sub-teams
adoption
retention,
activation
and
upsell
slash
conversion,
we're
working
on
the
name
on
that
one
I
think
telemetry
and
fulfillment
will
probably
operate
more,
like
traditional
teams.
Would
so
sorry
for
that?
If
that
was.
B
Yeah
no
yeah
and
maybe
I've
worded
that
a
bit
strongly
but
like
we're
implementing
all
kinds
of
new
things,
even
though
the
things
you
already
have
are
being
used.
It's
just
look:
I've
tried
version
to
get
louder,
call
me
times
out
the
whole
time
and
there
seems
to
be
focus
on
new
ways
of
collecting,
which
is
great
I
want
that
too,
but
like
let's.
Let's
make
sure
that
the
stuff
that
people
are
actually
using
is
working
yeah.