►
From YouTube: Product Analytics PM/UX Sync 2023-05-24
Description
Today we had a quick sync discussion about faster solution validation, what's next for the custom dashboard flow and validating the visualization designer after that.
A
The
weekly
PM
ux
I
think
for
product
analytics
for
May
24
2023.,
so
take
a
peek
at
the
sticky
items.
First,
do
you
want
to
look
at
as
we
revive
the
looking
at
latest
prototype
or
what
we're
validating,
I
think
dashboard
design
is
the
latest
thing
that
we're
doing
if
you
want
to
take
a
peek
at
that
today,
at
the
very
input
that
you
need
from
me,
or
should
we
talk
about
what
is
the
next
step
in
getting
that
validated
and
moving
forward.
B
B
Yeah,
so
the
thing
is
I
think
we've
been
discussing
in
the
research
issue
around
how
we
wanted
to
validate
and
what
we
wanted
to
get
out
of
our
study,
and
this
is
where
I'm
I'm
kind
of
not
necessarily
blocked
but
like
I,
think
we
really
need
to
pin
down
what
we
want
to
get
out
of
it.
For
me
in
order
to
stop
building
it,
the
build
time
shouldn't
be
so
long
and
we
already
have
a
direction
because
we
started
talking
into
the
into
the
issue,
but.
B
A
What
I
want
to
get
out
of
this
exercise
is
instead
of
just
saying
hey.
We
think
this
is
the
next
right
thing
to
build
and
we're
not
going
to
talk
to
a
customer
about
it
before,
but
do
a
solution.
Validation
pass
through
it,
but
streamline
that
process,
because
I
think
that
we,
our
best
opportunity
to
make
this
successful,
is
to
move
very,
very,
very
quickly
faster
than
we're
used
to
moving.
And
it's
going
to
be
uncomfortable
for
all
of
us
of
not
feeling
like.
B
A
A
So
it's
it's
moving
different
than
we're
used
to
moving
it's
moving
faster
and
we're
used
to
moving,
but
I
think
that
we
have
an
opportunity
to
really
treat
this
group
as
a
startup
and
move
out
and
break
things
for
lack
of
a
better
pair
in
a
way
that
still
gets
us
some
customer
feedback
before
we
launch.
So
that's
that's.
My
ultimate
goal
is
to
let
us
move
back
with
a
little
bit
of
validation.
B
A
I
think
yes,
yeah
I
think
that
we
get
desirability
through
a
combination
of
inputs,
of
hey
our
users
uploading
these
things.
Hey!
Does
the
a
solution
like
this
match
up
with
a
problem
that
we've
heard
from
a
customer
like
in
those
conversations,
I
think
that
really
what
is
going
to
enable
this
is
how
do
we
talk
to
two
or
three
or
four
customers
every
single
week,
whether
it's
internal
or
external
and
say
Here's?
Here's
what
we
just
released?
Have
you
been
able
to
use
it?
A
Yet,
if
not,
let's
walk
through
it
and
try
to
solve
a
problem
together
that
you're
experiencing
that
you
have
used
it?
What's
your
feedback
right,
here's
the
next
thing
that
we're
going
to
go
build
based
on
the
feedback
that
we've
heard
over
the
last
couple
of
weeks.
Here's
a
potential
solution
for
it
and
that's
not
to
say
that
that's
like
checking
the
box,
but
now
we're
going
to
go
build
that
thing.
If
we
get
tangible
feedback,
that's
like
yeah,
that's
not
usable!
That's
not
my
workflow
at
all!
I!
A
Don't
know
where
to
get
that
data
or
I,
don't
know
what
you're
trying
to
tell
me
great,
we
iterate
on
it
and
then
it's
a
nice
rapid
cycle
for
us
to
go
back
and
talk
to
the
next
set
of
customers
and
go
back
to
that
same
customer
and
say:
okay,
we
took
your
feedback
based
on
that.
We
revise
this
to
this
different.
What
do
you
think
about
it.
B
B
It
obviously
like,
in
my
mind,
right
now,
like
I'm
having
a
hard
time
to
kind
of
put
it
into
the
boxes
right,
because
it's
out
of
the
box
but
I
guess
the
tool
that
would
probably
have
was
the
most
would
be
rapid
iterative
testing,
as
we
initially
felt,
but
let's,
let's
also
discuss
it
with
the
team
and
then
see
what
people
are
saying.
But
if,
if
I
follow
your
logic,
I
think
it's
probably
the
best
tool
we
can
use
and
yeah.
If
the
process
is
not
perfect,
I
guess
that's!
That's
it
yeah.
A
I
want
us
to
get
closer
to
the
model
that
we're
using
as
a
company
on
the
AI
experiments.
Then
what
we're
used
to
doing
like
when
I
hear
study,
my
brain
immediately
goes.
Okay,
great
we're
gonna,
have
results
with
Bixby
and
that's
just
way
too
slow
for
the
pace
that
we
want
to
move
per
product
because
I
don't
think
we
win
by
going
slow
unless
we're
getting
features
and
value
out
there
quickly,
like
there's,
not
a
compelling
reason
for
a
customer
to
move
over
or
to
try
the
try.
The
product.
B
A
And
that's
where
I
think
that
getting
that
first
customer
feedback
of
yeah
does
this
actually
solve
a
problem
you
actually
have
and
Engineering?
Is
there
to
listen
as
well
and
hear
what
what
can
we
build?
How
fast
can
we
build
this?
What
do
we
need
to
do
to
reduce
scope,
and
then
you
can
move
forward
with
it
I
think
all
three
of
us
have
to
get
involved.
A
A
Talk
about
hey
here's
audience,
dashboard,
here's
Behavior
dashboard
as
you're
going
to
see
them
there's
other
ways
to
build
the
dashboard,
though,
and
here's
the
flow
that
we're
thinking
about
if
you're
not
getting
the
data
that
you
want
out
of
those
two,
because
you
have
specific
questions
about
phpus.
That
I
think
we
can
kind
of
talk
through
building
a
specific
visualization
for
it
and
plotting
it
onto
a
custom
dashboard
through
the
prototypes.
B
A
A
B
A
It's
not
just
the
shopping
cart.
Well,
it's
just
a
classic
example
and
having
a
little
bit
Commerce
background,
like
that's
the
flow
for
me,
that
makes
sense
so
I
gotta
come
up
with
a
different
description
for
that,
as
we
talk
to
more
and
more
internal
tools
and
devops
tools,
kind
of
folks
I
think
we
can
do
there.
B
A
A
B
I
yeah
I'm
sure
your
thoughts
on
the
Bell,
like
the
visualization
designer,
is
probably
something
that
we
want
to
tackle.
At
least
to
me
when
I
went
through
the
flow
I
felt
that
there
were
a
few
things
that
we
could
improve
in
terms
of
like
interaction.
So
like
the
way
you
pick
your
metrics
and
your
Dimensions
like
we're
gonna
have
this
longer
list
of
metrics
and
dimensions
and
I
think
like.
A
B
A
Let's
say
moving
from
three
to
two
makes
some
sense
for
me.
As
far
as
like
picture
pick,
your
metric
picture
pick
your
groupings
pick
your
visualization,
here's
what
it
looks
like
then
the
safe
flow
I
think
at
some
point
that
list
of
potential
metrics
does
get
really
really
long,
and
so
switching
that
from
here
is
just
a
list
of
all
the
things
to
like
a
searchable
or
a
drop
down
that
like
autocompletes,
might
be
a
better
way
to
go.
A
A
B
A
In
like
I
want
to
look
at
this,
but
I
want
to
filter
it
to
like
if
this
was
actually
a
list
of
a
thousand
pages
and
I
know
that
so
actually
get
rid
of
page
title
and
give
me
pagepath
and
I
knew
that
all
of
the
pages
that
I
cared
about
looking
at
were
in
the
specific,
have
the
specific
snippet
of
URL
and
I
wanted
to
filter.
For
those
like.
B
A
Is
another
dimension
that
we
would
want
to
add?
We
don't
have
that
today,
but
that
might
come
out
in
our
chat
with
Jeremy
tomorrow,
as
he
was
talking
about
specific
bits
of
navigation
that
he
wanted
to
track
on
the
pajama
site.
But
then
taking
this
visualization
thing
and
adding
it
back
over
here.
Is
that
what
you're
thinking
like
for
first
step.
B
A
B
B
A
A
A
Let's
get
it
in
front
of
like,
as
is
let's
get
it
in
front
of
some
users,
just
get
some
additional
feedback
and
see
what
they
think,
but
I
think
that
cleaning
up
this
this
flow
makes
sense.
Is
the
next
thing
to
go
to
getting
this
a
little
more
polished
so
that
people
can
explore
and
save
data
I
like
where
we're
going
with
the
flow
of
add
data
visualization
and
then
be
able
to
add
it
to
a
custom.
A
A
A
B
A
A
In
a
time
that
everybody's
core
hours
or
open
hours
working
hours
and
that
we
were
all
free,
so
hopefully
you
can
attend
if
not
I'll,
definitely
record
it
and
I'll
mention
to
the
team
in
Black
here
in
a
minute
that
we're
meeting
up
with
an
internal
customer
if
they
want
to
join
and
listen
in
as
well
cool,
awesome
great
all
right.
All
right,
thanks,
Kevin
have
a
great
day.
You
too
see
you
cheers.