►
From YouTube: Growth Group Conversation (Public Livestream)
Description
Growth Group Conversation (Public Livestream)
November 11, 2019
A
Alright
looks
like
we
are
at
a
time
right
now,
so
hi
everyone
good
morning,
good
afternoon,
good
evening.
Welcome
to
the
growth
group
conversation,
I'm,
Mike,
Ram,
plus
I'm,
a
product
manager
on
the
retention
team
with
in
growth
and
I'm
filling
in
as
host
for
Scott
Williamson.
Today,
I
look
forward
to
answering
your
question.
Your
questions
so
Syd
looks
like
you
have
the
first
one.
B
A
Let's
take
a
look
so
I
don't
know
absurd.
Our
Tim
is
on
the
call
they
would
be
able
to
speak
to
this
better
than
I.
Would
let's
see
yeah?
So
that's
that's
great
feedback
soup
we'll
have
to
take
a
closer
look
at
that
and
get
back
to
you
with
the
answer
there.
But
thank
you
for
that
and
we
will
definitely
follow
up
and
get
that
right.
B
B
A
So
this
one
I'm
not
as
familiar
with
this
one,
it's
not
when
I
work
directly
on,
but
it
looks
like
there
is
an
issue
here,
so
this
was
submitted
by
Amanda
who's
in
our
supporter
work,
who
is
actually
our
partner
in
support
within
growth,
and
so
appears
that
when
a
group
is
subscribed
to
paid
tier
that
they
have
more
billable
users
in
the
group
on
gitlab,
then
it
is
purchased
in
the
subscription
when
they
get
additional
CI
minute
minutes.
There's
a
couple
of
issues
that
have
happened
so
new
subscriptions
created
for
the
CI
minutes.
A
Instead
of
the
minutes
being
associated
with
the
existing
paid
subscription
and
the
group
Association
the
previously
purchased
subscription
is
removed,
so
definitely
an
issue
there
that
we
need
to
address,
and
this
is
something
that
looks
like
the
expansion
team
is
planning
to
tackle.
Now
and
so
that's
that's
stalled.
The
context
I
have
unfortunately
I'm
not
sure
if,
if
Tim
is
on
the
call,
I
think
he
is
off
today
for
for
Veterans
Day.
So
we
can
follow
back
up
on
that.
As
well
said,
I.
B
Think
what
I'm
used
to
is
that
an
issue
states?
What
should
be
the
case
so
I
think
what
we
have
here
is
an
issue
that
is
the
problem,
not
the
solution.
So
would
it
be
accurate
to
say
the
issue?
Title
should
be
buying
CI
minutes
for
a
pay
plan
when
it's
over
using
licenses
shouldn't
an
associate
the
PT
R.
Yes,.
B
C
A
No
I'm
not
sure
if
this
could
be
related
to
potentially
the
usage
pain,
whether
that's
being
used
or
not,
and
the
data
that
we're
getting
back.
We
definitely
need
to
take
a
closer
look
at
this
to
understand
the
root
cause
and
figure
out.
What's
what's
going
on
there
that
thank
you
for
for
pointing
that
out.
That's
definitely
an
action
that
we
can
take
to
digging
further.
There.
D
Thank
you.
Thank
you
hi.
This
is
Jenson,
just
just
want
to
add
some
color.
Here
too,
we
know
that
some
of
the
things
that
we've
done
to
increase
trial
signups
on
about
docket
lab
comm,
have
led
to
an
increase
of
people
signing
up
for
trials
because
that's
the
primary
CTA
on
about
docket
lab
comm,
but
it's
also
led
to
a
decrease
in
exactly
what
you
pointed
out
here.
So
that
could
be
one
of
the
issues.
D
That's
that's
leading
to
that
decrease
because
we
removed
you
know
download,
get
a
get
lab
as
the
primary
CTA
and
replaced
it
with
trials.
So
that
said,
that
was
an
intentional
move
right
and
we
want
to
increase
the
number
of
people
signing
up
for
a
trial.
I
have
a
test.
That's
planned
later,
to
start
looking
at
how
we
can
push
people
after
they
download
a
trial
to
educate
them
on
how
best
to
download
get
lab.
D
B
D
Do
yes,
we
give
them
the
option,
but
we
don't
do
a
great
job
of
educating
them
on
how
to
continue
to
download,
get
Levin
and
instruct
them
on
how
best
to
do
that
after
they've
started
their
trial,
they
kind
of
get
their
trial
key
and
that's
the
end
of
the
process.
For
them.
We
need
to
do
some
more
onboarding
on
on
how
guiding
them
through
how
to
how
to
complete
that
installation.
E
So
as
we're
scaling
up
quality
engineering
counterparts
and
etc,
I
think
it's
true.
It's
really
important.
How
documentation
can
we
please
populate
more
in
the
handbook,
because
right
now,
I'm
only
seeing
team
composition,
so
the
context
is
we're
trying
to
hire
a
quality
engineering
manager
for
growth.
This
quarter
and
any
existing
of
communication
in
the
handbook
linked
from
the
handbook
I
think
that's
also
true.
It
would
be
great
yeah.
A
We
have
a
few
pages
right
now
on
the
handbook
under
the
direction
section
as
well
and
there's
something
work
that
we
need
to
do
to
clean
that
up
and
to
get
it
more
organized
kind
of
break
things
off
into
the
handbook.
That's
how
we
work
and
more
vision
items
in
the
Direction
pages.
So
that's
a
that's
an
action
that
we're
going
to
to
work
on
over
the
next
week
or
so
so.
Yes,
we
will
definitely
do
that.
F
A
All
right,
and
so
next
is
Alper,
whose
can't
speak
he's
asking
what
are
some
other
ways?
Growth
is
using
to
collect
customer
feedback
beyond
telemetry,
so
there's
definitely
a
couple
things
that
we're
doing
right
now,
so
Jeff
Crowe
and
our
UX
research
team
has
been
doing
customer
interviews.
I
know
that
Jensen
and
folks
did
about
ten
interviews
around
the
trial
creation
process
for
the
account
creation
process,
and
we
also
have
started
to
do
interviews
with
customers
that
have
recently
turned.
We
want
to
also
get
some
going
with
folks
who
have
gone
through
the
renewal
process.
G
Yeah
Mike,
if,
if
I
could
just
add
to
that,
if
anyone
has
anything
that
they
feel
like
is
necessary
to
investigate
from
a
qualitative
research
standpoint,
please
reach
out
to
myself.
We
also
have
Eileen
who's
on
fulfillment
and
does
collaborate
with
me
from
time
to
time
on
certain
growth
research
initiatives,
depending
on
how
the
work
overlaps
with
her
own
work
but
yeah.
D
E
A
F
I
So
we've
got
a
lot
of
customers
that
are
SCM
only
and
they're,
not
a
cm
only
because
they
don't
see
the
value
of
integrated
CI.
There
are
seeing
them
only
because
they've
invested
so
much
in
Jenkins
right
and
it's
just
the
moving
from
that.
You
know
taking
all
that
sunk
costs
and
investing
in
get
lab.
I
Ci
is
just
overwhelming
for
a
lot
of
them,
and
so
I
was
super
excited
to
see
the
Jenkins
importer
issue
and
but
I
just
was
keeping
up
with
it,
and
I
noticed
that
it's
getting
pushed
out
a
few
releases,
and
so
I
was
just
curious.
What
was
the
you
know?
What
was
the
thing
that
was
causing
that
to
get
pushed
out?
Maybe
there's
something
else.
That's
more
important,
but
I
just
wanted
to
as
someone
who's
interacting
with
customers
daily.
Just
reiterate,
this
is
a
huge
enabler
bringing
it
lab
CI
for
our
existing
SCM.
Only
customers.
A
Yeah
and
thanks
for
the
question
there
I
don't
have
the
full
context
on
that
one
I
I'm,
not
sure
if
someone
from
the
expansion
group
can
speak
to
it.
But
I
would
imagine
that
the
the
design
and
development
effort
is
just
a
little
larger
than
we
had
thought
and
because
of
that,
it's
pushing
out
but
I,
don't
I,
don't
know
for
sure.
They're
I
don't
know
if
we
have
Jackie,
perhaps
on
the
calls
who
can
speak
to
that
yeah.
J
A
So
I
would
say
in
terms
of
getting
feedback
from
those
groups.
You
know
each
p.m.
will
continue
to
work
with
their
stakeholders
to
do
that,
part
of
the
kind
of
design
process
and
as
if
you
all
have
feedback
or
questions
or
concerns
on
any
of
these
issues
feel
free
to
reach
out
to
to
the
PM's
directly
or
in
the
slack
channel
that
we
have
for
growth.
We
obviously
want
to
to
hear
the
feedback
and
make
sure
that
we're
doing
things
in
the
right
way
so
that
we're
not
causing
downstream
problems
with
any
experiments.
A
Do
have
a
doc
that
has
all
the
different
folks
in
the
different
orgs
that
we,
you
know,
need
to
run
things
by
and
work
with.
I,
don't
think
it's
you
know
published
public,
but
we
do
it's
one
of
the
things
that
we
actually
created
as
part
of
the
fastboot
when
we
got
together
in
Vancouver,
because
we
wanted
to
be
conscious
to
make
sure
that
we
are
keeping
stakeholders
in
the
loop
and
making
sure
everyone
is
aware
of
the
changes
as
we
go
forward.
A
K
A
Let's
see
Alper
has
the
next
one
here,
which
is
question,
is
what
are
some
exciting
recent
or
upcoming
things
for
growth.
You
know
I,
think
and
folks,
on
the
call
on
the
growth
team
feel
free
to
jump
in
as
well.
I
think
you
know
things
that
I'm
really
excited
for
I,
think
the
teams
are
really
starting
to
gel
and
we
identified
some
really
great
opportunities
for
things
to
immediately
impact
revenue.
Things
like
improving
the
renewal
process
for
comm
charging
for
the
right
number
of
seats.
A
A
lot
of
the
true
up
work
that
we're
starting
to
identify
to
improve
things
they're
both
for
our
customers,
but
for
their
folks
internally
around
the
process
there
so
I
think
you
know
we're
excited
about
all
the
opportunities
that
we
have
as
a
team
to
start
to
drive
meaningful
change
for
the
business,
and
you
know
now:
it's
just
all
about
execution.
We've
just
got
to
go
out
there
and
get
after
it.
Other
thing,
I
think
that
we're
all
excited
for
is
that
we
did
hire
a
director
for
the
growth
award
and
she
starts
in
December.
A
She
has
a
background
in
growth
and
she
actually
worked
at
growth
hackers,
which,
though
the
folks
there
are
the
ones
that
wrote
the
book.
Hacking
growth
that
we
all
read
as
part
of
our
onboarding,
so
I
think
she's
gonna
bring
a
lot
of
great
leadership
and
direction
to
the
team
and
that
that's
gonna
help
us
move
forward
with
some
speed
and
start
to
really
generate
some
results
for
the
business.
I,
don't
know
if
anyone
else
on
the
call
wants
to
jump
in
and
add
anything.
F
Think
what
I'm
excited
about
is,
whenever
you
start
up
a
growth
team,
there's
a
bunch
of
groundwork
which
you
need
to
do,
whether
it
be
getting
the
right
analytics
in
place,
I'm
getting
the
doing
doing
a
bunch
of
cleanup
in
the
code
so
that
you
can
rapidly
experiment
I,
just
getting
a
pulse
on
exactly
where
we
are.
There
I
think
we
are
nearing
the
end
of
that
cleanup
and
just
laying
the
full
foundation
so
that
we
can
do
the
quick
sort
of
iterations
and
tests
so
yeah.
That's
that's
the
most
exciting
part,
just
quick
experiments.
A
K
So
I
asked
for
more
information
about
under
the
challenges
slide,
bringing
our
billing
and
licensing
platforms
to
industry
standards
at
a
pace
that
can
keep
up
with
the
growth
of
the
organization.
We're
removing
barriers
for
sales
and
improving
self-service
tools
to
streamline
is
scale.
What
does
that
mean?
Yeah.
A
So
that
one
really
is
it's
about,
you
know,
think
you're
very
familiar
with
this,
that
there's
some
some
tech,
debt
and
other
things
with
our
billing
system
and
the
way
all
the
systems
communicate
with
each
other.
That
we
want
to
make
some
improvements
to
there's.
Also
a
lot
of
manual
back-end
process
that
we
do
for
things
like
renewals
and
true
ups.
A
That
I
think
there's
a
lot
of
opportunity
to
really
automate
a
lot
of
that
and
to
allow
our
folks
internally
to
focus
on
the
more
high
value
efforts
and
if
we
really
want
to
get
to
a
kind
of
seamless
experience
for
payment
and
renewals
and
true
ups,
that
we've
got
to
put
in
a
lot
of
groundwork
on
on
these
systems
and
tools
so
that
we
don't
put
too
much
pressure
on
them.
As
we
start
to
make
these
changes
and
have
it
become
a
bottleneck
where
there's
a
manual
process
that
that
could
break
things
down.
A
So
you
know
it's
a
lot
of
rounds
hora
and
how
it
talks
to
the
other,
apps
and
stripe,
and
really
getting
that
whole
data
flow
and
process
humming,
so
that
we
can
just
start
to
iterate
more
more
easily
on
it
and
provide
a
better
experience
for
for
our
customers
externally
and
internally
as
well.
So
all
the
folks
that
deal
in
you
know
in
billing
and
in
sales
with
with
those
tools
really
trying
to
improve
it
for
everybody.
I
D
Doing
an
amazing
job,
the
sales
organization
is
doing
such
a
good
job
of
bringing
those
customers
on
and
bringing
them
on
in
a
way
to
where
we
are
showing
them
how
best
to
use
the
tool.
We
can
see
that
in
the
value
that
we've
kind
of
extracting
from
those
users.
So
actually,
if
you
look
old,
we're
like
signing
up
less
users
but
at
a
higher
dollar
amount,
which
shows
that
they're
using
more
features
and
that's
more
stick
use
great.
But
if
you
look
at
that
from
bronze
and
silver,
it's
the
opposite.
We
are
signing
up.
D
We
have
a
declining
growth
rate
on
the
num
accounts
that
we're
signing
up,
but-
and
we
know
that
that
relates
to
a
lot
of
the
user
pain
points
that
you
see,
for
example,
like
the
biggest
thing
we
see
on
social
media
is
a
negative
or
a
detractor
from
gitlab
is
that
people
are
really
super
frustrated
with
renewing.
They
have
to
contact
sales
and
a
lot
of
times.
The
sales
just
doesn't
have
the
bandwidth
to
reach
out
to
them.
D
Personally,
so
when
I
see
self-service,
I
think
that
we
can
have
an
immediate
impact
in
turning
around
those
those
lower
dollar
accounts
that
may
not
get
the
that
high
touch
from
sales
and
create
an
experience
for
them
that
they
expect
and
have
an
immediate
business
impact
in
bringing
on
more
of
those
users
without
impacting
you
know,
sales
bandwidth.
That's
that's
where
we're
concentrating
a
lot
of
our
efforts
right
now
and
I
think
we're
gonna
see
like
a
huge
impact
just
based
on
some
small
changes.
There.
A
L
Sure
this
is
just
curiosity.
We
have
a
lot
of
customers
that
start
with
us
that
have
an
opinion,
a
SAR
coming
from
usually
a
cloud
and
we've
done
this
into
little
pieces
around
eks
and
gke,
but
wondering
if
this
is
something
that
if
I
were
an
Amazon
customer
coming
to
get
lab,
that
being
able
to
seamlessly
deploy
into
all
the
environments
that
I
think
of
as
an
Amazon
customer
might
not
be
something
that
could
really
increase
both
that
velocity
and
also
allow
us
to
offer
some
pretty
pretty
unique,
I
guess
value.
D
D
I've
had
conversations
with
the
expansion
group
and
just
internally,
or
things
like
having
some
way
to
generate
like
a
C
ICD
framework
for
places
like
Amazon,
just
to
show
users
like
hey
if
you're
using
these
these
items,
here's
how
we
suggest
to
set
up
your
C
ICD
framework
to
start
deploying
to
places
like
this
or
as
we
try
to
guide
users
on
how
to
download
their
instance
and
start
using
it.
This
would
be
a
great
opportunity
to
show
them
you
know
are
using
AWS
here's
how
we
think
that
it
would
be
best
to
get
started.