►
From YouTube: UX Showcase - Cross-stage Collaboration at GitLab
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
Hey
everyone,
I'm
nadia
the
product
designer
at
verify,
pipeline
authoring
and
today,
together
with
ian
the
senior
product
designer
package,
I'll,
be
talking
a
little
bit
about
cross-stage
collaboration
at
gift,
lab
big
topic
so
yeah.
This
is
how
I
kind
of
often
feel
when
I
try
to
collaborate
not
only
with
other
stages,
but
sometimes
even
within
my
stage,
trying
to
figure
out
what
the
other
groups
or
stages
are
up
to.
It's
not
easy,
because
their
product
is
very
complex.
A
So
I
was
wondering:
am
I
the
only
one
struggling
so
much
just
struggling
to
prioritize
cross-stage
collaboration
and
how
do
other
product
designers
feel
like?
Where
do
they
place
themselves
or
do
they
feel
like
they're?
Collaborating
enough?
Do
they
feel
like
they
know
enough
about
the
product
surrounding
their
immediate
area
of
focus?
A
So
I
decided
to
run
a
survey
to
learn
a
little
bit
more
about
it,
and
it
was
very
kind
of
low
effort
thing.
I
just
wanted
to
get
a
quick
kind
of
pulse
reading
to
see
how
much
actually
we're
struggling
and
what
are
the
main
challenges
that
we're
experiencing
and
maybe
actually
everyone
else
is
doing
great.
Maybe
it's
just
me
so
that
was
also
one
of
the
one
of
the
goals
to
determine
that.
A
A
So
here
you
see
that
most
product
designers
feel
like
they
are
up
to
date
on
the
majority
of
the
ux
work
that
the
product
designers
are
doing
within
their
stage,
so
either
they
agree
or
they
strongly
agree
or
they're
kind
of
on
the
fence.
So
maybe
it's
always
a
good
idea
to
collaborate
more
with
the
other
groups,
but
I
think
we're
doing
pretty
well
here,
where
things
start
to
get
more
interesting
is
when
we
start
venturing
outside
of
our
groups
and
outside
of
our
stages,
and
we
go
cross
stage.
A
So
when
it
comes
to
learning
and
being
knowledgeable
about
the
stages
that
surround
your
immediate
area
of
focus,
most
product
designers
actually
either
disagreed
or
were
unsure
about
it.
So
you
see
that
only
20
of
participants
said
that
they
agreed.
They
are
well
informed
about
the
efforts
outside
of
their
stage.
A
It's
because
our
product
or
different
parts
of
our
product
are
all
interconnected,
and
sometimes
you
don't
know
that
some
feature
that
is
being
implemented
in
the
other
stage,
how
it
might
impact
the
work
that
you're
doing
your
features.
How
might
it
impact
the
workflows
that
you're
working
on,
or
perhaps
maybe
there
are
some
opportunities
there
for
you
and
you
just
don't
know
about
them?
Maybe
there
are
opportunities
to
collaborate
and
really
find
some
synergy
and
provide
more
value
to
github
users
by
may
better,
connecting
the
features
from
two
different
stages.
A
So
it
seems
like
we're
having
a
bit
of
a
problem
with
that.
So
you
see
that
20
percent
of
the
participants
said
that
they
strongly
disagree.
That
they're
really
not
informed
at
all
about
the
opportunities
and
challenges
that
new
features
outside
of
their
stage
may
present
to
their
stage,
features
20
more
percent
disagree
and
everyone
else
is
just
unsure,
so
that
just
shows
that
we
really
struggle
with
press
stage
collaboration
and
that's
how
I
feel
as
well.
So
it
was
really
comforting
to
see
that
I'm
not
alone.
A
To
be
honest,
we
find
it
quite
difficult
to
prioritize
cross-stitch
efforts
as
well.
So
most
participants
agreed
30
disagreed.
So
it's
great,
it
seems
like
not
everyone
struggles
to
the
same
extent,
which
means
we
can
all
learn
from
each
other.
So
those
who
who
feel
like
they
they're
having
a
great
time,
prioritizing
cross-stitch
efforts.
I
really
hope
that
you
share
your
stories
because
it'd
be
really
great
to
learn
from
you.
A
I
was
wondering
how
well
are
we
familiar
with
the
jobs
to
be
done,
that
other
stages
are
working
on?
It
seems
like
we're
actually
more
familiar
with
jobs
to
be
done
than
with
the
ongoing
ux
work,
which
kind
of
makes
sense,
because
we
don't
iterate
on
the
jobs
to
be
done
as
frequently.
So
if
you,
if
you
read
the
other
stages
direction
pages-
and
there
are
jobs
to
be
done
pages-
it's
quite
easy
to
find
information.
A
A
A
So
really?
Most
of
us
don't
really
know
much
about
the
product
direction
of
other
stages,
which
makes
sense
it
can
be
very
difficult
to
stay
on
top
of
so
much
information,
but
I
I
just
feel
like
for
us
to
create
a
really
well
connected,
really
well
integrated
product,
it's
important
for
us
to
understand
the
product
strategy
that
goes
beyond
our
immediate
area
of
focus.
So
obviously
I
have
no
answers
to
that.
A
A
So
we're
not
even
talking
about
seeking
out
that
information,
even
just
consuming
what
is
being
shared
in
slack
and
issues
is
a
challenge
also,
there's
no
frameworks
or
tools
to
quickly
understand
the
context
of
a
stage
group
so
because
the
product
is
so
complex.
It
really
takes
a
very
long
time
for
us
to
gather
enough
knowledge
about
the
area
to
start
to
understand
how
it
all
works.
A
So
again,
it
also
kind
of
ties
back
to
the
lack
of
time
yeah,
so
there's
no
process
sometimes
for
different
stages
to
regularly
communicate
between
each
other.
I
guess
you'll
see
later
on
when
we
talk
about
the
things
that
we're
doing
well,
some
some
teams
are
doing
that
well
and
they
have
recurring
meetings
and
things
like
that.
But
this
can
also
be
a
challenge
and
cross-stage.
A
Communication
collaboration
is
just
difficult
to
prioritize
because
we're
very
busy
with
stage
work
and
cross-stitch
collaboration
is
just
not
number
one
priority
compared
to
stage
work,
which
makes
sense
so
why?
Why
are
we
struggling
with
those
things?
Why
are
we
all
experiencing
those
challenges
in
in
my
latest
meeting
with
christy
during
our
skip
level
meeting,
I
asked
the
question:
why
do
we
struggle
so
much
with
cross-stage
collaboration?
A
A
It
was
intentional,
so
this
culture
of
having
separate
autonomous
teams
focusing
on
their
little
area,
it
was
an
intentional
choice
to
help
us
move
faster,
so
not,
but
now
that
we're
not
a
brand
new
product,
we
need
to
calibrate
more
because
we're
starting
to
focus
on
polishing
our
product
and
making
it
more
usable.
And
you
see
now
we
have
this
new
focus
on
ui
polish
and
things
like
that
so
you're,
starting
to
see
that
we're
starting
to
kind
of
shift
gears
and
collaborate
more.
A
So
it's
great
to
know
that
our
leadership
knows
about
it.
So
we
know
we
need
to
collaborate
more
and
seems
like
there
are
some
things
that
we're
doing
right.
So
in
the
survey
some
of
the
participants
mentioned
some
of
the
things
that
are
helping
them
with
cross-stage
collaboration,
so
things
like
scheduling,
recurring
syncs
with
other
stage
groups,
learning
about
their
jobs
to
be
done,
aligning
those
jobs
to
be
done.
A
Take
time
to
provide
feedback
in
ux
working
channel.
So
that's
also
a
great
place
to
learn
more
about
what
other
product
designers
and
other
stages
are
focusing
on.
Just
getting
to
know
other
product
designers
and
product
managers
and
making
friends
with
them
and
scheduling
coffee
chats,
so
it
doesn't
have
to
be
something
very
big
and
serious
right.
Sometimes
you
can
just
have
a
30
minute
meeting
just
to
learn.
Okay,
what's
on
your
plate,
what
are
the
main
challenges?
A
You're
solving
right
now
and
you
never
know
when
it
will
spark
some
idea
for
collaboration,
or
you
will
see
some
area
where
there's
an
opportunity
for
you
to
create
something
together
and
also
attending
think
big
sessions.
So
some
of
the
teams
run
think
big
sessions
where
they
collaborate
across
stages,
collaborate
on
bigger
design,
efforts,
and
things
like
that.
So
these
are
these
were
the
only
things
mentioned,
but
I'm
sure
there
are
many
other
things
that
we're
also
doing
so.
A
If
you
have
any
tips,
if
you
have
any,
you
have
some
experiences
good
experiences
of
cross-stitch
collaboration.
Please
share
so
yeah.
We
don't
always
collaborate
enough,
but
when
we
do
we
do
it
really
well-
and
I
have
a
good
example
of
cross-stage
collaboration
in
ops
section.
So
it
happened
quite
recently
that
we
started
talking
about
auto
devops
again.
So
when
I
first
joined
the
pipeline
authoring
team
and
I
started
learning
about
ci
cd,
it
was
one
of
the
first
thing.
A
I
noticed
that
for
some
reason,
auto
devops
and
ci
cd,
even
though
they
seem
to
solve
a
very
similar
problem,
so
they
create
these
automated
workflows.
For
you
other
devops,
it's
like
an
automated
ci
cd
that
turns
on
a
bunch
of
features
by
default,
at
least
that's
kind
of
the
vision
that
everything
your
whole
devops
process
just
works
outside
the
box.
A
A
And
how
can
we
leverage
other
devops
in
csct,
onboarding
and
I've
been
trying
to
gather
the
product
managers
and
the
engineers
and
the
product
designers
to
discuss
this?
I
was
very
lucky
that
sid
also
took
interest
in
other
devops
right.
At
the
same
time,
so
I
created
an
issue
kind
of
communicating
my
vision
for
what
other
devops
could
do
for
gitlab,
and
you
can
go
to
the
issue
if
you
want
to
check
it
out.
A
I
made
a
weird
little
illustration
there
to
better
communicate
my
idea
and
the
leadership
jumped
on
it,
because
it
was
just
good
timing
and
we
started
having
async
discussions
in
the
issue
about
how
to
move
things
forward.
What
is
everyone's
vision
for
other
devops?
We
had
these
long
threads
of
product
managers
sharing
their
vision
and
it
was
all
great,
but
we
didn't
really
come
to
any
conclusions
like
the
discussion
kind
of
stalled
and
it
wasn't
clear
how
to
move
it
forward.
A
So
ian
because
he's
been
running,
I
think
big
sessions
for
ops
for
a
while
and
marie
also
had
this
idea.
We
decided
that
I
think
big
will
really
help
us
get
everyone
in
one
room.
While
the
excitement
is
still
high,
so
we
can
actually
make
some
decisions
and
hopefully
come
to
some
conclusion
and
determine
some
next
steps.
So
obviously,
us
product
designers,
we
were
super
eager
to
just
like
get
down
to
work,
start
wireframing
new
workflows,
and
you
know
we
didn't
get
to
quite
get
there
because
turned
out.
A
We
really
need
to
because
it's
a
really
big
thing,
like
redefining
vision
for
a
whole
feature
category,
so
the
product
had
to
do
lots
of
work.
But
ian
will
tell
you
more
about
that
when
he
talks
about
the
think
big
session
and
what
they
are
and
his
experience
with
those
and
how
it
worked
for
the
auto
devops
discussion.
B
Perfect,
I
am
so
excited
to
share
the
ops
section,
crosstags
think
big.
I've
certainly
shared
the
idea
that
package
uses
think
big
to
talk
about
our
large
initiatives
and
review
designs
and
the
power
of
having
that
kind
of
vision.
Level.
Communication
in
sync
with
your
team
and
how
it
actually
leads
to
viewers
thinks
needed.
The
op
section
was
our
attempt.
Sorry,
the
off
section,
cross
stage
thing
big
was
our
attempt
to
take
that
and
escalate
it
up
a
level.
B
So
we
have
created
some
really
thriving
conversations
that
are
specifically
tailored
for
exactly
what
nadi
had
just
described.
We
had
really
long
threads
with
lots
of
really
good
ideas,
but
somehow
we
just
couldn't
make
it
like
the
decision
to
move
us
forward
and
everyone
was
feeling
stuck
once
we
hit
that
point.
We
brought
everyone
together
and
when
we
they
everyone
we're
talking
about
mostly
the
product
strategy,
oriented
side
of
things.
B
So
this
is
kenny
as
a
product
leadership,
as
well
as
product
managers,
product
designers,
laurie
joined
with
research
and
was
able
to
give
some
insights
even
design
leadership.
Justin
jumped
in
there
at
some
point
to
kind
of
share
some
ideas
around
how
to
do
this.
I
really
encourage
you
to
watch
this
video.
B
I
know
what's
on
the
longer
side,
but
this
conversation
was
so
exciting.
You
could
see
all
the
different
product
managers
see
the
value
of
the
auto
devops.
You
could
hear
you
know
cole
talk
about
why
it
was
so
valuable
to
get
auto
devops
going
for
secure
and
how
it
enabled
these
things
or
how
we
could
use
ci
and
auto
devops
to
kick-start
a
lot
of
these
features
that
users
were
struggling
to
see
and
find.
We
found
all
of
this
really
great
information
and
we
had
an
incredible
conversation.
B
I
want
to
move
to
the
next
level
and
kind
of
talk
about
where
that
conversation
led.
So
this
was
great
because
it
validated
something
that
bringing
everyone
together
for
a
little
bit
of
sing
time
can
unstick
a
problem.
The
first
thing
that
happened
out
of
the
conversation
penny
committed
to
reevaluating
the
vision
for
auto
devops
in
the
handbook
he
opened
up
an
mr.
B
B
Lost
my
place,
I
apologize,
so
what
was
great
is
that
that
sparked
this
big
conversation
about
everything
that
autodevops
could
do.
How
do
we
improve
other
devops
adoption?
How
do
we
get
more
people
to
use
it?
It's
the
feature
that
I
think
everybody
wants
to
work
really.
Well,
it's
just
not
quite
there
yet,
so
we
were
able
to
come
together
and
talk
about
where
we
all
wanted
it
to
go.
I,
as
the
package
person
want
auto
devops
to
auto
publish
packages
to
the
registry
and
call
it
easy,
that's
something
I
want
that.
B
After
this,
we
had
some
really
thriving
conversations
around
how
design
could
utilize
a
design
pod,
which
I
think
was
justin's
term
as
the
way
that
we
handle
crosstag
collaboration.
We
as
designers
see
very
effectively
and
very
easily
how
the
different
parts
interact.
What
the
experience
is
like
why
it's
so
jarring
to
try
to
move
from
one
to
the
other
or
to
use
a
cross-stage
feature
like
on
a
devops,
so
we're
gonna
use
some
design
pods.
B
Take
a
look
at
that
vision
as
well
as
kind
of
move
some
things
forward,
and
it
was
also
really
great
to
see.
After
this
conversation,
a
real
result
happened
where
otto
devops
was
given
a
defined
owner,
where
I
believe
the
configure
team
is
now
the
dri
for
autodesk
and
is
kind
of
taking
lead
with
maria
and
victor
too.
This
is
how
we're
going
to
do
it,
and
this
is
your
part
nadia,
that's
going
to
be
included
in
this.
Is
your
heart,
vitica
and
ian.
B
This
is
the
packaging
you
need
to
do
and
they're
taking
ownership,
and
this
idea
that
everyone
talked
about
and
kind
of
struggled
to
get
moving
is
now
powering
forward
with
a
lot
of
momentum.
So
that's
kind
of
the
value
of
what
that
one
50-minute
sink,
really
ended
up
doing
with
a
feature.
I
think
we
all
love.
A
Thank
you.
I
was
just
thanking
you
for
such
a
great
intro
to
think
big
session.
So,
if
you
haven't
tried,
think
big
sessions
with
your
team
give
it
a
shot,
maybe
it
will
help
you
collaborate
closer
with
all
of
your
counterparts
and
yeah
we're
stronger
together
thanks
to
vitica.
We
now
have
this
amazing
illustration
to
end
our
presentations
with,
if
you
have
any
any
stories
of
how
of
like
collaboration
done
well
across
stages.
Please
share,
and
if
you
have
any
questions
should
thank
you.
C
D
D
Yeah,
I
feel
the
same
pain
and
and
something
I've
been
doing,
is
scheduling
a
specific
time
every
month
to
just
consume
content
from
other
groups,
and
that
has
helped,
but
unless
you're
in
the
weeds
going
through
the
issues
and
their
boards,
and
all
of
that
I
only
know
what
they're
planning
to
do
like
right
now
or
what
they're
doing
now,
and
not
what
they're
planning
to
do
ahead.
Also,
because
I
feel,
like
most
groups,
don't
plan
more
than
one
milestone
ahead,
and
that
has
a
lot
of
other
issues.
D
A
A
But
I've
been
thinking
that
it
seems
like
we
don't
prioritize
cross-stage
collaboration,
because
it's
not
it
hasn't
been
made
a
priority.
So
even
though
we
all
know
it's
important
but,
as
you
said,
our
main
responsibilities,
don't
focus
on
cross-stage
collaboration
and
make
sense,
but
there
could
be
some
forcing
function
of
sort
from
adjusting
somehow
our
responsibilities,
making
cross-stage
communication
part
of
our
responsibilities
or
maybe
having
recurring
meetings
and
things
like
that
and
all
of
the
counterparts
have
to
be
that
you're
working
with
like
your
product
manager
and
the
engineering
teams.
E
I
think
the
ux
showcases
is
a
good
opportunity
to
drive
cross-stage
collaboration-
that's
at
least
one
of
the
goals
of
these
calls.
So
I
would
certainly
keep
that
in
mind
as
a
opportunity
to
share
what
you're
working
on
and
learn
from
others,
as
well
as
the
design
pairs
like
people.
We
match
people
up
so
that
they
can
get
more
information
from
areas
that
they
they
aren't
directly
working
in.