►
From YouTube: Expansion Sync 2020 06 24
Description
Tim, Matej & Doug from the Growth Expansion team sync up
A
B
But
it
seems
like
we're
locked
on
that
issue
and
I'm,
not
sure
whether
it's
because
we
can't
run
proper
experiments
there
like
we
can
uncom
or
is
it
simply
because
we're
focusing
a
lot
more
on
calm
as
a
company
lately
or
is
it
a
combination
of
both
or
is
it
just
our
prioritization
that
it's
a
bit?
You
know
prioritizing
a
bit
more
dot-com
lately,
yeah.
A
So
I
think
there's
a
there's
a
couple
of
things
there
nuanced
things,
so
we
don't
have
an
easy
way
to
run.
Experiments
on
self-managed
instances
today
and
I
know
that
we
are
we're
digging
in
there
and
trying
to
learn
more
about
it.
The
the
second
piece
is
that
we
have
been
focusing
on
get
lab
comm,
mainly
because
it's
easier
for
us
to
collect
and
and
and
analyze
data
specifically
to
an
experiment,
and
we
also
have
better
control
over
that
experiment
through
the
feature
flag,
functionality
uncom,
it's
just
easy.
A
So
that
way,
if
something
goes,
if
it
doesn't
work,
how
we
can
simply
just
you
know,
do
the
chat,
command
and
shut
it
down,
so
I
think
that's
part
of
it
and
from
a
prioritization
perspective,
I
think
the
stuff
for
self-managed
is
it
should
be.
This
is
just
me
thinking
out
loud,
but
it's
it
should
be
very
high
priority.
It's
you
know
it's
where
the
majority
of
our
of
our
revenue
lies
today
we
still
haven't
figured
out
how
to
how
do
we
do
experiments
there
or
is
the
approach?
A
B
Good,
that's
exactly
how
I
see
it
as
well,
because
I
did
notice
from
when
I
speak
to
my
manager
from
when
I
speak
to
other
designers.
There's
been
I
focus
on
that
completely,
and
that
makes
total
sense
and
I
know
that
we
can't
run
proper
experiments
on
self-hosted.
But
in
this
particular
example-
and
maybe
there
would
be
other
similar
ones
where
we
just
know
hey.
This
will
improve
the
user
experience
quite
a
bit
and
it's
quite
a
small
change
right.
B
Does
it
need
to
be
an
experiment
in
order
for
us
to
prove
the
value
of
it,
or
should
we
sometimes
ship
things,
because
we
know
they
will
improve
the
experience,
and
in
this
particular
case
we
have
the
additional
option
of
running
a
pretty
much
the
same
experiment
on
comm.
So
we
can
basically
think
the
learnings
from
there
and
say:
hey
we're
expecting
something
similar
on
so
posted
right,
yeah.
A
A
Mm-Hmm
and
I
don't
think
that
everything
should
be
an
experiment.
I
feel
like
there's
a
lot
of
things
out
there
that
are
issues
that
we
can
work
on,
that
we
know
will
add
value
and
the
traditional
product
team
just
either
hasn't
been
able
to
get
to
it
or
it
hasn't
been
assigned
or
it
hasn't
been
picked
up
by.
A
You
know
a
team
to
run
with
or
a
group
to
run
with,
so
if
they
fall
in
line
with
what
we're
trying
to
accomplish,
we
might
as
well,
you
know,
give
it
a
shot
and
maybe
the
priority
the
order
of
maybe
the
sequencing
is.
If
we
can
do
it
on
self-managed,
we
should
be
able
to
do
it
on
comm
as
well.
So
why
don't?
We
run
us,
run
it
on
comm
and
if
it
works
well,
then
we
can
introduce
it
to
the
self-managed.
A
B
A
B
B
A
A
B
Contact
sales
form
it's
a
bit
more
complex,
but
the
step
before
we
go
and
do
that
is
just
exposing
a
link
to
that
documentation
page
somewhere
in
the
u.s.
more
in
the
app
right,
and
that
doesn't
feel
like
a
really
complex
thing
or
something
I,
don't
know
where
we
would
it's
not
even
specific
to
self-hosted
as
well.
So
again,
we
can
test
it
on
that.
Consider
the
results
right
like
same
thing,
so
yeah
I'm
glad
that
you
also
kind
of
share
this
view
that
not
everything
needs
to
be
an
experiment.
A
A
A
A
We
have
a
great
opportunity
here
to
to
make
some
big
improvements
and
in
this
issue
specifically
Jackie
myself
might
say,
I.
Think
a
bunch
of
folks
have
contributed
to
this,
but
what
we
did
was
we
we
dug
in,
and
we
basically
found
all
of
the
different
navigation
will
call
them
quote:
unquote:
navigation
elements
that
exists
today
in
the
product
and
and
documented
what
we
thought
they
were
and
then
what
we
did
was
we
we
even
went
as
far
as
to
say:
hey.
A
A
Specifically,
if
you
scroll
down
to
to
my
comment
here,
you
can
start
to
see
all
of
the
different
screens
that
have
navigation
components
and
the
things
that
we
would
want
to
focus
on.
So
we're
using
this
issue.
Specifically
as
a
catch-all,
so
that
way,
we
can
at
least
have
visibility
into
what
are
all
of
the
navigation
elements.
A
And
then
what
is
the
expansion
team
going
to
focus
on
specifically
Jackie
was
super
proactive
and
created
this
mural
doc
as
well,
which
basically
takes
all
of
the
different
screenshots
and
and
elements,
and
and
put
them
in
one
one
single
on
one
single
page,
which
is
a
little
it's
a
little
tricky
to
see.
As
you
can
see
this
map
down
here,
it's
it's
quite
large,
so
you
have
to
take
some
time
to
to
really
kind
of
wrap
your
head
around
it
all.
A
A
The
the
MVC
that
we
landed
on
has
been
basically
documented
in
this
issue
here,
which
is
coming
off
of
the
main
one
that
jackie
created
and
Doug
I
wanted
to.
Thank
you
for
just
going
in
and
checking
my
work,
but
what
we're
gonna
be
focusing
on
for
the
MVC
is
basically
those
main
that
here
so
there's
11
different
elements
and
then
down
here
we're
also
going
to
be
looking
at
the
side.
A
Nab's
for
project
group
and
user
I
did
verify
with
Sid
said
ready
that
some
of
these
are
actually
firing
in
snowplow,
but
they're,
not
all
custom
events,
they're
they're,
unstructured
and
some
of
them
fire
through
the
CSS.
Some
of
them
have
structured
events,
some
of
them
don't
have
any
we've
scheduled
some
time
for
tomorrow
to
just
go
through
and
basically
do
a
just
an
audit
of
all
of
these
different
elements
up
here
to
see
what
has
been
created
and
what
hasn't
been
created.
A
At
the
end
of
the
conversation
that
I
had
with
said,
he
basically
said
what
you're
doing
here
is
actually
a
pretty
pretty
solid
approach,
because
once
it
is
a
custom
event,
it
won't.
It
won't
change.
So
if
we
were
to
use
the
the
auto
unstructured
events
that
come
out
of
snowplow,
if
somebody
were
to
change
anything
in
the
code
days,
it
would
then
change
the
data
that
we
would
be
reporting
on.
A
C
A
B
I
think
it's
a
good
start,
because
when,
when
I
initially
asked,
when
I
found
out
that
the
expansion
team
would
own
the
navigation
and
I
asked
Jackie,
what
does
that
mean?
Is
it
just
the
main
now
elements,
or
is
it
pretty
much
everything
on
how
users
navigate
through
all
of
the
pages,
and
it
was
the
second
one
in
her
answer,
but
we
need
to
start
somewhere
right.
We
can't
capture
everything
from
the
start
and
I
think
this
is
a
good
start.
A
We
don't
know
how
much
work
is
gonna
come
out
of
this
I
mean
just
at
first
glance.
This
could
be.
This
could
be
a
completely
separate
category
for
us
and
I
did
raise
those
concerns
to
hila,
Bartek
and
Phil,
because
I
don't
want
and
I
and
I'm
pretty
sure.
Jackie
also
matei
is
aware
that
this
is
a
it's
a
pretty
significant
lift
and
as
it
relates
to
our
ability
to
to
manage,
you
know,
running
experiments
for
what
we've
already
signed
up
for
that
impacts,
not
retention.
A
We
also
need
to
spend
time
on
the
navigation
so
I'm,
assuming
that
we're
we're
gonna
have
that
request
for
additional
resources,
I'm,
just
not
sure
what
that
looks
like
for
when
that
conversation
is
going
to
happen
Doug.
So
in
the
interim
you
know,
I'll
take
prioritization
and
we'll
make
sure
that
we
get
everything
kind
of
leveled
out
sure
I
mean.
C
A
Wanted
to
talk
a
little
bit
more
about
this
one.
You
know
we're
coming
up
on
time,
but
click
where
we're
adding
the
invite
members
link
to
the
assignee
drop-down
alright.
So
this
is
close.
The
next
step
is
to
actually
move
it
into
a
modal.
That's
so
that
way,
users
don't
need
to
abandon
their
work
on
galib
comm.
A
It
looked,
it
looks
like
there
were
some
still
some
outstanding
questions
on
here.
I
didn't
necessarily
see
them,
so
it's
curious
if
they
were,
if
you
all,
had
any
outstanding
questions
for
them
or
if
we
can
begin
to
break
this
down,
we
could
we
could
break
it
down,
asynchronously,
Doug
or
or
if
you
and
me,
you
and
Jackie,
wanted
to
have
a
a
sync.
C
A
C
A
Awesome
just
an
update,
I
realized.
We
don't
have
an
epic
or
handbook
page
about
the
team's
ownership
of
navigation.
I
spoke
with
heel
about
it
last
week.
Her
recommendation
to
me
was,
you
know,
basically
come
up
with
a
philosophy,
identify
what
navigation
means
to
us,
how
we
want
to
manage
the
sick
of
things.
You
know,
if
you
think
about
what
we
have
the
ability
to
impact
it's
it's.
Basically,
the
we're
gonna
have
a
large
impact
on
probably
one
of
the
most
utilized
pieces
of
the
application,
which
is
the
navigation.
A
So
even
small
changes
can
really
drive
user,
behavior
and
traffic
in
certain
ways.
So
we
we
really
need
to
come
up
with
a
philosophy
so
that
way,
users
of
the
application
know
how
we're
calling
about
making
changes
and
why
we're
making
those
changes
and
then
we'll
also
want
to
make
sure
that
we're
getting
feedback
from
the
community
and
and
listening
I
think
those
are
really
really
important
things.
So
I'm
gonna
spend
some
time.