►
From YouTube: 2023-04-12 PM:UX Sync
Description
Weekly sync where we discuss latest UX development, questions and ideas in Product Analytics
A
And
this
is
the
product
analytics
PM
that
ebooks
weekly
sync
going
looking
at
the
agenda.
It
doesn't
look
like
we
have
any
sticky
items
to
review,
and
last
week
we
didn't
have
any
call-out
action
items
between
Kevin
and
myself
so
jumping
into
Kevin.
You
have
the
first
discussion
point.
B
Yeah
I,
as
I'm,
going
to
be
out
for
a
bit
I
just
want
to
kind
of
discuss
the
direction
for
the
customize
layout
issue.
So
essentially,
I
worked
a
bit
on
some
first
round
designs.
B
I
think
the
bulk
of
it
is
I
mean
the
direction
is
set
because
we
had
a
few
back
and
forth
and
the
issue
already
but
yeah.
What
I
would
like
us
to
kind
of,
not
necessarily
in
this
meeting,
but
at
least
you
know
in
the
next
few
days,
slash
weeks,
maybe
a
bit
less
than
weeks,
but
kind
of
Define
like
what
what
direction
we
want
to
pursue.
It
seems
like.
B
Ideally,
we
at
least
what
I
proposed
was
that
we
decoupled
the
customization
option
from
the
current
edit
object
so
like
for
context
when
you
are
editing
a
dashboard.
Currently
you
have
the
option
to
view
the
codes
or
cancel
your
edits
and,
while
you're
in
this
edit
State,
you
can
also
reorder
and
resize
paddles,
and
this
issue
is
about
kind
of
adding
some
visual
indicator
that
you
can
also
rearrange
and
resize
panels.
B
So
my
approach
to
it
was
to
kind
of
take
a
step
back
and
I
thought
that
we
could
actually
make
these
two
separate
things
so
like
editing
the
content
of
your
dashboard,
so
be
that
the
charts
or
any
type
of
data
that
you
want
to
add,
in
my
opinion,
for
now
to
be
kind
of
separated
from
actually
being
able
to
customize
the
layout,
so
I
would
say,
like
content
and
cosmetic
should
be
two
different
things.
B
That's
that's
my
overall
ID,
so
I
worked
on
some
quick
design
on
what
that
could
look
like
moving
the
customization
out.
Thank
you,
James.
Sorry,
let's
focused
on
talking
but
yeah.
B
So
basically
the
it
reads
from
top
to
bottom:
I
expanded
a
bit
on
the
different
changes
in
the
threads,
but
the
gist
is
that
we
would
pull
the
customization
out
of
edit
and
make
it
very
visible
in
this
Sub
menu
that
you
see
on
the
very
first
frame
yeah
here
and
then,
when
you
click
on
the
customize
layouts,
you
then
trigger
this
kind
of
customized
mode,
which
is
the
second
frame
right
below
and
yeah.
And
then
what
you
could
see
here
is.
Maybe
you
can
zoom
in
a
bit.
B
James
is
that
there
are
two
at
least
three
main
changes.
The
first
one
is
that
we
would
kind
of
update
the
cursor
when
you're
hovering
on
a
panel.
B
So
right
now
the
cursor
is
normal.
With
those
changes
it
would
be
kind
of
grab,
I
think
it's
yeah
grab
to
show
you
that
you
can
actually
reorder
some
of
these
and
then
the
second
thing
is
that
we,
the
resize
icon,
currently,
is
only
available
on
Hover,
so
the
ID
here
would
be
to
have
it
permanent
when
you're
in
this
customized
mode,
as
opposed
to,
however,
currently-
and
the
third
changes
would
be
to
add
a
toast
so
on
the
bottom
left.
B
So
then,
once
you
click
on
Save
changes,
you
can
kind
of
save
whatever
layout
changes
you
did
to
your
dashboard.
So
that's
that's
the
gist
of
it.
B
Where
I
think
it's
probably
worthy
of
us
to
discuss
technical
implementation
is
about
kind
of
moving
the
customization
functionalities
from
where
they
are
currently,
which
is
in
the
edit
mode.
So
when
you
click
on
edit
yeah
this
edit
button,
you
have
access
to
it,
so
my
ID
would
be
to
kind
of
move
them
out
of
them
and
I'm
wondering
how
much
work
this
is.
So
this
is
something
that
we
could
discuss
with
the
engineering
team
and
then,
depending
on
that,
we
could
kind
of
decide
how
we
want
to
chunk
this
out.
C
Yeah
so
I,
maybe
I,
missed
in
the
beginning,
like
what
is
the
advantage
of
separating
out
the
Cosmetic
from
the
content
in
terms
of
editing
functionality,
because
now
we
will
effectively
have
two
edit
modes
right.
B
Yeah,
because
I
think
what
we
want
to
do
with
the
edit
mode
is
going
to
be
much
more,
that
what
we
can
do
now
and
I'm
afraid
that
kind
of
correlating
both
is
going
to
be
really
tricky
to
handle
in
the
future
is
in
terms
of
UI,
and
one
thing
that
I
kind
of
check
out
was
how
others
so
there's
a
whole
thread
on
not
not
necessarily
competitors
but
like
how
other
products
do
it
and
what
you'd
see
is
like,
usually
editing
the
content
and
Visually
editing
a
grid
or
a
dashboard
is
separate
and
I.
B
C
Yeah
I
can
I
can
see
that
perhaps
I
guess
because
So
currently
how
it
works
and
we're
still
working
on
getting
this
stuff
merged
in,
but
like
our
as
you've
seen
from
demos
from
Tim
and
others,
but
like
the
dashboard
and
visualization
editing
experience
kind
of
bundles
that
all
together
right.
So
you
can
add
a
new
panel
with
existing
visualizations
or
new
ones
and
then
customize
the
parameters
of
that.
And
then
you
know,
visual
like
organize
and
arrange
and
resize
the
panels,
as
you
see
fit
kind
of
all
in
one
place.
C
C
Yeah,
it
would
be
yeah.
We
would
need
to
know
how
that
flow
looks
like
in,
like
the
the
dashboard
and
visualization
designers,
to
be
able
to
actually
assess
like
how
much
work
that
would
be
to
pull
it
out.
A
B
C
Yeah,
so
right
now
you
can,
like
you
know,
add
so
for,
like
the
dashboard
designer,
for
example,
like
you
can
yeah
the
visualization
designer
maybe
doesn't
make
as
much
sense,
because
that's
where
you're
just
defining
the
parameters
of
like
the
data
to.
A
C
From
a
user
perspective,
if
it's
like
I
find
it
I,
I
guess
I'm,
just
that's,
maybe
a
subjective
opinion
of
like.
Is
it
more
convenient
to
be
able
to
add
panels
and
resize
them
in
one
experience
or
do
I
have
to
add
them
first
and
then
click
edit
layout
to
then
go
into
the
different
edit
experience
which
yeah.
A
C
A
Combining
or
taking
the
treatment
of
when
you
click
edit,
you
always
see
the
resize
which
you
don't
get
today
and
you
get
the
different
the
grabby
hand
to
rearrange
things
like.
Let's
take
that
part
of
it,
so
that
when
you
click
the
edit
button,
those
things
happen
and
then
leave
the
red
where
code
is
still
and
edit
only
or
read
only
rather
yeah,
because
yeah.
C
A
Then
we'll
get
more
feedback
as
visual
visualization
designer
rules
out
and
people
are
actually
using
the
dashboards,
even
if
that's
internal
dog
fooding,
as
we
get
more
people
creating
dashboards
they're,
going
to
give
us
that
feedback
of
it's
non-intuitive,
how
I
need
to
edit
or
add
or
create
these
things
just
to
give
us
a
little
bit
more
space
to
merge
them
together.
Instead
of
creating
a
different
experience.
Now
that
we
have
to
tear
apart
yeah.
C
Because,
instead
of
because
I
understood
the
issue
like
James,
you
mentioned
of
like
just
signaling
to
the
user
that
they're
in
a
more
the
pronounce
edit
mode,
so
they
actually
know
that
they're
able
to
do
stuff.
But
now
we're
introducing
like
a
second
edit
mode.
Almost
so
I
feel
like
that's
a
little
bit
confusing.
So.
A
If
we
take,
are
we
okay
with
let's
take
the
treatment
of
hover,
gives
you
the
different
pointer
and
always
show
the
resize
after
you
click
edit,
but
we'll
leave
the
edit
button
is
the
thing
that
does
that
action
as
opposed
to
creating
a
drop
down
that
does
it.
B
Yeah
so
I
mean
the
DropZone
is
probably
something
that
we're
going
to
introduce
with
the
instrumentation
details,
so
that
would
already
be
taken
care
of,
but
that's
not
the
bulkiest
part
of
it
so
yeah.
For
me,
it
sounds
good
to
start
with,
like
a
smaller
iteration,
just
kind
of
fixing
the
the
affordance
of
resizing
when
you're
in
edit
mode
and
then.
A
B
As
we
go
through
user
research,
kind
of
have
a
bit
more
input
on
how
we
should
structure
this
edit
mode
overall.
A
Kevin,
can
you
leave
comments
on
the
design
to
reflect
that
and
I'll
update
the
proposal
in
the
issue,
so
yeah
forward
is
but
get
it
get
the
new
treatment,
but
we're
not
going
to
do
the
change
layout.
Part
of
things.
A
Cool
since
we
have
a
couple
extra
minutes,
I
also
wanted
to
talk
through
the
other
issue
that
was
in
your
coverage
issue
Kevin,
that's
determining,
but
the
instrumentation
detailed
I
think
we
settled
on
a
solution
for
that.
We're
going
to
put
it
into
the
settings
general
for
this
yeah
and
we
have
an
issue
for
that
already
in
160.
I
think
the
designs
just
need
moved
over
to
that
new
issue.
B
Yeah,
cool
and
yeah,
okay,
so
yeah
now
that
we're
gonna
set
on
this
design
is
ready.
I
generated
some
specs.
It's
linked
to
the
issue,
so
yeah
I
think
we're
good
to
go
copy.
It
was
reviewed
as
well,
so
very
good.
Awesome.
A
C
Out
which
issues
so.
C
Yeah
I
created
a
bunch
of
new
issues,
so
they
might
not
be
slotted
in
yet
we.
A
Have
this
issue,
which
is
just
figure
out
where
to
put
this
stuff,
it's
blocked
by
two
issues
that
are
in
the
backlog
and
then
this
in
turn
block
slash,
is
related
to
the
implementation
issue
of.
Let's
add
that
instrumentation
data
into
the
general
settings.
C
A
B
This
is
correct:
silly
yeah,
so
next
week,
I'm
out
the
week
after
I'm
out
I'm
out
until
the
30th,
okay
and
then
I'll
be
back
Monday
5th
of
May,
but
I'll
be
in
APAC
time
zone.
So.
A
Yeah
cool.
If
we
need
to
change
the
call
TimeWise,
we
can
take.
B
While
you're
an
apex,
yeah
yeah
I
have
no
idea
how
that's
going
to
pan
out
with
the
time
zone,
but
yeah
I
guess
we
can,
we
can
see.
Otherwise
we
can
always
do
async,
but.
A
Well,
I'll
talk
to
you
before
then
have
a
great
trip.