►
From YouTube: Release Group Product & UX Sync • 2022-13-01
Description
Daniel Fosco (Senior Product Designer) and Chris Balane (Senior Product Manager) discuss the current and upcoming work for the Release stage
Agenda (internal): https://docs.google.com/document/d/1Enn_E0guWmRBpi_sl_0Kw0p7K8QQNF6SbXliGvMwvxI/edit#heading=h.3mopkvc0fgpx
A
All
right
chris,
do
you
have
any
any
comments
before
we
jump
into
the
agenda.
A
So,
first
up,
let's
review
our
planning
board
for
the
upcoming
14-8
milestone,
that's
just
starting
monday,
so
speaking
more
specifically
to
design
the
things
that
I
currently
have
on
workflow
design.
Are
these
two
issues
or
usability
improvements
for
the
releases
page,
the
tags
page?
Actually,
that
are
almost
finished,
but
not
quite.
I
need
to
wrap
up
their
proposals
and
then
they
will
be
ready
for
planning
breakdown
and
they
are
marked
as
p3
on
14
8..
A
The
other
one
is
the
dynamically
populated
group
environments,
page
I'll
talk
more
about
it
in
a
bit
and
then
the
ones
ready
for
design,
especially
at
the
top,
are
the
ones
that
are
scheduled
for
14-8
right.
So
update
project
settings
is
to
support
the
deployment
approvals
effort.
These
two
other
issues
are
also
scheduled
for
the
milestone
and
the
others
will
be
picked
up
as
capacity
allows
them.
B
Yeah
no,
this
is
all
that
makes
sense.
These
are
a
great
mix
of
features
across
direction
to
support
the,
for
example,
the
improvement,
the
approval
feature
and
group
environments,
which
is
something
we're
focusing
on
next
and
then
I'm
glad
to
see
us
working
on
the
scorecard
issues
as
well
to
help
make
make
the
product
more
usable
for
our
users.
A
Yeah
great,
to
be
honest,
we
we
are
still
missing
some
issues
that
that
are
more
research
related
because
they
are
part
of
broader
efforts.
So
the
cms
card
right,
like
you
like
you,
mentioned,
for
release,
we
don't
have
a
link
yet
because
we're
still
working
on
jobs
to
be
done,
but
once
we
have,
it
will
be
you'll,
be
on
the
plan
board
as
well
back
here.
So
in
terms
of
review
direction
pages,
you
did
a
review
that
I
left
a
comment
already,
but
it's
already
merged.
A
I
actually
wanted
to
talk
a
little
bit
about
the
jobs
to
be
done
as
well.
We
have
talked
about
it
on
our
101,
but
I
think
it's
worth
reiterating
for
the
audience
here.
A
We
are
working
to
restructure
our
jobs
to
be
done
on
release
in
preparation
for
the
upcoming
scorecard
that
we'll
work
on,
and
the
idea
here
is
to
initially
was
to
do
a
live
review
of
our
drops
to
be
done.
But
as
we
worked
on
it
and
got
more
feedback,
I
realized
we
really
needed
to
restructure.
A
There
was
a
lot
of
duplication
across
our
jobs
to
be
done
and
a
lot
of
siloing
right,
the
jobs
to
be
done
were
directly
addressing
categories,
so
we
had
statements
that
were
duplicated
between
them,
so
the
link
will
be
on
the
agenda.
You
can
take
a
look,
but
it's
it's
a
large,
mr
and
I'm
super
interested
to
to
discuss
it
and
have
it
merged.
A
A
All
right
chris
already
commented
there,
so
so
I'll
just
skip
if
he
doesn't
have
any
additional
comments,
review,
ux,
vision
prototypes.
So
that's
the
what
I
added
here
is
the
group
environments
page
for
some
context.
This
is
essentially
a
high
level
page,
probably
on
the
group
level
that
will
implement
that
will
show
all
the
production
related
project
environments
right.
So,
instead
of
having
one
project
with
their
environments,
you're
going
to
have
a
page
that
has
multiple
projects
listed
and
all
of
their
environments
for
production.
A
As
we
progressed
with
this
proposal,
another
idea
came
up
to
have
just
scroll
all
the
way
down
here,
because
it's
here
there
you
go
a
page
that
lists
every
single
deployment
and
where
you
can
filter
by
different
different
aspects.
Different
facets,
so
almost
like
a
deployments
dashboard
so
that
this
discussion
started
to
grow
a
lot.
So
we
decided
to
separate
it
into
its
own
issue,
which
is
this
one
that
way
we
can
move
along
with
the
mvc
for
the
group
environments
page,
while
also
exploring
this
this
further.
A
A
So
I
think
this
is
a
direction
that
that
is
constantly
coming
up
for
our
team
and
it
makes
sense
for
us
to
explore,
but
we
also
have
to
do
so
looking
at
the
previous
research
and
making
sure
that
we're
going
into
a
direction
that
hasn't
been
invalidated
before
and
if
it
was
then,
if
it
makes
sense
to
revalidate
it
and
see,
if
now
it
makes
sense,
we
do
that,
but
also
respecting
the
previous
research
and
and
the
things
that
we
have
discovered
in
the
past.
A
This
issue
was
just
created,
so
there's
not
a
lot
of
discussion
on
it.
Discussion
was
the
other
one,
but
expect
expect
news
around
this
area
very
soon.
B
Yeah,
I'm
excited
to
see
that
one.
That
was
the
first
time
actually
I
saw
it
so
I'll
definitely
take
a
look
daniel.
Thank
you
for
putting
the
first
proposal
out
there
for
for
how
we
can
show
deployments
across
the
org.
A
I
mean
this.
This
was
the
I
didn't
create
the
new,
the
new
mockups
or
anything.
When
I
created
the
issue,
I
just
moved
it
moved
them
to
a
separate
one.
I
wish
I
did
it
before,
because
all
of
the
really
good
discussion
is
in
the
previous
issue,
but
that's
okay,
so
yeah,
let's
see
where
it
goes,
I'm
I'm
I'm
very
very
excited
about
this
direction.
But
again
I
don't
want
to
repeat
things
that
we
have
tried
before
without
properly
evaluating
them.
A
So
so,
let's,
let's
plan
around
it
before
before
we
dive
too
deep.
Otherwise
I
can
get
too
excited
about
this.
It
can
happen.
Yeah.
B
Yeah,
if
I
could
comment
or
add
my
thoughts
there,
I
I
totally
agree
with
everything
you
said.
I
think
I
think
it's
I
think
it's
actually.
I
think
it's
really
good
for
us
to
explore
sort
of
diverging
ideas,
especially
for
these
sort
of
vision,
concepts
and
so
yeah.
Definitely,
I
think
you
and
I
we
should
lean
on
the
previous
research.
B
I
think
we
should
do
an
exercise
of
like
trying
to
understand
where,
like
like
you
pointed
out
where
this
overlap
is
and
where
maybe
there's
common
things
that
we
can
start
on.
First,
if
if
they
are
aligned
and
then
since
we're
talking
about
vision
and
prototypes,
we
discussed
this
in
another
call.
But
I
think
what
what
we
both
want
to
do
is
get
in
a
sort
of
a
habit
of
putting
these
ideas
into
our
vision.
B
Like
refreshing,
our
vision
prototype
that
we
do
that
the
release
stage
has
done
in
the
past
and
then
use
that
as
a
like,
an
artifact
to
even
validate
the
artifact
to
one
like
see
how
all
these
pieces
fit
together
and
then
also
validate
with
our
customers
and
and
other
folks
that
we
work
with
as
well.
So
I'm
really
excited
to
see.
I
think
this
is
step
one
right.
B
I
think
I'm
really
excited
to
see
us
starting
to
lay
out
these
sort
of
future
concepts
and
then
then
yeah
next
step
will
be
putting
it
together.
A
Yeah,
absolutely
I
think
it
was.
It
was
a
natural
progression
of
of
me
expanding
the
the
proposal
for
that
specific
issue
and
then
growing
into
something
that
was
beyond
that
and
then
breaking
into
a
separate
separate
issue
was
a
necessary
and
really
good
first
step,
but
but
yeah
definitely
growing
these
these
ideas
into
into
the
vision,
level
and
validating
them
and
then
bringing
them
back
down
into
into
design
and
implementation
issues.
That
makes
a
lot
of
sense.
A
Awesome,
all
right
cool,
so
moving
on
to
research
needs,
I'm
really
happy
with
the
customer
calls
we've
been
having.
We
had
a
really
good
customer
call
this
week
that
chris
facilitated
about
deployment
approvals.
It
was
fascinating
to
see
not
only
how
much
the
solution
that
we're
building
matches
the
user.
Okay,
they
use
the
use
case
for
for
that
customer,
but
also
all
of
the
things
and
workflows
they
built
around
gitlab
to
have
that
functionality.
While
we
we
didn't
offer
it
yet.
A
So
it
was
really
interesting
and
I'm
I'm
interested
chris
in
in
structuring.
These
calls
not
only
calls
themselves,
but
everything
around
them
right
how
we
recruit,
for
these
calls,
how
we
make
up
screeners
like
our
scripts
and
then
how
we
share
results
and
track
follow-ups.
A
I
had
created
this
issue,
this
pilot
issue
for
recurring
customer
interviews
and
release
and
that
I
didn't
have
a
lot
of
time
to
work
on
it,
also
because
we're
researching
already,
but
that's
what
we've
been
doing
naturally,
so
I
think
it's
more
of
a
our
of
a
process
of
structuring
how
we
do
this
and
making
sure
that
we
have
repeatable
results
right.
I
also
mentioned
having
having
sort
of
a
small
database
of
customers
that
we
can
do
follow-ups
with
so
I'll.
A
Try
to
get
back
to
this
issue
soon
and
have
like
more
actionable
steps
for
us
to
build
this.
This
structure
around
interviewing.
B
Sounds
great
yeah
definitely
definitely
agree
there
and
actually
daniel.
I
I
didn't
tag
you
in
this,
but
I
did,
let
me
add
it
to
our
doc,
but
I
started
an
issue.
I
talked
to
victor
the
other
day
about
how
he
sort
of
just
his
process
for
doing
continuous
interviewing,
in
terms
of
you
know
where
to
document
the
the
notes
and
how
to
use
dovetail
and
all
of
that,
and
so
I
created
an
issue
in
our
cd
group
project
so
that
we
can
track
those
notes
and
so
on.
B
Yeah,
so
we
can
iterate
on
this,
but
since
we
did
since
since,
since
it
was
still
fresh
on
my
mind
after
that
call,
I
just
wanted
to
document
some
notes.
A
Yeah
I'll
I'll
check
out
the
notes
later
when
we're
number
one
thanks
for
for
sharing
the
link.
A
Point
on
cross-stage
collaboration,
and
one
of
the
points
that
came
up
in
the
discussion
during
these
jobs
to
be
done
was
a
job
from
package
that
had
a
lot
of
overlap
with
release
so
katie,
the
designer
from
release
was,
was
tagging
the
discussion
and
we're
trying
to
find
the
common
ground
like
one
job
for
that
specific
area
that
that
is
useful
for
customers,
both
in
release
and
package.
A
But
on
top
of
that
we're
getting
together
next
week
to
to
discuss
more
broadly
about
how
we
can
we
can
get
these
two
areas
together,
especially
because
there
are
issue
and
feature
proposals
for
reusing
pieces
of
package
functionality
and
release,
and
vice
versa.
So
I
think
it's
a
really
good
conversation
to
have.
That
is
a
little
bit
overdue
in
awesome,
yeah
I'll!
Keep
you
I'll!
Keep
you
updated
on
what
comes
out
of
that.
A
All
right,
those
were
some
of
the
topics
I
added.
Do
you
have
anything
else.
B
A
Same
yeah,
well,
thanks
for
watching
and
yeah,
see
you
next
time.