►
From YouTube: 2023-07-26 Product Analytics UX/PM Sync
Description
This week we discussed the MVC for Dashboard Designer and what else is in the 16.3 milestone.
Future projects include validation of the existing Visualization Designer flow, Usage Quota flow for Product Analytics and digging into the story map for that Usage Quota flow.
A
A
I,
don't
think,
there's
anything
more.
There
I
think
the
team
has
been
asking
questions
in
the
issue
which
is
great
going
through.
That
I
think
so
then,
review
upcoming
design
issues
for
what
should
be
in
the
next
Milestone
I
wanted
to
talk
about
specifically
16
free
make
sure
that
we're
not
missing
design
for
anything.
B
A
Yeah
I
think
it's.
This
is
just
there's
an
existing
toggle
that
when
we
get
to
the
beta
instead
of
users
having
us
having
to
manually
onboard
them
with
feature
flags
and
specifically
setting
a
project,
this
will
take
care
of
that
I
will
toggle
on
the
product
analytics
feature
for
everything
in
my
group.
A
B
B
A
B
B
B
A
All
right
so
then,
the
16th
for
and
Beyond
as
we
start
thinking
about
that
release
and
other
others
going
forward
as
we
get
closer
to
Beta.
The
things
that
were
top
of
mind
for
me
were
the
the
implementation
of
the
dashboard
designer
the
MPC
that
we've
talked
through
and
then
some
I
don't
know
how
to
form
up
the
research
yet.
But
I
can
talk
to
Nick
about
that
of
visualization
designer.
We
have
a
scorecard
against
it.
We
have
an
existing
implementation.
A
We,
the
approach,
I'd
love
to
take,
is
go,
show
it
to
users
and
walk
them
through
it,
because
it's
there,
it's
just
hidden.
You
can't
easily
access
the
feature,
but
you
can
get
to
the
feature
through
a
URL
see
what
they
think
of
it.
Have
them
build
visualizations
and
understand
where
there's
gaps
from
a
user
perspective
and.
A
B
A
B
A
B
B
So
both
actually
because
I
think
both
are
available,
like
we
already
had
usage
for
the
ages
in
the
app
that,
if
I'm
not
mistaken,
are
actually
already
showing
you
both
storage
and
CI
minutes,
so
yeah
I
guess
the
thing
to
do
is
just
kind
of
figure
out
how
we
can
Branch
into
that,
and
we
might
be
able
to
rely
on
previous
validation
instead
of
like
creating
our
own,
like
that,
we
would
save
quite
some
time.
I.
Think.
A
B
From
a
different
I've
worked,
I
worked
on
the
storage
side
a
bit
because
at
some
point
it
was
allocated
to
growth
and
then
it
moved
to
fulfillment
and
for
storage.
I
can
tell
you
that
we
did
validation,
but
I
don't
think
we
had
dovetail
at
the
time.
So
maybe
it's
somewhere
in
Google
drive
or
something
so
I
could
look
it
up
as
well.
Yeah.
A
Sorry,
I'm
gonna
sign
that
to
you
cool
does
that
seem
like
do
those
seem
like
the
right
things
to
go
check
over
16
4
Beyond
without
going
back
to
our
our
top
list
of
deck
group
designer
circuit,
getting
user
feedback
on
the
visualization
designer,
and
then
they
use
the
sort
of
work
that
we
need
to
do
before.
Ga.
A
B
A
Good,
so
the
process
so
far
has
been
the
team
got
together
and
brainstormed
a
bunch
of
tasks.
I
didn't
do
a
good
job
of
framing
of
this
is
specifically
around
the
I
got
a
bill.
I
want
to
understand
what
used
product
analytics
consumables
to
that
contributed
to
the
bill.
That's
what
we
think.
That's
our
assumption
is
going
to
trigger
the
flow
into
hey.
A
A
Let
me
just
view
data
that
would
contribute
to
the
last
bill,
so
the
Euro
groups
usage
for
the
last
billing
period,
a
few
projects
usage
for
the
last
billing
period,
and
then
we
think
the
next
logical
step,
because
a
number
in
isolation
isn't
useful
is
compare
it
to
the
period
before
first.
So
you
can
see
if
you
got
a
big
jump
in
your
build,
you
can
see
hey
what
contributed
to
that.
A
That's
what
I
want
to
see
immediately
of
what
jumped
up
in
usage
quite
a
bit
so
comparing
the
group's
usage
month
over
month,
comparing
to
projects
usage
month
over
month
and
then
maybe
comparing
within
a
specific
date
range
and
that
might
be
yeah.
Let's
give
them
a
date
picker
and
show
only
the
data
for
those
that
could
be
a
feature
iteration.
We
might
move
that
down
and
then
viewing
this
month
to
date,
that's
kind
of
the
follow-on
of
it's
a
lot.
Last
month
we
had
this
much
usage.
A
How
are
we
doing
this
month?
How
does
it
compare
so
being
able
to
see
that
to
date?
This
is
how
much
you've
used
compared
to
last
month
to
date.
So
are
you
already
trending
ahead
of
where
you
were
in
the
month?
You
got
a
surprise,
Bill
versus
or
is
it
you
know,
turn
it
back
down.
We
think
that
those
are
the
kind
of
key
components
of
the
flow
that
someone's
going
to
want
to
look
at
and
then
trying
to
figure
out.
A
So
then,
as
I
was
thinking
about
this
of
putting
together
a
mock
or
wireframe
and
looking
at
it
with
users.
Some
of
the
things
that
I
thought
we
would
learn
are
what
data
is
most
important
to
the
user.
What
word
level
is
most
important,
that
organization
being
do
I
care
about
it,
mostly
at
the
group
that
I
care
about
it,
mostly
at
the
the
project
level?
What
is
the
right
granularity
for
the
person
getting
the
bill?
A
In,
the
comparison,
it's
what
other
data
might
they
need?
So
if
we
show
them
the
comparison
in
the
wireframe
and
they
say-
hey,
that's
not
actually
useful
to
me.
I
need
this
other
piece
of
data
because
XYZ
and
then
what
data
they
need
to
be
confident
going
forward.
Do
they
want
just
where
they're
at
today
or
where
they
would
end
up
at
the
end
of
the
month,
trended
like
further
back
in
confidence
to
to
create
kind
of
a
trending
starting
to
understand
a?
A
B
I
have
one
thing
that
comes
into
mind
now,
if
it's
more
on
the
Assumption
side
or
the
learning
objective,
but
we
don't
necessarily
know
who
is
gonna,
be
the
main
person
using
that.
So
my
assumption
is
that
the
person
actually
purchasing
extra
click
events
is
not
necessarily
the
person
that
is
gonna
use,
dashboards
and
instrument
anything.
So
you
know
this
kind
of
like
difference
between
buyer,
Persona
and
user
Persona
in
a
way
yeah.
So
maybe
in
the
learning
objective
is
to
kind
of
make
this
crisper
and
to
understand.
B
A
Yeah,
based
on
experience
with
the
CI
minutes,
it's
going
to
be
this.
The
buyers
that
I'm
looking
at
this,
not
the
user,
and
so
we
don't
necessarily
need
an
entry
point
out
of
the
dashboard
back
into
the
usage
quota.
We'd
understand
if
we
can
get
them
from
a
bill
into
usage
quota,
though,
if
that's
the
right.
B
A
And
the
learning
objective
of
who's
actually
going
to
use
this
cool
okay,
so
there's
some
to
do
still
here,
I
think
just
from
a
sketch
out
what
we
think
would
be
the
right
or
The
Next
Step
sketch
out
what
we
think
is
the
right
trigger,
and
then
we
can
start
putting
together.
Some
box
to
I
think
show
folks
are
used
to
validate
with
the
team
of.
Is
this
feasible
to
go,
build
yeah,
cool
awesome
thanks
for
walking
through
that
with
me,
yeah
all
right!