►
From YouTube: 2023-04-05 Product Analytics PM:UX Sync
Description
Weekly sync where we discuss latest UX development, questions and ideas in Product Analytics
A
So
take
a
look
at
the
60
note
planning
issue
we
have
planning
meeting
later
today
and
if
there's
anything
that
I
don't
think,
there's
anything
that
we're
planning
on
implementing
that
facilities,
design,
I
think
there's
some
design
work
that
we're
going
to
help
schedule
than
the
Milestone,
though
cool
all
right.
So
then,
looking
back
at
last
week's
action
items
or
discussion
items
I
wanted
to
confirm
that
we
had
the
issue
for
instrumentation
placement,
updated,
slash,
result
or
updated
and
resolved
with
the
next
milestone.
B
How
would
you
call
this
like
Steps,
basically
like
how
to
set
up
because,
while
I
was
going
through,
it
I
thought
that
some
things
could
be
reordered
to
simplify
a
bit
so
I
just
share
this
with
the
team
and
yeah
I've
seen
yeah
then
and
Rob
has
been
giving
me
some
feedback
on
this.
It's
awesome
I
think
you
on
that
as
well,
so
feel
free
to
have
a
look,
and
let
me
know
your
thoughts
but
yeah
I.
Think.
B
A
B
A
C
A
B
D
C
D
D
B
C
B
C
B
D
D
To
your
point,
like
the
more
we
keep
adding
stuff,
then
it's
going
to
make
sense
to
have
a
dedicated
page,
and
then
we
have
instrumentation
details.
Custom
dashboard
configuration
repository
whatever
we're
going
to
call
that
can
I
bring
your
own
cluster
or
cluster
management
or
whatever
that's
going
to
be
called
and
then
whatever
else
we
add
there
so
like
this.
D
This
seems
like
a
pragmatic
approach
to
you
know
at
it
where
we
already
have
related
settings,
and
then
we
can
break
that
out
if
we
need
to
which
may
actually
just
effectively
be
the
configuration
page.
But
settings
is
a
great
section
for
that
to
be
in
anyways.
So
as
long
as
it's
like
all
somewhere
in
the
last
thing,
I
want
to
like
personally
I
want
to
see
is
like
you
know
where
you
have
settings
sometimes
in
the
apps.
D
D
And
I
appreciate
the
the
this
course
as
well.
Just
because,
like
we're
talking
about
data
sources
and
things
like
that
and
I,
it's
important
to
think
about
the
future,
but
like
I
just
didn't,
want
to
like
put
stuff
in
different
places,
and
then
we
have
to
consolidate
it
again
and
people
get
confused
of
like
well
I
used
to
configure
a
custom
dashboards
here.
But
now,
where
do
I
go
yep,
so
yeah
yeah
I,
think
that
approach
makes
sense.
A
I'll
add
a
comment
on
the
design
that
we
should
include
the
custom
dashboard
stuff
there
as
well,
and
then
Dennis
historically
has
the
team
given
that
Designer,
but
have
you
done
design
and
then
shifted
over
to
implementation
in
the
following
Milestone
generally
with
the
same
issue,
or
do
you
close
the
design?
Just
you
create
a
new
implementation
issue.
I
want
to
work
the
way
the
team
is
used
to
working
from
a
logistics.
D
Historically,
we've
done
a
little
bit
of,
but
it
depends
on
how
much
work
is
involved
in
the
design
side
like
if
there's
a
lot
of
discussions
happening.
There's
a
lot
of
things
you
need
to
get
done.
Like
you
know,
we
don't
want
to
take
a
an
issue.
That's
got
50
80
plus
comments
and
then
be
like
okay
and
here's
the
engineering
side,
where
we
kind
of
have
that
repeat
again
for
the
technical
implementation.
B
D
The
scope,
because,
if
we're
just
adding
an
error
state
to
a
panel,
for
example-
and
you
know-
we
generally
have
patterns
for
that-
and
we
can
just
click
fairly
fairly
quickly,
prescribe
like
the
approach
for
that.
Then
we
can
just
use
the
same
issue,
but
it
just
depends
how
you'd
want
to
track.
Historically,
we've
done
both
which
doesn't
help
you
answer
your
question.
B
D
D
If,
but
if
you
wanna
really
be
able
to
identify
like
here's,
what
Kevin's
worked
on
or
or
things
like
that
and
like
have
that
clean,
but
like
I've
done
my
job
from
design
and
then
like,
we
can
open
up
a
new
one,
because
we
do
that
all
the
time
when
we
like
have
a
large
technical
issue
and
we
have
to
break
it
up
by
back
end
or
front
end
or
infrastructure,
and
things
like
that.
So
again,
I
guess
it's
scope
based,
but
we
can
always
default
to
handing
things
over
until
we
feel
differently
about
it.
D
A
B
We
can
yeah
I
know
it's
it's
totally
up
to
me.
The
thing
is:
I,
try
to
save
some
time
per
day
to
create
issues
and
because
I
don't
want
to
spend
a
whole
day,
creating
confused
I'm,
just
like
doing
it
bits
by
bits.
So
hopefully
I'll
get
this
done
by
the
end
of
the
week
and
we'll
have
all
of
the
new
issues
created,
and
then
we
can
discuss
about
prioritization
and
everything.
B
D
D
B
C
A
And
I
are
both
gone,
so
we've
canceled
the
call
for
the
19th
yep
and
then
I've
left
the
call
in
place
and
as
an
async
for
you
and
I
to
check
in
or
for
me
to
just
kind
of
hang
out
and
answer
any
questions
for
front
end.
If
anybody
has
them
on
the
26th,
okay,
cool
cool,
all
right,
moving
path:
Logistics
Jess!
Do
you
want
to
jump
into
your
questions
because
my
last
one
is
kind
of
open-ended.
D
I
mean
mine
kind
of
well.
They
kind
of
they're,
not
really
yeah,
sure
just
wanted
to
kind
of
I've
been
trying
to
map
everything
out
and
I'm.
Still
in
the
progress
of
doing
that
and
I
know,
you
may
have
heard
James.
You
might
have
spoken
about
this,
like
kind
of
newer
Concepts
like
the
dashboard
designer,
and
we
have
a
lot
of
X,
Y
and
Z
designers,
and
so
I
just
wanted
to
help
try
to
clarify
things
until
I
have
the
documentation
to
kind
of
really
kind
of
display
it
for
everyone.
D
In
terms
of
supporting
custom
dashboards
and
adding
existing
visualizations,
but
we
really
haven't
refer
to
it
as
like,
often
as
that
and
so
I
just
wanted
to
see
if
there
was
any
confusion
or
anything
that
like,
or
at
least
as
you
were,
wrapping
up
that
I
can
try
to
address
in
this
documentation.
That
makes
sense.
C
D
Yeah,
that's
that's
exactly
it!
So,
basically,
in
terms
of
the
workflow,
like
you
set
up
your
your
product
analytics
as
a
customer,
you
get
pre-built
dashboards,
but
you
see
a
button
called
ad
dashboard.
That's
that
brings
you
into
the
dashboard
designer
workflow.
However,
that
workflow
will
ultimately
end
up
working.
D
We
can
definitely
decide
that's
just
kind
of
How
It's
been
explaining
issues
for
now
being
able
to
name
that
and
then
see
existing
visualizations
and
then
being
able
to
add
this
to
the
dashboard
is
the
extents
and
saving
that
dashboard
is
the
extent
of
what
that
dashboard
designer?
Does
that?
What
that
workflow
does
anytime,
you
would
want
to
create
or
visualize
new
data
that
would
actually
bring
you
into
the
visualization
designer.
B
D
A
clear
line
of
like-
and
this
is
what
I
was
doing
for
my
friend
and
Engineers
as
well-
to
understand
where
it's
like
yeah.
We
will
build
the
dashboard
designer
where
you
can
move
existing
visualizations
around,
make
them
bigger,
move
them
around
reorder
them
that
kind
of
stuff,
but
as
soon
as
you
need
to
go
into
like
ad
visualization,
for
example,
that
is
not
part
of
the
dashboard
designer
that
is
a
separate
workflow,
which
then
hands
over
it
to
the
visualization
designer,
which
of
course,
there
can
be
Integrations.
D
Where,
once
you
create
the
visualization,
it
can
come
back
and
add
it
to
that
dashboard.
You
were
working
on,
but
that's
a
whole
separate
like
that's
now,
integrating
two
different
workflows
but
yeah.
Hopefully
that
reaffirms
your
your
understanding,
yep
cool,
because
I
know
we'll
need
a
give
a
lot
of
love
to
the
design.
At
some
point
we
work
it.
I
just
wanted
to
explain
fundamentally
what
the
functionality
is
supposed.
D
Working
on
that
right
now,
because
we
kind
of
reuse,
an
existing
epic
and
I
know
Tim's
created
a
bunch
in
some
kind
of
like
auditing
that
to
make
sure
that
we're
not
missing
anything
because
I
get
the
sense
that
we
have
a
few
issues
that
aren't
in
that
customer
facing
releases
thing
that
I
really
want
to
like
help
clarify.
So
that's
that's
what
I'm
focus
on
last
week
and
this
week,
I,
don't
know
that
I'll
have
it
for
pre-planning,
but
between
now
and
and
final
planning,
I
should
but
yeah
awesome.
A
We
kind
of
set
expectations
that
we're
going
to
be
changing
a
lot.
It's
going,
yeah,
possibly
going
to
break
as
we
release
new
functionality,
but
we
are
here
for
kind
of
a
support
effort
and
me
being
me
and
then
we're
going
to
continue
to
roll
out
new
things
based
on
the
feedback
that
we
get.
So
there's
already
that
expectation.
It's
not
going
to
be
perfect
when
we
launch
so
I
feel
like
we're
in
a
good
spot
with
that
kind
of.
D
Right,
nice,
my
last
point
was
just
checking
because
I've
been
really
behind
a
lot
of
stuff.
So
if
there's
anything
specifically
from
me,
I
guess
I
jumped
in
at
the
right
time
for
the
the
one
question
for
me,
but
yeah
I'm,
working
on
documentation
and
charting
things
out
and
having
a
single
source
of
Truth,
as
I
mentioned
in
previous
group
syncs.
D
D
And
if
not,
it's
I
guess
consider
this
a
call.
If
there's
a
ping
that
you've
ping
me
on
and
I
haven't
responded
in
a
couple
days.
Just
please
slack
me
that's
kind
of
the
state
of
things
right
now,
because
I'm
sometimes
I
get
stuck
in
the
infrastructure,
stuff
and
I
I
don't
get
to
my
today's
but
yeah
trying
to
make
myself
available
otherwise.
A
Oh
good
I
will
let
you
know.
We
talked
to
a
potential
customer
yesterday.
I
won't
name
them,
so
this
could
be
a
public
call
and
initially
their
feedback
was.
We
would
have
to
have
this
have
our
own
cluster
for
this,
because
it
would
be
customer
data
because
we
got
further
into
the
call,
though,
because
it
was
part
of
their
normal
Cadence
call
yeah.
A
They
were
showing
us
an
internal
dashboard,
okay,
that
they're
less
likely
to
need
to
roll
their
own
cluster
for
because
again,
their
developer
team
kind
of
looked
at
things
like
Runner
status
and
it
was
kind
of
a
pseudo
of
visual
visual,
analytics
kind
of
or
not
visual,
analytics,
Dora
dashboard,
that
kind
of
thing
for
all
their
projects.
So
they
seemed
on
board
with
instrumenting
that
nice,
okay,
so
we
are
hearing
yeah
bring
your
own
cluster
is
going
to
be
important
already,
but
it's
we're
looking
at
it
can
still
be
down
the
line.
D
A
C
D
It
was
a
that
was
a
well
I,
don't
know
which
feature
flag.
That
is,
but
we
were
trying
to
consolidate
a
lot
and
then
we
needed
to
pull
one
out
because
it
prevents
us
from
managing
things
like
gitweb.com
and
then
there's
actually
going
to
be
one
more
to
make
it
even
better
for
the
whole
snowplow
switch
everything
and
so
I'm
having
the
engineers
document
that
GDK.
So
at
least
engineering
is
on
the
same
page,
but
I
want
to
bring
that
out.
A
A
Looking
at
it,
because
that's
what's
really
going
to
make
this
product
category
successful
for
sure,
so
it
was
like
I
said
more
of
an
open-ended.
We
don't
have
to
come
up
with
a
list
today
or
like
the
next
experiment.
We
want
to
run
but
I'd
love
for
us
to
use
product
analytics
to
run
experiments
and
figure
out.
D
B
D
B
Yeah
I
think
this
is
where,
like
we're,
gonna
have
to
be
careful
about
defining
what
is
an
active
user
for
product
analytics
because,
as
you
point
out,
I
think
once
you're
set
up
with
your
dashboard,
well,
you're,
not
gonna,
create
another
event
or
I
mean
once
you
have
enough
dashboards,
it's
more
about
you
returning
to
it
or
maybe
sharing
it,
or
maybe
something
like
that,
that
we
would
kind
of
need
to
uncover
along
the
way.
So
maybe
research
could
help.
Maybe
us
instrumenting.
The
tool
itself
would
help
as
well
I
think
for
sure
yeah.
D
Any
action
really
will
be
interesting
to
know,
especially
like
how
how
inclined
are
they
to
like
edit
dashboards
and
stuff
like
that?
Existing
ones
or
you
know
I
mean
we
haven't
I,
don't
know
if
it
really
I,
don't
think
we
really
entered
that
flow
of,
like
you
see
a
pre-built
dashboard,
but
can
you
duplicate
that
and
then
customize?
That
and
like
would
people
do
that
as
a
first
step
to
like
understanding
how
custom
dashboards
work.
A
Yeah,
for
my
purposes,
the
active
users
you've
looked
at
a
dashboard
or
edited
a
dashboard
yeah,
that's
going
to
be
the
at
least
my
working
definition
through
the
alpha
and
beta
phases,
because
that
shows
us
and
then
looking
at
recurring.
That
kind
of
shows
it's
Vicky
yeah.
But
if
we
create
a
way
for
people
to
share
work
with
just
the
straight
here's,
the
URL
go.
Look
at
it
great,
like
that's
going
to
be
that's.
D
B
D
They
saw
something
from
the
dashboard
and
decided
to
take
action
on
that
to
like
help
drive
like
how
long
they're
staying
or
how
long
they're
actually
or
how
much
they're
using
the
feature,
rather
so,
but
it'd
be
really
good
to
instrument
that
with
service
ping
and
also
with
our
own
instrumentation,
to
see
like
you
know
where
our
gaps
exist.
With
you
know
our
typical
sizes,
dashboards
for
snowplow,
but.