►
From YouTube: Designing in the open | GitLab Design Talks
A
B
Yeah
sure
I'm
vitica
and
I
am
a
product
designer
for
the
pipe
and
execution
team
which
was
previously
known
as
the
ci
team
and
yeah.
So
I
am
not
very
new
to
gitlab
anymore.
I
mean
I
finished
a
year
here
and
it
was
a
very
interesting
journey
for
me
because
I
kind
of
traveled
on
the
spectrum
of
oh,
my
god
is
my
work
accessible
to
the
other
end,
where,
oh,
my
god
did.
I
forget
to
make
it
accessible
so
yeah,
I'm
still
exploring,
and
it's
pretty
enjoyable
here.
A
B
Sure
I
mean,
as
far
as
I
could
recall,
the
first
time
I
was
introduced
to
this
value
was
through
a
solution.
Validation
exercise
that
I
was
supposed
to
do
in
the
very
early
days
of
my
like
when
I
joined
gitlab,
and
one
thing
that
was
very
different
about
that
whole
approach
was
that
it
was
kick-started
on
a
public
issue.
B
Was
it
really
kind
of
exemplified
transparency,
because
we
didn't
just
like
listen
to
all
of
the
participants
in
the
issue
we
also
kind
of
shared
with
them.
Our
plans
like
how
we
are
going
to
tackle
the
things
that
they
pointed
out
and
from
there
we
also
kind
of
recruited
users
for
user
interviews,
so
we
reached
out
to
those
participants
if
they
wanted
to
share
more
about
their
experience
because
most
comments,
they
were
kind
of
overreactive,
so
we
just
wanted
to
dig
deeper
into
what
was
happening
and
this
whole.
B
A
Yeah
yeah,
it
was
definitely
a
surprise
for
me
as
well.
I
think,
like
the
the
idea
of
having
this
low
level
of
shame
of
releasing
stuff
early
and
often
and
like
having
the
confidence
just
to
like
put
stuff
out
there
when
it's
incomplete
and
and
people
are
gonna
potentially
tear
it
apart
is
terrifying
to
start
out
with,
isn't
it.
A
A
B
B
But
overall
the
feature
was
more
like
a
black
hole
to
me-
and
I
mean
I
remember
asking
so
many
questions
to
everyone
around
me-
the
whole
development
team
that
I
don't
know
what
they
were
thinking
about
me
at
that
point,
but
it
kind
of
opened
up
pandora's
box,
because
we
figured
that
each
one
of
us.
We
had
a
different
level
of
understanding
about
this
feature.
So
what
I
went
ahead
and
did
was,
I
thought,
okay.
B
What
goes
goes
on
behind
the
scene
and
how
it
is
I
get
how
it
is
architectured
and
then
I
invited
the
whole
team
to
review
my
merge
request
and
I
think
there's
about
40
commits
to
it.
There
were
like
a
huge
number
of
feedback
and
I'm
pretty
sure,
like
maybe
every
single
word
was
changed
by
the
time
it
was
ready
to
be
merged.
But
this
whole
experience
of
discussing
this
complex
feature
with
the
team
and
finally
arriving
at
a
common
understanding.
It
was
an
amazing
experience.
A
Yeah,
that's
that's
really
interesting,
so
the
the
output
that
you
actually
got
from
this
from
this
article
and
and
thing
that
you
you
wrote
super
useful
because
it
meant
that
you
can
share
your
knowledge
with
everyone
else.
But
I
I
imagine
the
process
of
actually
working
through
that
with
your
team
and
trying
to
resolve
a
common
understanding
must
have
also
been
really
really
useful
as
well,
and
that
that
must
have
been
something
that
you
wouldn't
have
been
able
to
do.
A
B
A
Yeah-
and
I
mean
like-
I-
really
love
the
work
that
you're
doing
at
the
moment,
and
I
really
love
the
content
that
you
put
out
there
as
well,
because
you're
working
on
some
really
complex
features,
features
that
I
don't
understand
and
I
work
at
gitlab.
So
I
I
can't
imagine
what
users
are
going
through,
so
the
the
content
that
you're
putting
out
and
the
way
that
you
use
design
in
order
to
make
these
concepts
successful
accessible
is
is,
is
really
really
interesting.
A
So
I
definitely
appreciate
that
and
I
think
it
sort
of
speaks
to
using
transparency
as
a
value
to
like
cut
through
the
noise
and
the
potential
information
overload.
That
comes
from
the
amount
of
content
that
we
push
out
there.
So
maybe
you
could
tell
me
a
little
bit
about
why
you
went
about
why
you
but
went
about
like
creating
this
sort
of
content
and
whether
there's
any
sort
of
secrets
that
you
can
share
see
how
else
how
other
people
can
steal
from
you.
B
B
So
one
thing
that
I
figured
was
gitlab
the
user
base
of
gitlab.
It
kind
of
it
is
made
up
of
people
with
different
learning
abilities
and
even
though
some
people
are
users
of
very
technical
features,
they
are
not
necessarily
technical
themselves.
I
mean
they
might
also
be
like
struggling
with
understanding
what's
happening
in
there.
So
what
I
did
was
I
used
the
power
of
illustrations
that
I
do.
I
took
it
up
a
notch.
A
That's
really
cool
yeah.
Sorry,
I'm
having
some
camera
focus
issues,
I'm
just
trying
to
get
back
into
into
focus,
but
yeah
being
a
visual
learner.
Everyone
is
sort
of
different
and
it's
it's
it's
really.
It's
really
great.
I
think
it
really
helps
to
simplify
like
a
lot
of
the
stuff
and
I've
definitely
learned
a
lot
of
things
from
the
way
that
you've
the
way
that
you've
packaged
up,
merge
trains
and
discuss
that
sort
of
thing
yeah.
A
B
I
mean
that
was
a
moment
that
which,
where
I
was
again
scared
to
you
know,
intervene
because
things
had
moved
so
far
along
the
process,
and
I
mean
pulling
things
back
at
that
point
of
time.
It
would
have
just
meant
like
disrupting
the
whole
thing,
but
then
it
is
also
important
that
we
kind
of
express
our
disagreement
at
some
any
stage
and
make
sure
that
whatever
we
are
kind
of
rolling
out
is
actually
the
right
solution.
B
B
We
are
calling
it
a
win.
I
mean
there
are
different
ways
of
looking
at
it,
but
that
would
not
have
been
possible
if
my
approach
would
have
been
different
since
the
beginning
and
this
this
courage
that
I
got
it
was
mostly
through
the
process
that
I'd
have
developed
this
courage
to
speak
up
whenever
I
feel
that
I
should
speak
up
and
the
communication
style
that
has
been
developed
with
the
team.
It
like
really
helps
in
solving
big
problems.
A
Right
so
this
by
by
leveraging
transparency,
it's
impacted
all
these
other
aspects
of
the
team
that
relate
to
our
other
values,
like
collaboration
and
results
and
all
this
sort
of
stuff.
So
that's
that's
great.
So
final
question
from
me
is,
if
so
say
someone
new
is
joining
gitlab
or
wants
to
join
git
lab.