►
From YouTube: 2023-03-22 Product Analytics PM:UX Sync
Description
Weekly sync where we discuss latest UX development, questions and ideas in Product Analytics
A
All
right,
so
this
is
the
product
analytics
PM
ux
sync
for
March
22nd
2023.,
reviewing
sticky
items,
I,
don't
see
anything
up
and
sticky.
Today,
Kevin
looks
like
you
have
the
first
agenda
item.
B
Yeah
so
I
kind
of
wanted
to
focus
a
bit
more
on
this
Milestones
priorities,
I
kind
of
rank,
some
of
the
issues
myself
so
I
wanted
to
go
over
with
you,
but
the
first
time,
I
put
was
the
juristic
evaluation
so,
like
the
smaller
version
of
the
ux
scorecard
I
basically
did
last
week
the
whole
mapping
up
of
the
flows.
B
I
have
like
most
of
it
done
so
now,
I'm
kind
of
going
through
the
process
of
using
our
heuristics
to
evaluate
them.
I'll
basically
share
this
once
this
is
done.
This
should
not
take
me
a
lot
of
time
to
do,
especially
that
it's
a
trimmed
on
version,
since
we
don't
have
the
job
to
be
done.
So
I
just
put
this
on
my
priority
number
one,
because
it's
also
a
great
way
for
me
to
get
acquainted
with
the
setup
yeah.
B
Do
you
have
any
thoughts
on
that
before
we
move
on
to
the
next
one,
all
right
cool,
then
the
other
one
is
about
adding
a
visual
indicator
to
the
dashboard
panels
when
they're
in
edit
mode
yeah,
it
seems
like
basically
when
you're
in
a
dashboard,
you
have
a
normal
State
and
an
edit
state
in
the
edit
State.
B
You
can
tweak
your
dashboard
to
kind
of
reorganize
the
layout,
and
you
can
also
add
data
sources
as
far
as
I
understand,
at
least
for
the
dashboard
that
you
own
yeah,
so
the
the
visual
indicator
is
mainly
focused
on
the
layout
structure.
Part
I
don't
expect
this
issue
to
be
like
a
big
chunk
of
work.
B
The
only
thing
that,
when
I
started
doing
the
the
evaluation,
your
second
election,
that
I
kind
of
notice
is
just
the
edit
pattern-
is
a
bit
weird
in
a
way
that
it
kind
of
combines,
like
I,
said
both
the
appearance
of
the
dashboard,
as
well
as
the
content
and
I'm,
not
sure.
If
you
really
want
to
proceed
this
way,
so
it's
either.
We
just
tackle
this
issue
as
a
okay.
Let's,
let's
do
the
small
fix
now
and
then
later
on,
we
kind
of
refine
the
door.
B
B
But
that
is
probably
a
chunk
or
a
lot
of
work
for
sure.
Yeah.
A
I
would
take
the
slim
down
amount
of
work
on
that
on
slip.
We
get
actual
data
from
customers
which,
through
the
Alpha
and
the
beta
I
might
ask
of
customers
is
going
to
be
like
30
minutes
every
other
week
with
that
on
a
thing
call
talking
about
the
issues
that
they
run
into
I.
Think
that'll
be
a
great
point
for
us
to
validate
things
that
we
think
are
ux
debt
and
acknowledge.
Yes,
they
are
and
then
pay
them
down
or
say.
A
Actually,
no
users
are
fine
with
those
experience
and
we're
just
going
to
close
that
out
make
sure
it's
aligned
with
the
rest
of
the
kind
of
platform
experience
and
move
on,
so
I
wouldn't
run
down
a
solution.
Validation
path
on
that
I'd
say
get
it
to
a
point
where
we're
happy-ish
with
it,
and
we
can
move
on
to
the
next
thing
that
adds
value.
B
Cool
and
then
yeah,
then
I
got
like
P3
D4,
so
B3.
It
would
be
the
issue
about
where
to
put
the
instrumentation
details
after
the
dashboard
of
those
things.
So
it
seems
like
this
yeah.
This
part
of
the
UI
disappeared,
depending
on
which
dashboard
listing
you're
on
to
be
honest,
I
still
need
to
kind
of
go
a
bit
into
the
weeds
of
the
different
listing,
because
I
don't
fully
understand
it
right
now.
So
that's
going
to
be
probably
like
most
of
the
complexity
of
those
issues
with
me.
B
A
Yeah
so.
B
A
Just
to
I'm
going
to
restate
it
and
make
sure
I
understand
the
issue
today,
if
you
don't
have
any
dashboards,
you
first
need
to
point
in
the
data
source.
That's
what
instrumentation
details
gives
you
once.
B
Yeah,
which
is
yeah
so
what
I've
seen
so
far?
If
I'm
not
mistaken,
is
you
once
you're?
You
have
the
instrumentation
details
at
the
beginning,
then,
once
this
is
set
up,
the
buttons
change
for
a
new
dashboard,
something
that's
right
and
then
and
then
visualization
designer,
and
then
this
instrumentation
detail
disappear.
B
A
If
so,
I'm
sharing
my
screen
real
fast
going
from
this
is
what
you
see
with
instrumentation
details.
If
you
don't
have
a
data
source
and
then
once
you
do,
it
becomes
its
visualization
designer.
So
you
can
start.
A
For
your
dashboard
off
of
your
data
source,
yeah
I
would
either
make
this
a
drop
down
of
change
data
source
or
view
data
source
edit
data
source,
something
like
that,
at
which
point
we
might
need
a
different
screen
to
show
that
or
do
the
same
thing
here.
Let
me
see
my
data
source
or
change
my
data
source.
B
A
After
that,
I
think
you
get
more
complicated
because
you
might
I
can
see.
I
want
to
look
at
data
right
now
or
this
reproduction
environment,
and
now
I
want
to
look
at
data
for
this
production
environment,
and
then
there
could
be
a
use
case
later
down
the
road.
If
I
want
to
compare
the
data
between
the
two
environmentally
like
there's
just
going
to
be
some
limitations
there,
so
I
would
go
let's
solve
for
the
you
can
change
your
data
source,
but
it
completely
changes
your
data
source.
A
We
can't
compare
I
I,
don't
know
what
that
does
then
to
the
data.
The
dashboards
I
mean
this
use
case
is
blown
up
on
the
talk
through
it.
What
do
you
think.
B
Yeah
I
mean
and
there's
yeah,
it's
a
film
like
to
understand
the
purpose
of
the
instrumentation
details
beyond
the
initial
setup,
like
I
still
need
to
grasp
this,
because
it's
not
fully
clear
to
me
right
now,
like
I,
understand
why
we
have
it
in
firsthand,
but
why
would
we
want
to
have
it
later
is
most
likely
to
tell
me
okay,
where
would
that
live
and
then
and
yeah,
just
as
you're,
showing
just
to
call
out
that
I
know,
Tim
is
also
working
on
marriage
requests
to
interested
new
flow
on
creating
a
custom,
dashboard
and
I
think
this
will
add
another
CTA
to
this
part,
which
is
like
new
dashboard.
B
A
B
Cool
yeah
and
then
I
guess
that's
about
it.
For
now,
as
I'll
pick
up
the
issue
and
then
dive
in
and
I'll
probably
have
a
ton
of
questions,
is
there
anything
else
we
wanted
to
discuss
on
this
one.
A
On
this
one,
no,
let's
try
to
keep
it
small
again
for
the
alpha,
we're
not
guaranteeing
that
we're
not
going
to
blow
away
data
as
you
go
through
things
and
I
think
that
that
extends
into
dashboard.
The
nice
thing
is
that
if
you
created
custom
dashboards,
they're
in
your
git,
history
is
yaml,
so
you
could
go
copy
paste
out
of
an
old
commit
and
recreate
it
really
really
fast.
A
If
you
change
your
data
source,
if
we
have
to
go
down
the
path
of
changing
data
source
that
leads
the
existing
visualizations
or
to
acknowledge
that
they
could
be
broken
like
if
you've
built
a
visualization
on
data
that
doesn't
exist,
yet
it
can
be
totally
broken.
B
Okay,
right
cool,
so
moving
on
to
the
other
one
which
again
like
have
value,
read
it,
but
from
what
I
understand,
there's
a
bit
more
of
a
low
structure
issue
but
yeah.
Basically,
it's
just
to
show
how
we
are
listing,
knew
that
password
or
adding
new
dashboards
I'm,
not
sure
about
that.
Actually,
that's
also
why
I
wanted
to
discuss
it,
because
the
issue
has
design
to
it.
A
I'm
not
sure,
okay.
B
B
A
A
B
A
Like
I
said
what
I
would
want
to
get
an
answer
from
from
Rob?
Is
why,
like
that
last
one,
the
analytics
data
source,
this
shows
product
analytics
and
insight,
and
then
the
standard
page
and
the
empty
the
standard
page
one
shows
value
stream
and
vipd
when
you're
on
dashboards
and
not
product
damage.
I
just
can't
understand
like
what
will
the
user
actually
see
here
like
what
data
can
they
configure
and
go
get
to
or
what
dashboards
can
they
go?
Build
based
on
this
empty
state?
A
If
you
haven't,
if
you
haven't
set
a
data
source
product
Analytics,
what
will
they
see
and
then
the
treatment
of
it
we
can?
We
can
tweak
an
align
on
but
which
I
would
actually
show
it
up
there
today,
if
I,
if
I
had
an
empty
data
source.
A
I'm
gonna
just
add
a
note
to
I'm
going
to
reread
the
issue
and
then
I'll
add
a
note
for
Rob,
just
asking
cool
or
if
he
watches
the
recording.
He
can't.
Let
us
know
that's
kind
of
more
what
the
intent
of
the
issue
is.
That's
391,
495.
B
A
I
would
I
would
focus
on
the
work
within
the
first
external
user,
epic,
first
73
MP4,
the
visual
indicator.
I
would
do
after
that
and
then
the
heuristic
evaluation,
just
to
make
sure
that
we're
continuing
to
move
towards
getting
that
Weekly
active
user
number
Beyond
zero
and
we're
going
to
gain
a
ton
of
insight
from
users
as
soon
as
we
actually
have
users.
A
It's
kind
of
fun
to
go
from
product
area,
with
lots
and
lots
of
users
where
you
don't
think
about
that
to
how
to
go.
Get
that
first
user.
How
do
we
get
more
users
right
now.
A
Cool
and
then
looking
ahead
to
next
Milestone.
B
A
Preemptively
cancel
the
call
on
or
make
it
an
eight
think,
call
I
guess
on
the
19th,
since
both
of
us
will
be
out
we'll
let
the
team
know
we'll
both
be
out
that
day
and
then
I'll
be
available
or
do
async
on
the
26th
with
anyone
who's
around.
B
And
then
the
other
one
was
yeah,
I
mean
it's
just
following
up
some
of
the
discussion.
We
had
around
building
a
job
to
be
done
for
the
stage
I,
don't
know
what
you're
feeling
on
that,
but
I
would
feel
that
we
should
do
it
sooner
rather
than
later.
A
I'm
comfy,
with
building
a
job
to
be
done.
I,
don't
want
to
go
down
the
whole
research
path
with
it,
yet
just
to
keep
that
focus
on
getting
those
first
users,
because
I
think
we're
gonna.
Just
in
the
feedback.
We
get
we're
going
to
validate
a
lot
of
assumptions
around
the
job
to
be
done
and
understand
what
they're
actually
trying
to
do
and
where
there's
value.
B
A
B
Done
there
got
it
so
do
you
feel
that
we
would
get
to
this?
Doing
I
mean
retrieving
feedback
from
the
people
that
we
open
the
solution
to.
A
Yeah
I
think
we'll
validate
that
we've
got
the
right
problems
because
those
folks,
if
we
find
that
the
problem
they're
trying
to
solve,
is
different
than
what
we
imagined.
Then
we
can.
We
can
pivot,
and
maybe
we
find
that
they're
not
trying
to
solve
with
this
problem
at
all,
and
they
just
don't
need
data
like
there's.
There's
that
realistic
possibility,
not
probability
I,
don't
think
that's
going
to
be
true.
If
we're
going
to
find
lots
of
folks
who
are
like
yeah
I'm,
not
data
informed
at
all
about
my
product.
A
I
want
to
get
data,
but
the
job
that
they're
hiring
us
to
do
could
be
I,
don't
know
what
data
to
go
get
so
I
want
you
to
really
do
that.
For
me
not
give
me
a
framework
that
I
know
the
data.
I
know
the
events
and
I
just
need
to
visualize
that
maybe
they
already
have
that
it
could
be
a
different
problem,
they're
trying
to
solve,
and
so
we
can
start
with
an
assumption
of
they
have
no
data
and
they
need
something
to
collect
data
and
visualize
data.
A
That's
what
they're
going
to
hire
us
for
great
and
and
go
from
there?
Okay
does.
B
B
I
need
to
think
about
it
because
I'm
also
like
how
are
these
goals
structured?
Do
you
know
it
yet.
A
B
A
I
haven't
thought
through
it,
yet
I'm
gonna
start
working
on
some
onboarding
stuff,
yet
this
weekend
next
week
so
that
we
have
hey
you're
you're
joining
the
product,
analytics
Alpha,
here's
kind
of
an
intro
email,
here's
the
expectations,
here's,
maybe
we
even
do
an
office
hours
thing
of
you-
can
sign
up
for
office
hours
with
Kevin
and
James
and
Dennis
reschedule
find
that
somebody
can
book
themselves
into
and
approach
it
that
way,
but
the
the
structure
I
think
is
mostly
going
to
be
follow-up
from
their
last
call
of
you
know
what
did
you
run
into
and
have
we
fixed
it
because
we
should
be
releasing
fairly
often
new
insights
that
you've
gained
from
the
product
and
the
things
you
wish
that
you
could
solve
with
the
product.
B
Yeah
I,
just
I,
just
want
to
be
careful
that
we
don't
frame
this
as
a
solution.
Validation
versus
like
problem
validation
right
because
since
we
already
have
the
solution,
I
think
we
should
be
careful
of
not
falling
into
this
kind
of
trap
of
trying
to
validate
what
we
have,
knowing
that
it
was
not
informed
by
object.
We
don't
or
by
any
research
that,
like
problem
validation
in
the
first
place,
yeah.
A
A
B
Yeah
yeah
I've
seen
I've
seen
the
playlist
I
just
came
through
it.
A
I
think
you
shared
it
with
me.
That's
where
I
found
it
yeah.
B
Yeah,
okay,
let's
yeah!
Let's
just
see
how
we
can
kind
of
structure
these
goals
to
to
frame
this.
B
A
I'll
check
in
with
Heim
as
well
and
see
how
he's
approaching
the
calls
that
they're
doing
for
the
open
beta
on
the
value
stream,
because
I
think
he's
having
some
calls
with
customers
or
meeting
with
customers
pretty
regularly
about
that.
I'll.
Take
that
as
an
action.
B
B
A
Last
thing
I
wanted
to
touch
on
is
the
funnel
visualization
and
I'm
going
to
check
in
with
Dennis
on
this
on
our
one-on-one
tomorrow
or
I'll
should
just
ping
a
thinker
in
the
channel
I've
seen
that
listed
as
part
of
our
Alpha.
A
It's
not
in
the
alpha
epic,
though
it's
in
the
post,
G8
effect,
so
I
wanted
to
get
to
get
better
understanding
on
that,
especially
since
we've
started
to
do
work
on
the
funnel
funnel
analysis
and
just
see
where
we're
at
today.
What
the
plan
is
for
that
and
just
get
alignment
on.
Is
this
part
of
the
Opera?
Or
is
it
not?
If
it
is,
then
we'll
probably
need
some
design
on
the
shooter
than
later?
Obviously,
so,
I
wanted
to
make
sure
that
it
had
your
attention
as
a
hey.
A
B
No
though
I
mean,
if
we,
if
we're
talking
strictly
from
a
visualization
perspective
and
chart
perspective,
I,
think
we're
pulling
from
a
library
that
has
it
okay.
So
we
could
use
that
yeah,
but
then
again,
what's
what
we
kind
of
need
to
Define
like
what's
the
flow
and
how
you
can
build
this
visualization
with
what
we
have
right
now,
yeah.
A
Okay,
cool
I'll
check
in
with
some
Dennis
on
that.