►
From YouTube: Release PM/UX Design/UX Research Sync 2022-04-28
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
Yeah,
thank
you
for
chatting
with
me
yesterday,
walking
me
through
respondent.
I
haven't
used
that
before
so
I
appreciate
yeah
that
walkthrough
sounds
like
we
have
at
least
like
eight
qualified
and
willing
participants,
and
maybe
even
a
few
more
that
may
be
qualified
as
well
so
and
even
just
with
you
looking
through
like
the
the
different
responses
we
got
like,
they
seem
like
really
good
good
people
to
talk
to.
So
that's
so
I'm
excited
about
that
yeah.
B
B
B
C
B
B
C
All
right
and
then
the
solution,
validation
for
the
environments,
page
redesign.
So
after
I
think
like
a
week
and
a
half
two
weeks
of
complete
silence
from
the
people
that
I
had
initially
invited
to
the
interviews,
so
we'll
come
back
with
a
list
of
I
don't
know,
I
think
six
new
people,
maybe
more
and
I
send
out
the
invitations
in
the
email.
So
thank
you
so
much
will
for
the
the
help
there
for
being
so
super
quick
in
providing
that
that
list
of
participants.
C
I
got
so
far
three
replies
and,
let's
see
I
have
one
tomorrow
on
monday
and
next
wednesday,
so
that
will
total
four
people
that
will
be
speaking
with
about
the
the
environments,
page,
redesign
and
kind
of
sidebar.
To
that
the
first
interview,
the
first
person
I
talked
to
I
felt
like
I
didn't-
really
get
much
information
from
them.
They
were
a
bit
everywhere
and
wanting
to
talk
about
gitlab
as
a
whole,
so
I
often
had
to
keep
bringing
them
back
to
the
questions
into
the
environment
page.
C
So
when
I
look
at
yeah
the
quality
of
the
data,
I'm
not
super
confident
with
much
of
the
feedback.
They
gave
because
it
was
so
little
that
I
could
get
from
you
know
from
them
about
environments,
but
anyways.
That
was
one
person,
and
while
I
was
interviewing
them,
I
kind
of
not.
I
did
not
change,
but
I
mentioned
this
to
you
last
week
will
that
I
included
some
questions
right
about.
Let's
see
like
completely
forgot,
the
word
feel
free
to
finish
my
sentence,
because
today.
C
Satisfaction
in
single
of
these
questions,
that's
what
I
was
looking
for,
so
I
included
that
those
questions
that
were
not
initially
in
the
in
the
screen
right
but
anyways.
That's
that-
and
I
have
this
interview
tomorrow.
If
yeah
any
of
you
want
to
participate,
it's
at
7
p.m.
My
time
so
I'll
just
add
it
here
in
case
you
want
to
join
your
yeah
might
be,
might
be
available
or
curious
about
the
upcoming
ones.
C
C
A
Yeah
I'll
to
the
doc,
but
basically
my
question
is
like
it's
kind
of
more
of
a
statement.
You
know
it
sounds
like
if
you're
not
getting
much
out
of
that
interview,
you
could
just
consider
it
like
a
lost
cause
or
kind
of
like
a
pilot
study
or
session,
and
then
just
you
know,
recruit
another
person
or
two
to
kind
of
replace
that
individual.
Since
you
get
you
didn't
get
much
out
of
them.
C
B
C
Jamie
yeah,
so
I
I
reach
out
to
him
and
actually
see
if
he
replied
not
yet,
but
I
asked
him
to
just
schedule
or
get
in
touch
with
t-mobile
or
the
people
that
we
talk
to
right
from
t-mobile
and
disney.
I
don't
have
their
contacts
directly
and
I
think
you'll
make
sense
to
get
jamie
to
to
reach
out
to
them,
and
also
I
spoke
with.
C
B
C
No,
please
yeah.
I
love
that
and
if
I
cannot
join
if
it's
outside
my
my
work
hours,
I'll
just
drop
some
questions,
they
seem
and
if
you
record
I
can,
I
can
follow
up
later
with
the
directory.
Yeah,
awesome,
yeah,
cool
and
then
related
to
that.
I'm
coordinating
with
the
mate
he's
the
product
designer
for
our
growth
team
to
understand
how
he
can
help
with
this
particular
effort
like
if
it's
helping
conducting
somebody's
interviews
or
future
research
solution,
validation
for
for
release.
C
Somebody
he
reached
out
to
me
because
he
wants
to
help
out
with
the
other
stage
groups.
He
has
the
the
availability
for
that.
So
I'm
talking
to
him
to
see
if
he
has
the
time,
if
not
for
these
interviews,
then
yeah
for
other
design
work
in
release
that
we
need
to
move
forward
with
and
then
chris
we
can
talk
about
that
in
detail.
I
think
we
meet
today
again
yeah
but
yeah.
C
That's
it
for
the
solution,
validation
and
then
next
up
is
what
future
research
needs.
Do
you
have
I
added
a
job
to
be
done
for
the
environment
management.
That's
part
of
the
q2
ux
okrs.
The
goal
is
to
deliver
the
job
to
be
done
either.
You
know
to
validate
the
job
to
be
done.
Do
the
research,
if
we
haven't
done
so
yet
or
yeah,
revisit
or
improve
the
statement.
C
If
we
need
to
do
that,
I
know
that
daniel
did
quite
some
work
related
to
the
environment
management
jobs
to
be
done
since
last
quarter
for
the
previous
partner
and
but
especially
after
what
we
discussed
with
the
team
just
now,
chris
about
yeah
the
the
the
jobs
to
be
done
for
environment
management,
but
related
to
deployment
approvals.
You
know,
and
just
thinking,
if
there's
an
opportunity
for
us
to
look
at
that,
and
the
goal
of
course
of
the
kr
is
to
have
the
job
statements
done
before
the
end
of
the
quarter.
C
But
I
think
this
is
a
good
one
for
us
to
prioritize.
You
know
the
in
the
coming
milestones
and
not
the
end
of
q2,
because
since
a
lot
of
the
work
that
we're
doing
now
relates
to
environment
management
anyway,
yeah
just
having
the
well-defined
job
statement
and
the
user
stories
will
be
really
beneficial.
I
think
to
how
we
are
breaking
down
the
problems
in
any
ways,
just
validating
the
maturity
of
this
category,
but
I
think
it's
kind
of
to
you,
q2,
by
maturity.
Now
right.
A
Yeah,
let's
see
so
on
a
kind
of
a
related
note.
I
know
that
it's
different
from
like
jobs
to
be
done,
research,
but
I
previously
told
you
all
that
you
know
the
benchmarking
study
would
be
able
to
like
overlap
with
existing
like
cm
scorecard
work
and
after
doing
a
little
bit
more
digging
like
talking
with
other
members
of
my
research
team.
They
said
there
are
some
overlaps,
but
you
still
have
to
treat
those
as
separate
studies.
A
A
Yeah
because
kevin
is
basically
going
through
like
tomorrow,
like
all
the
different
projects
that
have
been
requested
for
ops
and
prioritizing
them,
along
with
myself,
so
we've
gotten
like
four
or
five
different
projects
for
ops
that
have
been
requested
so
yeah.
If
you
can
get
that
to
me,
like
in
the
next
day,
that'd
be
great.
A
B
I
added
this
one
hyanna.
I
think
you
wanted
to
bring
this
up.
Maybe
if
I
interpreted
your
statement
correctly
well,
we
had
we
just
came
out
of
our
brainstorm
session
with
the
team
we
were
discussing.
Oh
sorry,
I
should
have
linked
these
I'll
link
to
the
issues
in
a
bit
we're
discussing
specific,
a
specific
issue
where
we're
proposing
to
build
to-do's
for
deployment
approvals.
So
we
built
an
mvc
for
a
deployment
of
approvals
where
you
know
specific
teams
might
be
able
or
might
need
to
specify
an
approval
for
a
deployment.
B
The
original
proposal
was
to
do's,
but
the
team
had
other
thoughts
or
and
concerns
related
to
that
had
we
talked
about
brainstorm
different,
like
alternative
solutions,
but
then
there
were
specific
questions
that
came
up
then,
where
we
realized
well
we're
not
exactly
sure
from
a
user,
a
user
perspective,
what
the
answers
are.
So
specifically,
you
know
one
of
the
potential.
B
Consequences
if
we
built
to
do's
is,
maybe
teams
may
get
a
lot
of
to
do's?
If
there
are
a
lot
of
deployments
happening,
we
were,
you
know,
there's
a
concern
that
there
that
might
be
too
noisy
for
specific
groups.
We've
heard
that
concern
similar
concern
for
other
stages
and
other
features
in
gitlab.
So
you
know
we
potentially
worried
about
that.
B
I
think
another
one
is
very
specifically
like.
If
there
are
lots
of,
there
are
a
lot
of
deployments
that
that
are
happening
like
let's
say
in
the
course
of
the
day.
Teams
may
only
want
might
only
want
to
do
the
latest
one,
and
so
how
do
we?
And
if
they'll,
build
a
solution?
Build
notifications
such
that
you
know
we
support
that
use
case,
so
ayanna
suggested
we
bring
that
up
here,
something
that
we
might
want
to
continue
further
yeah.
Anything
else
to
add.
From
your
perspective,
did
I
cover
that.
C
My
goodness
yeah
it's
just
difficult
to
expand
on
the
interface
and
add
more
information
to
it
right,
so
we
have
been
working
on
the
usability
of
the
view,
etc,
etc.
So,
a
lot
of
the
questions
that
I
heard
today
with
the
team,
because
we
were
talking
about
technically
how
to
solve
this
problem,
I
feel
like
yeah
ux
wise.
I
don't
think
I
think
we
could
understand
the
problem
better
before
breaking
down
you
know
and
deciding
on
a
direction
for
it,
especially
that
yeah.
C
There
are
many
many
ways
that
we
can
solve
this
problem.
I
think,
what's
ali
chris,
that
mentioned
about
dog
fooding
right,
so
understanding.
If
we
are
the
git
lab
where
to
use
this
feature,
how
would
we
do
it
right?
If
and
that's
all
the
conversation
you
had
with
with
emmy
so
yeah?
I
think
it
it.
It
relates
to
this
environment
management
jobs
to
be
done,
it's
kind
of
a
sub
job
of
that
so
yeah
about
understanding
what
what
is
the
problem?
A
A
C
And
we
also
talk
about
iteration
right
if
we
do,
for
example,
to
do
the
notifications,
there's
a
conversation
about
the
flow
of
how
people
are
notified,
emerging
requests
and
how
we
can
yeah.
You
know
we
mock
that
behavior
in
the
api
for
deployment
approvals,
but
does
that
make
sense
right,
but
I
think,
and
then
chris
please
share
your
your
thoughts,
I
think
yeah.
B
B
A
Yeah,
that
makes
sense.
I
guess
one
of
my
related
questions
that
I
had
underneath
was
you
know
hayana,
since
you
brought
up
that
this
is
kind
of
connected
to
the
jobs
to
be
done
for
environment
management.
Says.
Is
there
kind
of
an
opportunity
to
do
kind
of
two
studies
in
one
in
a
sense
like
a
round
of
jobs
to
be
done
and
also
some
problem
validation
work
at
the
same
time?
C
I
think,
and
that's
my
my
gut
feeling
is
that
we
could
do.
I
think
we
could
potentially
do
it
together,
but
knowing
that
this
would
be
a
sub
job
right
of
environment
management
and
then
I
think
for
what
we
want
to
do
with
the
validation,
for
the
the
jobs
to
be
done.
Is
the
high
level
jobs
for
the
category,
and
this
is
yeah
it's
like
a
child
of
of
that.
C
A
A
B
A
B
A
A
Okay,
so
the
to-do
item
that
I
have
is
for
the
upcoming
benchmarking
study.
I've
had
some
conversations
with
some
of
the
other
researchers
who
have
actually
done
some
of
these
types
of
studies
before
so,
I've
been
able
to
kind
of
pick
their
brain
about
how
to
do
it
and
all
the
different
steps
involved.
A
A
I
think
it
might
be
a
good
activity
to
just
build
like
a
an
async
workshop,
just
between
the
three
of
us
to
go
through
and
and
kind
of
determine
like
what
are
the
workflows
that
we
want
to
focus
on.
What
are
the
tasks
within
those
workflows,
and
then
I
could
really
get
started
with
you
know,
recruiting
and
all
the
research
heavy
stuff,
but
we
certainly
want
to
be
in
alignment
on
like
what
we're
wanting
to
tackle.
A
C
A
Yeah
yeah
glad
to
have
your
your
participation
in
this.
It's
gonna
be
really
interesting
to
see
what
we
get
out
of
this.
This
whole
process,
so
I'll
share
more
details,
probably
within
the
next
week,
but
I'll
at
mention
you
within
the
issue
when
that
happens,
and
then
provide
plenty
of
instructions
and
everything.
So
you
know
how
to
get
started,
especially
since
we're
doing
this
async.