►
From YouTube: Testing UX / PM Sync 2021-09-02
Description
Gina and James talk about how the changes to Maturity dates (https://www.youtube.com/watch?v=4dRkVVS-0s4) impact the UX KRs and Gina's research in FY22Q3.
A
B
B
B
This
is
the
one
that
we
created
in
the
research
project,
okay
and
yeah,
and
then
hayana
said
that
yeah
we'll
have
to
do
the
30
minute,
job
interviews
and
the
final,
and
just
so
you
know
the
final
deliverable
for
this
ux
kr
at
least,
is
just
to
create
an
mr
that
updates
the
job
to
be
done.
Yaml
file,
so
yes,
we'll
get
a
ton
of
research
out
of
it,
which
is
also
nice
for
us,
but
for
the
uxkr.
It's
just
updating
those
jobs,
okay,
cool
okay,
so
I
watched
your
the
category.
B
Maturity
walk
through
that
you
had
posted
the
video
and
it
gave
me
a
lot
of
inspiration
to
start
looking
into
14
5..
What
I
did
there
was,
I
believe
I
moved
one
of
the
validating
performance
testing
to
there.
My
guess
is
that
I
actually
will
start
this
in
14
4,
but
I
moved
it
there
just
so
that
I
could
focus
on
usability
testing
for
the
first
one.
A
B
B
A
B
A
Testing
yeah,
it
looks
like
the
move
to
viable
on
10
22
of
2022
okay,
so
we
would
basically
looking
at
when
we're
shifting
usability
from
minimal
to
viable
we'd
want
to
just
apply
the
same
set
of
things
one
quarter
forward.
So
if
we're
starting
our
jobs
to
be
done,
research
on
usability
testing
in
this
quarter
to
wrap
up
by
january,
we
would
want
to
start
it
in
january
for
performance
testing
to
wrap
up
by
april
okay.
So
I
think
we
can
push
that
out.
B
Cool
status
update
on
this,
so
this
is
the
usability
job
to
be
done.
Research
I
had
started
a
discussion
guide
and
I
brought
I
also
brought
will
into
this:
will
is
a
researcher
for
ci
cd
and
he
just
joined
so
probably
not
the
top
of
his
priorities
right
now.
But
what
I
did
here
is
started
a
discussion
guide
and
I
see
that
you
added
comments
that
I
have
not
seen
yet
so
I'll
have
to
go
through.
B
A
B
A
B
A
I
didn't
get
down
to
the
jobs
beyond
questions
actually,
but
I
think
the
biggest
thing
is.
I
wouldn't
use
the
terminology
usability
testing,
because
that's
what
we
use
this
name
in
the
category
but
like
if
you
go
out
and
you
ask
20
developers,
hey
tell
me
about
your
usability
testing
they're
going
to
say
what
are
you
talking
about?
A
I
think,
based
on
my
interactions
with
them,
so
I
think
that
we
just
need
to
come
up
with
different
terminology
around
like
acceptance,
testing
or
validating
that
the
feature
works
or
okay,
something
like
that
or
as
we
talked
to
designers,
talk
about
hey
you've,
you
made
changes
to
a
design.
How
do
you
validate
that?
Those
are
actually
happening
as
part
of
your
work?
A
A
B
A
B
A
I
think
so,
but
we
might
want
to
check
in
with
with
our
friends
in
research
and
see
what
they
think
about
it
or
sanity
check
the
payout
about
that
we
could
always
use
external.
I
was
thinking
more
down
the
line
when
we
say
there's.
Gitlab
has
widely
adopted
this
feature
that
those
use
cases
could
fit
where
handbook
changes,
and
especially
in
the
in
the
process
of
doing
the
monthly
release
post
starting
to
utilize
this
functionality.
A
Instead
of
going
back
and
forth
it's
like
when
sid
and
even
scott
do
their
review,
they
leave
a
bunch
of
comments
in
slack
and
then
you
have
to
go,
make
sure
that
they
all
get
done
and
the
right
people
get
pinged
and
instead,
if
they're
just
leaving
the
comments
directly
in
the
review
app,
it
saves
them
going
back
and
forth,
and
then
you
can
tag
somebody
in
each
different
comment
in
the
thread
of
hey.
Can
you
address
this?
Hey?
Can
you
address
this?
Hey?
A
Can
you
address
this
and
then
they
can
go
and
make
their
changes
in
the
emr
yeah?
That's.
I
think
that
I
think
that
workflow
could
work,
but
we'll
we'll
get
closer
to
that
down
the
line
for
for
the
jobs
we
don't
know
check
in
with
hayanna,
and
she
would
see
what
she
thinks
about
internal
versus
external
for
the
the
jdb,
the
jobs
to
be
done.
Discussions
okay,
because
we
did
always
do
a
recruitment.
Caitlin
can
help
us
with
that.
Pretty
quick.
B
B
But
I
think
now
that
we've
had
this
conversation,
I
had
made
a
placeholder
for
performance
testing,
job
to
be
done,
validation
and
I
had
set
it
for
14.5.
So
I
think,
based
on
our
conversation,
about
pushing
that
back
based
on
the
maturity
date,
I'll
change
this
so
that
it
correlates
with
that
date
now
yeah.
I
would
just
move
that
one.
A
A
The
team
will
be
working
on
building
out
either
the
project
test
summary
or
working
on
chicago
parsing,
depending
on
what
I
find
in
this
quarter,
and
then
that's
when
we
would.
No,
if
we
do
the
validation
next
quarter,
then
we
would
have
no
research
items
go
in
february
through
april
of
22
and
then
may
through
july
of
22.
We
would
do
a
category
maturity
scorecard
with
external
users
on
those
additional
jobs
to
be
done.
A
B
A
This
is
more,
I'm
gonna
do
yeah.
I
wasn't
even
thinking
in
context
of
the
uxkr
when
I
was
putting
this
together,
so
I
wouldn't
extrapolate
out
of
anything
from
it
to
influence
what
you
need
to
do
in
your
kr
in
this
quarter.
I
was
just
thinking
about
hey.
I
need
to
look
at
the
jobs
to
be
done
and
see
start
brainstorming.
What
other
jobs
to
be
done?
Does
this
category
cover
so
that
we
can
do
that
validation
next
quarter.
B
B
Week's
yes,
okay,
yeah,
that's
what
it
was.
Okay,
so
then
you're
up
to
date
about
that,
but
they
did
just
create
this
handbook
page.
I
think
this
morning
and
it's
like
a
summary
of
what's
going
on
and
then
down
here
it
gives.
Who
is
the
lead
for
everything
so
hopefully,
because
they
have
gotten
the
working
group
solidified.
I
think
things
will
start
rolling
now.
That's
my
hope.
B
A
In
the
discussion
that
I
saw,
though
it
was
more
of
a
there's,
not
the
intent
that
they
will
actually
finish
the
work
that
the
working
group
will
not
do
the
work
on
these
ten
widgets
and
their
intent
is
that
they
may
not
have
everything
delivered
to
us
so
that
we,
as
the
individual
teams,
can
finish
the
work
either
within
this
quarter,
which
is
fine.
I
just
want
to
make
sure
everyone
is
on
the
same
page
with
that.
That
was
my
takeaway
from
that,
watching
that
recording
was
they're.
A
I
have
a
sales
enablement
webcast
today,
just
talking
through
positioning
of
our
categories,
and
it's
really
it
talks
about
the
value
prop
each
of
the
categories,
how
it
fits
into
the
business
drivers
that
the
sales
team
is
using
and
then
how
you
can
take
very
common
use.
Cases
like
lots
of
people
have
a
code
coverage
badge.
Here's
all
the
other
features
that
you
get
if
you
are
parsing
for
code
coverage
as
an
example,
so
that's
getting
that
content
wrapped
up
and
getting
ready
for
that
today
was
my
top
priority.
A
The
customer
journey
map
customer
journey
map
research.
I've
been
working
on
moving
forward.
I
have
a
I
need
to
put
the
issue
link
in
here,
but
I
have
a
research
issue
open
for
that.
I
need
to
start
recruiting
on
that
probably
next
week,
so
that
we
can
talk
to
some
folks
about
that's
the
user
path
of.
I
intend
to
run
some
tests
as
part
of
my
git
lab
get
my
pipelines
and
then
how
do
they
get
artifacts
actually
uploaded
and
review
those
tests?