►
From YouTube: Release PM/PD/UXR Monthly Sync - June 2022
Description
This meeting is a monthly touchpoint between Chris Balane (Product Manager), Rayana Verissimo (Product Design Manager), and Will Leidheiser (UX Researcher) to discuss research within the Release stage group.
A
So
I
guess
we
can
get
started
at
the
top.
So
one
of
the
first
things
that
I
put
in
the
agenda
was
that
the
interviews
have
wrapped
up.
I've
heard
you
hyanna
talk
about
the
solution,
validation,
work
for
the
environments,
page
redesign,
so
I
was
just
kind
of
curious
when
the
results
and
insights
would
be
shared
out,
and
you
know
what
are
the
next
steps
that
are
kind
of
coming
out
of
that
work?.
B
Yes,
good
kala,
thanks
for
the
reminder,
because
indeed
I
think
this
week
I
started
with
a
prototyping
and
I
totally
forgot
to
share
the
results
so
I'll
do
that
this
week,
I'll
write
down
the
summary
and
also
share
with
the
team,
yes
slack
and
team
meeting
and
last
time
we
also
talked
about
actionable
insight
right.
So
there's
a
couple
of
issues
there
already
on
my
on
my
plate
that
relate
to
that.
B
A
A
You
know
what
people
actually
learned
from
the
study
because
we
had
heard
complaints
about.
Like
you
know,
if
I
go
to
a
research
issue,
I
don't
really
know
what
they
learned.
I
have
to
like
dig
into
the
comments
or
something
so
we
just
added
a
little
table
at
the
top
that
you
can
easily
edit
and
we're
only
looking
for
just
like
a
couple
sentences.
I
know
that
you've
already
included
like
a
link
to
the
dovetail
project
and
other
summaries
that
are
linked
within
that
issue.
A
So
that's
good,
but
in
addition
to
that,
if
you
want
to
make
like
a
very
short
video
summary
just
talking
through
that-
and
you
know
showing
some
of
the
things
in
real
time-
you're
welcome
to
do
that.
But
I
don't
want
to
put
more
on
your
plate.
I
think
the
stuff
that
you've
already
proposed
is
is
fine.
B
Okay,
awesome
I'll
look
into
that
this
week.
My
writing
summarized
from
each
interview
the
main
insights
but
yeah.
I
don't
know
I'll
I'll
think
about
the
video.
I
think
it's
actually
a
fun,
but
also
a
nice
way
to
share
out
the
results
with
more
people,
so
I'll
put
that
in
my
backlog,
but
thanks
for
the
thanks
for
the
heads
up
will
be
helpful.
B
C
Thanks
will
transparency
I'm
like
I'm
just
very
behind,
and
so
I
think
I
do
have
a
lot
of
free.
I
have
not
free
time,
but
I
have
some
time
today
to
like
focus
on
this,
and
I
will
try
to
get
a
few
of
these
scheduled
like
in
the
next
week.
Okay
yeah,
thank
you
for
the
offer
and
thanks
for
checking
in
I,
if
I,
if
I
this,
is
sort
of
new
to
me.
C
C
D
B
Yeah,
I
got
an
email
I
think
today
about
a
participant
I
haven't
received
your
thank
you
gift
after
well
participating
in
the
the
interviews
for
the
the
environment
page
and
I
actually
don't
remember.
I
submitted
the
the
request
with
katelyn
or
not
because
was
one
of
the
period
where
I
was
either
filling
in
in
the
in
the
spreadsheet
that
you
and
erica
use
for
the
common
screener
and
katelyn's
sheet
right
for
that
particular
recruiting
request
for
that
issue.
B
A
I
think
if
it
involves
using
participants
that
we
get
through
the
common
screener,
I
would
put
it
in
that
sheet
just
so.
We
can
track
people
across
those
different
studies
because
they're
all
essentially
coming
from
one
pool
of
people,
but
I
would
also
in
terms
of
your
original
question
at
mention
caitlyn
and
then
just
tell
her
about
like
hey.
These
are
the
names
of
the
people
or
their
email
addresses
and
I'm
not
sure
if
they
were
paid.
B
Will
thank
you
so
much
and
then
a
follow-up
question
to
that
that
there
was
one
participant
I
think
the
first
person
I
talked
to
that
wasn't
really
helpful.
I
think
not
that
they
were
not
gitlab
users,
but
for
you
know
the
particular
they
they
did
not
have
experience
with
with
git
lab
with
the
deployments
and
releases
and
they
were
not
applied
with
releasing
gitlab.
How
do
I
give
that
feedback
about
the
particular
person
so
that
when
they
are.
B
A
I
think
within
the
recruiting
issue,
it
should
be
confidential,
so
you
could
just
mention
the
name
of
that
individual
and
like
tag
caitlyn
and
erica,
so
that
either
they
can
like
drop
that
person
altogether
from
the
qualtrics
data
or
they
can
like
flag
them
in
some
way.
I
think
there
may
be
some
way
to
do
that,
so
that
other
people
don't
recruit
them
and
run
into
the
same
issue.
B
Okay
sounds
good
I'll.
Do
that
and
I'll
after
I'll?
Do
that
and
I'll
share
that
that
default
with
my
team,
because
there
were
some
instances
in
the
past
where
they
also
feel
like
the
registration
that
wasn't
really
helpful
or
that
they
were
all
over
the
place
or
remind
them
to
do
that
as
well.
After
the
interview
right
so
flag
that
for
the
team.
A
A
So
my
plan
is
to
follow
the
same
set
of
steps,
create
a
sample
project
and
then
I'll
need
to
generate
fake
data.
I
have
looked
into
what
the
fake
data
or
what
type
of
fake
data
will
be
generated,
and
it's
a
lot
of
just
kind
of
basic
stuff.
Like
issues
merge
requests,
it's
not
stuff.
That
seems
to
be
applicable
to
our
situation
like
environments.
C
C
A
A
I
was
looking
at
the
mural
and
there's
31
different
tasks
that
have
been
proposed
across
you
and
hayana,
so
we
won't
be
able
to
go
through
every
task
in
the
study.
I
would
imagine
just
because,
as
I
added
a
little
note
for
context
here,
the
other
researcher
who
did
the
same
type
of
study
in
create,
went
through
20
tasks
and
it
took
two
hours
per
participant
and
that
was
with
20
participants.
A
So
it's
it's
going
to
be
a
pretty
big
time,
commitment
and
everything
so
I'll
just
have
to
like
whittle
down
what
tasks
we
go
through.
So
I
may
set
up
a
a
separate
conversation
once
I've
had
a
chance
to
look
at
all
those
different
tasks
and
then
we'll
figure
out,
you
know
what
you
know
roughly
20
or
so
we'll
want
to
go
with,
and
then
then
I
can
give
you
and
the
team.
A
better
idea
of
you
know:
here's
the
set
of
information,
I'll
need
for
those
tasks.
B
Because
there
are
a
couple
of
scenarios
and
tasks
that
can
only
be
set
up
via
api
today,
because
we
don't
have
the
ui
we
can
highlight
those
in
the
mirror
board.
So
just
say
like
this
is
a
back
and
only
task
right
or
a
scenario.
I
also
have
an
idea,
but
to
chris's
point
yeah
like
if
it's
about
the
scenario
or
the
task
is
managing
deployments
or
setting
up
a
deploy,
pipeline,
etc.
B
I
think
it's
good
to
have
those
first,
so
that
the
team
can
set
up
the
particular
ui
and
a
particular
test
project,
with
not
only
relevant
data
but
meeting
the
criteria
right
that
we
want
to
validate
yeah,
and
I
can
also
help
out
if
you,
if
you
need,
will
okay,
please
reach
out
to
the
team,
but
also,
let
me
know
there
are
a
couple
of
things
I
think
I
might
be
able
to
to
help
you
with
okay.
I.
C
Think
this
is
just
also
great,
because
this
is
a
good
like
learning
exercise
for
all.
I
think
all
for
all
of
us
too.
So
I
think
we'll
learn
a
lot
by
trying
to
generate
this,
like
all
the
pieces
that
we
need
to
be
able
to
showcase
the
different
features
and
the
tasks
that
are
done
in
the
product.
So
that's.
I
think
this
is
awesome
and
yeah
same
I'm
happy
to
help
as
well.
Will
when
you
get
to
that
point,.
A
Yeah
and
to
piggyback
on,
I
don't
know
what
you
were
saying
just
a
moment
ago.
I
think
it
would
be
good
to
know
which
ones
are
api
based,
and
we
may
want
to
have
that
discussion
in
our
next
chat.
Like
are
those
things
out
of
scope,
or
do
we
want
to
focus
on
the
ones
that
are
just
within
the
get
lab
ui
and
that
decision
doesn't
have
to
be
made
right
now,
but
just
maybe
something
to
think
about
before
we
we
have
that
chat.
B
D
B
A
Questions
that
you
know
I'll
be
asking
about,
like
you
know,
what's
the
happy
path
to
do
this
task
from
start
to
finish,
what
are
the
different
ways
that
they
can
like
complete
the
task,
because
one
of
the
main
aspects
of
the
usability
benchmarking
study
is
to
kind
of
determine
if
they've
completed
it
or
not.
So
we'll
have
to
know
like
okay
when
they
do
this,
that's
a
success,
but
if
they
do
it
this
other
way,
that's
maybe
a
failure
or
something
so
we'll
want
to
determine
that.
B
Boys
my
comments:
you
have
a
new
product
designer
joining
soon
all
right
and
I'd
like
to
include
them
in
the
conversation
as
well,
for
the
the
benchmarking
for
release.
So
that's
yeah
that
can
be
part
of
their
onboarding
process
and
then
yeah,
just
not
only
experiencing
the
benchmarking
process
itself,
but
give
them
the
opportunity
to
learn
more
about
release
with
us.
So
I'll
I'll.
Let
you
know
when
I
know
more
about
and
then
when
you
can
include
them.
Okay,.
D
B
A
I
guess
just
for
context
chris
that
hayana
and
I
have
like
a
separate
ux
related
meeting,
and
I
had
asked
a
question
about
how
right
now
in
that
planning
issue,
we've
got
like
a
jobs
to
be
done
and
a
cm
scorecard
both
for
environment
management,
and
so
I
wasn't
sure
like
if
one
of
those
had
to
be
completed
before
the
other
one.
Just
in
terms
of
like
how
to
stack
them.
You
know
priority
wise,
so
hyanna
had
advised
me
that
the
jobs
to
be
done
should
be
completed
before
the
cm
scorecard.
A
B
D
A
I'll
I'll
keep
writing
this
in
the
the
doc,
but
basically
when
he
picks
it
up.
You
know
whether
that's
15.2
or
something
else
he
can
just
ping
me
for
feedback
and
consulting
I've
done
a
couple
jobs
to
be
done.
Studies
that
I'm
currently
helping
the
configure
team
their
designers
is
leading
one
for
kubernetes.
D
B
We
do
thank
you
for
that
anything
for
this
one
in
particular,
because
we
have
so
many
insights.
That's
just
my
initial
gut
feeling
that
we
might
not
necessarily
need
to
do
the
the
interviews,
but
I
would
think
I'll
leave
that
up
to
to
him
and
to
you
to
decide
on
the
approach,
because
he
also
needs
to
become
familiar
with
the
area,
but
because
we
have
not
only
talked
but
investigated
environment
management
in
the
past.
I
think
you
can
leverage
from
that
from
the
inside
that
we
have
in
our
backlog.
D
A
C
That
makes
sense
well
yeah,
thanks
for
clarifying
linking
linking
also
to
their
handbook
pages.
Yeah
sounds
good.
I
I
think
yeah
and
thanks
hannah
for
raising
this.
I'm
just
thinking
about
I
know.
Are
you
asking
also
like
what
what
should?
How
should
we
move
this
forward,
and
what
are
the
next
steps?
Is
that.
C
Yeah,
I
think
it
sounds
like.
Then
you
got
to
will's
point
it.
Maybe
it's
it's!
It's
problem
validation.
I
think
what
the
research
would.
I
think,
what
like
it
would
could
look
like
is
interviewing
or
discussing
even
with
internal
teams
like
one,
maybe
just
more
color
about
this,
like
what
like,
we
have
the
digital
experience
team.
C
I
think
that's
what
they're
called
in
the
in
marketing
and
they're.
They
decided
to
use
launch
darkly,
which
is
one
of
our
competitors
for
their
needs,
and
I
would
love
to
know
why,
and
you
know
why
they
made
that
decision
and
why,
if,
if,
if
they
considered
using
git
lab
for
dog
fooding,
rather
than
that,
so
like
that's,
that
that
would
be
one
data
point,
I'd
love
to
to
know,
and
then
maybe
even
some
internal
engineering
teams,
but
then
yeah.
C
A
C
A
B
D
B
A
D
C
C
A
So
I
talk
about
sus
and
it's
like
yeah,
you
know,
sus
is
like
up
in
the
clouds
and
it
tells
you
like
get
lab
is
like
a
little
bit
better,
a
little
bit
worse
overall,
but
it
yeah.
You
know
besides,
that,
doesn't
really
tell
you
much
so
this
is
gets
like
very
granular
and
says
like
okay,
when
they're
trying
to
do
this
very
specific
task
within
you
know,
environments,
you
know,
can
they
do
it?
I.
A
B
B
Do
you
want
to
have
do
we
want
to
have
like
we
are
validating
the
usability
right
through
the
for
the
interface
versus
the
api
right
and
how
the
those
rate,
because
the
personas
are
also
different
and
the
tasks
are
going
to
be
different
and
back
then,
when
we
did
that
exercise,
no
one
could
complete
they.
If
we,
we
had
to
close
the
the
meeting,
because
it
was
just
taking
so
long
and
people
had
to
configure
xyz
before
being
able
to
complete
the
task
and
it
didn't
have
permissions,
etc.
B
A
Yeah
and
that's
why
we
want
to
like
narrow
down
the
tasks,
not
just
because
we
have
a
broad
list,
but
you
know
we're
only
gonna
have
so
long
to
talk
to
a
participant.
I
mean
they'll
gladly
take
more
of
our
money
for
more
of
their
time,
but
we
don't
want
to
like
overload
them
with
participating
in
you
know
a
three
hour
study
or
something
with
us,
so
yeah
it'll
be
like
finding
that
right
balance
between
you
know
what
tasks
like.
A
B
Yep
I
understand
I
agree
with
that
information,
so
I'm
going
to
look
into
that
right
after
a
call,
because
then
it
will
be
still
fresh
in
my
mind
and
because,
when
I
was
doing
this,
this
exercise
also
in
the
mirror
board,
I
was
like
this
is
a
persona
that
would
definitely
do
this
through
the
ui
or
this
is
the
person
that
would
set
up.
You
know
acquire
the
via
api
and
I
think
also
based
on
all
the
limitations
that
we
are
we
have
in
on
the
interface
today.
B
A
A
B
D
B
Well,
because
I
remember
with
jackie,
was
really
frustrating
because
we
couldn't
complete
any
of
the
the
interviews
and
the
setup,
because
we
really
underestimated
how
much
setup
people
have
to
do
before
going
to
the
the
session
with
us.
So
I
think
in
particular,
because
we
are
looking
at
the
release
as
a
whole,
really
interesting
to
yeah,
try
to
frame
that
and
see.
If
there's
anything,
we
can
do
to
avoid
the
security.
A
A
D
D
C
I
just
I
was
just
I
just
wanted
to.
Let
will
know
that
about
the
ux
roadmap,
like
projects
yeah
and
then
so
so
I
linked
a
linkedin
issue
will
where
I
think
I
I
think
it's
a
subset
of
like
the
ux
design
team
or
like
want
to
try
to
try
this
new
ux
roadmap,
like
kind
of
creating
one
to
define
sort
of
like
what
are
the
pieces
of
work
in
terms
of
design
and
research.
That
are
that.
C
B
And
we
want
to
like
one
of
the
goals
for
this.
That's
the
the
secure
team
ran
a
pilot,
and
then
we
are
trying
this
out
with
the
other
design
teams
so
that
well
we
can
test
their
this
framework.
The
process,
but
also
and
then
give
feedback
but
also
see
like,
is
this
helpful
right?
Does
it
bring
more
clarity
to
I
don't
wanna,
I
don't.
I
don't
wanna
call
it
roadmap,
because
we
already
have
the
product
roadmap
and
then
that
doesn't
really
replace
anything
right.
B
For
for
ux,
not
just
in
terms
of
here's,
an
issue
that
we
are
solving
or
here's
the
problem
that
we
are
closing
or
validating,
but
in
the
longer
term
this
is
the
chunk
of
work
that
ux
is
going
to
be
working
on,
that
contributes
to
the
product
roadmap
or
the
you
know
our
stage
vision,
but
really
I've
never
done
this
before
I'm
curious
and
I
think
it'll
be
an
interesting
exercise
for
us
to
do
so.
Let's
see
yeah
it's
a
it's
a
part
of
a
okay.
I
will,
by
the
way,.