►
From YouTube: UX Showcase: Setting up GitLab CI
Description
Dimitrie shares UX work on Setting up GitLab CI in GitLab Verify
A
All
right,
hi
welcome
and
everybody.
It
seems.
I
have
a
little
bit
of
extra
time
so
I'll
see.
If
I
can
you
fill
another
level?
This
is
the
usual
case
for
verify.
Ci
setting
up
get
lab
CI.
So
a
little
bit
of
background.
First,
the
CI
stage
group
lives
under
the
umbrella
of
verify.
This
is
the
first
uux
showcase
for
the
verify
stage,
and
the
error
on
the
right
kind
of
pinpoints
mean
so
hi
I'm,
Lucas
Roth,
one
with
the
product
designers,
with
get
lab
working
on
PCI
stage
and
I.
A
Think
it's
interesting
to
point
out
that
we
have
a
ship
which
is
in
a
lovable
state.
I'll,
come
back
to
that
a
little
bit
later
into
this
presentation
as
well
and
I
want
to
point
out
that
we
have
a
new
product
manager
tau,
which
have
been
working
together
with
closely
with
to
through
some
of
this
effort.
So
let
me
see
towards
the
next
one
I'm
using
this
presenter
views,
I'm
wondering
how
exactly
works,
but
here
we
go
so
I'm
going
a
little
bit
about
the
background.
A
A
A
So
let's
go
on
to
2019
q3
q4,
so
we
moved
into
the
q3
territory
and
what
we
decided
to
do
is
to
evaluate
or
reevaluate
this
experience,
but
then
validating
it
with
nine
real
users
in
the
end,
I
want
to
point
out
that
this
is
the
first
yield
scorecard
validated
by
real
users.
It
was
a
really
nice
experience
to
do
so,
and
it
was
tested
with
six
software
developers.
A
A
We
synthesize,
together,
together
with
product
management,
UX
and
UITs
research,
and
arrived
at
insights,
that
you
can
give
a
little
bit
of
a
more
of
a
view
into
those
following
the
links
below,
but
the
themes
that
were
emerging
and
I
hear
that
my
air
calls
are
low
on
batteries.
I
hope
they
will
last
through
this
session
is
that
the
creation
and
the
validation
stage
kind
of
are
the
most
important.
A
So,
let's
move
on
to
I
want
to
highlight
some
key
insights
coming
out
of
the
validation
effort.
To
kind
of
you
know
showcase
why
it
was
important
to
do
so,
as
six
out
of
nine
uses
were
absorbs
erv
by
reporting,
you
know
being
low
in
confidence
when
setting
up
gitlab
CI.
So
that's
a
creation
stage
and
they
kind
of
pinpointing
it
directly
or
indirectly,
to
you
know
a
need
for
a
guided
setup.
A
Experience
I,
think
it
kind
of
tells
as
well
that
you
know
on
average
people
needed
four
page
navigation,
so
they
need
across
at
least
four
pages
in
get
lab
so
think
of
the
pipe
on
this
page.
The
pack
on
detail
page
the
job,
the
job
view
where
they
can
read
the
job
blog
then
move
back
to
the
type
on
this
page
again,
including
the
page
loads
that
take
time
right
for
user
to
complete
the
validation
part
of
their
flow
for
setting
up,
develop,
CI
and
I.
A
Think
there's
a
lot
of
time
awesome
as
well
as
an
area
of
opportunity
for
us
to
improve.
Let
me
see
the
last
one:
four
out
of
nine
users
encounter
PayPal
and
failure.
As
their
first
feedback,
some
pinpointing
a
little
bit
or
pointing
at
some
chance
for
us
to
do
some
positive
reinforcement
and
up
that
confidence,
while
sending
out
the
Pepsi
I
think
there's
an
opportunity
there
and
additionally,
you
know,
as
a
pipeline
reports
on
a
failure.
A
The
pipeline
does
not
in
fact
do
the
things
that
the
user
wants
to
do,
or
at
least
partly
doesn't
do
that
and
will
not
generate
the
immediate
user
value
they
will
indeed,
instead
need
to
spend
additional
time
fixing
it
in
order
to
move
on
and
do
the
next
step
in
that
more
information
again
in
the
in
a
link
below
so
then
we
are
the
time
labrang.
Now
there
are
10
issues.
Currently
that
came
out
of
that
for
our
attentively
scheduled
and
two
are
in
development,
already
I
think
it's.
You
know,
I
to
name
a
few.
A
An
example
of
that
is,
for
example,
direct
status
reporting.
You
know
when
users
are
hopping
between
the
different
pages
within
get
lab
to
find
out
what
what
is
going
on
with
their
pipeline.
Why
don't
we
offer
that
information
directly
page
agnostic,
basically-
and
you
know,
inform
them
in
in
a
better
way,
as
well
as,
for
example,
improving
the
efficiency
of
use
force,
this
bi
limping,
for
example?
A
If
your
configuration
is
misconfigured,
you
know
we
should
report
back
to
the
user
as
fast
as
possible,
instead
of
them
needing
to
copy/paste,
go
to
the
CI
limping
tool,
page
copy
and
paste
it
in
there
and
then
press
the
validate
button
in
order
to
find
out
what
is
wrong
with
it,
instead
of
just
knowing
that
it
is.
You
know
invalid.
A
Just
some
examples
there
and
I
think
that
the
most
important
part
of
this
is
that
some
of
these
issues,
where
pain
points
are
a
little
bit
more
difficult
to
fix,
and
for
that
we've
set
up
a
discovery
to
have
a
north-south
approach
towards
iteratively
guiding
the
user
setting
up
github
skies.
We
were
when
I
have
a
high
amount
of
confidence
and
and
give
them
small
amounts
of
data
at
the
same
time
so
that
they
can,
you
know,
set
up
gate
lab
see.
I
will
be
positively
reinforced
along
the
way.
A
There's
a
link
again
at
the
bottom,
if
you
are
more
interested
so
to
get
a
little
bit
more
body
as
to
why
we're
doing
that
I
dive
a
little
bit
into
our
direction
page
into
you
know,
reports
that
we
officially
recognize
that
get
lab
and
also
discussed
it
with
my
product
manager
and
I.
Think
I
want
to
start
out
with
the
first
one,
which
is
actually
an
old
research
done
by
Leif
Katherine.
A
One
of
our
UX
research
is
on
the
CI,
see
that
see
the
adoption
and
usage
research
results
and
a
specific
insight
from
that
report
is
that
the
set
up
of
gait
lab
CI
is
indeed
a
cumbersome
process.
So
it
kind
of
aligns
with
our
story
here
what
we've
seen
from
validating
with
our
users,
the
CIA
see
the
direction
page
in
the
states
that,
for
example,
github,
has
a
strong
product,
positioning
and
adoption.
A
So
we
have
a
strong
competitor
there,
where
we
want
to
be,
of
course,
a
little
bit
better
and
our
CSC
ICD
performs
particularly
well
under
analyst
review
and
represents
our
foot
in
the
door.
So
you
know,
as
people
are
using
competitive
products,
our
CIS
be
alongside
of
our
gig
repertoire.
Is
you
know
the
way
to
get
users
using
get
labs?
A
I
think
you
know,
having
CI
be
on
top
of
their
game,
be
the
door
towards
all
other
state
troops
in
in
get
lab
on
the
up
side
of
it
is
I,
think
a
really
good
thing
to
have,
and,
lastly,
we
have
the
opportunity
to
engage
better
the
customers,
basically
the
same
thing.
What
I
was
saying
there.
This
is
a
quote
from
a
direction
page
with
our
better
solution
and
bring
them
on
board
and,
lastly,
the
in
terms
of
like
analytics
report.
A
This
is
not
solely
focused
on
CI,
as
you
know,
in
a
way
that
we're
now
describing
it,
but
I
think
it's
still
relatable
that
our
developer
experience
is
being
rated
at
three
point.
Eight
out
of
five
and
our
platform,
strength
for
a
sea
ice
would
be
frigate.
Lab
is
ready,
there's
a
three
point:
two
out
of
five,
so
I'm
working
with
towel
on
a
hypothesis
that
we
potentially
improve
this
with
results
coming
out
of
this
discovery
when
implemented.
A
So,
let's
go
on
to
the
business
goal:
increase
adoption
of
gitlab
CI
for
potential
customers
looking
for
a
better
CI
to
Ladakh,
to
adopt
by
lowering
the
bar
to
setting
it
up
so
kind
of
falling
in
line
with
those
opportunities
and
direction
page
scribblings
and
here's
a
little
bit
of
a
guesswork
still.
So
this
is
a
work
in
progress,
but
I
think
it's
worth
telling
about
the
the
smile
score.
A
So
this
is
unique
uses
editing,
for
example,
the
gitlab
CI
MO,
and
these
are
daily
unique
uses
over
each
data
point
represents
a
seven-day
and
it
is
quite
low.
It
doesn't
grow
too
much
and
I
think
that
as
we
improve
get
lab
notes,
ending
up,
get
lab
CI.
That
number
will
grow
as
more
individual
users
will
be
able
to
edit
the
CI
and
also
will
be
willing
to
do
so.
A
Let
me
see
so
then
the
job
to
be
done.
So,
with
its
new
exploration,
we
define
the
job
to
be
done
again.
It's
closely
similar
to
the
user
stories,
who
went,
tryout,
Kaleb
CI
and
wants
to
learn
the
feature
quickly
so
again
get
my
code
test
and
deploy
it
fast
and
with
more
coffee.
Eventually,
you
can
then,
for
example,
compare
it
with
your
existing
configuration
with
a
competitor
product
again.
I
think
this
is
all
not
another
highlight.
We
can
mention
the
exploration
already
kind
of
pin
points
towards
a
few.
A
You
know
opportunities
and
when
looking
at
the
moonshot
a
very
little
use
a
label
within
our
issue
tracker,
we
have
a
few
issues
there,
which
are
literally
moonshot,
so
big
big
areas,
opportunity
and
two
of
them
already
aligned
with
with
the
way
we're
we're
thinking.
One
of
them
is
a
visual
editor
for
get
lab,
CI
mo
and
there's
also
suggested
edits
to
fix
common
errors
detected
by
CI.
A
So
we
want
to
you,
know,
be
of
help
or,
if
of
assistant,
towards
the
user,
even
before
it's
needed
and
helped
use
it
that
way,
so
going
a
little
bit
into
the
next
one
and
I
see
I
have
one
more
interesting
issue.
Actually
it's
also
about
you
know
less
context.
Switching
is
I
heard
in
one
of
the
other
presentations
we
can.
A
We
can
help
automate
that
navigation
as
well
so
showing
jobs
in
context
of
pipeline
might
be
an
opportunity
to
for
us
to
explore,
but
that
comes
up
later,
so
we
started
out
with
a
story
map.
This
is
just
an
intermediate
one,
but
I
think
it
was
nice
to
highlight
that
you
know
sometimes
working
behind
the
PCs
remote
designers
can
kind
of
not
bring
that
spark
of
creativity.
So
then
moving
towards
real
paper
might
beat
up.
You
know
a
solution,
as
I
did.
A
Eventually
we
have
to
move
to
a
digital
platform
to
make
collaboration
a
little
bit
easier.
So
this
is
the
story.
Map
highlighted
out
with
the
the
pink
ones
being
the
major
steps,
the
orange
ones
being
the
actions
taken
by
the
user
and
then
the
green
ones
being
the
solutions
proposed
and
you
know
to
be
to
be
explored
even
further.
A
A
We
can
see
that
here
as
well,
activating
CI
and
validating
CI,
and
it
kind
of
the
last
one
adjusting
also
falls
a
little
bit
into
that,
but
there
are
no
the
most
important
themes
or
steps
of
improvement
where
we
can
know
where
we
can
highlight
the
most
improvement.
So
here
you
see
them
circled
or
highlighted
with
the
green
ones
representing
areas
over
solution,
eyes,
areas
or
opportunities.
A
So
there's
lots
of
us
to
explore
there,
and
let
me
see
this
is
a
work
in
progress.
So
what
are
we
doing
right
now?
Is
that
we're
intending
to
have
the
first
impact
with
this
on
12
a
date
we're
following
the
product
development
workflow
has
been
detailed
before
by
Amelia,
and
the
immediate
next
step
for
the
exploration
is
that
we're
going
to
get
cross,
functional
knowledge,
influencing
the
story,
map
and
brainstorm
the
opportunities
together?
So
this
is
up
next
and
I'm
very
excited
to
do
so.
A
I
think,
there's
gonna
be
great
things
coming
out
of
it
and
the
story.
Map
kind
of
allows
us
to
work
together
with
product
management,
engineering
Ficino,
but
it's
going
to
be
in
each
iteration.
What's
going
to
be
in
12a,
what's
going
to
be
in
12
of
nine,
at
cetera,
et
cetera,
and
with
that
we
have
a
narrow
road
map,
or
at
least
the
beginning
of
a
road
map
setup
for
improving
this,
a
very
important
step
for
the
CI
stage,
with
that
I
hope.
I
have
talked
a
little
bit
to
fill
at
the
time.