►
From YouTube: Expansion 14.4 Milestone Kickoff 2021_09_16
Description
14.4 Milestone Kickoff session - reviewed milestone commitments and covered outstanding needs and/or questions as a team
A
Success:
yes,
there
we
go
all
right
for
anyone
who
might
be
watching.
My
name
is
gail
dowd.
I
am
a
senior
pm
on
the
growth
team
for
the
expansion
group,
and
this
is
our
14-4
milestone
kickoff
session,
we'll
walk
through
what
we
have
allocated
for
this
milestone,
discuss
as
a
team.
If
there's
any
remaining
data,
ux
technical
writing
needs-
or
you
know,
perceived
conflicts
and
then
kind
of
adjourn
and
go
from
there.
Sound
good.
A
Great
from
a
development
perspective
for
14
4,
we
have
a
couple
experiments
that
we're
targeting
and
those
are
labeled
as
growth
deliverables.
We
as
a
growth
team,
have
kind
of
been
refining
how
we're
using
this
label-
and
I
can
link
the
discussion
and
kind
of
where
we're
near
like
narrowing
in
on
kind
of
what
the
new
definition
for
growth
deliverable
is
going
forward.
But
we
do
have
a
goal
and
kind
of
tpi
metric
as
a
larger
team
to
deliver
two
growth
deliverables
per
milestone.
A
A
This
is
when
there
are
no
additional
users
in
a
namespace,
we're
adding
invite
members
to
the
left-hand
nav
for
all
three
namespaces,
as
kind
of
a
prompt
to
try
and
get
that
that
first
invite
sent
jackie
has
started
this
work
and
it
should
probably
wrap
up
early
in
this
milestone.
But
since
it's
technically
going
to
get
completed
and
ship
in
14
4,
we
have
it
allocated
here.
A
The
second
expansion
experiment
we're
going
to
run,
or
at
least
do
the
development
work
in
14
4
will
be
effectively.
What
is
a
invite
modal
with
a
celebration
activity
that
we're
going
to
place
right
after
the
completion
of
the
registration
flow?
This
one's
exciting
for
a
couple
different
reasons.
One
is
that
we
are
going
to
be
testing.
You
know
this
concept
of
peak
end
rules
which
are
effectively
like
memorable
moments
in
the
user
journey.
A
A
I
can
scroll
down
and
find
what
we
actually
landed
on,
but
we
think
we
have
a
viable
option
for
kind
of
integrating
a
open
source
confetti
component
and
adding
that
to
the
invite
modal
also
be
some
congratulatory
copy
here
and
then
a
prompt
to
compel
them
to
invite
another
user
or
two
emily.
Is
there
anything
you
want
to
add
about
this
one?
I
know
we've
talked
about
it
quite
a
bit.
This
is
the
final
design
fyi.
D
Yeah,
the
only
thing
I
would
add
here
is
when
we
chatted
with
jackie.
It
was
like
easier
to
have
the
confetti
within
the
modal
than
behind
or
something
behind
it,
so
we're
just
figuring
out
the
final
animation
aspect,
but
just
having
a
little
banner
of
it
at
the
top
and
then
seeing
all
that
how
users
interact
with
it
if
it's
something
they
find
exciting
from
there
yep
cool.
I
think.
C
A
A
A
A
It
just
is
wise
to
put
a
little
buffer
there
as
well,
but
with
this
spike
completed,
we
will
then
be
able
to
round
out
some
ux
design
work
that
emily's
been
running
and
then
finalize
the
experiment,
design,
and
you
know
with
a
little
luck.
I
think
it
would
be
really
awesome
to
be
able
to
run
this
url
invite
experiment
in
q4
before
the
end
of
the
year.
A
A
A
This
had
a
lot
of
review,
but
finally
had
like
mr,
was
finally
approved
and
should
be
moving
forward
into
production.
However,
tracking
did
not
make
the
scope
of
the
original
like
development
work,
so
we
want
to
add
that
in
so
we
can
kind
of
watch
and
monitor
behavior
and
potentially
experiment
there
in
the
future.
A
We
also
have,
in
our
kind
of
like
due
diligence
of
making
sure
we're
cleaning
up
our
experiments,
have
a
experiment
allocated
to
clean
up
and
kind
of
tidy
up
from
a
standpoint.
This
is
the
add
and
by
option
to
the
comment
component,
I
don't
believe
that
was
a
successful
experiment.
If
I
remember
correctly,
I
think
it
was
invalidated
so
we'll
remove
that
code
and
clean
it
up
for
the
next
thing
and
last
but
not
least,
notify
inviter
of
bounce
email.
A
This
is
another
experiment
that
we've
been
working,
multiple
milestones
over
towards
this
experiment.
Essentially,
we
want
to
let
admins
know
when
their
invite
emails,
bounce,
there's
a
theory
that
we
have
or
hypothesis
that
we
have
that
emails
might
get
typed
in
incorrectly
and
then
invites
never
get
delivered.
There
was
a
decent
amount
of
kind
of
like
prep
work
that
we
had
to
do
within
mailgun
and
itsrelation.com
to
enable
us
to
do
this.
We
are
blocked
by
kind
of
one
final
approval
from
the
info
team
to
be
able
to
kind
of
enable
this
work.
A
That'll
unblock
our
ability
to
actually
go
run
this
experiment,
so
I
have
it
as
a
stretch
due
to
the
fact
that
there's
that
one
last
piece
that's
blocking,
I'm
hopeful
that
we
might
be
able
to
have
that
unblocked
by
the
end
of
the
week,
but
we'll
we
will
see
with
different
stakeholders.
That
depends.
A
I
will
probably
remove
this
item
just
this
is
something
that
this
adding
the
invite
accepted
values
for
social
and
ldap
doug
had
started.
Some
work
here
got
an
mrn
and
it
bounced
back
with
a
bunch
of
different
feedback,
and
I
talked
to
him
yesterday
effectively.
He
thinks
it's
going
to
be
easier
to
split
this
into
and
do
individual
issues
for
both
for
social
and
then
the
ldap
sign
ups,
and
that
should
be
more.
A
A
A
What
we
saw
was
that
non-invited
users
of
a
large
chunk
of
the
non-invited
users,
maybe
close
to
25
percent,
were
saying
that
they
were
joining
joining
gitlab
to
find
their
existing
team
or
project
which
was
really
interesting
to
us,
because,
if
you're
joining
via
invite,
that
makes
a
lot
of
sense
and
there
is
a
kind
of
natural
flow
that
drops
you
into
your
namespace
and
the
project
or
group
of
which
you
have
been
invited
to
join.
If
you
are
not
invited
finding.
A
Your
team
is
kind
of
up
to
you
and
I
think,
there's
a
lot
of
curiosity
that
we
have
around
how
that
how
people
actually
find
their
teams
today.
What
are
they
doing?
How
are
they
navigating
within
the
product
to
to
get
to
where
they
need
to
be
and
then
start
their
work?
They
aren't
provided
much
guidance
at
all
of
how
to
do
this
today.
A
You
know,
there's
you
know
some
fair
assumptions
that
this
could
be
a
frustrating
user
experience
that
people
could
just
give
up
if
they
can't
find
their
team,
and
I
think,
with
some
better
understanding
that
can
help
inform
and
loop
into
some
of
the
larger
efforts
that
we
have
going
around
or
have
started
around.
Inviter
use,
invited
user
onboarding
and
you
know
in
general,
just
getting
people
to
value
as
quickly
as
possible,
no
matter
kind
of
like
what
their
use
case
or
vector
is
into
the
product.
C
I
just
think
this
one
is
a
the
data
insights
that
we
got
in
the
last
month
or
so
are
just
super
interesting,
and
I
think
the
research
here
is
going
to
be
really
impactful
and
eye-opening.
So
I'm
personally
really
excited
to
see
us
dig
into
this.
I
think
it's
a
great
opportunity
for
not
only
not
this
team,
but.
A
Also
for
growth
in
the
company
as
a
whole
totally,
I
feel
that
way
too,
and-
and
I
was
chatting
with
emily
yesterday-
but
you
know
this
will
help
us
dig
into
some
of
the
qualitative
side
of
this
experience
and
what's
happening.
One
thing
to
call
out
that
mike
and
his
team
are
going
to
do
this
coming
milestone.
Is
that
they're
adding
some
randomization
to
the
list
that
they
display?
A
A
and
then
last
but
not
least,
emily
is
working
on
some
designs
for
an
experiment
where
we're
kind
of
starting
to
test
communication
within
the
product
between
admin
and
non-admin
users.
This
is
a
initial
test.
Where,
for
users
who
don't
have
invite
capabilities,
we
are
informing
them
how
they
can
get
others
invited
and
that
is
through
connecting
with
their
admin.
B
A
A
D
A
A
B
Okay,
what
I
usually
do
is
well
what
we
are
doing
in
the
tech
writing
team,
or
some
of
us
are
trying
to
do
at
the
moment-
is
we're
trying
to
estimate
by
applying
labels
with
weights,
to
issues
that
we
think
we're
going
to
be
working
on
in
the
next
milestone.
So
what
I
will
probably
do
next
week
is
go
through
all
of
those
and
just
apply
appropriate
technical
writing
labels
to
them
so
that
we
can
get
an
idea
we're
just
trying
to
estimate
to
see
if
we
can
predict
tech
writing
workloads
for
a
milestone.