►
From YouTube: 2023-02-15 Product Analytics PM:UX Sync
Description
Weekly sync where we discuss the latest UX developments, questions and ideas in Product Analytics.
A
Hello,
everyone
and
welcome
to
the
product
analytics
PM,
ux,
weekly
Meetup
for
February,
the
15th.
We
have
no
sticky
items
and
also
no
action
items
from
last
week.
So
Rob
you
have
the
first
generation.
B
Yeah,
so
with
the
announcement
of
the
new
release,
schedule,
which
makes
absolute
sense,
I
want
to
just
try
and
align
ux
work
to
coincide
with
what
we
need
to
get
done
to
at
each
point
in
that
release.
Schedule,
because
anything
we
do
in
ux
realistic.
It
needs
to
be
a
good
couple
of
Milestones
ahead
of
when
we
need
to
actually
start
developing
it,
especially
on
the
front
end.
B
So
I
just
wanted
to
see.
I
know
you
Sam
and
Dennis.
B
You've
both
been
going
through
all
the
issues
trying
to
allocate
them
to
various
stages,
so
I
wanted
to
get
a
feedback
from
you
both
what
you
felt
the
ux
work
that
we
should
be
targeting
is
going
to
be
I've
listed
some
known
unknowns
like
the
visualine
solution,
designer
and
onboarding
flows
like
saving
dashboards,
visualization
flows
connecting
to
the
project
group
level,
params
that
optimize
built
into
the
back
end
and
how
the
visualization
designer
links
into
that
creating
an
editing,
dashboard
flow
funnels
the
widget,
the
configuration
of
funnels
all
that
sort
of
stuff,
plus
more
that
we
probably
don't
know
about
so
yeah.
C
Yeah,
so
on
the
the
different
feature,
States
Alpha
is
basically
our
release
where
we
want
to
share
something
with
the
world,
but
we
don't
know
if
the
feature
set
is
complete
or
not
so
a
lot
of
that's
going
to
be
trade-offs
in
terms
of
like
oh,
this
is
easy.
C
We
can
do
it
in
a
day,
let's
just
throw
it
in
or
this
is
going
to
take
a
year,
let's
not
so
so
we'll
figure
that
out
as
we
get
closer
to
Beta,
which
is
where
we
should
really
have
our
feature
set
locked
down
by
in
my
mind-
and
this
is
just
open
for
feedback
as
well.
Funnels
is
something
we
can
do
after
GA.
If
we
need
to
I'm
expecting
that
to
be
a
big,
lift
and
it'll
also
be
a
good.
C
You
know
release
number
two
where
we
can
say:
here's
the
brand
new
funnel
release
a
lot
of
the
other
items
you've
listed
there,
Rob
I
would
like
us
to
Target
for
what
ultimately
becomes
our
first
GA.
A
lot
of
these
feel
more
like
ux
polished
help.
Users
have
a
good
experience.
C
That
said,
though,
if
some
of
these
are
bigger
or
smaller,
I'm
open
and
happy
to
have
trade-off
conversations,
I,
don't
think
any
of
these
are
things
we
won't
ever.
Do
it's
just
going
to
be
a
matter
of
where
do
we
sort
of
draw
that
line
and
the
same
with
what's
Alpha
Beta
versus?
What
do
we
do
in
v23,
Etc.
B
Okay,
that
makes
sense
it's
a
few.
A
lot
of
the
things
I've
pointed
out
are
just
we
have
we
when
we
all
joined
the
team
a
while
ago,
we
had
this
vision
of
how
the
flow
would
work
from
a
user's
point
of
view
in
terms
of
going
adding
a
dashboard
and
filling
it
all
in
and
saving
it
and
then
coming
getting
it
reviewed
and
all
that
sort
of
stuff
and
obviously
right
now
we
don't
we're
missing
large
chunks
of
that
flow,
which
is
where
these
questions
came
from.
B
B
That's
fine,
so
would
it
be
fair
to
say
that
next
week
we
should
have
a
good
idea
of
what
features
we
are
we
we
want.
We
need
to
start
targeting
next.
C
Yeah
I
think
that'd
be
reasonable.
A
week
should
give
us
enough
time
to
get
things
at
least
slotted.
For
all
these
different
release,
Cycles
I
mean
we
know.
All
of
these
are
going
to
be
important
for
us
to
do
as
well.
So
I
think
if
some
of
these
aren't
already
covered
in
either
1510,
we
should
get
them
slotted
for
1511
to
be
be
worked
there
as
well.
C
Elisa
will
know
how
big
of
a
an
item
something
is,
so
we
can
really
have
a
data
driven
way
to
say.
Oh,
this
is
too
big
we're
going
to
push
it
out
or
it's
small
enough.
It's
critical
to
the
workflow
we're
going
to
pull
it
in.
B
A
There's
an
epic
for
schema,
driven
customizable
dashboards
for
product
Analytics,
which
is
kind
of
like
running
parallel
to
the
product,
analytics
Epic,
some
of
the
issues
there
covers
some
of
this
things
we
touch
on
so
I
just
wanted
to
highlight
that
to
yeah
I
think
everyone
should
just
go
and
check
out
the
issues
there.
D
Yeah
sorry
I
was
just
trying
to
like
take
a
look
at
the
listen,
try
to
quickly
like
mentally
stack
with
them,
but
I
think
that's
that's
part
of
what
stem
and
I
just
have
to
do
in
terms
of
slotting
these
and
doing
that
exercise,
but
also
how
that
would
fit
into
their
at
least
basically
repeating
what
Sam
said.
D
But
I
did
add
one
comment
that
I
wanted
to
cover
if,
unless
this
is
covered
elsewhere,
but
that
configuration
screen
I
think
we'll
need
to
create
a
home
for
that,
and
it
is
a
I
think
it's
a
Known
Unknown
whether
that
needs
to
exist
for
customer
number.
One
is
debatable,
but
I
don't
want
to
get
your
thoughts
on
that.
If
that's
something
that
we've
missed
as
far
as
what
this
agenda
initially
had.
B
The
configuration
screen
is
a
concept
we
have
the
implementation,
details,
I
low
priority,
low
hanging
fruit,
something
that
I
want
to
mock
up,
eventually,
probably
in
the
next
week
or
so
when
I've
got
a
bit
more
a
bit
of
time,
but
more
broadly,
the
configuration
screen
is
so
at
the
minute.
We
don't
have
anything
else
to
put
into
it,
because
we
don't
have
that
full
configuration
flow
that
we
haven't
even
figured
out
what
that
is
yet
right.
So
so.
A
Speaking
of
priorities,
as
Rob
just
mentioned,
one
of
those
issues
being
like
a
low
priority
change
is
there
anything
we
can
do
to
help
like
prioritize
or
with
with
the
scheduling
of
these
issues
as
they're
broken
down
into
smaller,
Milestones
or
epics?
Rather,
since,
like
everything
in
the
customer
like
currently
everything
in
in
the
customer
preview,
epic
just
has
like
the
same
priority
attached
to
I.
Think.
D
Yeah,
that's
the
exercise
that
sander
and
I
have
to
kind
of
go
through
in
terms
of
if
you
want
to
assist
with
that,
we
can
potentially
turn
it
into
just
a
group
wide
refinance
session,
where
we
are
quite
literally
reviewing
it
together,
and
you
know
your
thoughts
would
be
useless
until
you're
closer
to
the
to
the
actual
work
to
be
done
and
that
can
inform
Us
in
terms
of
priority
and
feasibility
for
each
release.
D
That's
one
way
to
do
it
or
you
know
the
alternative,
is
you
know,
Sam
and
I
can
go
through
the
exercise
and
give
it
a
first
pass
and
do
it
Ace
and
pass
it
to
y'all
y'all
async
and
you
can
see
if
there's
any
gross
item
or
items
that
are
like
you
know,
that's
a
lot
of
effort
that
may
not
make
sense
based
on
that
but
Sam.
What
do
you
think.
C
Yeah,
so
one
thing
I
think
that
would
be
really
helpful
if
you
see
any
issues
or
epics
that
are
in
there
already,
that
are
just
essentially
placeholder
issues.
If
you
wanted
to
add
any
details
or
context
and
in
the
issues
themselves,
that
would
be
helpful
or
if
you
see
things
that
are
too
big
and
we
should
really
break
them
down
into
epics.
Let's
go
ahead
and
do
that
that's
going
to
be
a
big
part
of
the
the
exercise
to
break
the
customer
preview,
epic
down
into
Alpha
Beta
Etc.
C
C
C
Because
a
lot
of
those
issues,
I
think
are
even
from
like
August
or
October
of
last
year,
when
it
was
very
much
like
we're
just
talking
synchronously.
We
just
make
an
issue
while
we're
talking
and
we
don't
forget
it
and
we
haven't
Revisited
it
since
then
so
I'm
sure
there's
lots
of
things
in
there.
That
could
do
with
a
another
review.
A
Yeah
I
was
actually
kind
of
doing
some
housekeeping
today
on
just
renaming
a
lot
of
the
stuff
that
was
still
called
Widgets
or
using
terminology
that
which
no
longer
used
and
doesn't
exist
and
I
think
it
will
be
a
good
good
thing
for
like
during
the
next
week
to
do
some
housekeeping
and
remove
some
of
those
old
issues
if
they're
no
longer
applicable,
because
it
is
kind
of
I
I
can
imagine
that
it
would
help
make
it
less
overwhelming
for
the
new
Engineers
joining.
A
And
also
I
have
the
next
agenda
item
yeah
I've
gone
through.
This
is
just
like
FY
I've
gone
through
all
the
product
analytics
epic
issues
and
not
everything
that
I
think
is
ux
related
with
a
ux
labels,
just
making
it
easier
to
find
those
and
identify
what
needs
ux
input
which,
for
the
time
being,
is
Robert
myself
then
also
I've
created
a
few
new
ux
issues.
This
is
mainly
to
resolve,
bugs
and
improve
the
ux
of
the
product.
A
Analytics
dashboard
Chief
among
them
is
to
implement
the
new
look
and
feel
design
that
mutated
for
during
the
dashboard
group
or
looking
at
how
to
do
filters.
I've
also
confirmed
with
Brandon
from
optimize
that
this
is
the
direction
that
they're
heading
in
or
planning
to
head
in.
So
we
can
go
ahead
and
do
that
and
Rob
I
see.
You
commented
there
that
Tim
has
made
some
progress,
which
is
awesome
and
I
just
wanted
to
also
note
that
I
did
check
out
his
mrnc.
B
Oh
yeah
100,
it
is
just
a
small
iterative
Improvement
towards
getting
towards
what
those
designs
look
like
more
or
less
that
he's
added,
so
yeah
I
can't
I
would
be
very
happy
if
we,
if
we
ended
up
looking
exactly
what
mate's
made,
they
are
lovely.
A
Yeah
to
totally
agree-
and
the
good
news
is
it's:
it's
not
that
many
issues
that
we
need
to
solve
that
I
think
would
will
get
our
dashboard
looking
nice
and
Polished
like
currently
it's
very
rough
around
the
edges
like
it's,
it's
good
enough
for
us
to
develop
quickly
and
trade
on,
but
I
think
with
a
few
few
of
those
issues
solved.
It
would
be
looking
very
nicely
sure.
C
D
C
Thing
we
could
do
on
the
improved
dashboard
and
panels,
look
and
feel
if
we
could
find
a
way
to
articulate
what
the
scope
of
that
is
beyond
just
using
the
word
improve
I
think
that
would
be
helpful
because
we
could
fix
a
typo
and
call
it
done
since
it's
improved
in
that
case,
so
I'm.
Looking
at
this,
these
are
you
said
in
the
taste
designs
that
he
had
put
together,
because
it
looks
like
there's
all
the
Dora
metrics
here,
as
well
as
our
stuff
mixed
in
right.
A
Yeah
so,
unfortunately,
the
design
like
includes,
like
a
bunch
of
other
things,
that
the
proposal
like
really
breaks
it
down
in
depth
like
what
exactly
needs
to
change.
I'll
I'll
update
it
the
title
to
something
that
encapsulates
the
scope
or
explains
that
a
bit
better,
specifically
about
like
what
exactly
we're
we're
trying
to
improve
here.
Okay,.
D
Yeah
freaking,
like
not
for
the
sake
of
creating
more
issues
but
separate
them
from
like
the
the
the
you
know,
spacing
versus
coloring
versus
you
know
and
further
defined
looking
field,
and
we
can.
That
will
also
help
us
in
terms
of
how
that
bounces
against
the
release
schedule
where
we
can
prioritize
some
of
those
above
others
and
yeah.
A
As
it
is,
I
actually
think,
like
it's
everything,
that's
I'm
proposing.
We
do
I
feel
like
it's
small
enough.
It
has
like
a
weight
of
two
that
I
feel
like
it
could
be
like
done
in
the
same
like
I
I'm
I'm
wondering
like
if
this
is
like
big
enough
to
break
down
into
separate
issues,
also
help
with
scheduling,
since
it's
like
quite
small,
the
the
overall
change.
B
Considering
what
we've
coded
already
and
the
second,
the
segmented
nature,
making
our
dashboard
look
like
the
design
or
progressing
towards
that
I
think
I,
agree
with
young
would
be
relatively
small
in
terms
of
line
changes.
B
You
just
have
a
big
broad
impact,
because
each
one
of
those
lines,
just
repeat,
is
generated
on
the
page
in
multiple
locations.
If
that
makes
sense,.
A
D
A
B
I
think
we
based
off
these
designs.
We
could
Implement
a
similar
style
into
the
visualization
designer,
but
more
broadly,
the
resultation
designer
needs
considerable
fault
put
into
it.
Whereas
right
now
it's
a
bit
like
what
the
dashboards
were
at
the
very
beginning
you
know
put
on
the
page
to
make
it
show
that
it
functions
and
works
effectively
and
does
what
we
need
it
to
do.
But
it
has
no
real
considerations
in
terms
of
product
and
user
accessibility
and
usability
and
stuff.
C
In
my
mind,
we're
going
to
have
to
say
this
is
V1
a
visualization
designer
really
do
the
like
formal
sort
of
ux
design,
reviews
and
everything
else
and
say
what
do
we
want
for
v2,
and
that
would
be
something
that
would
probably
take
us
a
couple
Milestones
to
say
we're
going
to
make
everything
look
exactly
like
we
want
these
designs
to
look
versus.
You
know,
we've
been
trying
to
iterate
quickly
and
get
get
to
that.
First
version
up
to
this
point,
so
I
I
think
I.
C
Think
it's
okay
for
right
now
that
you
know
we're
we're
iterating
and
Building
Things
as
we
we
think
of
them,
but
we
should
expect
that
we'll
revisit
this
in
the
future.
At
some
point.
A
Yeah,
that's
that's
exactly
like
what
I
think
or
what
I
have
in
mind.
What
I
think
will
work
with
a
visualization
designer
it's
it's
functional,
it's
just
that
it
has
so
many
like
difference,
flows
to
it
different
ways
of
accessing
multiple
things
like
You're,
designing
things
for
cracked
events
for
sessions
for
Unique
users,
potentially
also
funnels
each
of
these
are
kind
of
like
unique
in
a
way
you
have
like
the
different
visualizations
in
it.
A
D
Right
again,
as
I
was
saying,
based
on
the
proposed
solution,
since
it's
largely
with
font
sizes,
colors
and
padding,
that
was
that
was
purely
what
I
was
analyzing
it
from
not
from
is
this
from
a
ux
flow,
the
right
thing
or
not?
Yeah.
A
I
am
busy
reviewing
a
visualization
designer
update.
That's
that's
made
so
I
will,
while
I'm
looking
at
that,
like
just
kind
of
see
if
it's
going
to
be
feasible
to
apply
these
changes
to
the
visualization
designer
and
I'll
create
issue
for
that.
A
Right
with
that.
The
next
item
is
private,
so
I'll
wave
goodbye
for
the
recording.