►
From YouTube: UX Showcase: Four years of Design at GitLab
A
So
to
kick
this
off,
I'm
going
to
do
a
little
bit
of
a
different
ux
show.
Okay,
since
I
thought
this
was
going
to
be
the
last
ux
showcase
of
this
year.
I
saw
in
the
updated
schedule,
there's
actually
one
or
two
more
in
december,
but
this
is
the
last
one
in
this
kind
of
format,
where
there's
like
multiple
york,
showcases
in
one
kind
of
big
setting.
A
So
for
those
who
don't
know,
I
I'll
be
off-boarding
at
the
end
of
this
month,
and
I
thought
it
would
be
nice
as
this
an
amazing
year
to
kind
of
look
back
at
how
gitlab
has
been
in
the
last
four
years.
Pedro
and
tori
have
been
at
gitlab
as
long
as
I
have,
and
I
think
we
all
can
kind
of
present
a
unique
opportunity.
A
So
that
is
what
I
would
love
to
highlight
here
a
bit.
So
why
look
back
in
time
right,
I
think,
there's
quite
some
value
in
knowing
the
past
from
where
we
have
come
to
kind
of
you
know
recognize
how
far
we
have
come
for
enjoyment,
but
also
for
inspiration
to
see
you
know.
Where
should
we
be
headed
next,
I
did
some
interviewing
across
the
organization
spoken
with
dz.
A
The
original
creator
of
gitlab
spoke
with
sid
our
ceo,
I
spoke
with
christy
and
I
spoke
atari
there's
many
more
people
that
I
could
have
spoken
with,
of
course,
but
at
some
point
you
got
to
stop
and
bring
bring
the
story
to
to
everyone
here
so
on
to
the
next.
So
what
I've
done
is
basically
to
have
some
kind
of
like
a
measure
of
progression,
and
for
that
I'm
I'm
taking
a
little
bit
towards
the
news
norman
group,
which
have
created,
like
some
blog
posts
on
design
maturity
in
organizations.
A
This
is
quite
old,
though
the
general
lessons
are
still
applicable
to
today's
time.
There's
a
little
bit
of
a
bias
towards
agency
consumer
focused
design
and
research.
Maturity
isn't
well
as
well
mentioned
in
that
in
that
article,
as
it
as
it
could
have
been,
I
think
they
kind
of
skip
over
it
a
bit,
though
you
know,
research,
maturity,
kind
of
influenced,
design,
maturity
in
the
end.
A
A
brief
note
on
design
maturity,
there's
like
these
levels
that
you
skip
through
these
phases
and
for
some
reason
there
are
right
now
cars
coming
through
my
through
my
street.
Well
the
whole
day.
There
wasn't
the
car
to
be
seen,
but
it
makes
it
difficult
to
progress
through
these
levels
very
quickly,
although
I
think
throughout
the
journey
I'm
gonna
tell,
is
that
gitlab
has
been
exceptional
is
growing
through
these
stages.
A
So
there's,
of
course,
always
some
internal
friction
getting
everybody
along
in
this
kind
of
mindset
of
why
design
is
needed
and
what
kind
of
value
it
can
provide
skill
development.
Of
course
the
ux
team
needs
to
be
all
you
know,
get
up
on
that
that
higher
level
of
understanding
and,
of
course
the
regressions
can
happen
as
well,
for
example,
by
hiring
too
quickly
that
can
happen.
A
So,
to
give
a
brief
overview,
I
got
a
lot
of
the
slides,
I'm
not
going
to
pause
too
much
at
every
slide,
but
if
you
want
to
hit
back
on
the
slides,
please
do
so
in
the
in
the
presentation
link.
I've
provided
there's
always
resource
links
at
the
bottom,
but
this
is
a
brief
overview
of
news
and
norms.
Group,
description
of
every
level
kind
of,
and
they
kind
of
decide
on.
A
You
know
hey
what
is
what
is
happening
in
each
of
these
stages
and
how
do
you
progress
so
going
on
to
where
we
are
at,
or
at
least
where
we've
begun
design
before
2016?
This
is
even
before
our
time
before
the
first
ux
team
kind
of
design,
there
was
a
first
design,
though
you
know
the
design
project
was
created,
was
tested
with
users,
though
it
was
mostly
done
by
internal
release
candidates.
A
A
I
think
daily
these
days
with
the
newest
of
the
newest,
which
is
amazing,
and
I
spoke
with
dz,
and
he
said
the
reason
why
we
hired
the
first
designer
back
at
that
time
was
basically
to
have
better
better.
You
looking
ui
to
get
a
little
bit
beyond
the
bootstrap,
a
ui
that
was
used
back
at
the
time,
and
there
was
also
a
lot
of
controversial
changes
and
then
ui
being
implemented
by
developers
that
basically
just
needed
professional
input
through
from
there.
A
We
went
on
to
2016
and
I
think,
we've
never
hit
stage
one.
I
think
we've
always
started
at
stage
two,
which
is
developer,
centered,
music
experience.
It's
like
it's
developer,
use
experience.
You
know
application
and
the
the
mindset
behind
that
as
well,
so
going
into
that
a
little
bit
further,
I
think
we've
might
have
entered
even
stage
three
a
little
bit,
which
is
called
skunkwork
user
experience.
A
So
there's
like
these
small
kind
of
things
that
are
happening
in
design,
people
are
acknowledging
that
you
know
design
is
needed,
though
we
we
are
relying
too
much
still
on
personal
judgment
of
the
design
team.
You
know
you
are
not
the
user.
This
is,
of
course
a
given
these
days,
but
back
in
that
time,
that
was
a
bit
different,
I
would
say
feel
free
to
read
through
all
of
this.
I
don't
have
time
to
go
over
too
much,
but
that's
where
we
have
the
link
for
so
going
into
gitlab
design
in
2016.
A
A
This
was
basically
done
in
in
four
months
to
grow
from
one
to
six.
People,
which
was
quite
a
lot,
was
more
than
originally
intended
fun
fact.
If
you
go
towards
the
issue
included
in
the
resource,
this
is
the
original
issue
that
kind
of
discusses
it,
it's
kind
of
fun
to
jump
into
back.
Then
we
have
reporting
to
a
back-end
director,
then
a
front-end
lead.
You
know
it
was
a
lot
of
chaos
around
that
time,
but
it
was
still
a
you
know.
A
So
if
it
was
its
own
department
back
at
that
time-
and
it
would
grow
to
be
that
way,
then
we
would
optimize
for
better
design,
but
you
know
less
off
of
an
output
etc,
and
you
didn't
need
the
best
design
frequent
lap
at
that
time.
Just
you
know,
get
us
on
that
way
and
get
us
moving
basically
going
forward,
I'm
going
a
little
bit
faster,
because
I
know
the
time
we
had
some
important
changes
in
navigation.
This
was
actually
before
the
ux
team
started.
A
There
was
a
change
from
the
left,
sidebar
navigation
structure
to
the
overall
horizontal
navigation
structure.
This
is
actually
personally
a
trigger
for
me
to
get
interested
invested
in
git
lab
as
a
community
designer,
because
I
thought
this
change
was
controversial,
controversial
to
say
the
least,
and
I
was
interested
in
like
why
would
you
make
this
change
while
the
other
one
worked
so
much
better
and
also
differentiated
that
much
more
from
the
competitor
of
github,
for
example?
A
Anyway,
a
lot
of
things
to
read-
please
read
through
it
here,
are
some
examples
of
how
it
originally
looked
like
and
how
we
kind
of
moved
to
where
more
towards
a
more
horizontal
design
change.
This
doesn't
show
the
eventual
horizontal
design,
but
it
gives
you
some
some
cues
and,
of
course,
we
moved
to
sketch,
which
was
quite
important.
A
I
think
tori
and
pedro
can
still
remember
using
entertype,
which
kind
of
was
like
a
browser-based
design
program
very
interesting
to
work
with,
but
didn't
scale
that
well
when
we
scaled
up
to
towards
six
people
with
most
of
the
people
kind
of
used
to
more
design
programs
like
sketch.
So
that
was
a
quick
decision.
I
would
say,
then
the
first
results
were
coming
in,
I
would
say
for
the
new
design
team,
so
we
were
implementing
or
at
least
designing,
for
search
and
filters
instead
of
a
tabbed
or
drop-down
interface
for
scanning.
A
Through
backlogs
of
our
issue,
tracker
pipelines
were
introduced
where
we
used
to
only
have
builds.
Those
are
now
called
jobs.
We
introduced
them
at
our
higher
pla
level,
which
was
pipelines
which
kind
of
combined
multiple
jobs
into
one
big
pipeline
and,
of
course,
empty
stage,
which
kind
of
was
the
first
evidence
of
us
having
personalized
illustrations,
so
that
was
kind
of
like
a
nice
milestone
to
to
mark
there.
A
Then
I
think
this
was
a
good
point
in
time.
Our
first
ux
research
service
hired
sarah.
There
was
a
gap
in
between
designers
and
developers.
This
was
what
dz
told
me:
devs
knew
the
product
better,
and
you
know
designers,
weren't,
subject
matter
experts
and
we
needed
to
get
some
things
very
right.
So
that's
why
the
need
was
recognized
for
ux
research
to
to
get
in
there
and
that's
what
we
did.
I
think
that
has
been
a
great
great
help
since
review.
Apps
is
a
quick,
a
quick
note.
A
There
review
apps
were
already
there
in
2016
and
it
was
an
important
step.
I
think
you
know,
because
to
consider
like
a
featured
not
geared
at
a
very
technical
persona,
but
also
for
all
the
other
stakeholders
involved
in
software
development
such
as
product
managers,
designers
and
kind
of,
like
decrease.
That
iteration
cycle
is
an
important
step
into
you
know:
git
labs,
product
maturity,
as
well
as
our
process
improvements
going
on
2017,
I'm
going
a
little
bit
faster
every
time
our
persona
discovery
started.
A
A
So
it's
funny
that
the
first
navigation
redesign
was
restructured
again
was
turned
around
because
we
went
back
to
the
left
navigation
bar
design
because
it
did
work
better
and
people
were
confused
basically,
and
it
was
also
kind
of
like
the
first
case
of
where
we
had
something
resembling
a
feature
flag
where
people
could
turn
on
these
new
navigations
of
being
forced
into
it,
which
we
had
a
lot
of.
You
know
negative
feedback
on
from
the
first
time
we
thrown
that
around.
A
So
this
was
gitlab
9.4
10.0
around
that
time,
a
little
shoot
back
to
to
pedro.
There
was
also
some
pool
information
architecture
or
semantic
versioning
or
architecture,
where
you
know
we
grouped
the
information
and
we
redesigned
what
had
to
be
the
top
level
navigation,
what
come
gonna
go
in
the
sidebar
etc.
A
It
was
an
interesting
time
to
see
that
finally
change,
we
still
have
the
benefits
today,
so
the
design
system.
Of
course,
we
didn't
immediately
have
design.gitlab.com
yeah.
We
had
the
repository
and
using
brand
ai
at
that
time,
which
was
kind
of
like
a
plug-in
for
sketch.
We
were,
you
know
very
much
in
the
need
of
growing
design,
especially
scaling.
Visual
consistency
of
cross
gitlab
was
getting
harder
and
harder.
The
more
team
members
were
adding
towards
the
team,
so
we're
looking
into
this.
That
was
super
interesting.
A
Let
me
see
the
gitlab
svg
project
was
introduced
there
at
that
time
as
well,
and
we
had
a
dedicated
designer
kind
of
focusing
on
the
visual
aspects
of
every
new
icon,
moving
us
away
from
font
awesome,
which
was
the
icon
library
we
were
using
before
that,
and
then
the
dev
to
devops
move
happened
inside
of
git
lab.
We
kind
of
finished
the
the
master
plan,
but
it's
kind
of
like
this.
A
This
moved
us
towards
the
territory
of
vision,
work
like
do
how
much
ahead
into
the
future
are
we
looking
at-
and
this
is
kind
of
like
that
first
opportunity,
there's
a
little
link
into
the
vision
presentation
back
at
that
time.
I
think
tori
and
I
worked
on
some
of
the
vision,
mock-ups
but
the
whole
the
whole
team
was
invested.
I
would
say
so
get
that
first
look
big
big
point
in
time.
We
needed
you
know
a
research
participant
database.
A
Sarah
was
focusing
full
time
on
this
and
this
kind
of
evolved
over
time-
I
would
say-
but
this
was
a
like
the
blog
post
mentioned
here
kind
of
like
invested
the
audience
and
community
into
like
hey.
Why
do
we
need
this,
and
this
is
kind
of
like
the
first
step
into
that,
so
looking
back
at
that,
this
was,
I
think,
our
step
into
stage
four
dedicated
ux
budget.
A
There
was
a
budgeteering
involved
and
if
you
can
say
it
like
that,
to
get
that
ux
participant
program
set
up,
there
was
now
a
dedicated
ux
team.
You
know
we
were
getting
into
that
into
that
phase
of
of
you
know
we
were
still
scattered
around
the
company,
but
you
know
we
had
some
things
going
for
us
which
were
dedicated
towards
ux.
A
We
had
some
ownership
over
you
over
the
years
experience
as
a
whole,
and
basically
you
know,
as
I
said
here
in
the
last
phase,
it
was
on
for
us
now
to
collect
evidence
in
towards
moving
us
higher
up.
In
into
that,
you
know
strategic
place
that,
where
design
is,
is
will
be
able
to
thrive
2018.
This
is
like
the
last
year.
I
have
some
points
on
and
then
2019
and
2020
is
going
to
be
a
blur.
The
color
system
was
introduced,
microsoft
acquires
github.
A
A
This
was
super
important
according
to
to
sid
and
I
think
it
kind
of
highlighted
you
know
also
the
shift
a
little
bit
at
that
time
as
well
for
breath
over
depth,
and
perhaps
after
that,
we
were
beginning
to
understand
that
all
right
depth
over
breath
is
also
super
important,
which
is
where
design
is
going
to
thrive
as
as
much
as
it
can
so
yeah
catalyst
for
2019
and
beyond.
So
this
kind
of
influenced
everything
that
happened
beyond
beyond
that,
the
web
ide
was
introduced.
A
A
So
here's
like
some
some
product
decisions
how
they
were
involving,
or
you
know
how
ux
research
was
influencing
product
decisions.
We
needed
to
know
more
about
our
users.
It
wasn't
as
easy
over
problem
space
as
we
thought
it
was
going
to
be
and
ux
research
was.
It
was
a
problem
there.
So
that's
a
good.
You
know
good
evidence
for
for
how
important
ux
research
was
so
look
into
the
into
the
blog
post.
A
If
you'd
like
the
ux
team,
was
at
that
point
increasing
from
12
to
15
people,
so
we
already
doubled
in
size.
At
that
time,
annabelle
had
become
the
first
front-end
engineer
to
shift
ux.
I
kind
of
think
that
has
a
lot
of
influence
on
how
we
were
you
know,
collaborating
with
engineering,
and
can
I
have
that
improved
insights
there
as
well,
and
we
made
the
shift
to
stage
groups
which
was
kind
of
important
into
visualizing.
A
The
balance
between
designers,
product
managers
and
engineers
in
each
of
the
teams
going
on
ux
research
evidence
database
super
important
to
get
us
up
to
that
maturity
level
as
well.
You
know
how
where
we
were
collecting
all
that
that
evidence
we've
collected
through
our
research
that
was
defined
first
in
the
handbook
kind
of
got
that
towards
our
stage
five
and
take
this
little
grain
of
salt.
A
Of
course
it
doesn't
apply
one
to
one,
but
I'd
like
to
think
that
we
kind
of
managed
you
know,
went
to
that
phase
of
managing
stability
so
going
on
to
title
1920.
There
is
so
much
happening
at
this
point
in
time,
there's
so
many
more
people
into
the
team
that
have
kind
of
collab
combined.
All
of
that
info
into
a
couple
of
slides
and
I'm
going
to
highlight
a
few,
I
think
ux
team
increasing
from
15
to
46,
excluding
technical
writing,
is
a
big
part
of
that.
A
We
rebalance
product
design
to
product
manager
ratio
to
one
to
one.
I
think
this
increased.
You
know
the
sync
synchronously
between
product
management,
product
designation,
lot
and
you
know
getting
us
to
have
that
strategic
level
of
thinking
our
design
tooling
improved
a
lot
with
qualtrics
and
used
to
testing
and,
of
course,
figma
and
mural
have
played
a
big
role
there
as
well
for
design
thinking.
A
Let
me
see
so
you
know
the
design
system
finally
got,
and
I
think
this
is
one
of
the
most
important
points
to
highlight
here
as
well.
Scalability
in
our
design,
resources
is
super
important,
but
up
until
that
time
the
design
system
really
didn't
have
a
dedicated
budget.
So
now
the
ux
foundation
team
was
founded,
design
system,
opr's
were
defined,
or
these
were
part
of
our
otrs
and
kind
of
really
propelled
us
forward
with
that
place.
It
was
really
good
to
see
and
we
reap
the
benefits
of
that
today.
A
Very
much
I
would
say
I
love
seeing
the
new
things
being
added
to
figma.
I
love
being
able
to
just
say,
use
this
component.
It's
amazing,
if
you
compare
it
to
the
old
times.
Of
course,
some
highlights
from
our
blog
post.
I
think
you
know
the
figma
plug-in
is
amazing.
Dark
ui
forget
about
this
has
been
a
dream
for
a
long
time
we
called
like
we
have
a
special
little
label
in
our
issue.
A
Backlog
called
moonshots
and
they've,
been
there,
for
instance,
forever
and
dark
ui
forget
what
has
been
one
of
them
as
far
as
I
can
remember,
of
course,
our
higher
focus
on
holistic
iterative
design.
I
think
this
is
going
to
be
the
most
important
to
really
you
know,
flesh
out
the
vision
of
of
the
year
or
even
our
three-year
vision
that
is
currently
out
there.
So
I
think,
with
these
changes,
I
know
this
has
been
like
really
short
for
2019
2020,
where
actually
the
most
happened,
I
would
say,
got
us
towards
the
stage
six
stage.
A
Seven
maturity
level.
As
said
before
this
is
this
is
geared
at.
You
know:
agency-based
consumer-based,
design,
where
we
are
business-to-business
and
more
enterprise
design
focused,
but
still,
I
think,
we've
gone
a
long
way,
and
that
is
where
you
know
we
come
to
this
kind
of
part.
You
know
what
can
we
learn
from
the
past?
A
I
think
we've
come
become
fairly
mature.
Speaking
with
christy,
she
said,
like
hey
design,
embedded
with
cross-functional
teams
play
a
big.
You
know
have
played
a
big
part
into
getting
us
this
far.
Our
research
maturity
has
increased
by
length.
I
think,
as
as
you
can
see,
the
process
has
perhaps
have
matured.
Our
tooling
has
matured
it's
easy
to
kind
of
set
it
up
and
then
kind
of
roll
through
the
entire
lifecycle
of
getting
your
research
set
up
and
then
done.
Basically,
product
is
invested
in
research.
A
They
are,
you
know,
making
decisions
with
research
right
now
and
one
of
the
the
things
we've
seen
in
you
know.
The
amount
of
people
that
have
joined
git
lab
is
there
is
a
ceiling
on
how
fast
you
can
grow.
As
long
as
you
know,
you
want
to
up
that
that
maturity
and
I
think
we
are
now
establishing
a
foundation
to
grow
even
better
after
this
whole
covet
situation
is,
is
gone,
I
would
say:
where
should
we
be
headed?
A
I
want
to
close
this
off
a
little
bit
with
some
quotes,
or
at
least
have
quotes.
There
might
be
some
words
from
my
own
in
there,
but
they
generally
describe
the
thoughts
of
who
I
discuss
with
these
we're
from
synthesized
from
raw
notes.
I
quickly
wrote
down
from
the
interviews,
but
sid
said
you
know
we're
doing
the
best
we
we
can
or
the
best
in
the
industry
with
completing
devops,
but
now
he
has
a
very
much
focus
on
you
know
getting
us
the
best
sus
core
as
well.
A
He
says
basically,
our
most
used
functionality
isn't
as
smooth
as
I
could
as
it
could.
I
think
the
less
changes
in
restructuring
are
going
to
focus
on
this.
So
I
think
that
is
a
positive
thing
to
see
that
way
that
we
are
geared
to
kind
of
fix
our
mistakes
there,
or
at
least
where
we
can
do
where,
where
we
have
opportunities
to
do
even
better,
then
we
have,
of
course
we
were
very
feature
oriented
we're
now
usage
oriented,
especially
with
our
smile,
xml
kpis.
What
we're
looking
at!
A
I
think
this
is
a
positive
change
as
well
we're
already
on
it.
It's
a
positive
thing
and
we
are
focusing
on
refining
that.
So
I
think
that
is
something
we
are
already
all
doing
for
the
upping
this
escort.
Basically,
I
think
the
answer
from
dz
was
also
interesting.
You
know,
as
the
original
founder
of
of
gitlab,
he
would
love
to
see
some
freshness
in
ui
and
also
something
that
really
excites
you,
as
a
customer
to
you
know,
breaks
away
from
the
flow
of
releases.
A
A
I
think
this
was
very
admirable
to
say,
like
hey,
would
like
gitlab
to
be
held
up
as
an
exemplar
for
developers
to
use
kind
of
like
hey,
which
application
is
amazing
to
use
in
our
in
our
industry
and
the
image.gitlab,
because
it's
so
easy
and
so
useful
and
so
delightful
to
use.
Basically-
and
I
I
would
say,
we're
heading
in
towards
the
direction
collaboration
on
pm,
ux
engineering,
most
important
out
of
all
of
this-
let's
continue
to
focus
on
that
remove
the
tech
ux
depth.
A
I
think
this
has
been
a
you
know,
a
big
thing
with
gitlab,
since
since
all
time
we
have
such
a
huge
application-
and
I
would
say
right
now-
is
finally
the
time
we're
kind
of
touching
upon.
All
of
that,
while
we
used
to
have
to
pick
our
battles
back
in
a
time
as
to
okay,
what
are
we
going
to
improve
on?
Because
we
cannot
touch
everything
and
the
design
system
is
really
helping
out.
A
These
days
like,
where
can
you
add
real
value
as
a
community
contributor?
Perhaps
we
should
make
that
a
little
bit
easier
and
kind
of
you
know
get
that
playfulness
back
into
contributing
to
kit
lab,
even
though
I
I
also
have
to
say
you
know
seeing
gitlab
progress
as
fast
as
it
as
it
is
doing
today.
That
is
super
exciting.
A
A
I
also
acknowledge
we
cannot,
you
know,
stay
a
small
company,
we're
a
big
company
now,
but
I
think
you
know
a
focus
on
on
getting
and
staying
connected
with.
Each
other
is
always
a
good
thing
in
every
company.
So
I
would
love
to
see,
see
us
improve
in
that
sense
as
much
as
we
can
and
that's
it
actually.
I
think
we
have
progressed
through
design
maturity
in
an
amazing
way.
I
highlighted
some
key
points.
A
I
thought
was
interesting
for
the
design
maturity
at
git
labs
or
to
piece
our
road
towards
that
that
point
in
time,
and
I
would
like
to
congratulate
everyone
on
this
amazing
journey,
especially
in
the
last
two
years
where
everyone
has
been
contributing.
As
far
as
I
know
that
are
currently
at
the
at
the
company,
so
thank
you
so
much
and
feel
free
to
reach
out.
If
you
want
to
know
more
about
specifics
and
in
the
history
of
design
at
gitlab,
thank
you.