►
From YouTube: Release Group Product & UX Weekly - 2021-05-19
Description
Daniel Fosco, Sr. Product Designer, Rayana Verissimo, Product Design Manager, and Kevin Chu, Group Product Manager discuss work for upcoming milestones for the Release Group.
Agenda: https://docs.google.com/document/d/1Enn_E0guWmRBpi_sl_0Kw0p7K8QQNF6SbXliGvMwvxI/edit?usp=sharing
A
A
A
We
just
finished
the
solution,
validation,
but
about
a
week
ago
sheena
made
a
comment
that
was
overlooked
and
essentially
there
is
an
issue
with
the
way
the
the
workflow
was
built,
both
in
the
sense
that
it's
not
the
merge
requests
in
the
pipelines
are
not
the
places
where
operators
that
operate
deploys
usually
use.
We
were
aware
of
that
and
that
came
up
in
solution
validation,
but
there
is
a
technical
issue
where
the
merge
request
is
not
the
ideal
artifact
for
us
to
base
the
approval
of
the
deploy.
A
B
B
C
B
B
There's
there's
several
blockers:
that's
blocks
a
group
level
permission.
However,
that
said,
given
the
amount
of
deprecation
work
that
are
in
14-0,
I
I
believe
many
of
the
p2
bugs
and
issues
and
features
we
actually
won't
get
to.
So
I
I
do
expect
us
to
not
touch
the
things
that
are
listed
in
p3,
currently
maybe
get
to
some
of
the
items
in
p2
and
have
a
bunch
of
carry
over
in
140..
B
B
I
think
it's
a
it's
a
great
time
to
kind
of
kind
of
really
focus
in
on
some
of
the
bugs
performance
issues
that
have
been
piling
up
over
time,
and
this
is
also
out
of
self
selfish
interest.
This
will
give
me
more
time
to
understand
the
longer
term
release
roadmap,
to
figure
out
some
of
the
things
that
we
might
be
interested
in
making
progress.
B
B
B
The
other
item
I
listed
here
you
go
back
to
the
issue,
daniel
or
sorry
the
the
note
stock.
I
included
a
link,
I'm
interested
in
making
progress
on
this
discovery,
discoverability
issue.
So
right
now
we
have
an
experiment
running
the
growth
team,
provided
some
guidance
on
the
data
we
need.
We
should
look
for
before
we
deem
the
experiment,
whether
successful
or
not
a
success.
B
There's
there's
more
ideas
on
here.
I
haven't
examined
these
in
detail.
I
love
yours
help
in
looking
through
these
you,
you
haven't
already
they're
they're,
directly
related
to
adoption,
or
lack
thereof,
for
many
of
our
features
and
really
love
to
collaborate
with
you
to
look
through
this
list
and
kind
of
dig
into
them
to
see
what
makes
sense
to
do.
B
A
Yeah,
especially
for
now
talking
more
specifically
about
the
design
issues
starting
in
14-0,
I
started
to
shift
focus
into
environments
and
then,
especially
in
141,
I
scheduled
more
mostly
environments,
issues,
there's
some
stuff
that
relates
to
our
ux
okrs
for
q2,
but
they
are
also
in
a
way
related
to
environments.
Just
by
luck,
even
though
the
focus
is
a
merger
quest,
these
issues
were
pulled
from
the
improving
environments,
epic,
that
hayana
and
jackie
research
and
prioritize
back
in
the
release
orchestration
team.
A
Now,
in
my
opinion,
the
environments
page,
is
a
really
central
piece
for
our
group.
That,
in
terms
of
usability,
it's
like
has
has
many
things
that
need
to
be
improved.
That's
why
I
I've
focused
on
it,
but
we
can,
of
course
accommodate
other
things
and
and
not
just
accordingly
cool.
Why
are
your
thoughts.
B
I
totally
by
the
argument
that
it's
really
central
to
everything,
release
related
and-
and
I
also
have
a
strong
opinion
that
it's
not
very
good
in
good
lab
at
the
moment,
and
we
have
a
problem
where
we
we
mix
this
concept
with
other
concepts
such
as
deployment,
which
is
frankly
confusing
to
me.
I
can
imagine
it's
confusing
to
many
others
as
well,
and
if
we
think
about
environments
from
a
deployment
perspective
or
release
perspective,
it's
right
now,
it's
not
a
like
a
like.
B
B
I
think
this
is
this
is
an
area
while
we
can
make
improvements
on
the
stuff
that
we
have
currently
because,
like
there's
a
lot
of
things
to
improve,
you
may
be
in
an
area
following
hyanna
and
what
jackie
did
like
take
a
step
back.
What
what
are
we
actually
talking
about
here?
Maybe
hyanna
and
jackie-
already-
has
the
answers.
I
I
I
just
haven't
gotten
bored.
C
Ahead
but
patiently
waiting,
my
question
to
you
of
the
regarding
the
increasing
discoverability
of
these
features
is
how
how
does
that
prioritize
against
improving
environments
in
general,
because
that's
all
the
things
that
they
write
environment
as
deployments
as
an
application
and
having
group
environments-
let's
say,
enterprise
management
deployments
is
part
of
the
research
that
jackie
and
I
did
last
year.
And
if
you
look
at
this
link
here
in
group
environments,
that's
the
epic,
jackie
and
I
created
based
on
the
research
that
we
did
problem
resolution
validation
for
environments
and
we
created.
C
There
you
go,
you
can
see
improving
environments
right,
epic,
yeah,
so
jackie
and
I
worked
on
the
research
for
our
environment,
I'll
link
you
later
to
to
the
opportunity,
canvas
and
right
before
the
release
management
team
was
dissolved.
This
was
our
priority,
so
we
learned
that
the
low-hanging
fruits
for
environments
would
be
to
burn
down
the
the
list
of
bug
fixes
right.
C
Then
we
have
a
number
of
issues
related
to
usability,
just
discoverability,
whatever
just
inconsistent,
ui
et
cetera,
related
to
environments
that
exist
today
and
then
look
into
developing
designs
for
these
issues
or
design
testing
proposals.
So
there's
mostly
talk
about
that
a
similar
age
or
similar
epic.
C
That
daniel
has,
that
is
about
improving
the
environment's
page
so,
for
example,
an
environment
folder
in
the
index
page,
it's
a
math
right,
so
there's
a
bunch
of
behaviors
for
users
cannot
really
understand
the
hierarchy
or
which
environment,
for
example,
has
the
latest
deployment
and
who
triggered
that
and
why?
Where
is
that
pointing,
etc?
C
Things
related
to
that
so
status
batch
for
environments?
These
all,
if
not
most
of
them,
if
not
all,
they
come
from
research
findings
and
they
align
with
what
we
learned
from
our
customers
during
this
investigation
and
then
the
last
thing
will
be
the
design
and
breakdown,
which
is
also
that
continue
to
do
validation
on
high
level
things
so
operation,
environments,
tags
related
to
environment,
so
that
goes
back
to
release
orchestration
anyways.
C
These
are
more
complex
things
that
they
don't
have
proposals
per
se,
but
and,
as
you
can
see,
some
are
a
really
old
legacy,
but
those
are
things
that
we
know
we
will
have
to
do,
and
so
my
question
is
kind
of
trying
to
summarize
it.
How
that
looks
to
you
about
kevin,
looking
comparing
to
what
you
had
there
about
objective
coverability
of
the
td
features,
because
we
already
validated
those-
and
we
already
had
well
a
plan
for
them,
but
because
of
the
change
in
the
structure.
C
B
I
I
love
that
if
it's
it's
a
problem,
that's
validated
and
the
solution
is
validated
to
me.
It
becomes
a
no-brainer
and
I
also
know
that
in
general,
that's
a
much
bigger
thing.
The
reason
I
pulled
the
kind
of
discoverability
issue
forward
is
because
it
was
number
two
on
the
list
from
the
yearly
priority
issue
that
I
was
referencing,
but
if
it's
like
issues
that
we
haven't
really
dove
into-
and
we
know
environment
is
super
important-
the
relative
priority
answer
to
me
seems
pretty
clear
that
we
can.
B
C
B
B
C
Sure
and
that's
exactly
what
we
learned
also
from
this
validation
right,
we
we
had
a
whole.
I
linked
here,
an
epic
where
I
have
all
the
opportunity
campuses
for
release
management
well
release,
so
the
the
categories
that
I
that
I
own
until
last
year
and
that's
exactly
what
we
learned
that
dora
for
metrics
was
really
the
top
priority,
but
also
the
low-hanging
fruit.
C
So,
instead
of
having
that
dashboard
for
the
enterprise
personas
right
with
everything
about
your
diplomas,
let's
show
them
how
their
applications
are
are
comparing
to
whatever
other
competitors
or
the
market
and
then
the
dollar
for
metrics,
where
those
the
way
to
show
that
plus
environment
needs
to
get
better.
That's
what
we
learned-
and
I
asked
jackie
for
a
link
of
that
opportunity-
canvas
presentation,
I
think,
is
going
to
be
helpful
to
the
both
of
you,
because
then
you
can
you
don't
have
to
read
all
the
documentation.
C
B
B
A
So
in
terms
of
design
issues,
the
ones
that
I
schedule
for
fourteen
one
are
mostly
the
the
bugs
they're
on
the
top
of
the
list,
but
focused
on
on
design
and
front
end.
So
there
that
I
can
start
working
on
as
developers
are
still
focusing
on
wrapping
up
the
work
on
door.
For
so
we
can
have
this
gradient
between
the
two.
The
two
focuses.
B
Okay,
cool
the
other
thing
that
I'm
thinking
a
lot
about.
That's
a
bigger
thing
is
group
level
group
level
release
groups.
Resource
groups
are
so
this
is
really
beneficial
and
I
wouldn't
weigh
this
as
being
more
important
than
environments,
because
environments,
I
think,
has
a
lot
much
larger
impact.
This
is
like
this
is
important
because
we
already
have
project
level
resource
groups,
but
resources
in
my
opinion
is
really
most
useful
when
we
have
it
at
the
group
level,
because
it's
less
likely,
you
need
to
you
know,
constrain
yourself
within
a
specific
project.
B
It's
at
the
at
the
group
level,
where
this
becomes
really
really
useful,
and
I've
heard
from
people
talking
about
this
and
this
this.
The
issue
I
linked
under
14.2
also
has
gotten
some
interesting
comments
from
customers
that
make
me
think
that
it
is
actually
important.
I
don't
have
a
specific
method
of
weighing
it
against
the
other
things
we
talked
about,
but
this
is
the
other
thing.
That's
on
my
mind
anyway,.
B
B
B
B
A
Yeah
I've
pasted
a
link
on
the
agenda
of
it
was
the
best
recording
about
environments.
I
I
watched
which
one
ion
and
jackie
it's
this
one
at
the
very
end
of
the
list.
Okay,
it
gave
me
the
overview
I
needed
to
to
start
fighting
these
issues
in
a
way
that
I
felt
like
I
understood,
then
we're
just
like
just
gonna
pick
up
top
and
bottom.
A
A
C
Yeah
with
all
these
things,
you
say:
I'm
like
yes,
yes,
yes,
we
heard
this
from
so
many
people.
That's
I'm
saying
please
watch
these
recordings
because
then
you're
not
going
to
do
any
rework.
You
know
in
terms
of
validation
and
ux,
because
these
things
are
documented
and
there
are
research
insights
on,
for
example,
documentation
where
we
need
to
improve
well
what
language
we
need
to
use.
How,
for
example,
icons
for
deployments?
How
do
people
treat
the
deployments
versus
environment?
C
We
didn't
even
some
surveys
asking
people
to
explain
what
they
think
environments
mean
translate
environments
to
us.
What
do
you
understand
from
what
you're
saying
here?
So
I
think
a
lot
of
if
you
spend
some
time
looking
into
the
existing
findings,
you'll
be
able
to
not
just
understand
environments
and
but
also
help
shape
the
direction
and
shape
your
your
next
steps
and
not
the
rework.
I
think
we'll
all
be
very
happy
if
you
don't
have
to.
We
do
yeah.
B
A
No,
not
at
all
from
the
perspective
of
environments
and
and
releases,
not
so
full,
but
I'm
still
caught
up
with
some
rewarding
things
that
I
want
to
wrap
up
properly.
This
this
milestone
and
there's
also
the
the
current
issue
that
we're
blocked
on
so
that
will
spill
over
a
little
bit
for
this
milestone
but
yeah
for
for
the
next
141.
I
plan
to
be
fully
fully
on
board
for
for
environments.