►
From YouTube: Testing UX / PM / Research sync 2020-05-04
Description
We discuss if we need to do a Usability test before a score card for some categories that are set to mature in Q2 and Juan provides an update on the Category Maturity Scorecard for accessibility already in progress.
A
C
B
For
the
categories-
and
we
had
talked
about,
we
do
a
usability
test
first
for
accessibility,
so
Before
we
jump
into
in
you
know,
six
to
eight
weeks
wanting
to
do
a
scorecard
for
code
quality
or
for
unit
testing
or
code
testing
and
coverage
wanted
to
talk
with
this
group
about.
Does
it
make
more
sense
for
us
to
go
through
a
usability
test
around
these
categories?
First
of
hey.
We
want
you
to
go
and
use
this
feature
and
understand
where
there's
friction,
points
versus
understanding.
D
Yeah,
the
the
ideal
process
is
that
you
would
verify
what
you
guys
have
created
with
usability
test.
So,
like
you
need
to
understand
like
is
there
anything
that
doesn't
work,
how
they
expected
it
to
or
anything
like
those
kinds
of
things
I
can
cover
all
of
those
issues.
With
with
that
kind
of
research,
you
can
do
one
session
with
multiple
tasks,
so
you
don't
have
to
do
one
for
each
little
jab
be
done
or,
however,
you
guys
design
II
didn't
put
it
all
in
one
session,
for
the
jobs
to
be
done.
D
D
You
have
jobs
to
be
done
interviews,
you
talk
with
them
about
what
they
do
in
their
life.
Why
they
do
it?
What
tools
they
you
use
and
then
you
craft
the
jobs
to
be
done.
So
if
you
do
it
that
way,
you
have
already
a
high
level
of
confidence
in
these
jobs.
Soso
you
did
that
you've
got
jobs.
Great
you've
done
the
usability
test
with
those
those
designs
with
those
tasks
know
exactly
what
you
might
need
to
fix.
You
go
get
stopped.
D
You've
got
your
jobs
to
be
done
now,
you're
ready
to
do
the
maturity
scorecard.
The
thing
with
that
is,
though,
it
needs
to
be
done
in
the
production
environment,
so
hopefully,
after
you've
done
your
usability
test.
We've
got
to
the
point
where
we've
made
some
changes
and
pushed
it
out
out
there.
People
are
using
it
great
now.
Let's
do
that
maturity,
sport
process,
so
maturity
scorecard
process
is
in
the
there's.
An
EM
are
out
there
to
change
it
right
now
and
basically,
how
it's
getting
changed.
D
D
What's:
failure
for
a
task
and
noting
that
using
the
jobs
to
be
done
that
you
verified
to
create
the
scenarios
that
people
would
run
through
in
the
production
environment
and
then
asking
them
a
very,
very
short
questionnaire
after
each
scenario
to
say,
does
this
thing
basically
match
my
expectations
and
visions,
and
is
it
easy
to
use
those
are
the
two
questions
and
then
taking
all
that
data
and
then
we're
giving
that
to
the
product
management?
To
say:
okay,
here's
here's!
D
What
we've
learned,
you
guys
tell
me
how
this
maps
to
category
maturity,
because
it's
just
basically
numbers
right,
so
I
presented
this
to
the
UX
leadership
and
Christy,
and
my
hope
has
been
that
at
some
point
somebody
higher
than
me
will
start
talking
about
like
how
they
how
to
consume
those
numbers.
The
the
two
question
to
question
questionnaire
really
easy.
It's
on
the
five-point
scale
right
so
like
four
point.
Five
and
above
is
probably
great
for,
is
probably
not
too
bad.
D
Three
and
a
half
like
that
kind
of
thing,
where
you
kind
of
get
into
a
more
slippery
slope,
is
what
time
on
task.
So
you
look,
how
long
does
it
take?
We
may
not
know
right
now
how
long
it
takes.
So
this
is
really
like
the
first
time
you
do.
It
is
more
of
a
benchmarking.
It
takes
three
three
point,
two
five
minutes
to
do
this
task.
Then
you
go
back
and
you
look
at
that.
Those
two
questions.
It
wasn't
easy
and
did
it
didn't
satisfy
my
use,
it
back.
D
It's
a
high
score
and
you're
still
at
three
point:
two:
five
minutes.
That's
great
they're,
not
they're,
not
proceeding
any
active
like
oh,
my
god.
It
took
forever
and
I
didn't
get
to
do
my
thing.
So
that's
that's
kind
of
those
those
things
that
we
haven't
really
hammered
out
like
how
to
interpret
that
information
yet,
but
we're
gonna
put
that
in
the
bucket
of
Ted
of
management
to
do
we're
just
really
doing
the
gathering
of
the
data
for
you
guys
in
a
way
that
can
be
repeatable
over
time.
D
A
A
B
This
is
all
now
mapping
up
in
my
head
and
it
makes
the
time
as
that's
great
so
then
bring
back
two
then
two
categories
that
I
mentioned
for
code
quality,
Co
testing
and
coverage.
We've
made
some
changes,
but
it
was
based
on
items
that
were
highly
upvoted,
had
a
lot
of
community
discussion,
things
that
we
understood
through
not
necessarily
interviews,
because
the
issues
are
multiple
years
old
that
were
important
to
do
so.
We've
missed
that
jobs
to
be
done,
part
of
it.
B
D
D
started
to
move
before
she
got
involved,
and
so
what
I
suggested
to
her
was
to
have
a
conversation
with
your
customer,
your
users
and
say,
but
but
kind
of
build
it
around
the
jobs
to
be
done
without
telling
them
that
so
your
trade,
like
more
focused
on
those
jobs
to
be
done.
In
that
conversation,
you
really
just
trying
to
validate
whether
or
not
that's
a
thing
and
at
the
end,
like
I,
always
tell
people
like
start
broad
like
have
as
long
big
conversation.
They
go
really
really
specific.
D
At
the
end,
you
can
actually
pull
out
those
jobs
to
be
done
very
similar
than
what
Ian
did,
but
just
on
a
survey
and
say
does
this
resonate
with
you?
Is
this
something
that
you
do
do?
Would
you
change
this
to
match,
and
so
you
can
get
bad
verified
in
that
same
session
that
you
would
be
doing
these
go
new
test
with
them.
D
B
A
A
A
A
A
D
A
This
there's
many
people
who
responded
to
the
survey
who
we're
like.
Oh
you
know,
what's
usability
I
know
what
accessibility
I
know,
what
I
know
that
it's
important
and
all
this
stuff,
but
I'm,
not
an
expert
like
that's,
certainly
fine,
you
don't
need
to
be
an
expert.
You
just
need
to
be
capable
of
like
doing
a
flow
inside
a
merge
request,
so
I
can't
I
cannot
want
to
give
them
that
assurance
that
we're
not
much
just
the
flow.
You
know,
yeah.
A
Yeah
I'll
pre-press
scripts.
For
that,
because
I
want
to
make
sure
that
I'm
not
improvising
on
that,
but
yeah
that's
happening
on
Wednesday
I'm
running
by,
do
you
guys
feel
free
to
come
and
then
I
have
one
point
for
James.
So
the
design
issues
for
thirteen
point?
Oh
they
are
still
in
progress
and
I
did
a
lot
of
brainstorming
last
week.
I
think
what
I'm
going
to
do
is
they're
gradually
them
all
like
in
a
big
bank
type
of
design.
A
B
B
A
A
B
Is
that
there
was
a
design
item
to
go
from
the
unit
test
summary
on
the
merge
request,
page
to
add
a
button
to
go
to
the
full
report
of
the
unit
tests
very
similar
to
what
we
have
for
the
security
report
where
you
can
go
from
just
the
summary
report
of
what
has
changed
in
the
security
report
to
the
full
security
report.
Writing
the
same
functionality
for
the
unit
test
results,
so
I
had
created
a
design
issue
for
want
to
go
ahead
and
do
the
design
on
it.
Just
so
we
have
mock
and
well
I.