►
From YouTube: CI/CD UX meeting (EMEA/Americas) - 2022-02-23
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
All
right,
so
this
is
the
americas
europe,
cicd
ux,
call
for
my
goodness
february,
23rd
2022.,
I'm
going
to
start
with
some
of
the
announcements
and
some
of
the
things
that
I
didn't
add
in
the
agenda
for
the
apac
call.
So
I'm
going
to
vocalize
that
so
the
girls
in
case
they
watch
the
recording
later
on
they
can
see
and
hear
this
update
so
daniel's
last
day
is
tomorrow
february.
24Th
I'll
hear
the
dislike
announcement.
You
can
check
that
out.
Also
small
update
since
daniel
is
leaving
and
he's
currently
in
brazil.
A
This
call
is
like
it's
at
7
pm
my
time,
so
I'm
gonna
try
to
move
it
up
so
that
I'm
not
sure
how
that's
going
to
work
for
you
will
for
your
time
zone,
but
heads
up
I'll
try
to
find
some
time
in
our
calendars
so
that
we
can
meet
a
bit
earlier
on
my
day,
because
it's
really
end
of
my
day
here.
B
C
A
A
Cool
then
I'm
gonna
update
that
later
this
week
and
then
standing
topic
okr's
progress.
I
don't
think
we
need
to
go
over
those,
because
I
already
reviewed
this
with
the
regina
this
week
and
I'm
gonna
review
those
with
both
nadia
and
vitica
tomorrow
morning
and
already
checked
in
with
katie
yesterday.
So
I
know
what
the
latest
status
update
is
and
then
update
for
product
designers,
I'm
going
to
post
this
in
our
slack
channel.
A
A
So
if
you
haven't
done
so
yet,
please
start
your
interview,
interview
training
process.
I
linked
here
in
the
agenda,
the
handbook
page
and
also
once
you
do
that,
make
sure
that
you
add
yourself
to
the
interview,
shadowing
tracker
and
being
rupert
for
approval
and
then
later
on.
I
will
invite
you
I'll
invite
you
to
the
I
think.
It's
ux,
it's
called
ux
hiring
channel.
It's
a
private
channel.
Today
but
once
you're
ready
to
shadow
to
take
on
interviews,
let
me
know
so
I
can
add
you
manually
invite
you
to
this
channel.
A
B
So
I'm
already
a
part
of
the
ux
hiring
channel
like
what's
the
process
to
get
involved
with
interviews.
Do
I
like
need
to
contact
rupert,
or
should
I
probably
look
in
the
handbook?
What
would
you
recommend.
A
So
you're
already
in
the
channel
and
have
you
started
or
completed
your
training,
the
interview
training.
I
have
okay,
so
if
there
are
open
positions
for
the
research
team,
just
mentioning
the
team
and
let
rupert
knows
that
you
are
available
to
either
shadow
or
lead
those
interviews
and
I'm
not
sure
for
research.
You
have
a
tracker
for
who
has
completed
the
training
or
you
know
who
the
panel
really
is,
but
for
product
design,
usually
the
designers
either.
A
Let
me
know
or
post
in
this
private
channel,
saying
that
hey
I'm
available
for
interviews
and
looping
reverts
if
that's
the
safest
match.
Okay,
thanks
no
problem,
so
I
went
up
here,
look
in
robert
in
the
slack
channel
cool
and
then
my
last
update.
I
also
reviewed
this
today
with
gina,
but
I'm
gonna
voice
it
here
for
everyone
here,
hackathons
they're
happening.
A
We
are
like
midway
through
the
current
hackathon
and
they
are
great,
but
we
all
know
that
they
often
require
product
designers
to
spend
much
more
time
or
sometimes
unplanned
time.
Reviewing
these
changes,
or
sometimes
these
changes.
They
come
without
meeting
a
source
of
truth
or
like
an
acceptance
criteria
for
a
specific
issue.
A
When
that
happens,
if
an
issue
is
either
sorry
if
a
merger
quest
is
written
incorrectly
as
in
the
issues,
the
merger,
by
description,
if
it's
lacking
a
description
or
if
the
proposal
doesn't
meet
or
guidelines,
whether
that's
pajamas
or
meet
the
not
not
me
but
add
value
to
our
product,
please
look
in
your
pm
and
em
for
next
steps.
So,
my
goodness!
This
is
why
I
don't
want
calls
at
a
7,
7,
30
p.m,
because
my
english
vocabulary
disappears.
A
But
if
you
see
something
pretty
much,
what
I'm
gonna
say
say
something
right
you
we
are
not.
You
know
we
forced
to
move
forward
with
this
merge
requests
as
per
the
code
review
guidelines.
If
they
don't
meet
the
criteria
we
have
to
loop
in
the
teams
and
then
make
a
decision
around
what
we
want
to
do
with
this
merge
request.
Do
you
want
to
sculpt
it
in
a
different
milestone?
A
Do
we
want
to
take
over
and
work
on
the
fix,
or
do
we
want
to
park
those
so
bring
up
those
issues
in
the
merge
request,
comments,
look
in
your
pms
and
em
and
if
you
approve
the
ux
awesome,
if
not
also
state
that
and
explain
the
why
in
the
changes
right,
so
that's
point
one
and
also
I
know
that,
especially
for
verify.
A
We
have
a
high
volume
of
merge
requests
each
hackathon
and
you're
not
well
you're,
not
being
asked
to
take
on
all
these
merge
requests,
reviews
by
yourself
right.
That's
why
we
have
the
ux
community
contributions
like
channel.
So
please,
if
you
are
being
looked
in
in
a
lot
of
merger
pasts
or
if
you
have
a
high
volume
of
things
in
your
pipeline
together
with
milestone,
work,
leave
a
comment
in
the
ux
community
contributions
channel
and
say
I
need
someone
to
review
this
and
then
drop
it
there.
A
If
you're,
not
getting
replies,
look
me
in
so
I
work
with
other
product
managers
to
find
a
backup
and
find
someone
to
review
these
merge
requests.
Wanna,
make
sure
that
the
review
is
evenly
distributed
across
all
stage
groups.
So
I'll
pause
now
my
very
confusing
monologue
to
see
if
I
made
sense,
if
you
have
any
questions
to
me,.
A
Julio
then
last
item
a
friendly
reminder
that
I'm
also
a
pajamas
maintainer,
and
I
can
review
your
merge
requests
and
also
merge
them
now
that
jerick's
leaving
gitlab,
I
think
next
week
we're
gonna
have
one
last
maintainer
for
pajamas,
so
reminder
lupine
assigned
me
to
those
pajamas
and
mars
so
that
I
can
help
merge
them
and
review
them
as
part
of
the
approval
flow.
A
That's
it.
We
don't
have
any
updates
for
daniel
in
the
agenda,
so
we
can
move
to
to
your
items.
Gina.
C
Okay,
I
tried
to
pick
out
just
two
of
like
the
most
recent
things
for
both
the
groups
so
for
runner.
C
C
So
I
ended
up
putting
those
in
dovetail
and
I
transferred
a
lot
of
it
to
mural
just
so,
I
could
group
it
better
pretty
much
and
and
then
check
off
like
whether
or
not
these
requests
that
they
were
asking
for
have
been
captured
by
us
in
issues
or
if
we
have
plans
upcoming
that
will
like
that,
we'll
get
features
out
to
satisfy
them,
so
I'm
I'm
still
working
on
the
mural,
but
right
now
what
I'm
doing
is
like
transferring
a
lot
of
that
stuff
into
problem
statements
and
then
putting
like
the
related
feature
requests
into
each
problem
statement,
because
I
think
I
was
talking
to
pedro
and
he
suggested
that
from
the
ux
team,
and
I
think
that
will
help
my
team
also
be
able
to
know
like
what
all
these
features
are
really
bubbling
up
to
and
what
they'll
fix.
A
So
before
that
I'm
gonna
ask
just:
is
this
everyone,
your
team
has
access
to
doctor
when
you
say
your
team.
I
I
imagine
that
you're
talking
about
not
only
your
pm,
but
your
the
engineers
as
well.
A
Yeah
awesome
cool
and
then
I
have
follow-up
question.
It's
awesome.
That's
yeah!
These.
These
meetings
with
the
customers
are
happening
today,
and
I
know
that
you
talked
a
little
bit
about
it
in
yesterday's
ux
call,
but
I
just
want
to
hear
how
are
these
sessions
going
so
far
and
any
learnings
or
any
thoughts
that
you
can
share
with
us.
C
Then,
like
oh
we're
thinking
of
adding
this
feature
based
on
your
pain
point
that
was,
that
seemed
like
the
best
way
to
format
the
call,
but
the
also
having
establishing
a
relationship
with
tams
is
really
important
because
I
wouldn't
have
been
able
to
meet
with
them
if
not
and
and
darren
like
introduced
me
to
the
tam.
So
that
was
important
as
well.
I
think
of
anything
else.
C
Another
one,
other
learning
is
that
you
can
always
like
if
you
have
additional
notes
that
you
you
wanted
to
get
across
to
the
customer
that
you
didn't
have
time
to,
you
can
always
tell
the
tam,
and
then
they
can
tell
the
customer
as
well,
because
they
seem
to
continuously
being
be
interested
in
learning
what's
coming
up
and
if
you're
actually
gonna
be
like
be
satisfying
their
feature
request
or
not
so
yeah.
I
learned
that
that
that's
helpful
too,
and
just
keeping
the
relationship
like
active
is
good.
A
Yeah
thanks
for
the
thanks
for
the
overview,
then
a
follow-up
question,
for
you
is
the
customers
you
you
talk
to.
So
let
me
I'm
gonna
start
typing
here,
so
I
don't
forget
the
customers.
In
fact
today,
are
they
aware
of
our
the
handbook
pages
with
the
the
runner
direction
and
the
updates
do
you
think
they
are
consuming
that
information
today.
C
C
We
brought
that
up
at
the
beginning
of
each
of
those
calls
so
that
they're
aware,
and
then
they
can
reference
it.
So
actually
you
know,
I
don't
know
if
they
were
aware
before
the
call,
but
we
did
bring
that
up.
A
Awesome
then,
that
clarifies
the
my
my
next
and
my
follow-up
questions.
That's
good!
It's
awesome,
gina
that
this
is
happening.
We
mentioned
this
in
our
101.
I
think
I
know
that's
something
that
darren
has
been
thinking
about
for
a
while
now
by
setting
up
these
calls
and
involving
you
right
and
having
your
wax
to
absorb
this
information
and
also
to
help
drive
the
conversation,
and
I
think
to
your
point.
Yes,
having
a
structure
and
agenda
is
it's:
it's
super
it's
critical
there.
A
C
Yeah,
it's
really
nice.
It
cut
like
it's
nice
to
get
their
direct
perspective
on
the
product
rather
than
just
reading
it
from
an
issue.
C
A
And
then
my
next
follow-up
question
is
for
will:
how
are
other
teams
balancing
out
this
customer
request
with
the
research
inside
insights
to
inform
design
and
product
decisions
today?
Are
you
aware
of
any
other
teams
where
the
product
designer
is
in
contact
with
customers?
The
way
that
gina
is
today
and
how
is
that
working
from
what
you,
what
you
know.
B
Just
from
my
like
light
observation,
because
I'm
not
super
involved
with
those
customer
calls-
is
that
they
tend
to
like
make
a
a
template
in
like
the
pms,
we'll
make
a
template
in
get
lab.
They
will,
you
know,
write
out
like
an
overview,
so
take
a
lot
of
notes
to
add
into
that
template
and
then
we'll
post
it
like
in
a
comment
of
that
particular
issue,
and
then
I
think,
when
it
comes
to
video
recordings,
they're
fairly
good
about
uploading
it
to
dovetail.
B
But
I
haven't
really
seen
some
of
that
next
step
of,
like
okay,
we've
talked
to
like
a
cust,
a
couple
of
different
customers.
We've
found
these
like
like
observations
and
maybe
opportunities
from
you
know
three.
Six.
Nine
of
these
different
calls.
B
Let's
you
know
translate
that
into
like
an
actionable
insight,
or
you
know
something
that
we
actually
do.
Something
with
that's
been
harder
to
grasp.
If,
if
like,
the
pms
are
like
just
integrating
that
into
the
you
know,
backlog
of
you
know
they're
coming
up
with
new
ideas
for
features
and
things
or
if
you
know
that's
something
that
we
need
to
be
a
little
bit
more
like
aware
of
and
kind
of
connect
them
to.
Like
hey,
let's
make
an
issue.
A
Yeah
my
first
thought.
My
first
question
is:
if
you
have,
if
you
have
links
to
to
those
insights
or
to
those
where
this
is
being
documented,
so
that
we
can
look
at
it
later
on
also
to
have
a
reference.
A
So
that's
point
one
and
to
your
point:
yes,
it's
it
can
be
tricky
to
separate
from
just
what
customers
are
asking
and
that
problems
that
really
serve
their
used.
Cases
with,
I
would
say,
the
the
general
the
insights
I'm
seeing
that
the
conversation
bubbling
up
in
in
verify.
So
going
back
to
my
previous
questions,
if
you
have
examples
of
where
else
this
is
happening,
I
think
it's
good
for
us
to
see
how
other
teams
are
solving
that
or
if
the
the
situation
is
similar.
A
One
of
the
things
that
might
help,
at
least
for
us
for
ux,
is
using
that
actionable
insight.
Template
I'm
not
sure
if
we
have
a
template
or
if
you
have
a
way
today
other
than
in
dovetail
of
tracking
the
customer
insights.
Do
you
know
that
will
so
that
we
can
kind
of
cross
link
things
and
compare
them?
A
A
And
how
do
we
not
only
address
the
need?
That
is
an
actual
real
need
for
its
customers,
but
make
sure
that
we
are
validating
it
and
have
enough
insights
to
support
that
based
on
the
research
that
that's
either
done
that's
in
the
backlog
or
that
is
planned,
no
yeah
tricky
one.
B
So
I
actually
included
a
a
project
that
looks
like
chris
did
maybe
a
couple
weeks
ago.
So
I
hadn't
really
followed
this,
but
it
looks
like
he
did
a
lot
of
like
tagging
and
to
generate
some
insights.
B
A
Yeah,
I
think
so,
yeah,
okay
and
just
the
additional
random
thought.
I
think
this
is
also
as
far
the
conversation
of
you
know,
defining
the
mvc
and
breaking
down
the
nbc.
So
we
get
a
lot
of
other.
We
are
really
influenced
from
this
insights
and
requests
and
what
we
see
our
competitors
doing,
etc,
etc.
A
So,
just
a
reminder
that
for
product
design
in
general,
the
mvc
is
not
the
big
picture
right.
The
nbc
is
the
smallest
thing
that
we
do
that
can
address
that
customer
need
and
bring
value
to.
Of
course,
our
customers
are
users
and
git
lab.
So
thinking
back
of
insights
versus
requests,
I
think
it's
important
that
we
are
very
critical
of
the
ux
quality
and
how
scalable
the
solutions
are
right,
so
not
only
thinking
of
looking
at
the
insight
and
running
with
it,
but
how
is
that
impacting
the
bigger
picture
and
how?
A
How
is
that?
Does
that,
like
a
proposal
in
a
sense,
builds
up
to
the
vision
exactly
broader
picture?
I
was
looking
for
that
yeah,
so
I'm
gonna
link
here,
I'm
gonna
find
the
handbook
page
for
iteration.
I
think,
rather
than
a
handball
page
there's
a
recording,
I
think,
where
pedro
talks
about
design
iteration,
that
it's
really
interesting
and
he
talks
about
breaking
that
down,
might
be
relevant
for
our
team.
So
I'm
going
to
add
that
hyena
to
link
if
duration,
youtube,
recording
yeah,
no
okay.
C
Okay,
the
other
well
actually,
before
I
move
on,
is
there
anything
else
we
wanted
to
say
about
that.
C
Thanks
for
the
discussion,
the
other
update
I
have
is
for
pipeline
insights,
which
I'm
not
sure
if
I
told
this
group
before
but
testing
is
now
pipeline.
Insights,
so
you'll
see
that
that
word
being
used
tomorrow.
We
have
our
first
think
big
as
our
pipeline
insights
group
and
it's
to
discuss
artifacts
and
review
apps.
And
then
I
talk
about
performance
testing.
C
We
did
some
research
on
both
artifacts
performance
testing
and
review
apps
recently
and
our
teams
like
we
have
a
lot
of
good
ideas,
and
so
we
wanted
to
get
together
and
do
a
thing
big.
There's
an
async
issue
that
I
linked
there
for
the
specific
things
that
we'll
be
brainstorming
on
and
yeah
and
then
I'll
have
some
more
updates.
Once
we're
done.
B
Yeah,
I
don't
really
have
a
whole
lot,
but
you
know
I'm
just
gonna
miss
working
with
daniel
he's
been
tremendous
to
work
with
and
has
done
a
lot
of
great
work
in
the
release
space.
B
B
And
I
honestly
that
you've
got
a
a
comment
here.
Do
you
want
to
talk
about
that.
A
Yeah,
so
you
are
when
talking
to
chris
and
kevin
about
the
coming
research
needs.
Please
look
me
in
and
also
I
think,
I'm
sure
if
we
have
a
call
this
week
next
week,
yeah
with
eric
and
I
so
let's
also
talk
about
that.
If
there
isn't
any
updates,
I
forgot
to
mention
that
so
once
then
you're
off
board,
I
will
be
the
backup
for
release
so
I'll
take
over
all
the
work.
Until
we
we
have
a
backfield
right.
A
We
hire
someone
new,
so
I'm
gonna
be
more
involved
in
that.
So
any
discussions
will
that
you're
having
about
release,
I
mean
priorities.
Please
look
that'll
be
the
deal
right
yeah,
I
couldn't
add.
B
Any
you
know
things
that
we
talk
about
to
our
meeting
agenda
for
next
week.
I
think
I'm
meeting
with
kevin
later
today.
A
Yeah
I'm
also
meeting
gapping
tomorrow.
So
let
me
know,
let
me
know
if
there's
anything
relevant,
that
we
can
catch
up
async
also,
maybe
will.
I
think
it
would
be
a
good
idea
for
us
to
have
here
the
link
for
yours
and
erica's
priority
trackers,
so
that
yeah
just
have
a
standing
item
so
that
designers
can
see
and
go
through
this
the
items
and
check
the
updates.
B
Yeah,
oh
I'll,
add
that
here,
but
I
can
also
add
the
to
the.
I
guess
the
template
is
another
good
place.
To
put
it.
A
For
real
I'm
reading
erica's
update,
because
I
haven't
gotten
that
far
in
the
agenda
today,
so
she
say:
rin7.
A
So
I
think
it's
a
good
good
to
do
for
everyone.
We
have
a
chance
check,
erica's
update
here
in
the
dock,
all
right
we're
almost
the
time,
but
I
wanted
to
ask
you:
how
is
this
session
working
for
you
now
that
we
split
it?
You
know
between
apac
and
then
america's
and
europe.
A
Is
there
anything
about
the
format
that
you
change
or
is
there
anything
that's
working
well
and
what's?
What's
not
working
well
just
curious
to
hear
feedback
so
that
we
can
keep
the
sessions
productive
but
also
interesting
for
us.
C
C
B
Yeah,
for
me,
it's
been
good.
I
don't
really
have
any
complaints.
You
know
I
could
just
check
the
document
async.
You
know
if,
if
there's
something
just
for
me
to
look
at,
but
if
I
need
more
context,
it's
always
nice
that
I
could
just
go
to
the
recording
and
see
like
okay.
What
other
discussions
were
they
having
on
that
particular
topic
that
day.
A
Yeah
thanks
for
that,
I
think
for
me
ralph
as
a
manager,
one
of
the
things,
for
example.
Now
in
this
call,
and
now
that
daniel
will
leave
we're
gonna,
be
we're.
Gonna
have
like
two
researchers
well,
if
erica
is
not
joining
the
apac
session,
but
then
gina
won't
have
appear
right
in
the
call
to
provide
design
feedback.
So
maybe
that's
not
an
issue
now,
but
maybe
that's
something
gina
that
we
want
to
look
into
and,
of
course,
this
goals
are
again
for
you
to
set
the
agenda
in
the
conversation.
A
We
can
maintain,
like
a
design,
studio,
atmosphere
right
looking
at
each
other's
work
and
providing
feedback
in
a
open
forum.
I
think
that
still
be
helpful,
but
it
might
be
challenging
now
that
we
split
the
two
groups,
but
it's
it's
part
of
the
it's
part
of
a
challenge.
I
guess.
C
I
think
that's
a
great
idea.
I
I
can
add
that
as
a
standing
item
I
sometimes
don't
like.
I
want
to
be
respectful
of
other
people's
time,
so
I
don't
always
know
exactly
what
to
share,
because
I
don't
want
to
take
up
too
much
time
myself.
So,
if
we
have
examples
of,
I
know
we
have
like
add
something
to
share
discuss
on
the
next
call.
But
if
we
have
like
a
specific
thing
to
bring
to
the
call,
I
think
that
would
help
me
figure
out
what
to
share.
A
Yeah,
that's
a
good
point
because
that
that
was
one
of
the
challenges,
especially
when
we
have
like
a
a
full
full
meeting
with
the
five
six
people
that
not
everyone
gets
the
chance
to
to
talk
about
their
items.
A
I
think
for
maybe
more
diverse
groups.
We
can
can
at
least
recommend
them
to
bring
one
to
two
important
things
that
they
want
to
discuss
and
time
box
that
but
yeah
this
is.
A
So
that's
a
thought,
but
again
a
challenge
for
how
we
we
can
do
that
with
with
two
different
groups:
let's
see
how
that
goes,
and
then
we
can
adjust
on
the
fly.
Okay,
that's
awesome,
cool
anything
else
that
you'd
like
to
share
that
we
haven't
discussed
today.
A
A
Cool
then
I'll
see
you
well
gina.
I
think
I'll
see
you
tomorrow
in
the
call,
the
not
the
testing
by
applying
insights,
call
and
I'll
see
you
next
week
right.
Awesome,
bye,
bye,.