►
From YouTube: 2023-03-29 Product Analytics PM:UX Sync
Description
Weekly sync where we discuss latest UX development, questions and ideas in Product Analytics
A
This
is
the
product
analytics
PM,
ux,
weekly
sync
for
March
29th,
starting
at
with
the
agenda.
The
review
of
the
sticky
items.
I,
don't
see
anything
in
sticky
items
so
moving
right
along
to
you.
Looking
back
at
last
week's
action
items
earlier
this
morning,
I
can't
hold
the
call
for
the
week
that
we're
both
on
PTO
and
left
the
call
for
the
week
that
you're
on
PTO
but
I'm
back
in
case
there's
any
issues
that
front
end
wants
to
discuss,
but
otherwise
it'll
just
be
async
and
we'll
catch
up.
A
When
you
get
back
with
everything,
I
wouldn't
worry
about
anything
there
and
then
I
added
to
do
to
check
in
with
other
PMS
about
how
they
structured
their
check-ins
with
customers
during
the
album
beta,
Heim
and
I.
Who
is
doing
that
on
the
optimized
side?
I'll
actually
meet
later
today,
so
I'll
talk
I'll,
add
a
note
back
to
either
the
agenda
or
I
started
a
issue
about
onboarding
and
AD
configuration
into
that
so
that
we
have
that
ready
to
go
and
long
term.
A
I'll
move
that
over
into
internal
handbook
kind
of
here's,
how
we're
going
to
run
the
beta
product.
Analytics
and
then
funnel
visualization
I
wanted
to
follow
up
on
that.
I
think
I
made
that
an
agenda
item
but
I'm
just
going
to
jump
on
it
now,
because
I
was
not
really
an
action
item
but
kind
of
an
action
item
of
how
we're
going
to
proceed
to
that
and
talking
with
Dennis
about
it.
A
I
think
the
plan
that
was
that
not
written
down
anywhere
was
the
initial
visualizations
there's
going
to
be
a
line
chart
of
like
visits
or
events
on
this
page
and
then
the
page
and
then
this
page
and
then
this
whole
visualization.
That
actually
looks
like
a
funnel
we'll
do
Post,
GA
or
leading
up
to
ga,
but
the
perfect
condition
for
that
would
be
a
line
chart
not
a
they're
a
column
chart
and
that
rather
not
a
line
chart
but
yeah
all
right
station.
A
A
B
Yeah,
so
not
so
much
yet,
because
I
was
kind
of
wrapping
up
the
other
issue.
I'm
working
on
so
yeah
I
remotely
followed
the
conversation
and
yeah
I
just
dropped.
Like
a
quick
comment
about
I
mean
it
was
like
where's
this
list.
Should
this
be
a
configuration
somewhere
in
the
app
or
something
that
we
kind
of
keep
locally
scoped
to
product
analytics
if
I'm
memorizing
this
well
I'm,
more
leaning
toward
keeping
it
in
product
Analytics?
A
Yeah
I
think
to
Dennis's
Point.
We
don't
have
any
other
external
data
sources
right
now,
so
configuring
a
data
source
is
required
for
any
of
the
other
things
that
will
show
up
in
analytics
as
a
whole
umbrella
product
analytics
is
the
only
one.
So
we
keep
that
product
analytics
for
now.
We
can
move
it
at
some
point
and
make
it
a
more
generic
thing
of
their
external
data
source,
product
analytics
and
X,
Y
and
Z.
A
If
we
get
there,
okay,
cool,
awesome,
I
think
the
the
most
confusing
part
for
me
of
all
of
this
is
all
of
these
are
put
into
that
they
Milestone,
but
some
of
them
are
design
issues.
Some
of
them
are
implementation
issues,
but
we're
asking
design
questions
about
a
lot
of
them
ends
up
like
wait.
Why
did
we
do
this
if
this
other
issue
just
undoes
that
later
like
in
the
same
Milestone,
so
that
was
yeah
just
might
hold
up
mentally
for
that
cool?
A
And
you
just
make
sure
that
the
latest
comment
on
that
where
to
put
instrumentation
issue
is
for
the
Alpha
of
the
first
user,
we're
going
to
keep
it
contextual
to
product
analytics
and
then
we'll
continue
to
discuss
with
the
other
teams
that
have
dashboards
if
they
have
external
data
sources,
how
to
configure
those
and
we'll
make
it
a
generic
solution.
At
that
point,.
B
Got
it
right,
yeah,
so
yeah,
that's
also
something
in
terms
of
how
do
we
wanted
this
to
look
like
notes
know
what
what's
going
to
be
the
final
usage
of
it.
So
that's
something
that
I've
still
yet
to
figure
out,
because
I'm
thinking
out
like
this
is
going
to
be
my
next
stop
this
issue,
so
yeah
we'll
go
a
bit
more
granular
this
stuff.
A
Yeah
I
think
that's
been.
The
hardest
part
is
that
we
have
a
lot
of
things
that
could
it
could
potentially
look
like
and
we're
making
some
guesses
a
little
bit
about
what
else
is
going
to
be
there
and
available
I
like
if
we
can
put
it
through
the
lens
of
what
are
we
going
to
do
for
the
first
user
from
product
analytics
perspective,
always
like
that?
B
So
I
actually
just
finished
it
I
just
uploaded
the
video
to
YouTube
to
still
processing
but
I'm,
going
to
share
this
with
the
team
probably
later
today
when
it's
going
to
be
finished,
when
people
can
actually
actually
access
it,
but
yeah
so
I
basically
generated
like
a
few
stuff.
So
the
first
thing
was
the
heuristic
evaluation
and
then
an
experience
map
so
which
is
kind
of
mapping
the
different
steps
I
went
through
and
kind
of
threaded
down.
My
thoughts
on
that
yeah.
B
So
I
guess,
the
the
probably
my
biggest
grip
with
getting
started
was
just
like
the
initial
inverted
steps,
which
are
three
Goods
in
a
way
like
the
initial
empty
state,
is
pretty
good,
but
the
fact
that
it
kind
of
processed
like
you
have
a
loader
once
you
click
it
and
then
you
end
up
on
the
actual
instructions.
I
thought
it's
something
that
we
could
have
kind
of
trimmed
down.
B
So
there's
something
I'm
kind
of
calling
out
and
then
the
other
thing
is
when
you're
on
a
dashboard.
The
edit
pattern
is
a
bit
raw
I
would
say
for
now,
because
it's
very
different
from
what
we
have
across
the
app.
So
usually,
when
you're
in
an
edit
mode
and
in
some
kind
of
view,
you
have
either
a
drawer
or
a
model,
but
something
that
comes
to
Overlay
the
UI,
and
here
it's
directly
embedded
so
like,
if
you
click
edit
you're,
not
sure
in
edit
mode,
but
the
CTA
changes.
B
A
A
B
Yeah
for
sure
and
yeah
and
then
another
designer
I
think
it
was
the
end
of
the
flow
or
and
I
guess
it's
probably
because
we
haven't
built
the
whole
functionality
yet,
but
once
you
picked
all
of
the
metrics
and
the
dimensions
and
that
you're
ready
to
add
to
dashboard
to
your
dashboard.
Sorry,
if
you
add
it
to
your
dashboard,
then
it's
just
showing
you
the
code
tab
of
digitalization
and
then
it's
like
okay
can
I
deal
with
it.
B
So
I
was
like
wow
I
thought
this
is
going
to
add
it
to
a
dashboard.
I
was
expecting
since
it's
living
higher
up
in
the
arc
that
I
would
get
prompt
of
like
okay.
Where
do
you
want
to
put
it
now
so
I
guess
there
are
two
things
here
to
unpack
as
the
first
one
is.
Do
the
visualization
designer
needs
to
live
in
such
a
high
place,
as
in
I
would
assume
that
people's
workflow
is
oh
I,
want
to
add
a
video
Safe
into
my
dashboard.
B
So
first
I'm
going
to
go
into
my
dashboard,
then
I'm
going
to
have
the
visualization
and
then
the
second
thing
is
like
yeah.
The
the
flow
doesn't
seem
to
be
fully
functional
yet
because,
if
I
click
on
that
two
dashboard
I
would
expect
it
to
be
added
to
a
dashboard
but
yeah.
That's
that's
two
of
the
big
things
that
I've
noticed
and
then
the
rest
is
like
small,
visual
tweaks
or,
like
simple
components,
change
that
we
can
do
to
better
fit
what
exists
in
gitlab
already.
A
A
So
if
we
can
do
that,
it
makes
me
more
comfortable
with
hey.
Let's
pull
that
forward
in
our
progression,
because
right
now
it's
not
planned
as
part
of
our
first
external
user
or
Alpha,
so
it
if
we
can
get
it
to
a
point
where,
like
hey,
here's,
how
you
would
start
to
design
a
panel
within
your
dashboard
through
this
tool
over
here
and
then
kind
of
help,
those
users
kind
of
babysit
them
through
it
a
little
bit
or
handle
them
through
it
once
they
get
it.