►
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
Hi
Lauren
we're
going
to
discuss
the
racy
for
the
AB
testing
program.
The
the
document
that
I
shared
in
the
chat
was
my
initial,
like
what
I
think
it
should
be,
but
I
just
wanted
to
get
everyone's
feedback
to
say
like
yes,
this
is
something
that
I
would
own
or
no.
This
is
like
absolutely
not
me.
A
I
tried
to
follow,
get
Labs
dri
method,
but
it
just
wasn't
like
as
clearly
laid
out
as
the
racy
chart
that
I
shared.
So
what
I'm?
Seeing
as
R
is
someone
that's
like
responsible
and
they're,
the
one
that
actually
like
goes
and
does
the
task
and
accountable
is
someone
that,
like
double
checks
it
or
like
make
sure
it's
complete
and
then
consulted
and
informed
just
kind
of
makes
sense.
A
So
yeah
I
was
hoping,
maybe
like
the
way
that
I
split
it
out
was
just
like
these
are
kind
of
like
the
tasks
or
like
the
flow
that
it
would
go
in,
but
just
curious
on
people's
thoughts.
Essentially,
maybe
we
can
just
start
from
the
bottom
and
go
down
so
the
first
one
would
be
ideations
or
generating
ideas.
I
think!
That's
like
anyone
and
everyone.
Your
free
everyone's
welcome
to
put
in
ideas.
Everyone
can
contribute,
no
problem.
A
The
second
one
is
selecting
and
green
flagging
an
A
B
test
idea,
so
that
one
would
be
like
a
combination
of
Dennis
uni
around
like.
Are
we
good
to
go
like?
Do
we
want
to
do
this
test?
Yes
or
no
I,
say
you
and
I,
but
I
also
mean
like
with
Michael's
approval
and
informed,
informing
Michael
test
design.
This
one
I'm
curious
Dennis.
A
A
No
sorry
I
meant
like
which,
like
the
control
and
variable,
are
defined,
which
we
need.
That's
what
I
mean
sorry
I
can
clarify
that.
B
Yeah
I
think
R
makes
sense,
because
I
feel,
like
the
past
two
weeks
has
been
a
good
learning
curve.
For
me,
like
some
tests
are
going
to
be
multivariate,
some
tests
are
going
to
be
a
b.
Some
tests
does
not
make
sense
at
all
like
they
shouldn't
be
a
test
it.
Maybe
it's
a
just.
Do
so
I
think
that
makes
sense
for
R
do.
C
You
know
a
40
day,
30,
whatever
long
long
time
like
data
analytics
analytics
on
that
test,
even
though
it's
not
like
an
abts,
but
what
we're
trying
to
test
there,
the
big
gets.
We
can
like
document
that
separately.
A
B
So
in
the
ideation
phase,
you,
like
someone,
creates
an
issue
for
the
idea
right
and
then
I
go
into
that
issue
and
yeah
label.
Everything
like
this
is
what
we
need
to
track:
okay,
yeah.
A
And
then
I
think,
with
the
a
b
testing
issue,
template
I,
think
I'm,
going
to
add,
like
an
approval
section
and
like
maybe
we'll
write
yours
like
Dennis,
has
signed
off
on
these
metrics
and
like
fills
a
side
off
that
we're
going
ahead
with
this
type
of
thing.
So
then,
maybe
there's
just
okay.
C
We
could
also
kind
of
do
what
onboarding
does
with
different
things
like.
We
could
have
a
set
like
path
of
like
check,
marks
that
when
it's
set
up
then
like
a
little
bit
more,
maybe
at
the
bottom.
It's
like
okay
has
test
design
been
done,
Dennis
can
like
add
his
comments,
and
then
he
can
check
that
check
that
off
and
then
the
next
person
can
see
that
gets
their
turn.
A
And
then
the
next
one
would
be
us
ux
design
us
design,
ux
design.
So
obviously,
like
me,
and
the
design
team
I
think
that
one's
fairly
reasonable
and
that
one
would
be
like.
If
we
have
the
A
B
test
issue,
then
we
should
create
another
issue
for
design
design
would
go
and
create
the
design
there
and
that
one's
pretty
straightforward
implementation
I
think
that
one's
straightforward
as
well
once
designed
is
there
engineering
issue
that
gets
shipped
out
to
whichever
group
makes
sense.
A
C
I
think
it
could
be
one
line
but
could
be
kind
of
like
implementation
code
or
it
could
be
like
implementation
and
then,
like
code,
slash
launch
Darkly.
So
we
know
that
yeah.
A
Okay,
so
once
it's
live
on
lunch
directly,
The
Next
Step
would
be
like
declaring
a
winner
based
on
statsig.
Is
that
you
Dennis?
Is
that
me
I
wanted
Clarity
there.
B
That
would
be
me
like
if
we
had
a
normal
test
running,
the
p-value
would
be
under
0.05
and
then
like.
Okay,
that's
pretty
that's
a
good,
solid
number
and
then
we
can
just
close
it
out.
Okay,.
B
C
There's
something
in
there
we
can
look
at
to
try
to
either
email
or
Slack
I
know
we
took
away
like
that
that
launch
directly
data
Channel,
but
maybe
there
is
a
channel
that,
like
this
data
gets
pushed
to.
So
when
we
have
multiple
tests
like
we
can
start,
we
can
see
how
the
tests
are
running
and
it's
just
like
a
bot
system
that,
like
gives
us
the
information,
yeah.
A
Of
helpful
I
was
like
yeah
anyways
side
conversation,
okay,
so
we're
good
Dennis
will
be
responsible
for
that
and
then,
like
probably
accountable,
like
I'll,
probably
try
to
check
in
just
in
case
turning
on
the
winning
variant
that
one
I
also
have
questions
about.
So
for
the
last
test,
Michael
asked
me
to
do
it,
but
I
don't
know.
If
that
should
be
me,
I
happy
to
do
it,
but
just
curious
on
what
people's
thoughts
are.
There.
C
I,
don't
know
if,
if
there's
like
a
two-parter,
if
it's
setting
I
don't
know
if
it
needs
to
be
I,
think
it
can
be
the
engineering
manager
if
it's
kind
of
a
two-parter,
it's
setting
it
in
launch
directly
to
100,
but
then
we
also
we
need
to
have
a
time
frame
where
we
say
like
yes,
this
is
what
we
want
to
do
now,
make
it
fully
live,
remove
Logic
the
code
and
just
have
that
variance
code
in
repository,
so
I
don't
know
if
that's
if
it's
a
two-parter,
if
it's
Single
part,
but
that
I
would
say
that's
an
interesting
manager.
A
My
thing
is
like
what
is
the
process
we
want
when
something
hits
stat
stick.
That's
the
part
that
I'm
a
little
bit.
The
dentist
goes
as
great.
We
hit
what
we
needed
to
hit.
How
is
that
communicated
out?
Is
that
in
the
issue?
Is
that
in
slack,
is
this
a
sync
meeting
because
I
think
that's
kind
of
the
determinant,
because
even
if
it
does
hit
that
stick
for
some
reason
there
might
be
a
business
reason
where
we
don't
want
it
to
be
a
hundred
percent?
C
I
can
see
that
then
yeah,
maybe
that
okay,
so
maybe
then
I'm
incorrect,
maybe
they're.
Turning
on
the
winning
variant
in
lunch
directly,
that's
not
an
engineering
manager
responsibility.
That's
either
product
manager,
slash
Dennis,.
C
B
C
I
could
also
see
that
if
we
can
set
up
some
sort
of
notification
system
or
whoever's
checking
these
tests,
this
kind
of
this
kind
of
goes
down
to
like
burn
down
charts
and
whatnot,
but
I
feel
like
they'd,
be
either
each
a
B
test
is
an
epic
and
we
have
multiple
issues
Associated
or
if
it's
a
single
issue,
part
of
that
checkbox
thing
like
heavy
rich.sig,
yes
check,
and
then
the
information
gets
added
to
that
issue
of
like
here.
C
It
is
so
like
I,
don't
know
if
we
want
to
consolidate
all
this
information
into
a
single
issue
which
I
think
is
cool,
but
then
we
check
the
box
statsig,
here's
what
here's
the
plan
of
action
and
then
in
there
like
there's
another
check
box.
It's
you
know,
code
implementation,
but
we
have
a
some
conversation
around.
C
C
Is
there
a
follow-up
AP
test
we
want
to
run
like
I
know.
There
are
some
multiple
step.
Maybe
tests
coming
down
in
the
future
that
we
were
talking
about
that?
Yes,
we've
got
stats
like
on
this
cool,
but
now
here's
the
here's,
the
next
issue
for
the
next
A
B
test
running
as
like
a
second
step
of
this
flow
kind
of
a
thing.
A
Yeah
we
can
make
it
an
issue,
no
problem,
I
think
the
A
B
test
epic
issue.
Whatever
you
want
to
call,
it
would
have
like
the
test
information.
C
I
think
kind
of
in
the
racy,
like
the
third
one
down,
selecting
and
green
flagging.
Maybe
test
idea,
that's
when
we
turn
into
it
we're
turning
into
epic
and
that's
when
we
start
opening
up
these
other
issues
to
make
that
happen,
but
I
think
that's
probably
that
that
step
and
we
add
the
checklist
and
all
those
sorts
of
things
would
be
in
my
mind,
the
right
plan
of
attack.
C
So
then
we
can
track
everything
else
separately,
but
we
still
have
like
the
main
epic,
that
houses,
everything
and
I
would
say
like
all
of
the
like.
Subsequent
data
goes
into
the
Epic
information,
not
necessarily
like
the
engineering
issue
or
the
design
issue.
Those
should
be
purely
like
yeah,
like
focus
on
like
design
or
engineering
questions
and
then,
like
the
data
information
in
like
next
steps,
are
in
the
Epic
yeah.
B
I
think
in
the
initial
issue,
though,
there's
going
to
be
a
section
that
outlines
what
launch
directly
kpi
to
track
and
then
what
business
kpis
attract
and
then
I
would
also
like
a
separate
measurement
issue
where
I
can
basically
copy
and
paste
the
report
into
and
then
tag
the
appropriate
people.
Okay,.
A
C
I
can
do
that.
You
just
can't
have
it,
you
can't
have
it
nested
like.
A
C
Think
no
I
think
it's
like
seven
seven
epics
deep,
so
you
can
have
like
so
yeah.
We
can
do
that,
so
you
can't
have
a
because
we
have
like
our
okrs
and
then
we'll
have
like
another
epic
and
then
another
epic
inside
of
that.
So
this
can
like
you
can
you
would
create
the
issue
and
tie
it
to
the
okr
Epic
and
then,
when
you
promote
the
issue
to
an
epic
it'll
still
be
pointed
to
where
it
needs
to
be.
A
A
C
C
I
I
think
that
might
be
maybe
that's
we
can
bring
that
up
with
Lauren
as
like
a
what
is
the
better
like
I
like
the
project,
the
grand
scheme
of
things,
but
when
we
start
like
I
know
the
engineers
it
gets
a
little
messy
I
feel
like
is
it
you
know:
where
does
this
work
so
I
think
we
can
have
it?
We
can
kind
of
figure
that
out
yeah.
A
Keep
everything
yeah
my
only
thing
with
nixing
the
project
is
I
worry
about
people
pulling
in
things
or
like
seeing
an
A
B
test
and
being
like.
Oh
we're
doing
this,
and
it's
like.
No,
that's
just
an
idea
like
this
is
also
just
a
backlog.
So
that
would
be
my
only
reservation
there,
but
I
think
maybe
we'll
get
more
in
the
kitchen
here.
Yep.
C
The
other,
the
other
options
would
still
keep
the
project,
but
one
like
that's
the
just
people
can
we
have
the
ideas
there
and
we
can
kind
of
triage
those
ideas
yeah
and
when
we're
ready
to
like
action
them.
We
essentially
copy
that
data
over
to
like
what
it's
going
to
be
in
the
buyer's
experience.
Yeah.
A
A
Okay,
so
sorry
just
going
back
to
the
screen
in
a
couple
minutes,
so
turning
on
the
winning
variant,
where
did
we
land
on
that?
Then.
B
A
A
I
see
this
as
like
an
engineering
manager
situation,
I,
don't
know
Justin.
If
that's
you
or
Nathan.
That's
taking
that
on,
but
like
technical
ownership
of
the
actual
platform,
I
would
see
that
as
an
engineering
manager,
responsibility.
C
I
think
it's
kind
of
it's
a
mixture
of
like
Nathan's
kind
of
like
the
dri
for
the
platform
yeah,
but
with
that
said,
like
he
doesn't
own
all
the
A
B
test
and
all
the
code
that
everyone's
working
on.
So
it's
going
to
be
more
kind
of
like
a
flow
from
the
engineer
working
on
it
on
the
maybe
testing
up
to
the
engineering
manager,
and
then
we
can
kind
of
bring
Nathan
in
as
needed
to
kind
of
close
that
Loop
and
we
can
figure
it
out.
Okay,.
A
Cool
okay,
sweet
so
like
just
take
a
look
over
this
again,
I
think
we're
in
alignment,
but
we'll
obviously
like
need
Lauren's
input
as
well
and
then
I
think.
Once
we
get
this,
we
can
get
it
into
the
handbook
or
like
the
A,
B
test
project
issue.
I,
don't
know:
I'm
gonna
fall
back
on
Lauren
she's
better
at
this
stuff,
and
then
we
can
just
share
it
out
with
Michael
and
the
rest
of
the
team.
So
everyone
has
alignment
of
like
if
there's
an
issue.
People
know
where
to
go
to.
A
A
Sweet
thanks,
Lauren
I'll,
update
this
video
and
share
this
out
with
them
cool
thanks.