►
From YouTube: Testing UX / PM Sync 2021-09-23
Description
Gina and James discuss how to analyze the data coming from the Jobs To Be Done interviews for the Usability category, when we lock down the planning issues and the research James and Scott are starting to schedule.
A
B
Okay,
I'm
going
to
share
a
couple.
The
first
couple.
Things
is
just
more
of
updates
on
where
I
am
in
the
usability
testing
research,
so
just
wanted
to
jump
over
and
show
you
if
you
I've
started
to
analyze
two
of
the
sessions
thus
far
and
I'm
planning
to
finish
up
the
rest
of
them
today
and
you're.
Welcome
to
like
jump
in
and
see
what
I've
done
so
far.
B
But
I
was
wondering
if
there's
any,
if
you've
done
this
type
of
research
in
the
past.
I
was
just
wondering
if
there's
any
methods
that
you've
used
to
analyze,
that
data
outside
of
dovetail,
because
I
did
see
that
there
was
this
template
for
job
maps
and
mural,
which
looked
really
cool.
But
I
wasn't
sure
if
this
is
something
that
we
should
be
like
using,
because
it
looks
like
it's
something
for
the
team
to
use.
A
I
haven't
used
that
before
what
we
did
when
we
did
the
jobs
to
be
done.
Research
around
code,
testing
and
coverage
and
code
quality
was
did
the
initial
brainstorming
with
the
team
and
then
surveyed
those
things
out
and
that's
how
we
settled
on
our
jobs
and
that's
part
of
the
reason
that
they're
really
broad.
So
that
was
the
research
method
we
used.
I
would
take
whatever
you
think
is
going
to
work
best.
B
Yeah,
this
looks
cool,
so
I
I'll
figure
that
out,
I
think
I'll
have
a
better
sense.
Once
I
finish
analyzing,
like
the
data
that
I
found
and
and
then
the
other
question
I
had
was
the
video
you
sent
out
around
14
5
refinement,
I'm
just
wondering
in
general.
Do
we
have
like
a
timeline
of
when
we
can
stop
making
edits
to
this
page?
Basically,.
A
So
I
stopped
making
edits
to
the
page
when
we
record
the
kickoff,
and
at
that
point
I
always
drop
a
comment
that
says
that
now
the
board
is
the
source
of
truth
like
up
until
then
the
board,
and
this
may
not
exactly
match.
I
try
to
make
sure
that
they're
matching-
and
I
kind
of
use
this
as
a
guiding
here's
where
we're
going.
A
A
No
worries
and
what
is
on
there
when
we
close
it
still
may
not
be
reflective
of
what
we
work
on
like
between
the
time
that
we
do
the
kickoff
recording
and
when
we
actually
start
work,
things
might
shift
still.
So
we
always
talk
about
in
the
kickoffs
that
we
played
ambitiously.
This
is
our
best
guess
right
now
of
what
we're
going
to
work
on,
but
things
come
up
like
different
opportunities
arise
that
literally
we
just
can't
miss
or
performance
problems
or
whatever
it
might
be,
and
that's.
Okay,.
B
A
That
would
make
sense.
That's
our
most
widely
used
feature.
So
that's
probably
why
and
then
I
don't
know
if
you're
following
along
with
the
mr
widget,
yes
yeah
working
group-
that's
the
word
I'm
looking
for
they
are
working
on
changes
that
standardize
and
then
they
also
added
a
they're
gonna,
add
into
the
core
components
tracking
for
these
things
as
well,
which
is
really
exciting.
So
I
both
of
these
might
just
get
closed
off.
A
At
that
point,
like
I
said,
we
don't
have
any
issues
opening
here
if
we
can
get
some
stuff
opened
up
for
q4
great,
but
I
would
really
wait
for
the
working
group
before
we
change
anything
drastic.
What
I
would
think
is
that
we
change
content
like
data
we're
sending
to
the
widget
and
maybe
even
the
type
of
widget.
It
is
beyond
just
the
standard
list.
A
B
Okay,
I
don't
know
that
just
reminded
me
too.
Yesterday
there
was
a
showcase
and
I
need
to
like
dig
up
the
issue,
but
there
was
a
ux
showcase
around
the
security
widget,
and
I
think
you
had
already
seen
that
issue,
because
I
saw
that
you
and
scott
were
commenting
on
it,
but
there
were
some
changes
or
they're
going
to
be
some
changes
to
the
security
widget
and
how
it
works
and
I'm
pretty
sure,
you're
aware
of
it.
But
I
just
wanted
to
bring
that
up
for
awareness.
A
A
So
I'm
recruiting,
we
have
a
ton
of
people
who
wanted
to
talk
to
us
about
the
customer
journey
map
research,
our
build
artifacts.
So
today
I'm
gonna
send
out
emails
to
try
to
get
those
scheduled
started
next
week.
So
next
week
and
the
week
after
we'll
probably
be
really
busy
with
interviews
I'll
try
to
loop
you
into
as
many
of
those
as
optional
as
I
can.
This
is
problem
validation,
so
not
it's
more
than
80
pm
than
on
you.
A
So
that's
why
I'm
gonna
include
you
optionally,
but
I'll
always
be
recorded
and
you'll
be
able
to
weigh
in
or
review
them
there
rather
and
then
supporting
scott.
He
is
also
working
on
a
recruiting
request,
we're
just
slamming
katelyn
with
those
lately
but
we're
getting
them
filled
and
which
takes
me
to
my
next
agenda.
Point
on
our
agenda,
which
is
the
practice
interview
session
that
we're
doing
today.
A
So
my
goals
coming
out
of
that
are
that
we
give
scott
feedback
on
his
interview
style,
as
well
as
the
content
that
of
the
questions
so
that
it's
refined
going
into
the
interviews.
So
that's
what
I'm
hoping
to
get
out
of
that
I'll.
Be
taking
notes,
he'll
be
conducting
the
interview
and
you're
the
interview
subject.
So
that's
how
we're
going
to
approach
that.