►
From YouTube: Progressive Delivery UX/PM meeting 2020-06-18
Description
Meeting to improve alignment between Product Management and UX for progressive Delivery
A
All
right,
let
me
see
first
up
what
works
research
issues
are
currently
in
progress.
I
have
a
small
update
about
mine
and
recruiting
has
been
started
for
a
b
testing.
The
idea
is
to
do
all
the
sessions
in
the
next
two
weeks.
A
Additionally,
I
reached
out
to
the
growth
team
to
interview
them
as
well.
I
was
like
I
was
brought
on
this
idea
by
kevin,
who
is
one
of
the
growth
team
product
designers,
and
we
had
a
little
time
together
in
indonesia,
so
it
was
cool
to
be
able
to
speak
with
him
again
about
this
potentially.
So
I
was
wondering
if
you
have
any
thoughts
towards
you
know
like
bias
internally,
how
useful
that
feedback
is
going
to
be
versus
external
participants,
etc.
B
I
actually
think
that
I
wouldn't
mind
to
do.
Only
internal,
I
mean
external
is
great
because
it's
another
perspective,
but
since
we're
building
the
future
for
the
entire
population-
and
it
currently
doesn't
exist
and
we're
going
to
start
with
dog
fooding
anyway,
I
think
it's
smartest
to
understand
their
needs
and
build
it
accordingly,
because
probably
what
they
need
is
what
the
community
needs
as
well.
Maybe
it
doesn't
fit
every
use
case,
but
it
definitely
fits
some.
So
I
think
talking
to
growth
is
great.
B
We
spoke
to
a
few
people
already,
so
we
just
need
to
find
them
in
the
issues
and
stretch
out
them.
It's
actually,
you
know
a
b
testing
is
really
unique
in
the
sense
that
it's
not
a
devops
engineer
per
se.
B
A
Cool
lori:
what
is
your
idea
about
testing
internally
first
external
here.
C
A
All
right
that
sounds
good,
then
I'll
move
forward
with
you
know
interviewing
internally.
I
think
I
can
set
it
up
a
little
bit
sooner
than
getting
the
recruitment
participants
scheduled
in
meetings
with
me,
which
should
happen
somewhere
next
week
at
the
earliest
yeah,
and
then
I
I've
reached
out
already
to
growth
theme,
so
I'll
probably
get
some
recommendations
to
speak
out
with
the
idea
I
had
is
to
speak
at
least
with
like
four
to
five
people
internally,
or
do
you
think
there
might
be?
You
know
you.
B
B
Feature,
I
don't
know,
I
think
a
good
place
to
reach
out
to
interviewers
is
the
feature
flag
channel.
You
know
to
see
if
anyone
wants
to
participate.
B
B
Yeah
so
a
few
weeks
ago,
when
we
spoke,
I
kind
of
completed
everyone
when
we
had
a
list
for
the
recruitment
for
post
monitoring
and
there
were
two
interviewees
that
I
wasn't
very
happy
with.
So
I
wanted
to
replace
them
and
we
got
three
new
respondents.
So
one
of
them
I
interviewed
last
week
and
it
was
great
and
then
there
was
two
more
one.
I
wasn't
really
excited
about
his
profile,
so
I
skipped
him
and
there
was
another
one
that
I
invited
I
invited
to.
B
C
A
Cool
thanks
for
that
that
seems
in
a
good
place.
So
with
that
in
mind,
let
me
let
me
see
I
will
get
back
to
that
later,
because
that
is
kind
of
targeted
or
linked
towards
the
thing
big
session,
but
before
we
get
to
that
some
other
points
in
between
there's
the
request
from
verify
in
release
ux
department
to
push
forward
the
issue
around
the
merch
quest
recommendations.
A
Do
I
have
it
correct
nadia
that,
like
we
want
all
of
those
issues
to
be
a
ready
for
development
to
start
working
on,
to
be
weighted
and
to
be
scheduled?
Ideally,
but
I
would
love
for
you
to
add
context
here.
D
Yeah
and
thanks
for
bringing
this
up,
this
is
something
that's
connected
to
the
okr
that
we
are
having
around
improvements.
Merge
requests
in
gitlab
and
the
expectations
are
here
actually
like
that
that
by
13th
of
june
well
or
like
you
know,
we
should
be
aligned
with
the
engineering
and
product
management
on
which
items
we
can
prioritize
for
quarter
two
right,
so
that
could
be
13.2
13.3
milestones
like
and
my
expectations
here
is
like
if
we
would
say
two
to
four
to
five.
D
That
would
be
perfect
if
we
feel
like
okay,
we
can
prioritize
those,
but,
for
example,
13.4
looks
more
realistic.
That
could
be
fine
as
well
and
yeah
like
I
guess
that
means
there
earlier
we
prioritize
it
the
more
like
designs
proposals
have
to
be
in,
but
yeah.
That's
also
not
a
like,
not
a
serious
requirement.
If,
especially,
if
you
say
that's
at
13.3
or
13.4
or
whatever
so
yeah.
B
The
issues
that
we
prioritized,
which
you
know
we
chose
them
from
the
whole
list-
don't
seem
like
that
that
there's
such
a
great
improvement
to
the
merge
request.
Widget,
I
mean
they're
nice
to
haves,
but
it
doesn't
seem
like
that's
going
to
make
such
a
big
difference
in
terms
of
the
user
experience.
B
So
a
13-2
planning
is
already
done,
so
the
only
next
place
that
we
could
probably
put
it
in
is
13.3
and
the
question
is
how
much
effort
do
we
want
to
do
because
really,
I
don't
think
this
is
like
something
that's
going
to
change
the
world
of
the
users.
D
Fair
point
and
my
my
counter
question
to
that
is:
how
did
we
prioritize
that?
I
know
that
you,
you
had
a
run,
and
now
you
had
done
a
nice
exercise
there,
and
I
mean
if
we,
if
you
if
we
would
say
that
hey
this
seems
to
be
a
minor
improvement
or
something
well
fair
enough
like
of
course,
the
whole
point
of
that
would
be
to
contribute
to
the
well
to
the
improvement
of
the
user.
D
Experience
on
mmr
so
like
if
we
say
yeah
if
that
helps
us
to
cover
at
least
certain
part
of
the
users,
for
example,
like
review
app
links
is
not
are
not
shown.
That
sounds
like
well
quite
a
problem.
I'm
not
sure
how
download
artifact
on
the
mark.
Widget
is
important
to
users
or
not
et
cetera,
et
cetera.
You
know
so
again.
This
is
your
and
in
dmitry's
call.
Our
goal
is
here
to
help
out
to
make
the
mrs
a
bit
better,
because
we've
seen
all
with
the
martial
investigation
of
like.
D
B
And
then
you
know
sorry,
dimitri
yeah,
just
one
more
thing
like
this
week,
someone
opened
up
an
issue,
that's
not
on
the
list
that
seemed
really
relevant
to
this,
and
I
had
tagged
them
and
I
was
like.
Maybe
we
should
add
it
to
this
epic,
so
you
know
things
change,
I'm
not
sure
like
how
strict
we
need
to
be
on
this
list.
D
Sounds
like
a
good
point.
I
mean
I
at
this
point.
It
doesn't
sound
like
we
have
anything
prioritized
again.
I
would
be
like
I
would
be
flexible
here
to
make
sure,
for
example,
like
today,
I'm
communicating
with
christy
about
what
we
have
prioritized
today.
It's
a
little
least.
I
would
actually
expect
more
but
hey
again,
it's
about
the
result
and
not
about
the
quantity
necessarily.
So
if
you
would
say
or
either
there
is
an
item
that
makes
much
more
sense.
D
Let's
just
draw
one
of
these
three
and
say:
hey,
let's
prioritize
the
other
one.
If
you
say
that
that's
13.3,
that's
fine,
I
would,
as
I
said,
even
15.4
would
be
kind
of
like
okay
as
soon
as
yeah.
We
have
the
attention
to
that.
I'm
not
sure
dimitri.
If
you
agree
with
me,
but
that's
that's.
According
to
my
like.
A
Yeah,
I
I
think
it's
important
to
see
those
issues
not
in
the
context
of
the
whole
gitlab,
but
in
the
context
of
what
the
otr
tries
to
to
to
complete
right,
we're
trying
to
like
make
the
experience
of
the
merch
quest,
lovable
small
improvements,
help
they're
equally
as
large
as
large
ones.
I
am
not
saying
that
the
ones
that
we
prioritize
based
on
our
exercise
are
the
only
ones
that
are
that
fit
that
you
know
objective.
A
If
we
find
one
you
know
afterwards,
as
you
suggested,
that
better
fits
that
theme
than
the
ones
that
we
exercised
with
then,
let's,
let's
prioritize
those
amongst
those
right
like
I,
I
did
not
see
that
we
should
block
any
of
that.
However,
I
would
like
to
say,
let's,
let's,
let's
look
at
this
within
the
context
of
the
opr
and
not
the
whole
application.
B
D
D
B
We
have
something
like
close
to
nine
or
twelve
eight.
I
think
we
had
a
really
really
great
improvement
that
I
worked
with
the
delivery
team
on
and
they
did
it
for
the
progressive
delivery
group.
It
was
really
awesome.
They
managed
to
mark
when
actual
deployment
happened
for
an
mr,
which
was
missing,
which
is
like
really
cool.
D
That
would
be
amazing
to
see
yeah
and
yeah.
Definitely
that's
something
that
would
be
fitting.
This
theme,
which
seems
to
be,
I
can
communicate
it
as
well
together,
yeah
anyway.
I
love
this.
I
love
this
attitude
of,
like
you
know,
trying
to
be
helpful.
D
I
understand
that
you
have
a
lot
of
other
things
but
yeah,
like
you
know,
if,
like
we
have
this
funny
saying
in
russian,
if
you
collect
I,
I
know
it's
hard
to
translate
like
piece
by
piece
you
collect
from
people
like
there
is
a
whole
like
thing
for
the
whole
world
anyway,
it
doesn't
sound
that
dramatic
as
it
sounds
in
russian,
but
I
really
appreciate
everyone
pushing
it
forward
and
you
know
if
you
would
say
if
you
would
say:
hey
like
there
are
only
two
items
that
I
think
could
be
really
beneficial
for
beneficial
for
mrs
and
we
can
prioritize
that
for
13.3
perfect,
I
mean
good
good
enough.
C
D
So
what
are
the
our
next
steps
here?
How
do
we
like?
What
is
that
issue,
or
it
can
you
add
it
here
like
the
force,
and
how
do
you
know.
B
So
there's
actually
two
here's
a
really
nice
one
that
was
in
twelve
nine,
which
is
should
count
twelve
nine
accounts.
It's
track
cherry
pick
deployments
that
wasn't
12
in
12
9..
I'm
sorry.
D
And
you
mentioned
also
something
just
came
up
yesterday
or
this
week
that
you
think
is
more
important
than
the
the
issues
that
we
haven't
released.
D
What
was
that
sorry?
I
need
to
find
it:
okay,
gotcha
gotcha
yeah.
So
what
is
what
are
our
next
steps
here?
Oops
on
this,
you
know:
how
do
we
cherry
pick
from
this?
You
know
like
just
for
me
to
understand
where
we're
going
with.
That
was
prioritizing
some
of
these
issues
that
we
have
we're
talking
about.
That.
B
To
be
realistic,
I
think
only
one
issue
will
make
13
3..
It's
a
pretty
loaded,
milestone
and.
B
A
Yeah
the
review
app
links,
even
though
that
is
the
let
me
see-
which
one
was
that
the
one
that
we
put
at
highest
or
yeah,
I
think
so-
review
uplinks-
are
not
shown
in
a
merch
quest
widget
for
non-members
that
one
is
weighted
and
should
be
ready
for
development.
D
A
A
Sounds
good
and
or
what
was
the
other
issue
you
were
talking
about
that.
B
B
A
A
I
will
probably
find
it
in
like
five
minutes.
Let's
go
on
to
the
next
one.
Let
me
see
preparing
the
thing
big
session,
which
is
related
to
your
post
deployment,
monitoring,
which
is
scheduled
for
next
week.
A
As
far
as
I
know,
ideally
in
order
to
best
fuel
this,
this
thing
big
session
I
proposed
in
the
past,
like
hey,
let
me
look
up
some
white
boarding
exercise
and
when
I
started
to
look
into
it's
ideally
that
we
know
exactly
what
the
goal
is
of
this
thing
big
session,
because
otherwise
it's
not
going
to
align
well
with
what
we
want
to
get
out
of
it.
So
the
question
here
is:
we've
you've
scheduled
this
thing
big
session.
B
Session
so
the
idea
to
present
the
idea
of
post-deployment
monitoring
as
a
high-level
picture,
to
discuss
what
we're
trying
to
gain
yeah
and
what
the
users
are
gonna
benefit
from.
It
talk
a
little
bit
about
the
user
interviews
that
I
have
done
and
to
talk
about
a
little
bit
of
cross-collaboration
and
I've
talked
to
other
stages
of
what
can
be
done
on
this
issue.
A
Because,
like
one
of
the
like,
I've
had
one
exercise
specific
in
mind
that
might
fit
this
this
larger
picture,
and
that
is
the
opportunity
solution
tree,
which
kind
of
connects
our
opportunities
with
any
potential
ideas
that
we
have
and,
as
you
have
done,
the
like.
You
know,
we've
done
our
like.
You've
done
your
homework
with
the
validation
process.
So
we
have
our
opportunities,
clear,
our
insights
we
have
at
the
ready
and
where
I
think
it
would
be
very
helpful
for
us
to
do
this.
Whiteboarding
exercise
is.
A
We
can
display
all
those
insights
next
to
each
other
and
then
start
to
solutionize
a
little
bit.
At
least
I
get
ideas
go
in
with
the
team,
but
then
we
need
to
connect
them
to
the
to
the
solution,
because
often
what
we'll
find
is
that
some
of
the
ideas
that
we
come
up
with
will
not
be
tied
to
any
of
the
insights
we
have,
and
that's
kind
of,
like
the
thing
that
I
want
to
want
to
want
to
prevent.
A
So
as
I
think
that
that
kind
of
goes
into
into
your
point
is
like
discuss
what
users
want
from
it
right
like.
B
A
Cool
yeah,
ideally
for
this
session,
and
I
was
wondering
what
what
nadia
and
laurie
think
about
this
exercise
fitting.
The
things
that
word
has
says
is
that,
ideally,
it
has
an
overarching
desired
outcome,
so
the
desired
outcome
is
x.
Then
we
have
the
opportunities
that
align
with
that
desired
outcome
and
out
of
those
desired
opportunities,
you
will
have
the
ideas
that
eventually
lead
to
the
implementation
issues.
D
Yeah,
I
think,
from
what
I'm
hearing
I
actually
by
the
way
I
really
love
the
using
whiteboards
for
that
exactly
to
make
it
visual
and
like,
like
we've,
been
doing
it
in
other
stage
groups
like
to
this
for
different
purposes
and
it
always
like
unites
everyone.
So
I
really
like
that
proposal.
That's
one!
Second
of
all,
before
the
goal,
I
think
it
sounds.
What,
where
read
is
going?
D
It's
more
kind
of
like
hey,
discuss
all
of
the
like
data
that
we
have
right
now
and
maybe
like
find
out
that
well
the
issues
that
we
want
to
focus
on
and
maybe
then
prioritize
them.
I
know
it
sounds
like
about
problem
opening.
You
know
this
love
like
double
diamond
exercise,
dimitri,
so
it
sounds
like
we're.
Gonna
be
like
going
wide
and
maybe
at
the
end
we
can
go
narrow
again
so
like
we
will
talk
about
hey
what
are
all
of
those
things
that
we
hear.
D
What
are
all
of
those
needs
that
users
have
told
us
about
like
okay.
What
is
it
all
that
we
know
we
need
to
focus
on
and
then
maybe,
if
we
have
time
in
that
session,
maybe
we
schedule
a
separate
session
where
we
would
from
that
wide
range
we
would
go
back
to
the
narrow
again.
Okay,
what
are
those
like.
A
D
A
Need
to
get
it
correctly,
the
solution
tree
solution,
opportunity
three,
is
more
of
an
exercise
to
converge
rather
than
diverge
right.
That's
what
you're
saying.
A
Yeah,
like
the
exercise
I
had
in
mind,
I
think
it
is
about
you
know
getting
the
things
converged
towards
where
we
eventually
want
to
be
rather
than
diverging
and
getting
us
towards.
You
know
the
idea,
like,
I
think
it's
perfectly
fine
to
do
it.
The
way
you
said
like
like
have
a
discussion
with
engineering
in
the
think
big
session
generate
loads
of
ideas,
and
then
we
have
a
different
set
separate
discussion
around
all
right.
D
Yeah,
I'm
not
exactly
sure
which
exactly
method
or
exercise
you
are
talking
about,
but
it
seems
like
we
understood
each
other
dmitry
and
I'm
just
dropping
one
of
the
links
about
the
double
diamonds
here
there
are
tons
of
them.
A
Yeah
I'll
what
I'll
do-
or
it
is
I'll
set
up
like
the
whiteboard
for
us
to
collect
the
ideas
in
and
the
idea
is
just
to
get
everybody
on
there.
And
then
you
know
if
everybody
has
their
ideas
like
we
just
jot
them
down,
etc,
and
then
we
can
work
with
that.
Those
ideas
on
the
different
sticky
notes
in
the
the
follow-up
session
after
that
sounds
good.
C
B
A
All
right
on
to
the
next
point-
and
that
is
for
thanks
for
including
me
on
this
direction-
merch
request-
I
was
thinking
as
I
saw
this
message
on
slack-
that
they've
added
this
nice,
this
nice
thing
in
the
handbook
as
to
who
are
you
know,
dris
for
this
specific
direction.
Page,
you
can
add
like
code
owners.
A
Basically,
so
I
was
wondering,
might
it
make
sense
to
include
you
know,
of
course,
product
management,
but
also
product
design,
and
indeed
technical
writing
as
the
ari
is
for
those
pages,
so
that
we're
you
know
we're
aligned
on
hey
these
people
kind
of
push
forward
this
these
direction
pages.
B
I
don't
think
we
need
to
change
anything.
I
think
you
can
just
go
in
and
you
know
add
suggestions.
The
direction
page
is
basically
my
vision,
so
I
don't
want
people
changing
it
without
me,
going
through
their
suggestions,
but
I
definitely
encourage
you
to
go
in
and
suggest
whatever
you
want
to
change.
I
think
I
think
I
think
this
is
more
of
a
joint
collaboration,
nothing
painful
between
between
the
both
of
us,
but
at
the
end
of
the
day
I
think
there's
only
one
dri.
A
Yeah,
like
I'm,
not
I'm
not
suggesting
that
you
know,
product
management
should
be
pushing
it's
more
like
you
know
who
has
eyes
on
this
page.
I
think
that
is
what
what
is
what
is
being
done
there
with
the
code
owners.
I.
A
B
Like
anything
in
gitlab,
let's
iterate
since
up
until
now
no
ux
designer
actually
holds
on
that
page
at
all,
and
now
you
know
I
invited
you
to
join
so,
let's
see
how
that
goes,
and
then
we
can
think
about
how
to
improve
the
process.
So,
let's
do
it
slowly.
A
Then
that's
it
for
this
meeting.
Thank
you
so
much.
B
Wait,
I
also
edited
if
we
should
invite
marcel,
because
it
looks
like
he's
the
technical
writer
and
not
susan
susan.
So
maybe
we
need
to
switch
the
invite.
D
B
D
To
have
like
a
bit
more
how
to
say,
roles.
C
B
C
B
A
All
right,
yeah
I'll
reach
out
to
him,
and
then
we
can.
We
can
get
him
to
potentially
join
the
next
meetings.