►
From YouTube: Verify & Release By-weekly UX Meeting | 17th April 2020
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
B
Let
me
finish
my
line
of
thought
here:
yeah
just
this
kind
of
like
a
heads
up.
Well,
I,
don't
see
the
meters
it's
out
of
office,
so
perhaps
you
can
discuss
this
further
asynchronously,
but
I
had
a
conversation
with
Jackie
this
week
earlier
this
week
about
environment
variables
and
this
all
these
questions
you
know
in
wanting
to
standardize
things
and
having
an
extr
I.
B
A
It's
actually
a
good
topic.
I
think,
like
I,
saw
I
totally
forgot.
Where
did
we
discuss
that
yesterday?
A
I
should
share
later
I
had
a
great
discussion
with
Ian
today
in
regards
to
like
the
retrospective
on
the
thing,
big
cross
testing
big
session,
and
we
thought
that
we're
is
the
perfect
discussion
to
have,
as
a
think
big
session,
of
course
doing
some
of
the
adjustments
based
on
the
last
session
to
make
sure
that
we
have
it
a
bit
more
effective
and
a
bit
more
straight
to
the
point.
Yeah,
so
I
don't
know
Vienna.
How
do
you
want
to
approach
that.
B
I'm
not
sure
yet
I
feel
like
I
need
to
get
more
more
context
from
from
Jackie,
but
from
what
I
understood
and
also
based
on
the
research
that
she's
that
she's
conducting
how
the
interviews
and
the
latest
discussions
with
Wow
was
it
Kenny
anyways.
One
of
those
guys
was
that
the
discussion
was
about
me
in
the
split
and
yeah,
not
sure
so
sorry.
A
Yeah
I'm
just
typing
along
yeah,
so
that
I
think
like
or
it
is
planning
some
work
around
there
or
it's
already
actually
like
started
and
I.
Think
it's
very
important
for
us
to
align
so
hi
Anna.
Maybe
whenever
you
have
a
little
bit
more
information,
what's
what's
the
call
from
Jackie's
I
think
maybe
we
should
even
like
move
the
discussion
a
little
bit
sooner,
so
we
can
all
meet
an
align.
At
least
we
are
not
crossing
each
other
path
passes
and
maybe
we
can
be
helpful
to
each
other
there
and
work
together
on.
C
That
yeah,
because
I
think
with
the
AWS
the
point
AWS
research
that
I
just
finished
talking
to
people
about
one
of
the
questions,
was
around
environmental
environment
variables
in
secrets
management.
So
I
was
asking
them
like
how
do
they
use
environment
variables,
which
environment
variables
do
they
use
or
define?
And
then
there
was
a
question
around
secrets
so
like
how
our
secrets
past
how
our
secret
is
managed.
So
there's
data
on
both
of
those,
especially
in
terms
of
AWS
in
those
sessions.
C
So
I'm,
not
I,
don't
know
enough
about
the
difference
between
the
two
like
I
know.
What
secrets
are
and
I
get
what
environment
variables
are,
but
I
don't
know
how
they
either
are
different
or
work
together.
So
I
don't
understand
the
split
splitting
them.
It
seems
to
me
like
everybody
needs
them,
but
that's
my
ignorance
talking.
So
let
me
know
how
I
can
help
how
I
can
share
that
information.
B
Because
I
think
it's
also
more
from
a
new
point
of
view
that
we
don't
have
the
capacity
to
work
on
CI
variables
right
now,
so
we
can
collaborate
with
it
design,
if
that's
the
case,
but
then
we
don't
execute
anything.
So
to
me
the
concern
is
if
we
still
treat
as
one
single
thing
across
across
the
board,
we
still
need
to
define
a
DRI
and
if,
for
example,
verify
is
executing
everything
I
think
it
makes
sense
that
the
DRI
is
the
you
know
the
designer
of
verify
assigned
to
this,
and
then
we
collaborate.
Let's
look.
D
D
Like
obsessively
talking
about
stop
tick
a
lot
but
I
I
wanted
to
make
sure
that
we
we're
still
aligned
and
I
like
finding
areas
where
we
can
improve
on
this
process.
So
I
wanted
to
talk
about
the
category
mature
process
because
I
know
Hannah's
going
through
it
and
I'm
going
through
it
and
from
my
discussions
we
Neriah
with
Lori
and
with
other
people.
I
have
noticed
that
I
don't
know
your
my
life
met.
D
Then
the
process
is
gonna,
be
super
simple:
it's
not
daunting
and
not
spread
where
they
know,
but
it
feels
that
once
you
start
getting
into
a
larger
category,
it
can
become
very
daunting
right
because
there's
gonna
be
a
lot
of
job
to
be
done.
A
lot
of
testing
scenarios,
so
I
didn't
have
specific
questions
for
this.
Ii
just
wanted
to
see
how
people
are
perceiving
it,
and
perhaps,
if
see,
if
that
perception,
that
idea
shirt
is
the
correct
one
and
if
that's
the
case,
how
can
we
yeah?
D
Especially
when
we,
when
we
start,
we
like
very
large
categories,
I
think
that
this
still
needs
to
scale
and
like
it
doesn't
scale,
then
it
becomes
more
like
hard
rock
for,
like
our
work
and
I
want
to
be
sure
that
we
are
giving
that
feedback
back
soon
ori
and
to
anyone
who
is
involved
in
Pras.
Oh,
you
know
improving
the
process
of
the
category
maturity
scorecard,
I,
don't
know,
I
saw
how
Janna
wanted
to
type
something
and
she
stopped.
Maybe
you
want
a
little
eyes.
What
do
you
want
to
see.
B
Yeah
I
think
from
my
case
is
a
bit
different
because
I'm
already
using
my
user
insights-
and
we
collected
over
it
a
couple
of
last
few
months
to
support
the
change
in
the
maturity
forever
his
orchestration
and
that
for
us
we
have
one
main
job
to
be
done
and
one
scenario
that
we're
focusing.
So
it's
a
bit
different
in
the
sense
of
yes,
we
have
a
lot.
B
C
So
part
of
the
category
maturity
scorecard
process
will
change.
I've
got
an
update
in
the
UX
team
weekly
next
week,
but
I'll
tell
you
guys
so.
Basically,
I
didn't
interviews
with
designers
and
product
managers,
as
you
guys
know,
and
what
I
learned
was
that
exactly
what
Juan
is
saying
like
if
you
have
something
very
small,
it's
very
easy
process
to
go
through.
If
you
have
something
very
large,
it's
very
daunting
and
it's
hard
to
scale
it
up
to
something
it
scale.
C
What
we
have
now
up
to
something
very
large,
so
I
proposed
a
couple
of
changes
to
the
process
and
Sara
and
I
are
gonna
work
on
how
to
don't
look
for
those
changes.
I'm
not
really
sure
I'm
gonna
meet
with
Sarah
on
Monday
and
talk
about
it,
but
basically
we're
moving
away
from
the
qualitative
piece
of
it.
C
Piece
of
that
of
the
category
of
attorney
scorecard
process
and
more
quantitative,
so
more
numbers
driven
so
less
less
like
a
usability
tests
more
like
a
summative
or
benchmark
process,
where
you
still
give
the
person
a
scenario
or
a
couple
of
tasks
that
align
with
your
job
to
be
done.
But
you
don't
have
to
ask
them
any
questions,
they
don't
talk.
They
go
through
the
process,
you
capture,
how
long
it
takes
them.
C
You
ask
them
these
two
questions
that
are
from
the
UX
light
scorecard
and
it's
just
two
questions
and
they're
actually
calibrated
to
the
NPS
and
to
the
sus
score.
So
you
don't
have
to
ask
those
questions.
You
just
ask
these
two
as
well
as,
like
you
know,
any
errors
that
they
made
and
did
they
succeed,
or
did
they
fail
at
the
task,
so
that's
kind
of
how
that
process
is
going
to
change.
C
So
no
more
counting
clicks,
no
more
any
anything
like
that,
but
the
more
important
part
of
that
is
that
this
process
isn't
supposed
to
be
done.
Just
because,
oh
it's
Tuesday.
We
need
to
do
this
or
my
PM
told
me.
I
had
to
do
this
or
my
PM's
manager
told
them
they
have
to
do
this,
and
then
they
told
me
that
we
have
to
do
this.
This
process
needs
to
be
done
only
after
you
complete
that
UCD
process
with
that
feature
or
function.
So
that
means
like
all
the
stuff
that
you
guys
are
doing.
C
D
D
C
D
C
No,
it's
not
you
it's,
it
is
it's!
It's
I've
read
through
the
process
and
I've
talked
with
Jeff
I've
talked
with
the
research
team
of
toxic
Christi.
I
talked
to
the
leadership
team.
I
think
they
were
just
some
assumptions
made
in
how
the
process
was
written
up
that
this
would
only
be
used
after
a
feature
or
function
went
through
that
UCD
process,
but
because
we
didn't
explicitly
say
it,
and
there
was
that
okay
are,
that
everybody
had
that
pressure
on
them
to
feel
like
they
needed
to
do
the
scorecard
or
the
quarter
was
up
I.
D
C
Advice
if
we
can
get
James
to
back
away
from
wanting
to
get
this
done,
is
to
do
a
quick
five
user
test.
With
your
your
solution
run
it
through
usability
testing.
You
really
need
to
do
that,
because
this
new
process
is
not
going
to
have
any
qualitative
data
you're
not
going
to
get
a.
Why
you're
actually
going
to
actively
encourage
them
not
to
talk
during
the
task,
because,
if
you're
going
to
take
time
on
task
measurement,
they
can't
talk.
So
that's
it.
That's
a
big
change
from
how
we
initially
view
this.
C
This
measurement
so
I'm,
going
to
tell
everybody
again
on
Tuesday
you'll,
hear
it
again
to
do
that.
Ucd
process.
Do
those
usability
tests
because
you
need
to
get
to
the
point
where
you've
got
it
down
like
you've,
refined
the
feature
function,
you've
to
your
best
knowledge
and
your
product
managers
best
knowledge.
You
have
reduced
any
errors
that
could
come
up
any
confusion
that
could
be
there.
It
is
in
the
best
state
you
can
get
it
in
now.
Let's
go
see
how
it
performs
in
this
summative
evaluation.
C
Now
the
other
part
of
this
in
I
learned
this
recently.
That
is
missing
is
that
product
management
needs
to
tell
us
how
they
want
to
consume
these
measures
that
we're
going
to
give
them
I,
don't
know
how
they're
going
to
use
this
data
I,
don't
they've
had
time
to
think
about
it
either
but
like
if
we
go
through
all
this
process
and
we
get
these
measurements
in
this
data.
How
are
they
going
to
take
that
and
then
apply
that
to
the
category
of
maturity,
because
as
I
understand
it
we're
not
defining
maturity
for
them.
C
We're
only
gathering
this
data
and
telling
them
how
it
performed,
and
as
we
get
more
data,
we
can
tell
it
how
it
performed
over
time.
It's
their
call
to
say
how
are
they
going
to
apply
that
to
the
maturity
of
the
category?
So
there's
there's
also
that
other
half
there
and
my
message
to
Christie
and
the
leadership
team
is
go,
go,
find
whoever
is
in
the
product
team.
C
We
need
to
talk
to,
and
let's
have
a
conversation
about
that,
because
what
I
want
to
do
is
I
want
to
present
this
new
way
and
then
tell
them
what
they
will
get
out
of
it
and
then
work
with
them
to
figure
out
how
they
will
consume
it.
So
we
can
make
sure
our
process
matches
with
what
they
need
to
make
a
good
judgment.
So.
D
C
It's
like
yeah,
it's
like
I
felt
successful
on
a
scale
of
one
to
seven
like
I
yeah.
It's
it's
just
two
questions
around
that
like
success
and
feeling
good
about
it,
yeah
yeah
and
then,
at
the
same
time,
you're
like
you,
are
watching
for
errors,
you're,
counting
errors,
you're
counting
how
long
it
took
them
and
you're
seeing
you're
noting
if
they
succeeded
or
failed
at
the
task.
So
it's
very
much
more
stripped-down
one
of
Valerie's
concerns
was
this
current
process.
In
her
perspective
takes
like
three
months.
This
should
not
take
three
months.
C
D
D
C
So
that's
the
other
part
that
I'm
trying
to
figure
out
how
we
can
make
happen
because
you
need
the
video
right,
cuz,
you're
gonna
need
to
watch
them
and
I
talked
to
Ian
about
his
proposal
to
use
the
product
concept.
Testing
feature
in
Qualtrics,
along
with
a
pre
like
a
pre
setup,
zoom
room
that
automatically
the
course
when
somebody
goes
in
it,
but
he
hasn't
done
it.
Yet
that's
his
that's
his
proposal,
cuz
I
thought
he
had
done
it.
C
He
had
oh
I
need
to
figure
out,
or
somebody
needs
to
figure
out
if
that
will
work,
because
we
don't
have
user
testing
column
or
something
like
that,
we
have
Qualtrics
so
that
it,
but
you
are
right,
we
could
technically
do
it
that
way.
If
we
can
figure
out
the
best
way
to
get
the
tool
to
do
it.
There.
D
C
Yeah
cuz,
technically,
you
would
want
to
if
you
have
more
than
one
segment
that
you
designed
for
you
would
want
to
do
like
five
or
six
people
per
segment.
So
that's
where
we're
gonna
go
we're
not
there
yet,
but
yeah,
no
I
totally
believe
I
totally
get
you
one.
There
are
tools
out
there.
I,
don't
know
what
the
budget
is.
I
feel
like
that.
Should
the
sales
good
suite
we
started
our
new
new
year
but
I.
Don't
don't
quote
me
on
that,
because
I'm.
D
C
Sure
I
think
if
we
can
prove
that
we
really
need
another
tool
and
that
Qualtrics
won't
do
what
we
need
it
to
do,
will
most
likely
be
able
to
to
get
it
but
I
think
I,
feel
least
of
it.
You
could
pair
this
to
evaluation
with
another
session
with
somebody
so
still
scheduled,
like
30
minutes.
Have
them
do
this
for
10
of
those
minutes
and
then
have
another
conversation,
others
different
topic
all
together,
so
you
wouldn't
you
don't
also
have
to
think
of
this
as
one
ever
combined
to
write.
D
A
Agree
with
you
hon
and
thanks
for
bringing
a
topic
in
the
beginning,
Laura
I
think
that
was
like
great
to
share
some
of
the
insights
and
some
of
this
like
big
major,
well
changes
that
are
coming
in.
Hopefully,
this
will
allow
us
to
have
a
more
like
wait
process.
It
definitely
sounds
like
that.
So
thanks
for
it
for
an
update
on
that
side,
yeah,
we
will
be
sharing
more
details,
I
guess
as
we
go,
but
for
now
Laurie.
A
C
A
D
Ok,
so
this
is
just
a
small
note,
but
I
saw
that
we
had
we.
We
started
the
product
area
here
document
her.
She
had
a
table
now
what
the
table
is
gone
because
I
think
that
was
confusing.
Now
that
we
have
like
all
the
areas
added
I,
think
I
would
just
wanted
to
make
sure
what
are
the
next
steps.
So
should
we
start
like
drafting
our
names
next
to
the
listed
areas?
Should
we
I,
don't
know
I
kind
of
like
want
it?
I
don't
want
this
to
go
stale
so,
like
I,
just
I'm.
A
On
it
on
so,
it
will
not
go
stale
and
thanks
for
bringing
this
up
and
following
up
on
that,
so
I
remove
the
table
there,
because
I
have
put
it
in
the
beginning
to
just
keep
the
discussion
off.
But
then,
when
I
understood
when
like
I've
seen,
this
is
a
suggestion
from
Dmitry,
like
the
level
of
the
granularity
of
the
functionality
that
we
want
to
highlight.
I
was
thinking.
A
Okay
table
is
not
gonna
help
and
just
to
avoid
the
confusion,
I
removed
it,
and
if
that
cost,
as
some
thoughts-
and
this
is
a
great
question-
I
was
discussing
this
with
Christy
saying
that
hey
we
have
this
challenge
right
now
what
we
are
trying
to
figure
out.
How
do
we
want
to
talk
about
those
with
that
work?
That
happens
in
other
stages
and
we
may
like
walk
across
each
other?
You
know
ways
and
yeah
hey.
A
This
is
a
pretty
tough
love,
a
challenge
that
I
feel
we
need
again
I
what
we
have
summarized
with
Christy
that
we
need
to
bring
this
up
more
on
the
cross
level
and
I
have
this
topic
for
the
next
few
acts.
Leadership
team
just
to
see
team
meeting
just
to
see
if
anybody
was
doing
something
around
that
anybody
has
other
better
ideas,
and
let
me
be
honest
with
you
here:
I'm,
not
sure,
if,
like
for
us
making
that
theory
list
in
the
issue
would
be
very
helpful
again.
A
I
would
like
yeah
I,
appreciate
the
help
there
and
like
I,
think
we
should
just
try
to
get
it
started
thanks
for
everyone
who
have
put
it
the
insights
there,
but
just
FYI
I'm
searching
for
a
better
way
to
solve
the
challenge
and
yeah
I
think
we
need
to
work
here
again
cross
stage.
This
is
why
I'm
trying
to
involve
the
leader
from
others
from
other
stages
and
group
stages,
to
see
what
can
we
do
together
around
that?
If
anyone
has
any
input
or
ideas,
let's
share
them
right
now,
I.
D
Don't
have
I
think
that
there's
actually
a
challenge
there,
so
I,
don't
know
I'll,
Google
stuff
and
see
if
I
find
something
interesting.
You
know
we
can
so
it's
impossible
that
we're
the
first
people
who
are
like
facing
this
problem
like
there's,
like
thousands
of
organizations
that
are
like,
kidnapped,
we're,
like
probably
they
have
like
cross
group
dependencies
and
they
have
to
define
this
theorize.
So
I
must
imagine
that
there
must
be
like
something
out
there
that
already
solves
that.
Somehow,
like
some
framework
or
something.
A
Yeah,
as
I
said,
like
you
know,
I
was
I'm
trying
to
look
at
the
bigger
organizations
who
are
having
similar
like
huge.
You
axe.
Teams
that
need
to
be
aligned
cannot
really
spot
anything
yet,
but
I'm
on
that
and
look
yeah
I
would
be
keeping
you
posted.
If
anyone
wants
to
help
me
here
or
have
any
other
ideas,
super
open
for,
like
collaboration
and
brainstorm
together,
but
yeah
otherwise
I
will
be
keeping
you
posted.
A
A
You
okay,
next
one
is
mine.
I
already
touched
touched
upon
this
a
little
bit
today.
In
the
morning,
we
had
a
really
nice
kind
of
like
follow
up
with
Ian
about
how
the
cross
stage
thing
being
discussed,
went
I,
think
that
was
last
week.
He
shared
with
me
the
insights
from
another
session
that
package
team
had
involving
some
of
the
folks
from
the
security
because
they
have
some
dependencies
on
each
other,
and
let
me
actually
share
that
issue
with
you.
Just
bear
with
me
real,
quick
this
one,
because
the
feedback
was
really
great.
They're.
A
Here-
and
you
know,
I
was
asking
him
like.
There
was
another
like
cross
stage
session,
that
they
performed
and
I
was
asking
Ian
like.
What
do
you
think
was
the
difference
between
ours,
because
I
honestly
didn't
feel
like
if
that
session
was
very
successful,
that
we
had,
but
the
one
that
they
had
was
secured
together.
It
seems
like
it
went
smoother.
D
A
Was
much
more
positive
comments
there
in
the
issue,
so
we
aligned
on
them
a
lot
and
we
kind
of
like
did
a
quick
brainstorming
together
on
how
we
can
solve
some
of
those
feedbacks
that
we
received
and
some
of
those
concerns
that
we
have
heard,
and
we
have
found
ourselves
a
lot
of
of
that
like
brainstormed
in
this
narrow
board.
So
you
couldn't
use
mural
because
it's
really
like
post
crushing
on
me
every
time.
I
will
make
sure
that
I
extract
this
insight
and
add
this
to
the
retrospective
issue.
A
B
It's
like
what
we're
doing
for
release
management
you're
welcome
to
join,
but
we
are
we
don't
officially
in
fact,
everyone
we
have
the
dris,
for
example,
only
the
seniors
back-end
and
front-end
or
engineers.
There
are
currently
effectively
working
on
the
think.
Big
issues
are
stable,
counterpart,
let's
say
yeah.
If
you
want
to
join,
you
can
but
I
think
that
also
creates
more
accountability
for
the
cross
station.
B
Maybe
I
might
just
want
to
highlight
the
point
from
the
last
with
respective
that
I
think
we
should
prepare
more
AC
or
prior,
because
it's
a
bit
frustrating
when
you
have
room
for
with
product
managers.
No
one
has
anything
to
share
it's
like
it's
also
that
we
are
doing
this
to
be
more
design
wet,
but
we
need
their
involvement
as
well,
so
I
think
I
think
it's
a
good
points
to
know.
Just
have
more
focus
on
specific
specific
topics.
Yeah.
A
On
support,
hey
Anna,
that's
one
of
the
topic.
If
one
of
the
improvements,
we
are
also
making
sure
that
we
give
people
a
little
bit
more
like
homework
preparation,
because
the
success
point
was
for
the
session
that
Ian
run
that
they
have
prepared,
like
some
video
walkthroughs,
that
people
had
to
watch
before
joining.
So
that's
a
good
point
that
we
also
added
to
this
to
the
board
and
I
sent
you
an
invite
the
replica
Yahoo.
So
you
should
be
hopefully
also.
B
See
because
I
discussed
this
with
Rick
Jackie
last
week
after
and
she
created
this
virtual
quest.
I
think
your
your
added
to
it,
but
this
version
quest
to
identify
cross
off
sessions,
initiatives
and
link
them
on
the
pages
of
different
of
different
product
areas.
So
this
one
here
software
example:
when
we
are
reading
package
or
verify
there
is
a
link
to
a
release,
documentation,
page
or
little
release
vision
where
we
talk,
how
those
things
overlap.
A
Okay,
if
the
is
anything
happening
on
variables
or
module,
quests
or
whatever
that
they
can
check
in
and
maybe
like,
even
how
to
say,
lemonade
a
discussion
for
one
of
these
crossing
sessions.
So
it's
in
that
is
this.
Is
this
ideas
in
among
this
mirror
outcomes
there
and
I
will
have
a
look
into
this
amar
from
Jackie
I
to
see
if
this
is
something
that
can
help
us
with
that
idea.
So,
thanks
for
sharing
that
I'll
have
a
look
later.
A
B
That's
a
tough
one.
I
want
to
suggest
moving
this
call
to
a
different
day
of
the
week,
because
for
us
it's
like
Friday
in
the
day,
I
don't
think
it's
possible
to
move
any
earlier,
because
our
focus
on
the
other
side
of
the
world.
But
it's
difficult
to
find
something
like
on
a
Tuesday
where
everyone
is
free,
so
I
don't
know.
Do
people
have
a
strong
feelings
about
keeping
this
ball
on
a
Friday,
or
should
we
look
at
a
different
day
of
the
week?
What
do
you
folks
feel
about
this
topic.
D
I'm,
okay,
with
moving
it
I
mean
as
long
as
long
it's
something
that
works
for
everyone.
My
birthday,
it's
not
good,
usually
help
like
testing
calls
you
in
the
morning
Wednesday.
We
already
have
like
you,
you
have
showcases,
but
those
are
monthly.
I,
don't
remember
bi-weekly
whatever.
So
we
who
like
actually
take
that
slot
right
and
basically
every
other
week
will
be
you
extra
case
and
every
other
week
skip
week,
will
be
awesome.
D
C
B
A
B
A
I'm,
just
not
sure
if
people
have
other
meetings
scheduled,
for
example,
Laurie
in
one
of
the
Wednesday's.
Well,
it's
actually.
Instead
of
your
actual
case,
we
have
the
capstone
project
ketchup.
If
I
think
it
will
work.
If
people
do
not
schedule
other
sessions
already
in
that
spot,
so
I
can
yeah
move
it,
and
then
we
can
try
to
move
other
sessions.
If
everyone
is
after
that,
yeah.
B
Thank
you
finally
you're
next
yeah.
We
added
this
I
think
here
before,
and
the
hooker
on
a
thing.
Maggie
and
I
were
talking
about
like
swapping
books
and
just
book
recommendations,
and
my
idea
was
really
more
something
for
us
here
on
this
side
of
the
world,
especially
now
that
well
now,
because
the
meat
is
not
in
the
country.
But
since
we
are
in
the
Netherlands,
we
could
swap
physical
books.
B
So
instead
of
doing
the
digital
team
or
as
a
group
spend
some
time
like
doing
something
but
like
what
the
folks
are
doing
for
the
UX
book
club,
for
example,
areas
related
to
alternative
CI
CD,
if
it's
not
too
much
or
too
boring
or
anything
different
anyways,
it
was
just
a
really
a
brain,
fart
and
I'm,
not
sure.
If
any
of
you
are
already
part
of
the
book
club,
but
maybe
not
a
do
you
want
to
take
over
cuz.
You
are
yeah.
A
I
just
saw
I
did
it
there
also
what
to
see
how
that
overlaps
have
to
be
honest,
that
I
love
the
idea
of
the
Jax
book
club
that
hold
the
anything
idea,
I
have
started.
I
have
to
be
really
open
here
and
honest
I,
never
managed
to
join
one
of
those
I
think
this
is
like
the
same
situation
as
with
the
UX
Hangouts.
You
always
like
put
those
as
a
lower
priority.
A
B
Or
maybe
it
was
like
a
book
club
book
club
or
I.
Don't
know
we
just
spent
some
time
sharing
something
interesting
like
it
works
best
practice
or
something
that
I
don't
know
video
class
with
it,
whatever
something
in
that
sense,
every
now
and
then
I,
don't
think
needs
to
be
something
we
do
every
week.
This.
D
A
What
we
have
talked
with
the
horn
about
was,
if
we
have
the
design
review
sessions
like
finishing
too
early,
or
we
don't
have
much
to
discuss
there.
We
could
like
share
some
of
the
insights.
You
know,
okay,
who
have
read
anything
interesting
or
who
have
watched
something
interesting
words,
and
at
the
conference
there
was
nice
kind
of
like
sharing
some
best
practices
or
knowledge
sharing
session.
Instead,
I.
D
Yeah
I
now
remember
what
I
said:
it's
a
impasse,
things
that
I
have
worked
on.
We
usually
have
at
this
type
of
meeting
with
an
agenda
and
at
the
bottom
someone
would
put
like
articles
that
they
read
there's
time
at
the
end
of
the
meeting
we
can
like,
we
can
be
like
Oh
check
this
article
and
they
give
like
a
small
summary.
It
doesn't
need
to
be
you
X
either
you
know,
sometimes
people
will
just
put
like
memes
and
stuff.
So
this
is
just
like
a
fun
part
of
the
meeting.
D
B
Yeah
but
it'll
be
cool
like
I,
like
the
part
of
just
any
couple
of
links
or
some
things
that
we
found
interesting
I
remember
once
Christine
mentioned
some
things
about
I
know
you
wax
podcasts
or
whatever
just
some
things.
Indeed,
the
agenda
of
the
UX
call
and
I
thought
that
was
super,
not
no.
It
wasn't
that
it
was
a
newsletters
like
designers
letter,
so
I
think
I
miss
this
type
of
sharing.
B
You
know
between
the
group
and
I
think
that
I
personally
feel
like
with
the
design
group,
is
just
too
big
to
have
this
this
type
of
discussions,
and
then
it's
like
this
one
minute,
where
I'm
reading
something
and
saying
hey,
check
out
this
link,
and
then
we
don't
talk
about
it.
So
I
mean
we
can
try
it
out.
I.
A
Like
that,
and
just
like
brainstorming
on
your
thoughts
on
top,
do
we
have
like
a
place
where
we
dump
all
of
this
information
just
to
not
to
lose
it
like,
for
example,
a
selection
was
like
say,
go
and
say:
hey
I've
read
this
book
or
at
that
article,
and
then
maybe
you
could
just
use
that
as
a
like
a
historical
library.
During
this
time
some
will
have
some
time
left.
Looking
media
in
the
agenda.
A
Let's
do
it
I
mean
yeah.
I
could
add
a
section
to
this
document,
so
we
can
keep
this
as
a
library
and
also
like
if
someone
feels
like
hey
I,
suddenly
have
some
time
on
the
quarantine
to
go
over
some
additional
information.
That
would
be
a
nice
place
to
go
and
have
a
look,
and
then
we
can
also
use
it
as
a
discussion
whenever,
like
the
meeting
is
shorter
or
whenever
yeah,
whenever
we
just
want
to
talk.
I
like
that,
I
will
I'll
add
the
part
I'll
added
section
somewhere
in
this
document.
A
D
D
D
A
Yeah
I
feel
like
we
have
the
discussion
in
the
past
and
why
don't
we
I
would
encourage
everyone
to
use
milestone
retrospectives,
because
honestly,
I
don't
see
much
activity
from
our
team
and
I
know
that
we
talked
in
the
past
that
it's
the
timing
of
those
milestone.
Retrospectives
issues
is
sometimes
weird
like
you
like
the
tense
one
coming
up
and
we
are
almost
done
with
the
next
one,
but
it
shouldn't
be
really
the
big
of
a
difference
when
the
one
we
place.
A
B
I
agree:
I
tend
to
keep
it
for
last
minute
in
the
group
retrospective.
So
in
this
case,
for
example,
I
haven't
brought
anything
yet,
but
maybe
we
can
try
as
well
like
since
we
have
the
time
and
wrapping
a
flick,
the
calls
cuz
we
do
this
by
we
flavor
it
and
say:
okay,
what
did
we
learn?
What
could
have
we
done
better
and
then
yeah
later
on,
you
can
add
misinformation
yourself
to
the
the
you
guys,
because
I
feel
like
to
me.
This
is
really
something
that
I
have
to
stop
and
look
back
at
everything.
B
D
I
think
well
now
that
I
think
about
it.
There's
like
things
that
I
can
often
top
of
my
mind
that
I
can
say,
like
things
that
went
well,
I
think
that
we
as
a
team,
we
did
a
better
job
in
this
milestone
to
be
all
in
sync.
You
know
I
unashamed,
like
trying
to
like
be
sure
that
we
are
doing
things
that
cross
pollinate
and
that
we're
not
affecting
our
like
other
groups
in
the
intersection.
You
know
so
I.
D
Also
think
also
not
everything
writing
when
well
was
the
transition
between
what
we
had
before
when
we
were
like
CI
CD
and
now
that
we're
like
ops
is
slash,
verified
I
I
mean
that's,
who
do
soo-eun
area
and
just
him
that
I
felt
that
that
was
very
smooth.
You
know,
I,
don't
feel
that
I
mean
yeah.
We
had
some
moves
from
like
people
and
everything,
but
I
think
I
got
it
burg
pair,
like
you
guys,
communicated
that
very
efficiently
and
now
I
understand
why
we
did
it
and
like
yeah
and
get
until
disruptions
from
that.
B
One
from
this
is
like
general
right:
it's
not
just
us,
as
in
yeah
I,
think
for
me
what
we
can
improve
like
when
I
look
back
at
the
category
maturity,
the
conversations
it's
it's
a
bit
bumpy
but
I
know,
even
though
I
know
that
it's
a
bit
of
a
weird
process.
I
know
that
I
can
count
on
Laurie
and
all
the
feedback
and
help
memory
has
provided
to
give
us
not
just
work
context,
but
also
provide
a
North
Star
for
what
we're
doing
that
has
been
super
helpful
and
I.
Think
I
would
be
completely
lost.
B
Learning
without
you
thank
you.
So
that
was
a
good
thing,
but
I
think
in
general.
Moving
forward
yeah
when
I
look
at
this
book
er.
Is
it
it's
a
bit
frustrating
to
start
something
knowing
that
I
cannot
fully
finish
it
so
and
I
have
to
write
this
later
on
in
the
team
milestone
retrospective.
That's
yeah
I
understand
that
you
have
to
aim
high
when
you
don't
know
PR,
but
it's
a
bit
it's
a
bit
judgmental
for
when
it
causes
that
much
friction
our
figured
out
how
to
like
that.
A
That's
a
good
one
and
I
feel
like
that's
very
important
one
for
the
past,
milestone
in
our
terms,
yeah
I
feel
the
pain
but
I'm
happy
with
the
amount
of
help
and
support
we
got
from
you,
Laurie
from
who,
from
Chrissy
from
Jeff
from
everyone,
so
yeah
I
think
it
was
a
great
learning
at
the
end
and
I'm
happy
to
see
that
we
are
actually
coming
out
with
a
different
process.
Out
of
that,
you
know
with
with
some
good
lessons
learned
so
yeah.
A
A
I
wish
I
would
be
able
to
add
some
data.
My
head
is
just
like
so
blank
I
definitely
understand
your
current
plan.
Right
now,
I
really
have
to
I
feel
like
there
was
so
much
happening
and
I
don't
know.
I
need
to
really
go
back
and
see
what
were
the
the
things
that
we
could
improve
or
highlight
specifically
yeah
I
feel
like
we're
doing
a
lot
of
great
stuff.
B
A
D
B
Think
once
we
figure
out
like
okay,
this
is
a
good
format.
It
will
be
nice
to.
You
know
showcase
this
to
to
do
the
bigger
design
team
at
Kate
lab.
So
maybe
that
goes
into
the
what
we
can
do
better.
What
we
improve
I
know,
but
I
see
us
as
verify
release.
Designers
show
your
faces.
You
know
putting
our
faces
out
there
and
saying
hey.
This
is
how
we're
how
we're
doing
this
great
job
and
it's
our
communicating
with
the
PN's
and
the
teams
I,
think
that
would
be
nice
to
highlight
this.
A
For
sure,
good
one-
and
we
are
the
progress
working
on
that
as
well
and
actually
now
I
have
a
good
one
for
something
that
I've
already
started
a
discussion
with
some
of
you.
I
know.
We
talked
with
you
one.
We
talked
with
UK
Anna's
one
on
our
one-on-ones,
so
that's
something
that
we
could
improve
on
the
organizational
level
UX
organisational
level.
A
This
is
the
discussion
at
coming
up
with
Christie
and
see
it
about
our
possibility
and
ability
to
push
stronger
on
the
UX
work
on
the
UX
depth,
and
you
know
even
on,
for
example,
following
up
on
the
you
have
scorecards
on
the
maturity
scorecards
or
you
know,
any
new
apps
related
work
that
sometimes
I
think
in
other
stages
bit
more
than
another.
We
have
a
little
bit
of
a
troubles
to
like
push
it,
and
this
related
to
that
vision.
A
That
I
have,
in
my
perfect
scenario,
when
product
designer
or
EU
actor
is
an
advisor
for
p.m.
on
areas
that
we
have
to
look
into
in
order
to
be
competition
in
some
places
or
a
better
align
to
you
know
like
certain
strategy
on
the
business
level,
so
yeah
I
think
the
great
challenge
for
the
next
milestone
will
be
for
us
is
to
figure
out.
How
can
we
do
better
work
there
and
what
are
those
methods
that
we
could
use
in
order
to
push
like
our
priorities
to
the
product?
A
A
bit
better
and
I
know
that
we're
working
a
little
bit
on
discussing
the
you
have
stepped
right
now,
but
also
yeah
I'm,
following
up
on
the
UX
scorecards
we're
actually
one
at
you.
I
want
to
create
the
periscope
chart
as
well
to
showcase
how
much
it's.
Actually
twenty
four
percent
of
recommendations
only
been
completed
since,
like
nine
months,
I
think
we
have
the
process
already
in
place
and
we
have
been
making
those
calculations
with
the
UX
leadership
team,
and
it
was
only
24
percent
of
the
recommendations
have
been
like
taken
into
account.
A
So
I
think
this
is
somewhere
where
we
could
do
better
with
improve
better,
but
for
that
it's
like
it's
really
cross
cross
function.
How
do
you
say
work
project
so
yeah?
This
is
gonna,
be
probably
the
focus
for
the
next
milestone
and
we
definitely
working
with
you
every
one
of
you
really
close
and
then
also
bringing
it
up
to
the
product.
A
D
A
That
would
be
my
perspective,
but
we
are
I
feel
like
we
are
right
now
running.
We
are
right
now
in
the
middle
of
discussing
that
and
right
now
we
are
adding
the
labels
to
their
recommendations.
Okay,
this
UX
scorecard
rack
the
label
that
I
will
be
going
and
actually
adding
to
every
issue
for
the
recommendations.
So
we
can
make
these
charts
and
we
can
like
bring
better
attention
to
that.
To
you
know
to
bring
more
awareness,
and
maybe
more
results
will
come
out
of
that
on.
Why
and
how
can
we
improve
that.
C
Yeah
I
I'd
have
to
agree
on
that
I.
Think
too
it's
the
dynamic
between
product
and
design,
I
I
get
the
feeling
in
the
beginning.
It
was
products
here.
Do
this
for
me,
design
I
want
this
to
be
done,
go
make
sure
we
could
get
it
done
and
I
feel
like.
It
shifted
a
lot
more
to
being
more
of
a
partnership
now
between,
at
least
at
least
in
the
ops
group
of
product
manager
still
coming
to
to
us
with
like
ideas
but
not
demanding
that
they
get
turned
into
solid
designs.
C
A
E
E
E
It's
tempting
to
go
that
direction
of
like
we
need
our
features
to
be
more
polished,
but
I
think
that's
somewhat
anti
get
laggy.
I!
Think
that
exact
sentiment
is
rephrased
in
the
gitlab
mantra.
This
way
that
we
can
absolutely
come
out
with
features
that
are
crappy
at
first
mmm-hmm,
knowing
that
we're
going
to
iterate
on
them
and
I.
Think
that's
the
key
where
we've
fallen
down
sometimes,
is
that
we
don't
iterate
on
things
enough.
We
put
them
out
there
and
say:
okay,
this.
This
is
NBC
and
it
is
what
it
is.
E
A
A
It's
our
responsibility
to
constantly
bring
back,
PM's
and
say:
hey,
you
know
we,
we
are
not
complete
there
yet
or
you
know,
like
you
know,
to
a
certain
extent,
so
that
the
experience
is
complete,
not
saying
perfectly
right,
but
to
a
certain
level,
and
some
of
the
tactics
there
is
could
be
like
planning
out
the
full
experience
with
the
PM,
for
example,
playing
out
the
whole
structure
for
the
future
and
then
assigning
the
milestones,
pushing
them
to
put
and
number
there
and
then
every
time
we
will
push
away
that
number.
You
know
it.
A
We
it
will
get
their
attention,
hopefully
more
without
lay
with
those
labels
like
mr.
mr.
miles
from
mr.
milestone.
So
then,
as
soon
as
we
put
that
label
or
that
like
timeline
there,
we
could
be
pushing
that
a
bit.
But
this
is
going
to
be
constantly
on
the
view
that
we
have
to
come
back
and
complete
that
so
I
think
we
have
to
be
really
good
in
that
like
following
up
and
reminder
and
like
pairing
up
with
the
p.m.
to
make
sure
that
we
complete
whatever
we
plan
yeah.
E
It's
a
good
point,
and
that's
where
the
trust
has
to
happen
is,
if
you
know
it's
cool
to
say
like
yeah,
we'll
do
this,
but
we'll
fix
it
later
like.
If
we
don't
that's
when
the
trust
loop
gets
broken
and
that's
when
designers
and
p.m.
start
arguing
is
when,
when
the
we'll
fix
it
later,
never
happens
and
yeah
I
think
that
idea
of
sure
this
is
it.
This
is
the
MVC,
but
at
the
same
time
like
I,
was
in
the
design
file.
E
I
actually
made
the
end
state
as
well,
and
I
hear
the
issues
that
are
going
to
get
us
there,
throw
them
on
the
board,
put
milestones
on
them
that
are
far
out
there
and
then
force
them
to
deal
with
that
and
not
not
accept
like
those
getting
pushed
out
into
infinity
is
the
great
way
to
go
about
that.
I.
A
Think
so
at
least
I
would
be
willing
to
try
that
I
know
that
it
could
be
challenging
as
well,
but
yeah,
hey
everyone,
I
know
that
we
are
a
bit
over
at
the
time.
Thanks
a
lot
for
this
discussion,
I
enjoyed
it
a
lot.
I
think
there
were
some
great
points,
topics
and
yeah
great
learnings.
So
thanks
a
lot
for
that
I
wish
everyone
saw
a
sunny
weekend.
Hopefully,
you'll
find
some
good
tasks
for
yourself
to
get
away
from
the
computer.