►
From YouTube: Collaborate with kindness | GitLab Design Talks
Description
Nadia and Nick discuss what collaboration feels like at GitLab.
https://about.gitlab.com/handbook/values/#collaboration
https://gitlab.com/groups/gitlab-org/-/epics/4797
A
B
B
Well,
do
I
need
to
provide
a
bit
more
personal
details?
Maybe
well
currently,
I'm
in
beautiful,
tenerife,
spain
escaping
the
lockdowns
enjoying
some
good
weather
generally.
I'm
quite
dramatic
travel
a
lot
during
these
times
feeling
very
lucky
to
get
to
travel
a
little
bit
and
yeah
very
excited
to
talk
a
little
bit
more
about
collaboration
today,
because
lately,
there's
been
a
lot
of
shifts
in
how
I
collaborate
with
product
managers
in
engineering.
B
A
Nice,
I'm
really
excited
to
hear
about
that.
Okay,
so
I'll
kick
off
with
the
first
question
and
it's
it's
just
sort
of
more
broadly
around
around
joining
gitlab.
But
sort
of
tell
me
about
your
experience
of
the
the
culture
of
collaboration
within
within
git
lab
and
and
how
is
it
different
from
the
previous
jobs
or
roles
that
you've
been
in.
B
B
If
we're
talking
about
collaboration
with
the
engineering
teams,
for
example,
really
there
was
very
little
collaboration.
It
was
very
much
you
know,
close
collaboration
with
the
project
manager,
but
once
that
is
done,
the
designs
are
kind
of
just
thrown
over
the
fence
and
whatever
happens
afterwards.
You
know
it's
good.
If
I
get
to
see
my
designs
actually
implemented,
and
usually
it
comes
with
a
whole
set
of
surprises,
so
I
can
say
that
especially
collaborating
closely
with
the
engineering
team.
B
The
domain
expert
knowledge-
and
you
know
all
of
the
other
things
that
we
do-
the
user,
research
and
everything,
but
often
the
engineers
are
the
people
that
we
can
go
to
immediately
right
away
and
just
ask
a
question
about
how
things
work
so
yeah.
That's
that's
been
definitely
the
biggest
the
biggest
kind
of
learning
point
for
me.
I
realized
that
kind
of
my
success
as
a
designer
really
depends
on
my
collaboration
with
the
engineering
team
and
product
management
as
well.
A
B
Yeah
sure
so
generally,
we
have
a
separate
product
teams
that
focus
on
different
parts
of
gitlab,
so
every
product
team
can
be
focused,
let's
say
on
a
gitlab
ci
solution
or
continuous
delivery
or
monitoring
tools,
so
that
would
include,
for
example,
metrics
dashboards
incident
management.
Things
like
that,
so
every
separate
product
team
will
focus
on
their
own
area
and
a
product
team
has
one
or
more
designers.
It
depends
on
the
size
of
the
product
team.
Maybe
I'm
not
sure
what
the
ratio
is
exactly,
but
I
don't
know.
B
B
And
then
you
rely
on
the
engineering
team
to
help
you
understand
what
is
feasible
and
what
can
be
built
so
that
informs
your
designs
and
the
collaboration
really.
You
know
the
way
we
collaborate.
It
really
varies
from
team
to
team,
but
the
setup
is
pretty
much
the
same
and
all
designers
have
to
collaborate
with
both
pm
and
engineer
engineering
to
varying
degrees.
A
Cool
so
self-autonomous
teams
of
one
designer
to
1pm,
to
6,
to
10
engineers,
all
working
in
a
fairly
sort
of
yeah
autonomous
way
and
and
loosely
coordinated
with
other
product
and
vr
or
feature
teams
who
are
working
as
well,
and
I
think
we're
really
empowered
to
to
sort
of
make
decisions
for
ourselves
as
teams
and
that
that
really
helps
to
like
achieve
results
and
and
and
optimize
towards
throughput
and
speed
of
delivery
and
reduced
cycle
time.
Overall.
B
Yeah
sure,
well,
I
would
say
that
collaboration
affects
all
of
the
other
values
right.
We
have
to
collaborate
to
make
sure
that
we
are
all
aligned
on
those
values
and
it's
I
I
feel
like
it's
my
responsibility
to
make
sure
that
I'm
aligned
to
those
values,
but
also
it's
my
responsibility
to
notice
if,
as
a
team,
sometimes
we're
not
aligned
to
some
of
our
values
and
to
make
suggestions-
and
you
know
it's
like
it's-
a
continuous
we're
all
continuously
growing.
B
B
As
a
product
designer
on
in
my
day
to
day
mostly,
I
collaborate
with
fellow
ux
designers
for
my
team,
my
product
manager
and
the
engineers
and
when
it
comes
to
collaborating
with
fellow
ux
designers,
product
designers,
the
ux
team
at
large,
then
we're
kind
of
touching
upon
transparency,
values,
for
example.
So
at
this
point,
we're
what
like
60
people,
large
ux
team,
something
like
that
right,
we've
grown
quite
quite
a
bit
and
at
this
point
it's
become
very
important
that
we
all
share
the
work
that
we're
doing
transparently
across
the
team.
B
So
there's
a
lot
of
deliverables
that
are
being
produced
and
new
ux
research,
insights
and
you
know
just
a
lot
of
information
to
consume.
So
it's
very
important
that
we
efficiently
share
the
information
and
foster
collaboration
across
the
team
when
it
comes
to
collaboration
with
the
product
manager
and
the
engineering
team.
B
I
feel
like
it
really
really
strongly
ties
in
with
the
iteration
and
results
values,
so,
in
my
understanding,
iteration
at
least
to
results.
At
least
this
is
how
we
kind
of
look
at
it
at
gitlab
that
really
pushing
pushing
the
team
to
trade
faster
to
test
different
assumptions,
to
conduct
more
experience
and
to
learn
from
our
experiences
quickly.
It
leads
to
better
results
and
also
good
iteration
means
better
efficiently
efficiency,
so
really
it
all
plays
in
together,
so
figuring
out
a
good
way
to
iterate.
B
B
So
how
can
we
maximize
the
value
that
we
deliver
in
the
first
iteration
right?
We
call
it
an
mvc,
the
minimum
viable
change.
So
what
is
the
smallest
kind
of
chunk
of
new
improvements
that
we
can
provide
that
will
provide
value
and
solve
user's
problem
like,
but
also
at
the
same
time,
there's
another
angle
that
the
engineering
team,
the
engineering
managers
look
at
iteration
from
is
how
does
it
make
sense
to
implement
it?
B
So
what
is
the
most
efficient
way
to
implement
it,
because
there
are
so
many
complexities
and
dependencies
in
the
product
and
like
old
parts
of
the
product
that
as
a
product
designer?
I
have
no
idea
about
them,
usually
most
of
the
time.
So
then
it's
important
for
me
to
understand
it
and
then
compare
it
to
kind
of
my
perspective.
B
How
can
we
provide
maximum
value
in
the
first
iteration
then
somewhere
in
between?
Is
that
sweet
spot,
the
where
we
we
have
to
compromise
and
figure
out
what
what
those
the
mvc
and
the
further
iterations
will
look
like
yeah
now
that
I'm
on
a
new
team
again
we're
starting
to
figure
out
some
some
parts
of
it
all
over
again,
but
luckily
I
moved
together
with
my
product
manager,
so
together
we're
working
on
kind
of
bringing
our
work
process
onto
the
new
team.
So,
let's
see
how
that
plays
out.
A
Yeah,
I
think
you,
you
brought
up
like
an
excellent
point
there,
how
you're
working
in
these
multi-disciplinary
teams,
where
the
designers
are
bringing
the
perspective
of
the
user
and
the
desirability
or
usability
or
something
like
this.
The
engineers
are
bringing
sort
of
feasibility
and
the
technical
technical
constraints,
and
then
the
the
product
manager
is
there
to
sort
of
talk
about
the
business
goals
and
the
viability
of
that.
So
everyone
has
their
own
different
piece
of
the
puzzle
and
it's
that
intersection
of
the
different
disciplines
collaborating
together
and
bringing
their
knowledge
of
their
different
domain.
A
A
You
need
to
be
aware
that
there
will
be
some
creative
friction
happening
so
we'll
inherently
as
designers,
communicate
in
a
different
way
from
engineers
and
from
product
managers.
So
this
friction
is
sort
of
what
leads
to
sometimes
a
little
bit
of
confusion
and
sometimes
leads
to
like
a
little
bit
of
disagreement.
But
from
that
friction
actually
comes
a
resolution
which
tends
to
be
greater
than
the
sum
of
its
parts,
so
I
think
collaboration
in
gitlab.
A
We
are
allowing
this
creative
friction
to
occur,
but
the
fact
that
we're
working
asynchronously
has
like
quite
an
interesting
impact
on
that.
So
I'm
wondering
whether
you
can
sort
of
talk
a
little
bit
about
how
working
remotely
and
collaborating
asynchronously
has
has
impacted
your
work
and
how
you
collaborate
with
the
team.
B
Yeah
sure,
well,
one
thing
I
have
to
say
is
that
I
I've
been
working
remotely
for
a
very
long
time
and
I've
never
had
a
proper
full-time,
location-based
job
where
I
had
to
interact
with
with
my
team
face
to
face
every
day.
So
I'm
a
bit
I'm
a
bit.
You
know
my
case
is
a
bit
unique,
maybe
even
though
now
of
course
it's
very
it's
very
widespread,
so
maybe
not
that
unique
anymore,
but
yeah,
of
course,
generally.
B
I
think
the
impact
that
asynchronous
communication
has
is
that
we
put
in
more
effort
into
how
we
communicate
right
when
you're
writing
an
issue
comment.
Usually
most
people
would
re-read
their
comment
and
you
you
have
more
opportunity
to
become
aware
of
any
biases,
or
perhaps
you
might
notice
that
your
response
is
a
bit
too
emotionally
charged
and
you
have
to
like
go
back
and
tone
it
down.
B
It
certainly
happens
to
me
oftentimes
and
I'm
very
grateful
for
being
able
to
communicate,
asynchronously
and
really
put
my
put
my
thoughts
into
the
right
like
form
to
make
sure
that
it's
not
misinterpreted
that
it's
that
it's
you
know
it's
it's
received
as
intended.
However,
still
of
course
miscommunication
happens
and
I
just
think
it's
very
important
that
we
all
really
try
to
empathize
with
the
other
person
like
whoever
you're
talking
to,
and
I
know
we
talk
about
a
lot
and
it's
it's
one
of
our
values.
B
We
have
strong
opinions
about
things,
and
it's
also
happened
to
me
in
the
past,
where
I
took
some
comments
personally
and
it's
happened
to
me
where
I
said
something,
and
I
really
didn't
intend
to
offend
anyone,
but
it
happened
so
it's
normal
and
we
just
have
to
kind
of
talk
through
it
and
you
know
just
like
in
any
relationship.
You
just
have
to
communicate
and
try
to
understand
the
other
person's
side
for
collaboration
with
the
product
manager
and
the
engineering
team,
well
specifically
with
the
product
manager.
B
B
B
B
B
So
it
would
be
good
to
to
learn
more
about
how
engineering
managers
work
and
what
are
their
goals,
because
I
would
say
that
that's
something
that
I
still
need
to
learn
about.
So
if
anyone
has
any
comments
or
any
experiences
to
share
about
how
to
better
collaborate
with
the
engineering
team,
how
to
better
leverage
their
expertise.
B
Please
do.
Let
me
know
at
this
point,
like
my
my
kind
of
conversion
style
with
engineers
is
to
involve
them
in
the
design
process
as
early
as
possible,
because
they
will
still
have.
I
mean
they
have
a
lot
of
leverage
like
to
just
veto
your
designs
and
be
like
hey.
That's
just
not
going
to
work,
and
it's
it's
normal.
B
A
A
Sometimes
someone
provides
some
some
feedback
of
my
work
and,
like
my
immediate
reaction,
is
oh,
how
dare
you
you're
insulting
my
baby?
Oh
god,
but
I
think
the
the
beauty
of
async
is.
It
gives
you
time
to
press
pause,
step
back
diffuse,
the
immediate
first
reactions
and
first
emotions
that
you
get
from
that
feedback,
assume
best
intent
and
then
and
then
use
that
to
sort
of
go,
go
further
and
and
and
improve
the
designs
overall.
A
So
I
think
I
think
async
really
really
supports
that
way
of
working,
and
then
you
also
talked
about
involved
involving
the
pm
and
the
engineers
sort
of
early
and
often
within
the
design
process,
because
that
again
goes
to
the
efficiency
value
of
just
making
sure
that
they're
incorporating
their
perspectives
of.
Is
it
feasible?
A
If
you're
an
engineer,
is
it
viable
if
you're
a
pm
so
yeah?
So
I
think
that
that's
like
a
lot
of
great
great
stuff,
so
I
really
appreciate
what
you
said
there
so
for
me
collaboration.
You
know,
I'm
I'm
still
I'm
doing
these
these
series
of
design
talks,
so
I
I'm
just
trying
to
stay
open
and
and
listen
to
all
the
great
designers
on
our
team
and
also
all
all
the
engineers
and
and
pms
as
well.
Ideally
I'll
speak
too
and
sort
of
learn
for
myself.
A
B
I've
been
on
the
gitlab
for
more
than
one
year
and
now
I'm
joining
a
new
team.
I
feel
like
I
had
to
go
through
mine
boarding
all
over
again
and
yeah,
just
kind
of
remembering
that
it's
all
just
a
one
one
big
learning
experience
and
you
will
never
know
everything
that
really
helps
so
yeah
those.
I
think
this
would
be
my
best
advice
to
someone
joining
gitlab,
but
someone
considering
gitlab
like
if
you
are
looking
for
a
job
and
you're
considering
joining
gitlab.
B
Please
do
consider
us
because
our
team
is
awesome.
I
can
say
that
I
really
don't
think
there
is
another
company
that
has
such
an
amazing,
remote
culture
and
such
amazing
values
that
we
really
truly
live
by
every
single
day.
It
still
blows
my
mind
that
we've
grown
to
to
this
size
and
we
are
actually
living
by
all
of
those
values
so
join
us.
You
will
not
regret
it.
It's
fine.