►
From YouTube: Verify & Release UX Team Design Review | 7 April 2020
Description
Rayana raises a topic of how can we better align when touching the same UI functionality in multiple teams.
A
B
C
D
C
You
know,
anyways
I
just
had
to
read
it
everything,
but
while
also
I
was
working
on
this
issue,
which
the
scope
was
initially
to
make
its
more
visible
or
just
like
easier
for
people
to
select
an
environment
wild
card
while
creating
while
working
on
ci
City
settings
I
realized
that
a
lot
of
the
changes
that's
this
issue
proposed
won't
exist
anymore
because
of
the
improvements
of
the
change
in
the
CIA.
The
verifying
is
going
to
merge
now
in
12.
C
A
A
C
Like
this
UI
here
right,
where
you'll
be
able
to
select,
for
example,
the
scope
and
create
a
new
environment
scope,
I
can
actually
show
as
well
from
that
is
the
old
UI
right
yeah.
That's
like
an
old
prototype.
Let
me
show
you
so
everyone
also
knows
what
I'm
talking
about
it's
actually
here
on
project
settings
the
ICD
variables
yeah.
C
So
my
issue
is
about
when
the
problem
that
the
statement
was
like
when
I'm
selecting
or
searching
for
an
environment
here
and
I-
say:
I,
don't
know,
QA
QA
doesn't
exist
yet
it
shows
no
matching
results,
but
also
shows
great
wildcard
QE.
But
then
a
bunch
of
questions
raised
that
it's
keyway,
a
wild
card
and
I
also
saw
a
comment
by
UB
meter
that
a
wild
card
actually
needs
to
have
this
asterisk
symbol
next
to
it,
and
if
I'm
not
creating
a
wild
card
here,
what
am
I
actually
creating.
C
A
C
A
C
Thing
so
anyway,
so
I
just
wanted
to
highlight,
because
this
is
like
the
cross,
the
dependencies
that
we
need
to
know
about,
but
the
new
axle
for
me
was
clear
based
on
the
m/h
type
from
months
ago,
but
then,
when
I
want
to
check
your
brother
does
like
weed
whatever
wait
a
minute.
Why
is
this
now
just
a
plain
drop-down
and
then
my
question
is
going
back
to
so.
The
initial
scope
here
is
like:
how
can
our
our
teams
stay
more?
C
You
know
up-to-date
and
more
in
the
mood,
because
now
that
this
is
since
it's
not
in
the
product,
yet
I
cannot
move
forward,
because
my
developers
cannot
just
immediately
build
on
top
of
what's
there
in
the
codebase
and
how
do
you
think
we
can
stay
in
the
loop?
You
know
because
that's
just
the
point,
the
points
are
added
to
our
101
that
we
have
me
didn't
go
through.
C
Those
was
that
I'm
always
going
to
be
working
on
the
environment,
variables
I'm,
always
going
to
be
working
on
deployments,
and
sometimes
it's
difficult
to
track
what
the
engineers
are
doing,
not
even
what
the
UX
changes
that
we
have
been.
So,
maybe
not
only
for
limited
but
from
everyone
else.
How
do
you
folks
think
we
can
stay
more?
You
know
it's
saying,
even
though
about
those
very
changes.
Please
no
regressions.
A
If
I
get
so,
if
I
rephrase,
the
question
is,
how
can
we
make
sure
we
are
like
better
when
touching
the
same
UI
in
multiple
teams?
At
the
same
time,
right
and
this
been
it
is,
it
is
a
bit
of
a
strange
situation
that
happens
quite
quite
regularly
in
a
way,
yeah
I
think
it's
an
interesting
problem
both
from
like
you
know,
engineers
pushing
code
to
the
same
same
part,
I
think
rich
west
region
has
been
one
of
those
examples
as
well.
Yeah.
C
And
one
of
the
the
pain
points
I
found
is
that
because
my
p.m.
when
my
engineers,
they
don't
have
an
overview
of
not
even
just
the
overview,
but
they
know
that
some
things
are
in
progress,
but
I
think
other
teams
cannot
guarantee
the
delivery.
So
for
exactly
this
case,
they
actually
delivered.
But
there
was
a
problem
with
it
right.
So
now
there
is
regression
in
a
milestone
later
I'm
still
working
on
things
that
are
going
to
be
built
on
top
of
features
that
are
in
progress.
C
So
my
designs
might
not
match
what
they're
going
to
deliver
and
I
know
that
I'm
going
to
have
to
at
some
point-
maybe
not
in
this
issue,
but
usually
I-
have
to
go
back
to
the
design
phase
to
the
drawing
board
and
then
change
things,
because
this
called
change
or
because
the
copy
change
the
acceptance
criteria,
change
for
things
and
with
this
issue
in
particular,
I
think
in
with
the
environment
variables.
I
know
why
I
know
it's
because
they
had
to
refactor
the
whole
page.
But
it's
been
very
challenging
to
know
exactly
where
things
are.
A
C
B
A
Would
be
nice
if
we
had
like
something?
You
know
like
labels,
you
say
alright,
I'm
touching
my
clothes
with
you
and
the
other
one
is
such
as
much
press
widget
and
a
the
two
of
the
same
label
or
in
the
same
release
plan
then,
and
out
some
danger,
bada
versus
or
something
like
that.
But
I
mean
your
hand
that
kind
of
relies
on
our
label
hygiene,
which
can
be
not
the
best
at
some
times.
So
then
I
would
say
an
issue
to
discuss
this
further
would
be
the
right
right
way
to
go.
C
Don't
you
know
came
from
a
different
group
is
not
and
their
engineers
are
not
going
to
prioritize
and
their
design
is
not
designers,
also
not
going
to
prioritize
that.
So
I
would
like
to
share
the
monkey
you've.
This
problem
also
to
other
people,
because
I
know
that
us
as
designers.
We
cannot
solve
everything
because
it's
it
involves
coding.
It
involves
engineering.
D
But
how
people
know
when
it's
I
mean
environment
variables,
it's
very
clear,
but
there's
gonna
be
other
areas
where
it's
like
less
clear
like
that
cross
ownership.
So
that's
kind
of
like
one
of
the
areas
where
I
always
have
struggling
is
like.
Is
this
thing
that
I'm
gonna
be
touching
having
an
impact
on
someone
else,
and
it's
gonna,
because
I'm
super
I
will
love
to
have
the
label
something
it's
this
cross
stage
like
just
having
the
group
label
of
all
the
groups
that
affect
that
that
that
by
itself
should
be
enough.
C
It's
right
because
so
this
page
slash
features
where
it
has
like
not
only
screenshots
but
I
can
search
for
emerging
past
geo
pages.
Whatever
and
I
know
that
it's
not
the
ideal
place
but
I
think
in
general,
there's
no
like
granular,
there's,
not
a
Glenn
granular
way
to
find
who
owns
what
and
that's
one
of
the
big
problems.
I
know
that,
for
example,
I
don't
know,
Andy
works
is
secure
and
then
he
works
on
dashboards
and
he
works
on
some
analytics
things.
B
How
can
we
clearly
identify,
and
do
we
do
that,
often
what
a
design
your
arms
are
you
meaning
are
you
referring
to
the
wall,
because
it's
kind
of
like
hard
well,
for
example,
for
feature
flags.
We
could
say
like
Mike
right
for
like
yeah
I
know.
If
anybody
has
any
idea
like
how
could
be
better,
how
could
we
define
that?
Is
it?
Is
it
a
rule
of
thumb
for
us
you
can
keep
up.
Do
we
have
a
designer
responsible
for
a
particular
feature
direction
or
something
like
that.
C
C
B
C
E
C
And
then
you
have
the
name
of
the
designer
you
know
from
that
specific
group
and
you
have
like
they
can't
erase
under
that
specific
group.
But
then
you
don't
know
that
if
their
fault
reports
such
as
merger
quest
pages,
you
know
it's
bad
for
those
analytics
dashboards
has
settings,
that's
it
I
think
from
a
design
point
of
view.
We
don't
have
this.
This
workflow
and
I
try
to
build
this
for
release
with
my
management
and
in
progressive
delivery
where
we
went
through
all
the
features
and
word
overlap,
but
it
was
a
mural,
so
yeah
it's.
C
B
B
C
From
a
Google
sheet-
and
then
you
know
with
across
everything,
I,
don't
think
it
changes
that
much
I
mean
for
sure.
I
can
only
speak
for
myself,
but
when
I'm
working
some
features
now
definitely
going
to
be
touching
more
in
analytics
and
analytics
it's
not
per
se.
You
know
the
core
of
release
management,
but
I
know
that
there's
some
overlapping
work
with
secure
compliance
etc.
But
some
of
the
things
we
learn
on
the
fly,
so
it's
not
definitely
not
a
static
document.
It's
not
just
a
handle
page.
C
B
But
that's
a
really
good
point:
I
don't
know.
Maybe
we
could
help
well
start
with
a
boring
solutions
right.
Maybe
you
could
like
make
a
table
and
just
like
ask
everybody
to
fill
in
the
things
for
themselves.
Well,
maybe
it
could
potentially
be
a
handbook
page
right
now,
because
we
can
like
be
maintaining
all
together,
because
I
can
imagine
that
it
probably
would
be
often
visited
by
product
designers
who
are
trying
to
tackle
certain
thing
and
then
yes,
who's.
We
bump
into
that.
We
can
update
information.
B
E
B
C
Wise
yeah,
we
just
start
with
ourselves,
and
this
you
know,
find
the
approach.
For
example,
we
know
what
our
users
clothes
are.
We
know
like
the
commonality,
so
environments
deployments,
whatever
we
can
try
to
those
out
and
then
with
that
ready,
bring
two
other
teens
and
say:
hey
help
me
figure
about
how
those
things
connect.
That's
rather
than
having
30
designer
there's
trying
to
feel
me
dock
or
whatever
I
think
for
us
would
be
much
faster.
She
just
do
it.
D
D
Think
it's
it's
basically
an
effort
of
people
to
go
on,
say,
like
I,
don't
know:
what's
the
document
right,
it
could
be
a
table
it
to
be
what
everybody
needs
more
like
a
knife.
First
people
say
like
hey:
I
I
had
no
knowledge
that
I
own
this
page
right
on
this
feature
and
if
you
ever
have
to
work
with
these
work
now
that
I
own
I
have
tested
interest
in
this
particular
future.
So
if
so
on,
I
do
not
work
on
that.
Come
on
talk
for
me,
that's
more
or
less.
D
D
Think
them
are
widget
initiative
avoid
having
that
think
up
is
like
a
micro
version
of
these.
You
know,
I
think
we
I
don't
think
it
scales.
Well,
because
that
means
that
we
will
have.
We
will
need
to
have
one
one
of
those
channels
for
environment
variables,
one
for
feature
flags,
one
for
blah
blah
blah.
Then
we
will
have
like
a
million
1
million
channels.
It
doesn't
scale
right,
I'm,
just
trying
to
put
these
questions.
Here's
just
just
to
make
sense
of
the
size
of
the
problem.
D
It's
not
that
easy
to
solve,
like
it's
easy
to
solve
for
asked
here
in
this
section,
it's
very
hard
to
scale.
You
know
so
I
think
we
should
be
a
little
bit
more
creative
on
how
we're
gonna
fix
this,
because
it's
a
problem,
I
I,
experienced
this
at
least
twice
a
week.
You
know
I,
don't
know
I'm
gonna
work
on
something
I,
don't
know
who
should
I
talk
to
or
like
yeah
we're
off?
You
know,
nah
I
know
that
I'm
giving
more
problems
and
not
solutions.
Well,.
C
For
myself,
like
when
I
worked
in
the
release
stage
right
before
we
broke
it
down
to
progress
delivery,
you
release
management
I
had
such
a
hard
time
trying
to
like
figuring
out
where
the
user
flows.
What
are
the
things
that
I
own
right?
So
sometimes
it's
even
difficult
to
have
these
overview,
and
then
it's
something
that
I'm
working
on
touching
someone
else's
domain.
That's
that's,
definitely
something
that
I
really
miss
having,
since
we're
only
talking
about
problems.
This
is
something
that
I
miss
in
Italy.
C
We
have
here,
for
example,
category
and
vision
and
maturity,
pages
that
talk
about
the
product
and
talk
about
the
marketing,
but
we
don't
have
anything
to
talk
about
user
flows
in
release
management.
For
example,
we
say
that
we
are
not
working
in
such
we're,
not
building
workflows
for
release
management,
but
I
still
need
to
know
what
the
user
phones
are
and
I
cannot
find
this
anywhere
in
Italy
and
I
would
for
myself.
I
would
love
to
have
that
so
at
least
I
know
what
do
I
own.
You
know
and
yeah.
E
And
that's
a
good
point:
Hana
when
I
was
talking
to
Oh
Nadia,
the
designer
Nadia
she
mentioned
doing
the
category
maternity
scorecard
by
they
couldn't
actually
do
the
first
jobs
to
be
done
that
they
wanted
to
because
it
was
using
something
that
somebody
else
owned
and
it
was
broken.
So
she
had
no
responsibility
like
she
couldn't
fix
it
even
for
to
do
that
scorecard.
So
this
is
a
bigger
problem
than
you
know,
just
us
too.
E
C
C
B
Well,
hey,
but
I
think
it's
a
definitely
makes
sense
here
to
raise
this
point
and
involve
more
people
to
into
the
discussion.
Maybe
somebody
has
an
idea,
or
maybe
somebody
already
tried
doing
something
we
just
have
to
make
it
more
known
and
start
from
there.
Yeah
I
think
that
could
that
could
be
a
good
point.
B
I
can
go
ahead
and
create
an
issue
in
just
at
the
UX
department
and
and
ask
if
anybody
was
coming
across
that
there's
similar
issues
and
also
I,
don't
know
like
I
feel
like
it
would
be.
Yeah
I
like
the
idea
of
starting
small
but
I
yeah
I,
don't
see
a
reason.
Why
not
just
go
on
and
make
matrix
just
like.
We
have
dris
for
everything.
Indeed,
love
who
can
maybe
try
creating
a
handbook
page,
but
we
could
define
those
type
of
things.
B
Of
course,
I
think
the
curious
what
you,
what
you
guys
think,
obviously
have
a
bit
more
experience
there,
but
I
almost
feel
like
you
know
why
to
start
in
our
own
stage,
if
it's
fields,
for
example,
a
lot
of
things
that
one
is
talking
about
are
not
not
within
our
stage
groups.
It's
there
so
I'm,
not
sure
how
helpful
would
that
be
field
start
smaller?
Why
not
would
like
just
try
it
I
think.
C
It
would
be
nice
to
have
this.
You
know
secondary
part
of
school
like
we
start
small,
we
start
with
identifying
what
we
know,
because
yeah
I
can
go
and
ask
everyone
about
what's
going
on
their
stage
groups,
but
I
think
it's
useful
if
we
can
already
come
with
some
sort
of
information
and
then
maybe
as
a
pilot
know,
we
do
see
ICD
we're
close
and
then
we
start
to
see
ICD,
but
most
actually
sorry,
everyone,
ops,
ops,
plus
something
pops
bus
whatever,
and
then
we
start
building
out
with
with
the
counterparts.
C
B
Sounds
and
yeah
I
trust
you
here
of
course
you're
more
experienced.
So
you
are
for
sure
makes
sounds
and
question.
Maybe
a
little
clarification.
We
are
talking
about
user
flows
like
could
you
help
me
to
understand
a
bit
better
like?
What
do
we
mean?
Because
for
me
it's
like
the
user
experience,
user
flows,
it's
about
the
user.
Is
it
our
returning
on
the
same
page
or.
C
Yeah
to
me,
sir,
for
example,
as
a
release
manager
right,
what
is
the
user
flow
or
creating
a
release
with
Atlanta
or
analyzing
the
status
or
the
health
of
a
release
with
gitlab?
So
what
are
the
you
know,
the
places
that
you
need
to
go
and
the
facts
that
you
need
to
to
follow,
so
you
definitely
need
to
go
to
settings,
definitely
to
go
to
release
these
tags
and
dashboards
and
environments,
so
I
mean
not
the
workflows
as
in
step.
One
two
three
but
yeah
that
makes
sense.
I
know
that
either
flaws
and
workflows
are.
B
That
makes
sense
and
I'm
more
along
trying
to
see
how
that
connects
with
the
theorize
that
we
have
been
discussing.
So
it's
like,
maybe
it's
basically
when
you
are
working
on
there,
let's
say
could
be
it
creates
release
flow.
That
user
flow
would
help
you
to
understand
which
other
sections
you
will
cross
in
your
work,
you
mean.
B
So,
okay
and
I
mentioned
that
we,
you
know
we
would
take
advantage
of
having
user
flows
for
for
when
we
are
working
with
the
features
etc.
And
what
I
am
saying.
In
the
past,
we've
been
creating
user
flows
as
a
part
of
like
working
on
the
feature
you
know
so,
for
the
our
biggest
most
important
features,
we
will
be
having
the
user
flows,
because
it
helps
us
to
see
exactly
like
how
the
user
interaction
is
happening
which
part
of
the
product
he
will.
B
A
Yeah
we
I
mean
some
of
the
issues
I
know
in
the
past
personally,
I've
used
them
just
by
training
like
flowcharts,
and
those
kind
of
things
forgot,
the
name
of
the
of
the
you
can
do
it
with
like
the
horizontal
stripe.
You
can,
you
know,
say
like
alright.
This
is
what
the
user
will
mostly
do
and
then
the
alternative
options
you
can
connect
them.
I
forgot
the
name
currently
but
use
them
in
the
past
and
it's
worthwhile
to
put
them.
But
we
don't
have
like
a
specific
database
that
we
can
refer
to.
A
C
B
A
Yeah
thing:
the
thing:
that's
always
with
these
kind
of
things
I
find
is,
you
know,
is
the
overhead
worth.
You
know
like
the
valley
that
we
can
get
out
of
it,
or
is
it
just
another
thing
we
have
to
maintain?
If
it's
not
perfect,
if
it
is
them,
you
know
what
is
a
point
in
it.
I
think
the
more
cross-functional
and
more
people
activate
and
make
use
of
it.
Then
yes,
then,
can
show
enough
value
for
us
to
validate
the
effort
you
need
to
put
into
it
to
maintain.
C
Let's
go
definitely
a
requirement,
for
example,
you
know
needs
to
be
automated.
We
have
some
sort
of
information
right
into
him.
We
have
those
includes
where
you
know
they're
like
you,
can
get
the
list
of
the
DRI,
the
group,
the
whatever
feature,
what,
if
we
can
populate
the
data
from
existing
components
of
the
handbook
into
something
that
gets
automatically
you
know,
I
mean.
A
On
the
other
hand,
I
like
to
take
a
it
would
be
kind
of
cool
to
have
like
some
kind
of
like
it.
When
you
go
into
a
theme
park
and
I'm
gonna
go
on
a
tangent
here.
If
you
go
into
a
theme
park,
you
have
this
map,
you
get
and
always
look
so
colorful
and
with
all
the
happy
little
drawings
of
all
right.
There's
that
attraction.
A
There's
that
attraction
of
what,
if
you
had
something
like
that
off
the
giblet
product
that
you
could
see
all
right,
but
now
I
use,
you
can
leave
it
this
and
follow
this
route,
and
then
they
will
arrive
at
all
right.
It
can
configure
their
environment
scopes
and
then
all,
but
if
they
take
this
on
a
road
day,
I
know
they
do
this
other
thing
and
create
a
pipeline.
Go
for
your
age,
I'm,
not
something
like
that!.
D
One
big
thing
about
this
is
that
many
of
these
workflows
can
be
achieved
from
the
CLI
right,
like
many
people
are
doing
that
right
by
many
import,
creating
issues
from
the
CLI
and
then
for
creating
I
mean
if
you,
if
you
can
create
a
merge
request
from
neat
lab
itself,
go
to
get
love
the
the
column
and
create
the
merge
request
and
everything,
but
no
one's
gonna.
Do
it
like
that
way?
You
know.
D
So
if
you
document
under
the
workflow,
you
show
just
for
the
sake
of
documenting
it,
but
like
the
actual
for
workflow
that
everyone
uses
it's
been
in
the
terminal,
creating
the
branch
creating
the
absolute,
absolutely
upstream
branch
and
then
pushing
the
branch
and
that
creates
DMR
for
you
right.
So
that's
the
one
that,
like
I,
feel
eighty
or
ninety
percent
of
the
people
are
using
right.
D
So
it's
kind
of
easy
to
just
assume
that
one
workflow
is
the
core
work,
because
it's
the
one
that
it's
in
the
way,
but
it's
not
you
know
so
I,
don't
know.
I
I,
think
that's
another
area
to
consider.
There's
many.
Many
of
these
things
happen
from
git
itself
and
people
just
like
winter
work
under
environment
under
code
editors
under
terminal
and
then
get
lapiz
just
like
that
and
visualizer
of
total
workflows.
You
know,
but
many
of
these
workflows
are
still
happening
inside
their
their
computer.
So
how
do
we?
B
Yeah
yeah.
Well,
this
is
a
good
thought
and
I
think
we
could
start
by
the
first
topic
we
tackled
about
the
dris
and
and
see
if
that
will
have
any
influence
on
the
user
flows
and
yeah,
and
maybe
we
should
also
like
yeah
what
be
curious
to
reach
out
what
other
teams
are
doing
right
about
the
user
flows
and
how,
to
others,
attract
that
but
yeah.
Maybe
we
can
bring
this
up
in
the
u.s.
quickly,
for
example
as
well,
because
I
feel,
like
I'm,
missing
a
bit
of
a
history
here.