►
From YouTube: Testing UX / PM / Research sync 2020-05-15
Description
Discussion about adding JTBD to the team's handbook page, Marcel's video about MR widgets and next steps for moving maturity after the score card is finished for Accessibility.
A
A
B
Would
be
doing
so,
we
had
a
I,
don't
know
what
we
called
Malik
Nadia,
there's
different
names
for
it,
but
people
call
it
they
call
it.
Sometimes
they
call
it
jobs
to
be
done.
Skaar
fired.
Sometimes
it's
the
UX
scorecard.
It
is
not
the
category
of
maturity
scorecard,
but
I
can
tell
you
that
much.
So
it's
it's
another
process
to
go
through
for
each
of
the
jobs
to
be
done
to
get
that
grade.
B
C
And
you're
to
my
understanding,
Laurie,
this
is
exactly
how
some
of
the
jobs
to
be
done,
while
those
that
are
rated
on
teams
or
Jackie's
page.
This
is
how
they've
been
rated-
and
here
is-
am
here
I'm
posting
this
work
hard.
So
it's
not
the
maturity
scorecards,
but
the
UX.
There
really
is
easier
effort,
I
would
say,
and
in
the
past
it
was
more
heuristic
analysis
done
by
the
designer.
C
B
I
think
so,
and
I
haven't
gotten
to
this
piece
yet
with
the
giass
we've
done,
but
I
would
also
suggest
that,
if
depending
on
where
the
jobs
to
be
done
came
from
because
people
have
brought
them
from
all
over
the
world,
all
the
four
corners
of
the
world,
sometimes
they
show
up
from
if
they're
not
specifically
rooted
in
customer
conversations
around
jobs,
not
around
features
around
jobs.
I
would
highly
suggest
that
we
also
work
in
some
validation
of
the
job.
B
To
done
so
not
only
testing
that
thing,
but
also
saying
hey,
is
this
even
a
thing
you
do
and
what
do
you
do
with
it?
And
how
do
you
do
it?
So
it's
not
a
heavy
fast
rule.
So
if
you
guys
feel
confident
that
they
are
rooted
in
customer
conversations,
around
jobs
and
tasks
go
for
it
go
go
for
the
scorecard.
It's
just
that
if
you
go
to
the
scorecard
first
and
you're,
not
sure
where
the
game
thing,
it's
going
to
be
a
show.
A
B
D
A
C
B
B
So
I
suspect
they're,
going
to
probably
focus
on
those
priority
ones
first,
when
they
get
back
to
this,
because
I
think
he
had
to
stop
to
work
on
something
else,
but
when
they
get
back
to
grading
this
they'll
most
likely
work
on
those
ones
that
came
up
as
a
high
priority
in
that
survey
that
he
way
in,
and
so
that
was
part
of
their
validation
effort.
James
of
to
validate
the
jobs
to
be
done
as
well
as.
B
So
he
so
what
he,
what
they
did
was
they
constructed
it
in
a
way
that
had
the
survey
taker
selects
the
top
two
categories
of
things
that
they
felt
like
they
did
the
most,
and
then
they
only
asked
them
about
those
two
categories,
so
they
didn't
have
to
go
through
all
of
these,
the
pilot
they
didn't
they're,
like
oh,
my
god,
so
did
we
that
he
were
find
it.
So
you
really
only
got
good
feedback
on
the
top
two
things
and
then
he
had
them
prioritized
within
those
two
categories,
I
believe
to.
A
D
B
D
No
no
I
get
that
so,
but
it's
expectation
that,
like
it
doesn't
matter
that
there's
gonna
be
a
you
do
like
I,
don't
know,
I'd
say
like
a
year.
Has
ten
releases
right,
its
expectation
that
you
do
one
per
release
is
expectation.
You
do
one
every
other
release.
I
mean
there's
that
I'm
more
curious
about
that
than
any
of
you
know
the.
A
Survey
is
also
going
to
validate
like
if
you
have
a
good
base
of
users,
it's
going
to
validate
what
jobs
aren't
important
and
that
helps
prioritize
the
functionality
that
you're
delivering
the
outcomes
of
the
charge
of
leverage,
your
customers
as
well,
those
aren't
important.
So
we
don't
need
to
build
it.
So
we
don't
need
to
score
the
UX
for
it,
god
we're
doing
the
job.
We
can
focus
on
the
things
that
users
actually
need
as
an
outcome
from
our
software.
How.
B
A
Will
brain
dump
that
at
some
point
in
the
not-too-distant
future
and
then
I'll?
Probably
it's
knowing
me
it's
going
to
take
one
of
two
paths:
it
will
be
a
hundred
jobs
and
then
I
will
severe
the
edit
it
or
it'll
be
four
and
I
will
just
be
stuck
on.
All
of
these
things
are
just
the
same
thing.
You
could
just
say
that
in
a
different
way,
so
maybe
we'll
end
up
in
an
in-between
but
likely
that's
what
you're
gonna
get
is
four
jobs
or
a
hundred
jobs.
Okay,.
D
B
I
I
try,
I
started
and
in
my
it's
just
gotten
me
I
feel
like
you
just
wanted.
Tell
Christie
Lissa's
publish
it,
so
people
can
have
somebody
and
look
at,
but
it's
not
a
it's
not
agreed
upon
across
the
organization,
which
is
all
it's
not
published.
Yet
so
the
week
of
Memorial
Day
I'm,
going
to
run
a
workshop
with
a
couple
of
people
from
product
a
couple
people
from
design
and
we're
going
to
come
up
with
a
shared
confirmed
process,
definitions
all
the
things.
B
B
B
A
B
A
Today,
alright
I
just
wanted
to
touch
base
on,
and
one
I
think
you
and
I
could
probably
do
this
eight
days
a
sink
or
outside
of
this
meeting,
but
coordinating
some
usability
testing
with
internal
folks
for
that
code
coverage
design.
There
was
some
discussion
within
the
design
items
in
the
epic
and
we
wanted
to
try
to
do
some
testing,
so
is
that
something
that
we
can
tackle
async?
Yet
today?
Yes,.
A
Let
me
get
that
minutes,
not
he's
gonna.
Do
it
we'll
try
to
take
notes,
I'm
gonna,
keep
moving
then
I
finally
got
a
chance
to
watch
Marcel's
YouTube
review
of
the
mr
widgets
yesterday
and
just
added
a
couple
of
points
that
I
wanted
to
talk
through
with
this
group,
because
we've
also
been
talking
about
art
widgets,
the
biggest
thing
my
biggest
takeaway
from
that
was
I
made
changes,
and
these
widgets
don't
reflect
the
changes
that
I
made
specifically
but
and
I.
A
A
D
D
D
In
the
changes
like
the
actual
changes
are
just
are
just
the
CSS
changes
so
like
his
expectation,
is
that
you
should
be
only
seeing
changes
for.
You
should
always
keep
missing
reports
for
the
changes
and
that's
what
I
explained
to
him,
like
maybe
I'm
wrong
about
this,
but
I
think
correct
me
if
I'm
wrong,
but
like
the
way
that
the
reports
work
is
that
they
are
gonna,
confirm
the
base
and
the
head
of
the
right
and
savory
if
Yuri
base.
D
D
For
is,
if
you,
depending
on
how
you
created
your
branch
and
depending
on
how
your
rebasing
or
your
emerging
or
bringing
branches
into
your
into
your
feature,
branch
like
it's
gonna
change.
The
report
I
think
that
was
his
whole
point,
which
I
think
he
its
Bali,
that
it's
kind
of
confusing,
because
I
actually
had
a
drawing
I'll,
send
it
to
you,
because
I
had
to
do
it
to
make
sure
that
I
wasn't
a
Anders
I,
understood
fully
the
problem
and
yeah.
D
The
problem
happens
when,
because,
when
you
revise,
then
the
head
becomes
the
same
as
the
as
the
the
base
becomes
the
same
as
this
very
good
thing,
but
becomes
the
same
as
the
head
right.
So
the
report
generated
add
the
base
and
add
the
head
is
going
to
only
show
changes
for
your
mr
changes
right.
Sorry
II,
you
general,
if
you
generate
the
reports
without
refacing
and
what's
gonna
happen,
is
that
the
report?
It's
not
gonna,
create
there's
no
depth,
so
it
includes
the
changes
for
that
you're
bringing
from
the
other
branch
right.
C
If
we
ourselves,
not
even
paying
attention
like
I,
think
a
lot
of
people
mentioned
that
they
never
even
read
honestly
from
my
own
experience,
working
with
the
Mars
I'm,
not
off
like
I'm
kind
of
like
better
blinded,
so
that
section
the
beam,
because
it's
so
busy
and
we
are
there.
Ops
and
the
security
information,
looks,
has
the
same
feeling
and
the
same
look
and
feel
which
you
know.
We
should
help
users
to
turn
their
attention
to
the
serious
security
issues
more
than
to
the
other.
C
C
James
and
that
we
are
collecting,
while
we're
trying
to
see
how
we
can
contribute
to
this
and
from
the
very
fine
release
perspective
and
I
actually
went
today
and
look
specifically
at
the
testing
part
and
I
found
some
recommendations
around
improving
the
Amar's
in
general
right
now.
I'm
curious
model
is
really
irrelevant
today,
so
feel
free
to
go
ahead
and
look
into
there.
D
D
Oh
no,
it's
there,
that's
what
happens
before
we
base
and
after
we
base,
and
that's
that's
more
or
less
how
I
had
to
do
it
to
understand
it,
but
I
could
be
wrong
about
how
they're
being
compared,
but
that's
how
I
think
there
could
be
in
compare
and
that's
where
we're
generating
that
issue.
So,
okay
just
wanted
to
say
that
what
you
said
Nadia
is
completely
right.
C
And
because
not
only
like
I
can
imagine
that
not
only
like
technical
people,
though
I'm
not
an
engineering
and
using
that
functionality
right.
So
we
also
have
to
think
how,
like
other,
how
readable
is
to
the
other
users
as
well
I
feel
like
we
have
to
do
a
little
bit
of
like
experience.
Analysis
here,
I
think
that's
exciting
project.
It.
A
B
D
Just
have
to
one
push
one:
here's
gonna
be
for
Laurie
or
yeah
I
think
these,
but
what
it's
gonna
happen
after
we
come.
Also
like
the
category
my
tree
scorecard
interviews,
we
have
four.
We
are
waiting
for
a
fifth
one.
Hopefully
that's
gonna
happen
next
week
and
then
we
can
produce
a
score.
It's
looking
good
and
I
think
we're
gonna
get
a
good
score,
but
what
happens
after
we
produce
the
score?
I
mean
assume.
You
know
that
our
score
is
good.
This
Factory.
D
D
B
B
D
B
Guys
get
together
make
an
educated
guess
as
to
what
you
want
that
those
grades
to
mean
the
new
process
is
gonna,
be
much
more
prescriptive
of
like
there's
a
range
of
number
numbers,
and
this
range
of
numbers
corresponds
directly
to
dis
level
of
maturity.
So
you
won't
have
to
guess
anymore
right
now.
You
guys
just
look
into
it
and
they
make
the
best.
Okay.