►
From YouTube: 2023-06-07 Product Analytics PM/UX weekly
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
So
the
product
analytics
PM,
ux
weekly,
think
for
June
7th
2023
I
wanted
to.
After
looking
at
the
async
notes
from
last
week,
I
updated
the
invite
with
a
new
Zoom
link.
It's
the
zoom
like
in
the
agenda
now
and
Kevin
and
Dennis
are
both
go
hosts.
That's
the
right
word
for
meeting,
so
you
should
be
able
to
start
it
without
me.
Now
I
think
you
do
need
to
be
logged
in
to
be
able
to
get
into
it
at
all.
A
Okay
just
wanted
to
review
that,
and
with
that
then,
let's
start
looking
at
the
sticky
items
latest
proposal,
sorry
prototype
review
results,
I
haven't
scheduled,
but
I
will
schedule
those
I
wanted
to
touch
base
with
you
with
the
internal
folks.
Do
you
a
good
chunk
of
them?
Are
actually
a
Mia
based
or
you
or
Europe
based?
Are
you
company,
okay,
running
those
solo
and
then
actually
watch
the
recordings?
Okay,
cool.
A
B
Yeah,
in
other
words,
if
it's
easier
this
way,
yeah
happy
to
to
run
the
sessions
fantastic.
A
And
then
the
way
the
sessions
are
running
is
just
walking
or
I.
Guess
the
procedure
walking
through
the
discussion
guide
and
showing
them
the
dashboard
itself
and
the
steps
that
they're
going
to
take.
B
Yeah
as
well
as
I
think
we
had
a
few
questions
at
the
beginning
to
better
understand
that
the
context
around
them,
you
know
wanting
to
set
up
a
custom.
Dashboard
is
what
you
added
in
the
in
the
discussion
guide,
so
yeah,
yeah,
I,
think
these
sessions
should
be
around
30
minutes
tops
and
yeah.
B
If
you
could
also
try
to
schedule
external
people
for
the
upcoming
week
like
this,
we
have
a
whole
schedule
done
so
that
to
me,
I
know
when
I
need
to
either
because
the
point
of
Rights
is
to
kind
of
like
go
through
the
first
prototype,
get
some
feedback
and
then
iterate
on
the
on
the
Prototype
and
then
test
again
like
all
this.
Until
you
feel
like
you,
have
something
good
enough
to
start
building,
basically
so
yeah.
B
So
if
we,
if
we
could
have
like
a
timeline
scheduled,
that
would
be
great
as
well,
but
that
also
depends
on
the
participants
so
yeah.
A
I'd
like
to
talk
a
little
bit
about
I,
guess:
exit
criteria
for
lack
of
a
better
term,
because
we
could
do
that
cycle
forever.
But
should
we
cap
it
or.
B
That's
a
good
question,
so
I
know
what
you
would
do
usually
write
this,
like
you
start
with
three
you
test.
You
address
the
issues
that
you
have
during
your
test.
Then
you
rerun
with
two
and
then
you
kind
of
repeat
this
yeah
I.
A
Just
I
wanted
to
get
into
bike,
shedding
of
somebody
who
has
a
particular
way
that
they
give
data
giving
us
feedback,
based
only
on
that,
it's
more
of
yeah
for
the
task
that
you
need
to
accomplish.
Can
you
accomplish
it?
If
you
liked
it
or
not,
it's
a
little
secondary
like
did
its
life
is
great,
but
can
you
get
through
the
path
without
banging
your
head
on
the
deck
yeah?
It
feels
like
a
good
starting
point.
Yeah.
A
C
B
No
I,
I,
yeah
I
agree
with
you,
I
think
it's
it's
better
to
focus
on,
like
the
fundamental
part
of
the
workflow,
make
sure
that
this
is
kind
of
nailed
in
a
way
and-
and
then
you
know
whatever
we
think
is
like
secondary
to
this.
We
can
just
see
this
for
later,
basically
like
validate
validate
it
later,
especially
considering
the
the
state
that
product
analytics
is
in,
like
let's
just
focus
on
the
Main
and
core
workflow
and
then
we'll
refine
along
the
way.
I
agree
with
that:
okay.
A
B
Yeah
I
think
like
if
again
like
it's
not
going
to
be
a
fully.
You
know
very
high
detail
prototype,
but
then
we
can
also
increase
the
level
of
detail
but
yeah.
If
you
feel
that
people
can
successfully
create
a
custom
dashboard
and
that
they
don't
like
something
that
we
think
is
really
fundamental,
then
yes,
I
think
we
can
just
say:
okay,
let's,
let's
go
with
that!
B
A
A
B
A
B
I'm
looking
at
another
one
right
now,
which
is
the
smaller
one,
it's
about
or
alert
states
in
the
dashboard,
and
then
you
paste
that
year
yeah,
because
it's
something
I
can
have
felt
through
the
crackers
a
few
weeks
ago
and
I'm
just
looking
at
it
right
now,
because
I
kind
of
need
those
small
design
issues
during
the
downtime
of
Rights.
You
know
when
we're
not
testing
and
things
like
that.
I
can
pick
up
some
small
things.
Okay,
I
find
it
okay.
B
Okay,
I'll
drop
it
in
the
agenda
and
then
the
other
thing
that
I
did
as
well
was
to
rewrite
a
bit
the
problem,
validation
issue
that
makes
open
you
know.
Last
week
we
kind
of
discussed
with
Justine
and
Nick.
B
You
know
doing
kind
of
both
problem
and
solution.
Validation
in
parallel
and
I
can
thank
you
both
in
the
issue
to
maybe
think
a
bit
about
problem
violation
as
a
broader
scope
and
focusing
on
jobs
to
be
done
in
the
meantime,
because
I
think
this
is
really
like
important
to
have
this
done.
B
Pun
intended
yeah
before
before
we
move
forward
so
I'm
just
gonna
paste.
The
instrument
here
on
here,
but
yeah
feel
free
to
to
check
it
out.
It
changes
a
bit.
You
know
what
we
want
the
outcome
of
This
research
today
and
let's
see
what
Nick
is
saying
about
that
as
well,
but
yeah
yeah,
it
used
to
kind
of
go
beyond
simply
creating
dashboard
is
more
like
seeing
analytics
as
a
whole
and
who
is
performing
the
task.
B
What
are
like
some
kind
of
main
task
that
they're
trying
to
do
and
then
what
our
next
step
to
ask
everything
and
the
other
thing
I
didn't
drop
this
in
the
agenda,
but
I
wanted
to
kind
of
understand
this.
A
bit
better
like
I
know
that
we
want
to
have
some
kind
of
velocity.
You
should
think
hey
and
that's
how
we're
using
rights,
but
then
I
was
like.
B
Where
does
this
needs
come
from
and
in
my
mind
it
comes
from
the
fact
that
we're
a
bit
late
to
the
party,
if
that
makes
sense
right,
so
we're
gonna
need
to
catch
up,
because
there
are
a
lot
of
competitors,
but
I'm
so
curious
to
hear
it
from
you
like
what
like.
Why
do
we
want
to
be
very
fast
shipping?
A
A
A
Basically,
with
that
feature
set
available,
it's
a
very
light
feature
set,
though
so
I,
don't
think
that
there's
a
compelling
aha
moment
within
that
for
customers,
but
we
can
get
quick
feedback
from
those
customers,
internal
and
external,
on
problem
searchable,
trying
to
solve
the
faster
that
we
can
then
iterate
on
those
features
and
get
them
out
and
be
Traction
in
our
active
users
and
the
better
off.
A
We
are
right,
the
more
value
we
can
show
in
the
product
and
the
more
likely
that
the
feature
set
is
going
to
be
successful,
So
the
faster
we
can
iterate
on
those
things,
especially
Integrations
with
or
usage
of
other
git
live
features.
The
more
value
we
bring
to
the
customer.
If
we
don't
I
feel
like
this
ends
up
being
another
one
of
those
bolted
on
things
within
gitlab
that
we
get
to
MVC,
State
and
then
abandon,
and
eventually,
two
years
later,
it
doesn't
bring
a
lot
of
value
to
customers.
A
B
B
Maybe
this
is
also
something
we
could
tackle
instead
of
just
shipping
teachers
or
I,
don't
know
because
that
you
know
it's
kind
of
it's
like
either
we
do
it
boy
tipping
or
should
like
a
very
minimal
iteration,
which
we
have
right
now,
I
think
which
is
kind
of
like
a
proof
of
concept
that
is
getting
better
either.
We
do
it
this
way,
which
we're
doing
either
we
kind
of
take
a
step
back
slightly.
Do
the
job
to
be
done,
research
and
then
kind
of
see
the
value
that
it
can
have.
C
A
Just
different
ways
of
approaching
it
yeah
our
North
Star
right
now
is
weekly
active
users,
so
all
of
our
activities
should
focus
on
that
and
our
sense
of
urgent
station
focus
on
how
do
we
get
more
active
users?
And
if
we
find
that
we're
getting
new
users
week
after
week,
but
we're
not
getting
sustaining
users?
The
solutions
are
actually
solving
problems
because
they're
not
coming
back
and
getting
additional
value
week
over
week.
B
A
If
you
want
gitlab
to
go,
solve
five
problems,
for
you,
is
this
one
of
those
top
five?
And
so
we
want
to
find
a
problem.
That's
you
know
in
that
list
that
we
can
address
with
product
Analytics
to
a
certain
degree,
and
if
it's
integration,
like
hey
I,
have
deployments
going
out
and
I'm
seeing
with
my
door
metrics,
my
team
is
getting
more
effective,
but
I
don't
know
if
anybody's
using.
B
Yeah
yeah
I
mean
the
yeah.
The
number
of
active
user
I
think
is
an
interesting
metric
because
to
me
is,
if
you
want
to
see
returning
people
is
that,
as
you
mentioned,
you
see
that
there's
value
in
it
right.
They
see
that
there's
value
in
it
therefore
they're
coming
back.
Therefore,
this
metric,
like
increases
but
I,
think
a
good
way
to
understand.
B
The
value
is
to
actually
have
like
some
kind
of
job
to
be
done
or
something
yeah
done
and
and
yeah
we
I,
don't
think
we
research
through
first
look
to
be
honest,
I
think
job
to
be
done.
Research
I've
made
differently,
but
anyway,
if
it's
still
something
we're
doing,
parallel
I
think
that's
great,
but
we
yeah
I
think
it's
yeah.
It's
perspective,
yeah
like
in
my
mind,
it's
like.
B
So
then
down
the
line,
you
would
be
a
bit
more
assertive
when
shooting
something,
because
you
would
likely
see
Your
solution
being
used
sustainably.
Right,
therefore,
like
your
metrics
around
active
users
to
monthly
active
users,
ramping
up,
that's
yeah,
that's
this
different
side
of
of
the
coin.
Basically,
yeah.
A
A
Are
we
showing
like
that's
hard
to
get
at
today
for
a
team
who
has
nothing
they're
searching
in
logs
they're,
maybe
implementing
Google
analytics,
which
we
have
a
kind
of
a
great
opportunity
right
now
with
the
big
shift
into
ga4,
like
those
teams,
maybe
have
nothing
and
they
need
to
see
usage
and
they
need
to
be
path
through
their
product,
that's
their
job.
That's
what
they're
trying
to
solve
for
yeah.
C
B
B
Right:
okay!
Well,
thanks
for
inserting
this
question
maybe
took
a
bit
of
attention.
A
I
I
appreciate
the
perspective
and
the
importance
of
hey.
We
need
to
actually
have
like
a
thing
we're
going
to
try
to
solve
for
like
is
there
a
job
to
be
done
and
all
of
our
Solutions
should
focus
on
that
we
can't
take
a
scatter
shot
approach
and
that's
why
we're
not
trying
to
do
heat
mapping
and
surveys
and
session
recording
like
it's
all
about
feature
usage.
I
have
no
I,
don't
know
how
many
people
are
using
features
or
using
my
product.
A
A
I
wanted
to
talk
about
the
U.S
research
issue,
real
quick
before
I
answered
next
question
in
there.
I
think
that
Iran's
support
or
the
right
stuff
that
we're
doing
beyond
that.
Do
we
as
we're
looking
at
is
this
a
this
is
for
Q2
yeah,
so
in
the
quarter
that
we're
in
already
I
think
that
that's
the
support.
Yes,.
B
A
Get
us
into
the
work
that
we're
doing
to
enter
the
beta
phase.
I
think
that
that's
all
the
support
that
we
would
need
what
am
I
missing
now.
B
Yeah
so
I
think
for
everything
right,
related,
bronze
support,
Sims
good
to
me
for
the
job
to
be
done.
Research
I
would
put
gold
if
possible.
B
Yeah
I
know
that
you're
naked
might
be
also
a
bit
hard,
because
you
know
he
has
multiple
Birds
to
color,
so
everyone's
gonna
try
to
Gold
the
entire
their
issues
right
so
but
yeah.
If,
if
yeah,
if,
if
I,
were
to
to
pick
one
for
the
jobs,
we've
done,
research
I
would
say
it's
it's
gold,
knowing
that
I
can
also
pop
in
on
that
as
well,
because
that
was
like
before
moving
from
growth.
This
is
one
of
the
research
I
was
doing
so
I'm
cool,
also
jumping
on
that.
C
A
All
right
well
at
the
the
note
back
that
we
just
need
some
problem:
support
on
the
right
stuff
and
we're
good
and
then
we'd
be
looking
at.
Do
you
want
to
try
to
get
ahead
and
say:
hey
we're
going
to
do
a
scorecard?
B
C
A
B
B
So
we
have
the
ux
call
card
done
already.
Okay,
like
that
I
did
when
I
joined
yeah
the
group
so
yeah
category,
we
can
do
it
if
we
fill
that,
but
then
can
we
at
the
same
time
like
well,
we
know
that
product
analytics
is
going
to
be
an
alpha
and
then
beta.
B
So
yeah
I,
don't
know.
Let's,
let's
note
it
down
and
see
and
talk
this
through
again,
I
guess.
A
Awesome
so
for
Q2,
just
in
Broad
support
Consulting
on
the
right
stuff,
Q3
we're
looking
at
jobs
to
be
done
key
forward.
Looking
at
a
scorecard
okay,.
C
Cool
awesome,
I,
don't
think
we
had
any
follow-ups
from
last
week.
I
don't
see
any
action
items.