►
From YouTube: 2023-08-02 Product Analytics UX/PM Sync
Description
Today we what on the upcoming roadmap will need UX support, reviewed the MVC for Dashboard designer and the bigger vision.
A
B
Not
necessarily
so
I've
tried
to
keep
it
kind
of
short-term
Focus,
rather
than
dropping
all
of
the
UIC
views
that
we've
created
yeah
but
yeah.
If
you
or
anyone
in
the
team
have
you
know
strong
thoughts
about
what
we
should
be
prioritizing
like
feel
free
to
to
chime
in
so
I
can
kind
of
reorder
but
yeah
this
this
transition
issue
is
going
to
be
for
the
person
kind
of
coming
up
and
joining
products
analytics
to
replace
me
so
yeah.
B
A
B
A
A
So
as
I'm
calling
it
out
as
hey
waiting,
ux
Health
here
and
that's
going
to
immediately
jump
to
the
top
of
the
priority
load
like
any
additional
feature
set.
Beyond
default
dashboards
is
going
to
take
a
back,
beat
to
making
sure
that
billing
is
Rock
Solid
and
then
things
that
we
could
work
on
later.
That
we
talked
about
a
little
bit
are
funnel
visualization,
editor
previous
to
the
editor
dashboard
or
the
dashboard
editor
experience.
Where,
once
you've
saved
a
dashboard,
you
go
back
in
and
make
more
changes.
A
A
Done
your
initial
scorecard,
but
that's
requires
we
got
it
and
then
yeah
data
filters
within
those
dashboards.
So
starting
to
think
about
which,
like
as
we
think
about
do,
we
apply
filters
for
audience
to
things
on
Behavior
type
dashboards
or
you
want
to
start
the
filter
for
the
environment
that
this
is
deployed
to
if
you're
collecting
metrics
for
multiple
environments.
B
A
Agent
is
one
that
we've
already
started
to
talk
about
other
things
like
that
where,
where
the
solutions
that
might
solve
for
pain
points
customers
have
so
those
are
the
big
things
that
I'm
thinking
about
from
a
roadmap
perspective
implementation
perspective
that
we're
going
to
need
ux
assistance
with
in
the
next
year
against
the
12
months.
Even
probably.
B
All
right
yeah
for
sure
this
sounds
like
big
chunks
of
work,
so
we
can
out
I
can
or
you
can
as
you
want.
We
can
definitely
add
this
to
the
issue
so
that
there
is
a
like
a
long-term
plan
as
well.
Actually
so
maybe
you
can
have
a
like
a
different
table
to
add
all
of
these
and
then
in
terms
of
prioritization
yeah
I.
Think
I
mean
I'm
curious
to
hear
your
thoughts,
but
like
I'm
thinking,
visualization
designer
should
go
before
the
editing
experience
of
the
dashboard
Maybe
and
then
the
funnel
part.
B
What
I'm
thinking
is
basically
the
the
visualization
designer
and
how
to
build
those
digestion
should
be
good
before
we
introduce
new
option
to
create
visualization
to
the
funnel
right.
That
would
put
it
maybe
higher
than
than
the
funnel
and
then
yeah
usage
quota,
I
I
think
you
know
we
talked
about
it.
That
is
pretty
critical.
Before
we
launch
we
need,
we
really
need
it.
B
A
I
mean
it's
a
core
feature,
but
it's
not
what
we're
going
to
launch.
It's
not
required
for
the
ga
launch.
Okay,
so
we're
going
out
the
door.
The
the
required
features
are
the
default
dashboards.
Anything
beyond
that
is
great
and
we'll
keep
building
functionality,
but
that's
the
bare
minimum
that
we're
going
to
launch
with.
So
that's,
okay
ready
to
go.
B
A
A
Yeah
and
the
direction
page
and
all
the
epics,
like
everything
all
the
other
artifacts,
should
probably
service
their
single
source
of
truth,
because
there's
going
to
be
some
lag
between
your
latte
and
when
we
get
somebody
into
the
world
yeah
even
at
a
coverage
capacity.
I'd
imagine-
and
this
will
probably
get
out
of
date,
real
fast,
so
or
we'll
Point
them.
Probably
at
Direction
page
is
your
true
single
source
of
Truth
for
what
is
next
and
why?
Because
that's
always
the
source
truths
requested
X
and
Y
EP
all
right!
B
A
B
Can
jump
on
the
MVC?
Let's
do
it
yep
right,
so
yeah
so
I
think
we're
on
track
with
basically
having
a
set
version,
maybe
not
like
fully
fleshed
out
in
terms
of
you
know
all
of
the
flows
branching
and
the
interaction,
but
at
least
like
a
good,
solid
overview
of
where
we
want
to
go,
and
we
have
the
MVC
that
is
coming
out
of
this.
We've
had
like
a
few
conversation
in
the
design
with
with
the
team.
I
guess.
B
B
B
Yeah
and
the
other
thing
about
the
resize
is:
how
do
we
do
it
because,
like
in
my
mind,
I
think
it
was
kind
of
important
to
not
have
it
as
well,
like
always
visible
on
the
panel
when
you
have
it,
but
to
kind
of
trigger
it?
Just
like
you
triggered
the
edit
mode
on
your
dashboard,
but
the
way
it's
built
currently
is
that
I
think
whenever
you
add
a
panel,
you
can
resize
it
directly.
A
A
A
So
yeah
I
can
do
that
today.
So
this
is
basically
what
we've
done
is
I'm
going
to
fix
both
the
edit
screen
as
a
dashboard
designer
with
the
ability
to
add
things
and
then
we'll
include
the
ability
to
remove
them
as
an
iteration
on
this
I.
Don't
save
that
so,
yes,
the
same
experience
as
edit
today,
where
you
would
have
the
resize
it's
going
to
be
a
consistent
experience
for
a
user.
When
you
add
it
in
the
thing
is
clicking
the
edit
button
and
then
I
can
move
it
around
yeah.
A
B
That's
a
good
question
honestly,
like
yeah
most
likely.
If
you
have
more
elements
you
might
want
to
like
tweak
stuff,
but
at
the
same
time
I'm
also
wondering
again
like.
Is
it
really
necessary
at
this
stage
like?
Do
you
just
do
it
while
you're
creating
or
do
you
do
it
after?
You
know
you
just
want
to
create
your
stuff,
and
then
you
think
here
with
it
basically
yeah
yeah
I,
think
I
thought
we're
gonna
have
to
make
a
call
on
that
and
see
how
it
goes.
A
Because
it's
not
a
one-way
door.
If
we
leave
it
there,
yeah
like
it
is
today,
we
can
always
take
it
back
out
if
it's
confusing
to
users,
if
users
don't
give
us
feedback
one
way
or
the
other,
we
just
leave
it,
as
is.
If
we
see
you
suggested
or
talk
to
other
people,
and
they
we
see
that
they're
resizing
yeah.
B
A
B
More
yeah,
so
my
yeah
yeah,
my
original
thought
was:
do
we
need
it
at
this
moment
like
we
definitely
need
it,
because
we
have
it
later
on
right,
but
it's
like
they
really
need
it.
When
you
create
something,
I
was
wondering
because
and
again
that's
what
you
said
also
like
in
the
research
we
had
only
one
panel
if
they
had
multiple
with
that
change,
but
yeah
I
get
a
feeling
that
if
you
know
when
you
create
multiple
visualization,
we
already
ordered
them
for
you
on
the
the
canva.
B
For
like
a
better
word,
then
you
know
people
might
not
even
need
to
recite
stuff
and
they
can
do
it
later
on,
but
at
the
same
time
we
could
also
like
by
having
the
future
teach
them
that
they
can
do
it
later
on
yeah.
So
yeah,
that's
that's
a
tricky
that
you're
giving
also
is
the
way
we
interact
with
it
like
for
me,
I'm,
really
not
a
big
fan
of
having
everything
up
front
like
I.
B
Think
you
need
to
layer
stuff
so
like
what
is
the
primary
interaction
and
then
you
surface
this
one
and
the
rest
should
be
underneath,
and
this
is
kind
of
what
we
were
doing
with
our
edit
mode
right
like
when
you're,
not
in
edit
mode.
You
can't
resize
your
yeah
your
panel
and
that's
what
I
wanted
to
kind
of
bring
there,
but
right
now
the
flow
is
not
behaving
this
way.
A
I
think
it'd
be
a
funky
experience
for
user
to
add
a
bunch
of
stuff,
not
necessarily
in
the
order
they
want
or
the
size
that
they
want
and
then
have
to
go
back
and
redo
it,
but
yeah,
and
we
can
learn
that
from
releasing
it
with
one
or
both
or
none
and
then
getting
feedback
from
users.
And
we
can
run
that
in
front
of
some
users
internally
and
say:
hey
the
dashboard
creation
is
ready.
B
Yeah
I
think
that's
another
thing
and
I
thought
I
opened
that
issue,
but
I
may
have
forgotten,
but
basically
the
way
we
build
our
grid
right
now
kind
of
lets.
You
be
a
bit
well
with
the
resizing
option
and
then
things
don't
necessarily
keep
a
certain
like
it's
not
like
what
we
call
a
nice
and
regret
like
it
doesn't
readjust
too
much.
So
you
can
create
gaps
basically
in
it,
and
if
we
were
to
fix
this
I
think
just
visually.
It
would
look
a
bit
better,
but
that's
something
yeah
for
later
I.
A
B
A
So
I
think,
once
the
new
design
is
attached
to
the
create
blow,
there
might
be
a
few
more
more
issues
that
spawn
out
of
that.
But
all
based
around
that
initial,
really
small
use
case
that
we
got
to
and
then
we
can
put
the
the
the
design
with
the
bigger
Vision
alongside
the
design.
That's
in
the
existing
epic,
around
schema,
driven
customizable
dashboards.
A
A
A
B
Was
good
yeah,
yeah,
I'm
I'm
also
happy
with
the
result,
I
think
we've
we've
done
a
good
job
to
increase
our
confidence
in
it
and
I
mean
obviously
you
know
at
this
fruitful,
be
there
once
we
release
it
and
people
start
getting
used
to
it
and
use
it
on
a
daily
basis.
Yeah,
but
I
think
we
can
feel
pretty
confident
about
this
yeah.
A
I
think
so
too,
I
think
the
last
thing
that
I
want
to
get
started
out
with
the
team
is:
there's
some
error,
validation
or
displaying
of
Errors
in
this
epic.
That
I
think
we'll
want
to
move
in
to
our
MBC
just
to
make
sure
that
if
there
is
an
error
with
a
panel,
that's
included
in
as
we
display
a
custom
dashboard.
B
A
Cool
all
right,
well,
I,
think
that
is
that's
everything
on
our
agenda
unless
something's
stuck
in
while
I
wasn't
looking
cool
all
right.
Well,
we're
gonna
in
the
interim
after
you've
left
off
Kevin
we're
gonna
keep
this
meeting
so
that
the
team
and
I
can
think
I'm
any
sort
of
things
that
need
to
be
done.
As
far
as
like
to.