►
From YouTube: 2023-06-06 Product Analytics Team Sync
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
The
product
analytics
sync
for
for
me,
Tuesday
June,
6th,
Ellen
I,
think
it
is
Wednesday
June
7th.
For
you,
though,
they're
pretty
late
agenda
today,
Dennis
is
working,
a
think
and
we'll
just
be.
The
two
of
us.
I
did
want
to
take
just
a
minute
and
review
something
I
want
to
add
into
more
of
the
sticky
items
and
I'm
gonna
go
ahead
and
share
my
screen.
A
Our
Milestone
theme
and
objectives
for
16,
one
which
we're
in
our
theme
is
more
customer
feedback,
well
objectives
ability
for
customers
to
add
existing
visualizations,
but
more
of
a
stretch,
goal
for
where
we
want
to
get
to
closing
out
the
experimental
epic
so
that
we
can
onboard
customers
and
we
like
to
get
two
customers
feedback
from
two
customers
who
have
onboarded.
So
those
are
our
main
objectives
or
anything
really
blocking
our
ability
to
onboard
customers
is
something
that
we
want
to
try
to
get
closed
out.
A
In
design
we're
working
on
validating
the
dashboard
custom,
sorry
creating
custom
dashboard
below
we're
going
to
be
doing
that
with
internal
books,
so
I'm
working
on
scheduling
those
today
so
that
Kevin
and
I
can
do
those
interviews
and
validate
that
prototype.
A
Let's
see,
I
think
a
planning
breakdown
Ellen,
it
looks
like
all
of
the
blocked
issues
are
yours.
So
what.
A
B
I
have
been
keeping
that
reasonably
freshly
emerged,
so
it
shouldn't
be
too
too
much
work
to
pull
the
trigger
when
we're
good
to
go,
and
the
next
two
are
suppose
they're
just
waiting
on
a
schema
change.
That
Aaron
has
been
working
on
and
snow
plow,
and
so
once
his
stuff
has
emerged
in
these
two
should
be
unlocked
again.
Okay,
great.
A
And
working
on
as
its
Endeavor,
it's
in
review
and
ready
to
go.
B
Right,
yeah,
I
think
I've
just
gone
into
review
recently.
Okay,
awesome,
yeah,
good.
A
A
Nothing
there
allele
if
you're
watching
this.
Hopefully
we
can
get
an
update
on
that
one.
Soon,
all
right
end
of
I'm
gonna
comment
on
create
config
screen.
B
Not
too
much
to
say
there
I
have
started
on
it.
I
was
waiting
on
a
further
change
to
the
the
settings
pages
to
be
merged
just
to
avoid
conflicts,
but
it
looks
like
that
one
might
be
a
little
bit
longer
now
so
yeah
I'll
just
keep
tripping
away
at
that
one.
Okay,.
A
B
Yeah,
so
that's
the
one
that
I
had
been
waiting
to
to
get
merged
through,
just
because
I
know:
they're
gonna,
conflict
on
on
the
same
bits
of
code,
this
one's
got
into
review
and
has
been
split
into
two
merge
requests,
one
of
them
I'm
just
waiting
on
a
little
bit
of
feedback
from
a
designer
in
the
foundations
team.
Just
to
some
of
the
changes
I've
made
to
the
shared
component.
That's
the
one
that
kind
of
masks
that
sensitive
values
as
it's
like
a
password
field.
B
B
Yeah
I
think
some
of
those
we
can
start
working
through
now
that
some
of
the
infrastructure
is
in
place.
I
wasn't
totally
sure
what
the
best
way
to
do
that
was
in
staging,
though
like
which
group
or
project
or
any
or
was
set
up
with
the
right
permissions
and
and
features
and
stuff.
Okay,.
A
Can
you
drop
a
note
into
the
team
slack
asking
that
and
we'll
just
link
it
to
the
agenda
or
post
it
into
the
agenda
as
well
more
people
than
you
have
that
question
yeah
for
sure
awesome.
A
All
right
and.
A
B
No,
it's
there
in
the
settings
now,
so
you
can.
You
can
access
those
instrumentation
details
outside
of
the
onboarding
flow,
which
is
Handy
and
yeah.
We're
gonna
continue
to
work
on
that
in
the
other
settings,
page
change.
A
Awesome
cool
and
then
I
close
out
this
first
user
on
boarding
flow.
That
was
just
a
to
do
for
me
to
create
kind
of
an
issue
template
for,
as
we
have
both
internal
and
external
groups
who
want
to
use
product
analytics,
have
a
generalized
flow
of
what
we
need
to
do
with
them
to
check
all
the
boxes.
So
I've
created
that
and
I'm
just
copying
and
pasting
from
issue
to
issue,
as
we
on
board
folks
to
make
sure
that
we're
tracking
all
those
things
all
right,
cool
find
my
agenda
again.
A
And
I'll
update
the
bookmark
cool,
so
I
also
wanted
to
vocalize
update
at
the
experiment,
epic
description
to
call
out
that
any
of
the
custom
dashboard
visualization
related
work
is
more
nice
to
have
it's
not
required
to
onboard
customers.
A
I
might
even
move
that
into
its
own
epic
and
put
it
into
post
GA
just
to
keep
the
work.
That's
in
the
experimental
epic
focused
on
what
needs
to
be
done
to
onboard
a
customers.
So
we
can
close
that
out
and
probably
revamp
data
a
little
bit
too
of
the
things
that
are
really
required
for
beta,
which
we're
talking
about
getting
performance
metrics
so
that
we
can
understand
what
scalability
needs
to
look
like,
and
a
pricing
proposal
are
the
two
biggest
things
that
we
need
to
get
out
of.
A
The
beta
yeah
get
out
of
the
beta.
The
things
you
need
to
do
to
enable
that
are
what's
going
to
be
in
the
beta
Epic
cool,
all
right
and
then
I'm
gonna
vocalize
0.5
for
Dennis
and
I'll
move
down
a
review
of
the
clickhouse
config
created
a
number
of
issues
within
the
linked
epic
there
and
anyone
who's
involved.