►
From YouTube: Testing UX / PM / Research sync 2020-05-29
Description
Today we talked about how we'll record the kickoff video for 13.2 and had a follow-up discussion on where the Accessibility category ended up from the maturity scorecard review.
A
B
C
We
have
been
in
the
past
having
the
UX
kick
offs
videos
for
not
video
store
in
the
department
meetings
for,
like
all
of
the
you
actors
to
get
together
with
a
goal
to
talk
about
one
of
the
issue
that
we're
going
to
be
working
in
the
milestone,
just
to
make
sure
that
we
are
updated
around
the
work
that
we're
doing
in
different
stage,
groups,
updated
and
aligned
and
can
advise.
You
know
like
hey
I've
done
something
similar
in
the
past.
C
It
got
out
a
bit
of
out
of
the
hand,
because
we
are
so
big
right
now,
so
that
meeting
got
canceled
and
we
actually
thought
of
doing
a
similar,
smaller
initiative
in
verifying
release.
You
axiom
and
I
know
that
a
lot
of
other
like
stages
doing
that
as
well,
so
we
thought
of
first
we
started.
We
created
an
issue
where
we
started
posting
hey.
This
is
my
work
as
a
product
designer
in
that
stage
group
for
that
milestone
and
then,
when
we
thought,
let's
do
it
better.
C
I'm,
like
in
a
video
format,
so
we
recorded
the
video
and
then
Jason
de
Muro,
who
is
product
director
for
sei
CD.
He
said:
hey
I'm,
seeing
this
UX
kickoff
videos
that
talk
about
the
UX
work
goes
into
the
milestones
that
are
very
similar
to
the
product
management,
kickoffs
videos,
and
he
said
why
don't
we
combine
those?
We
thought
it's
a
nice
idea,
possibly
a
good
opportunity
for
p.m.
C
and
you
actors
to
calibrate-
and
this
is
where
it
comes
like
we're
trying
to
propose
for
product
management,
to
a
small
pilot
for
13.2
to
do
this
kick-off
videos
together.
I
know
the
different
PM's
are
new
actors
approaching
this
differently.
Somebody
says
a
product
manager
is
opening
the
video
and
talking
more
about
the
high
level
items,
and
then
designers
are
picking
up
the
details
or
the
other
way
around
or
some
product
management
are
saying.
Yeah.
You
extra
cover
the
issues
where
you
access
involved
and
I'm
gonna
cover
the
rest
kind
of
like
then
combined.
A
I'm
gonna
share
my
screen:
real
quick,
because
I
have
a
question
and
a
visual
would
probably
help
so.
We've
just
started
using
the
planning
issues
and
testing.
So
would
we
have
in
here
we'll
have
design
issues
that
are
called
out
and
there's
just
links
to
our
board
with
the
design
workflow
label?
But
we
can
absolutely
then
add
items
here.
Would
it
be
the
items
that
are
intended
to
deliver
the
design
within
the
milestone
or
more
like
up
here
in
our
top
priorities,
the
actual
functionality
is
going
to
deliver
within
the
milestone.
A
What
is
so
I
my
highlight
is
these
items
kind
of
the
key
one
or
two
things
that
we're
looking
to
deliver
from
the
testing
group
direction.
Items
primarily,
is
that
also
what
UX
has
been
delivering
in
those
videos
or
is
the
intent
of
here's,
the
design
that
we'll
be
delivering?
Then
then
the
next
milestone
will
likely
deliver
on
the
functionality.
A
A
I
mean
I
could
see
us
using
it
as
a
like
a
tool
with
customers,
especially
as
we
have
customer
interest
on
an
item
and
say
hey.
This
is
delivering.
You
can
also
be
interesting,
then,
to
say:
hey
this
isn't
its
design
phase.
Now
is
a
great
time
to
jump
in
there.
Look
at
the
user
experience
that
we've
put
together,
make
sure
that
we've
understood
your
problem
correctly
and
the
solution
we'll
get
to
the
outcome.
You
want
and
do
that
before
we
get
into
a
development
state
right.
B
A
B
Feel
as
as
long
as
we
are
clear
at
telling
them
I,
okay,
here's
what's
in
development
in
13.2,
and
this
is
what
we're
working
design
13.2
and
it's
finally
gonna
happen
on.
Like
future
releases,
then
I
think
it's
okay!
Alright,
he
wants
to
do
it
because
it
makes
the
content
of
that
video
more
rich
and
I
think
it
out.
It
opens
more
discussion,
opportunities
and
just
saying
like
most
likely
like
at
least
for
testing
many
times.
B
We
are
implementing
things
that
have
UX
but
then,
like
there's
more,
you
exiting
things
happening
outside
of
what's
been
implemented
in
the
in
the
actual
milestone,
because
we,
the
way
we
work,
is
so
MVC.
So
like
a
small
iterations
like
usually
the
UX
grows
bit
by
bit
by
bit
by
bit
right.
So
like
it's
more
more
likely
I
useful
approach
to
talk
about
what's
coming
and
then
we
can
break
it
down
as
we
move
forward
another
in
other
videos,
I.
C
Think
it's
it's,
it's
really
good
idea
and
I
would
be.
I
would
be
happy
on
and
you
James
we'll
try
that
this
and
yeah
and
we
could
see
what
comes
out
of
that
and
if
there
will
be
successful
tour
opinion
we
could
share
it
with
the
others
and
say
hey.
Maybe
you
want
to
try
this
format
as
well.
I
think
that's
great
I
only.
B
Had
one
question
about
the
logistics,
so
I
talked
with
Darin
about
these
and
so
apparently
some
PM's
the
way
they
are
like
the
majority
of
PM's.
From
what
I
heard,
what
they're
doing
is
the
like
separate
recordings
that
the
idea
that
they
have
is
separate
recordings
and
then
the
UX
work
combines
the
recordings.
But
Darin
had
this
idea.
He
already
actually
took
action
on
it
of
setting
up
a
call
on
the
mic
on
the
day,
some
around
the
release
and
we
go
to
that
cold.
B
We
record
that
call
and
that
call
becomes
a
video
right,
I
thought
that
was
a
great
idea,
because
it's
a
more
efficient
I
mean
we
can
maybe
be
beforehand.
We
can
before
we
start
recording
figure
out
how
we're
gonna
be
talking
about
things,
but
I
think
that
that
was
better
than
just
combining
things
later.
Yeah.
A
B
B
Yeah,
it
seems
that
that's
a
good
idea,
so
I
think
we
on
that
idea
as
well,
who
you
like
for
the
next
one
who
you
create
that
meeting
James
and
send
me
the
invite
Oscar.
Thank
you
all
right.
So
James
had
the
next
one
and
then
I
expanded
a
little
bit
on
these.
But
do
you
want
to
verbalize
your
point?
B
A
I
just
wanted
to
finish
up
our
discussion
on
the
accessibility
maturity
level
of
where
we
landed.
I
looked
at
the
score,
understood
the
score,
but
it
didn't
give
us
a
proposed
maturity
and
it
seems
like
there's,
there's
a
disconnect
in
what
we're
using
to
measure
the
maturity
of
is
this
so
minimal.
Or
is
this
now
viable
category
right.
B
B
Penetration
for
all
market
penetration
or
features
sure
like
displacement
of
other
tools
relative
to
the
market
and
our
users.
So
much
really,
as
he
explained
there,
has
to
do
a
lot
with
internal
adoption,
then
there's
adoption
of
outside
users
so
yeah
that
feature
adoption
seems
to
be
the
main
driver
of
what
makes
you
be
able
to
move
to
the
next
category
to
the
next
maturity
level.
I
understand-
and
this
is
my
interpretation-
the
category
maturity
scorecard-
is
that
you
run
it.
So
you
can
actually
say.
B
Yes,
we
can
move
because
the
the
usability,
the
UX
of
the
of
the
feature
validates
these
and
it
allows
us
to
move
to
the
next,
the
next
level,
but
it
seems
that
the
feature
adoption-
it's
always
gonna,
be
them.
So
you
take
the
decision
to
run
the
category
maturity.
Curves
ask
worker
when
you
know
that
the
feature
adoption
is
at
the
next
level
and
if
it
fails
and
you
cannot
move
because
the
usability
doesn't
it's
not
good
enough
to
move
to
the
next
level,
but
it
almost
feels
like
the
the
main
thread.
B
D
Well,
I
can
I
can
only
tell
you
what
I
know
I
mean
if
we
can
tell
you
that
Kristi
is
working
on
updating
all
of
those
definitions
on
that
page
with
with
products
so
with.
Is
it
a
new
or
do
they
keep
saying
his
name
wrong
and
furnish
she's
working
with
both
of
them
to
give
it
better
a
clearer
statement
around
like
what
does
it
mean
to
be
at
these
different
levels?
D
I,
don't
think
where
they're
going
is
so
much
with
adoption
as
it
is
with
the
functionality
features
like
this
feature
is
allowing
people
to
do
more
tasks
with
this,
because
we
don't
really
have
a
way
to
measure
adoption
right,
especially
with
self-managed
people.
We
don't
know
what
you're
doing
you
just
pay
his
money,
so
yeah.
A
D
B
D
We're
adding
things
to
testing,
adding
things
to
accessibility
testing.
How
is
that
measuring
that?
If
there's
something
out
there
in
the
market
that
we
are
comparing
ourselves
against
and
if
there's
not,
how
do
we
measure
against
what
our
users
are
expecting
us
to
provide
or
what
they
need
if
they
don't
expect
anything
when
they
need
us
to
provide
so
I
think
it's
that's
where
they're
headed
she's
still
talking
with
them,
I
think
it's
been
a
couple
weeks,
so
you.
B
D
B
A
B
D
Like
whoever
was
in
charge
said
we're
that
and
that's
why
we're
trying
to
put
this
scorecard
process
in
place.
So
it's
not
just
arbitrary,
but
all
of
those
are
arbitrary
and
I
was
in
that
discussion
with
Christy
and
finish
and
I
do
around
the
fact
that
what
we
have
now
is
very
arbitrary
on
that
page
and
we
are
going
to
need
to
redo
it
not
immediately,
but
over
time.
D
B
Looking
at
the
feature,
I
think
we're
Bible,
I,
think
I
think
what
the
model
I
think
about
it.
I
think
so.
Like
I
saw
the
new
process,
you
don't
need
to
run
a
category
maturity
scorecard
for
minimal.
So
that
makes
sense
so
like
it
doesn't
even
make
sense
to
me
that
we
rely
on
in
mini
ma
I
think
we
should
be
viable,
the
more
that
I
think
about
it.
What
I
know
and
what
I'm
like
noticing
right
now
is
that
from
viable
to
complete
and
loveable.
It's
a
huge
is
a
huge
step
right,
but.
D
D
B
A
I
mean
for
the
job
to
job,
to
be
done
that
we
described
and
for
the
customer
that
we
talked
to
I
feel
like
it's
a
viable
solution
as
we
talk
about
a
different
persona
like
your
design
manager
or
your
UX
director,
there's
no
feature
there
yet,
but
I
can
express
that
in
a
different
child
to
be
done.
So
then
I
think
at
that
point
it
just
becomes
a
problem
of
for
product
like
what's
the,
how
do
I
prioritize?
B
B
B
Totally
I
think
the
last
point
that
I
was
gonna
mention
about
these
was
that
yes,
we
we
learn
a
Bible
and
but
but
but
also
another
thing
that
we
have
is
in
which
James
has
been
sharing
this
with
me.
He
created
this
place
with
all
the
jobs
to
be
done,
which
all
of
them
are
gonna
have
their
own
score.
We
talked
about
these
before
so
I
think
it's
just
a
process
of
like,
as
we
keep
working
on
those
job
to
be
dance
and
we
keep
moving
forward
and
we
keep
moving
forward
like
next
year.
B
We're
gonna
look
at
that
patient.
We're
gonna,
be
like
you
know,
it's
time
to
run
a
new
category,
maturity
score
and
see.
If
we
can
move
to
complete
you
know,
and
most
likely
by
that
time.
This
is
gonna
be
way
more
clear,
so
I
think
we're
good
yeah,
I.
Think
the
mom
I
think
the
the
I
think
we're
buyable
and
I
think
we
should
update
the
page
to
show
that
we're
buyable
I
won't.
B
B
Oh
yeah,
great
yeah,
yeah
I
did
ensure
that,
but
was
you
will
pretty
smooth
besides
that
final
customer,
that
almost
didn't?
We
almost
couldn't
recruit
that
last
customer,
but
it
finally
happened.
Everything
went
well,
the
feature
was
like
yeah,
people
could
use
it
and
you,
the
most
exciting
part,
is
by
being
when
you
ask
them
about
gridlock,
and
everyone
is
happy
about
it.
Love
you
know
like,
like
everyone
like
says,
like
they
loved
you
love
and
they
really
like
what
we're
doing
and
yeah
there's
still
things
that
we
need
to
foliation.
B
There
should
still
I
mean
we.
We
are
a
hyper
growth
company
with
a
lot
of
things
going
on,
but
but
but
you
can
tell
by
talking
to
customers
that
we
are
on
the
right
track
and
I'm
excited
about
that
and
I'm
excited
about
being
part
of
that
you
know
so.
Yeah
I
went
well.
I
was
super
happy
with
the
with
the
result,
amazing.