►
Description
Nadia Sotnikova, Product Designer at Verify:Pipeline Authoring walks through the UX scorecard evaluation of the pipeline authoring experience from the novice user perspective.
A
Nadia
the
product
designer
for
verify
pipeline
authoring,
and
today,
I'd
like
to
walk
you
through
the
results
for
your
ux
scorecard
I've
just
conducted
around
the
pipeline
authoring
experience
in
this
ux
scorecard.
I
focused
on
this
job
to
be
done.
I
want
to
author
a
ci
pipeline,
so
others
in
my
team
can
leverage
ci
to
increase
the
efficiency
of
their
tasks.
This
is
a
very
broad
job
to
be
done
so
to
keep
it
more
focused.
I
specifically
focused
on
the
first
time
experience
with
gitlab
ci
for
a
novice
ci
user.
A
So
the
user
story
that
I've
been
testing
was.
I
want
to
create
a
gitlab
ci
pipeline
to
deploy
my
new
website.
A
So
I'm
gonna
go
through
this
walkthrough
feel
free
to
read
all
the
details
in
the
issue,
but
the
first
step
was
to
discover
github
ci.
A
So
if
we
start
on
the
project
page,
so
I
already
have
a
project
for
my
website
and
I
want
to
create
a
simple
ci
pipeline
to
deploy
my
website
and
I
know
nothing
about
gitlab
ci
and
I'm
not
familiar
with
ci
in
general.
A
So
when
I
look
at
the
project
page,
it's
not
clear
for
me
where
I
should
start.
There
are
many
things
competing
for
my
attention
and
it's
very
difficult
to
discover
gitlab
ci
here.
Furthermore,
I
also
see
that
I
have
an
option
to
enable
auto
devops
and
set
up
ci
cd,
and
it's
not
clear
to
me
what
is
autodevops.
A
Maybe
that's
something
that
would
help
me
accomplish
my
goals.
I
know
that
I
would
like
to
try
ci,
so
I
guess
setup.
Ci
cd
is
the
the
option
that
appeals
to
me
the
most
and
then
I
also
see
the
ci
cd
navigation
here,
but
I
started
with
clicking
on
setup
ci
cd
here
in
this
case,
when
I
do
that,
I'm
taken
to
the
file
editor,
where
I'm
faced
with
this
blank
page,
and
I
have
no
idea
at
all
how
to
move
further.
So
the
button
here
said
set
up
ci
cd.
A
However,
this
doesn't
help
me
set
up
ci
cd.
In
any
way,
this
doesn't
explain
to
me
how
it
works.
What
is
this
file?
What
I'm
supposed
to
be
writing
in
this
file?
It
doesn't
give
me
any
information
at
all,
so
if
I
kind
of
explore
this
ui,
I
notice
that
there
are
templates
here.
However,
the
experience
of
using
these
templates-
it's
not
ideal,
because
I
don't
know
what
these
templates
are:
there's
no
additional
information
about
the
templates,
what
they
do,
what
is
the
value
of
each
template
and
how
they
work?
A
So,
at
this
point,
as
a
new
user
who's
not
familiar
with
gitlab
ci
and
has
no
experience
with
ci
in
general,
I'm
I'm
just
lost.
I
don't
know
how
to
move
forward.
I
can
try
different
templates,
but
I
struggle
with
understanding
the
syntax.
I
don't
know
what
it
is
and
how
it
works.
So
really
I
just
need
to
google
because
the
documentation
is
also
not
linked
here.
So
there's
no
way
for
me
to
go
to
the
relevant
documentation
and
get
some
help.
A
A
And
only
on
this
documentation
page,
I
finally
learn:
what
are
the
requirements
for
me
to
get
started
with
gitlab
ci,
so
the
the
cta
bot
and
setup
ci
cd
actually
didn't
help
me
set
up
ci
cd.
I
had
to
go
outside
of
gitlab
and
I
had
to
google
documentation
to
get
this
information
about
what
is
necessary
to
set
up
cicd.
So
this
is
not
the
best
experience,
of
course.
So
now
I
know
that
I
need
to
create
the
ci
configuration
file
and
I
need
to
set
up
a
runner
now.
A
This
is
the
first
thing
I
hear
about
the
runner.
I
have
no
idea
how
to
set
it
up
and
what
are
the
options
so
in
documentation.
I
see
that
I
need
to
go
to
settings
ci
cd
to
set
up
a
runner.
It
says,
register
runner
or
install
github
runner
from
coming
to
this
page.
I
have
no
idea
if
the
runner
is
set
up.
A
If
some
runner
is
available
to
me
or
there's
still
something
for
me
to
set
up,
it's
really
unclear
so,
but
since
I
don't
know
really
how
to
move
forward,
I
just
assume
that
probably
some
runner
is
available.
Otherwise,
I
would
I'll
probably
be
notified
that
I
need
a
runner
if
it's
not
available,
but
this
is
definitely
an
area
for
us
to
improve,
because
from
this
page
it's
really
unclear
what
are
the
options
and
when
each
option
is
appropriate
and
it's
unclear
that
as
a
giflet.com
user,
I
already
have
access
to
the
shared.
A
Runners,
so
now
that
I
decided
to
just
move
forward
and
to
assume
that
I
have
access
to
some
runners,
I
need
to
move
forward
with
figuring
out
how
to
fill
out
my
ci
file.
So
my
use
case
is
that
I
have
a
website.
I
have
a
very
simple
website
project.
I
want
to
use
gitlab
ci
to
deploy
that
website
and
generally
just
set
up
a
simple
ci
pipeline.
A
So
I
google
youtube
chat
for
deploying
a
website
here.
There
are
some
options.
I
just
choose
the
top
result
and
from
this
documentation
page,
I
learned
that
there
is
actually
an
html
template
that
seems
like
it
would
be
a
good
fit
for
my
project.
I
don't
really
know
because
there
is
no
extra
information
about
it,
but
this
tutorial
suggests
an
html
template
for
a
website
project.
So
I
can
try
that
the
template
is
very
basic.
You
can
see
it
here
and
really
I'm
not
sure.
A
If
I
need
to
customize
it
further
or
not,
it
says
that
it
might
need
editing
before
it
works
in
my
project,
but
since
I'm
a
new
user-
and
I
don't
know
exactly
how
it
needs
to
be
customized
and
there's
no
helpful,
no
other
helpful
information
to
guide
me-
I
all
I
can
do
is
just
give
it
a
shot
so
just
trial
and
error.
I
can
just
commit
the
file
and
see
what
happens
next.
A
So,
as
I
come
in
the
file,
there's
no
way
for
me
to
see
what's
happening
is
the
pipeline
working.
It's
basically
just
the
default
editing
experience
here.
I
get
notification
that
this
github
chat.
Configuration
is
valid,
but
it
doesn't
really
tell
me
if
the
pipeline
is
running.
If
it
worked,
is
the
website
deployed,
and
actually
I
don't
even
know
where
to
check
it.
I
have
no
idea
where
to
go
from
here.
A
The
only
reason
why
I
know
where
to
go
is
because
I'm
a
designer
at
gitlab,
probably
so
I
navigate
to
the
pipeline
page,
but
I
imagine,
as
a
new
user,
I
could
be
pretty
lost
either
way.
I
found
my
way
to
the
pipelines
page.
I
went
to
icd
through
the
main
navigation
in
here.
I
see
that
my
pipeline
passed,
so
I
guess
I
guess
that
worked
now
when
I
come
to
the
pipeline
page.
A
One
thing
I
noticed
is
that
it's
not
very
discoverable
that
you
can
actually
click
on
these
on
these
jobs
in
the
pipeline
and
get
to
the
additional
details
and
logs.
So
perhaps
those
could
be
made
more
discoverable,
but
after
exploring
the
ui,
probably
I
would.
I
would
figure
out
that
I
can
click
on
them.
So
I
I
get
to
the
logs
and
I
see
that
the
job
succeeded
and
everything
worked,
but
there's
I
don't
see
any
links.
I
have
no
idea
how
to
access
my
website.
A
According
to
the
tutorial,
the
ht,
the
html
template
would
deploy
my
website,
but
I
have
no
idea
where
to
look
for
the
deployed
website,
there's
maybe
somewhere
in
the
logs,
but
I
wasn't
able
to
locate
it
so
again.
All
I
can
do
is
just
use
trial
and
error
to
explore
the
ui
click
on
things
and
hopefully
stumble
upon
something
useful.
A
So
after
some
time
I
I
noticed
that
there
are
these
job
artifacts.
So
maybe
the
job
created
something
that
will
help
me
find
my
newly
deployed
website.
A
So
if
I
click
to
browse
the
artifacts,
I
see
this
folder
with
an
index.html
file.
That
is
an
external
link.
It
has
this
external
link
icon.
So
that
kind
of
tells
me
that
if
I
click
on
it,
something
will
open
in
the
tab.
Maybe
it's
my
website.
So
probably
is
my
website
and
when
I
open
it,
I
see
that
my
website
has
indeed
been
deployed,
and
this
is
really
great,
so
the
template
worked
as
is,
and
it
worked
just
perfectly
for
my
simple
website.
A
A
So
the
feature
itself
is
really
amazing,
but
the
whole
experience
is
very
disjointed
and
it's
very
difficult
to
really
understand
if
it
worked
and
how
do
I
get
to
the
actual
deployed
website,
so
the
link
was
very
difficult
to
locate
so
here
throughout
this
experience,
some
of
the
steps
I
did
not
include
in
the
grading
for
this
us
scorecard
because
they
have
more
to
do
with
the
pages
feature
and
continuous
delivery,
rather
than
authoring
of
the
ci
pipeline.
A
So
these
steps,
where
I
was
I
was
I
struggled
with
finding
the
link
and
so
on.
I
didn't
include
them
in
the
grading,
but
the
release
team
can
perhaps
take
that
into
consideration
when
iterating
on
the
pages
feature.
A
A
The
experience
assumes
that
you
already
know
how
ci
works
as
a
whole.
Unless
you
have
experience
setting
up
ci
or
configuring,
ci,
yaml
or
you're
very
familiar
with
github
as
a
product,
you
will
really
struggle
so
yeah.
This
is
the
current
state
of
the
experience
for
authoring
a
pipeline
as
a
novice
user,
and
hopefully
we
can
take
it
from
there
and
really
improve
it.
If
you
have
any
questions,
feel
free
to
reach
out
to
me
feel
free
to
comment
on
the
ux
scorecard
issue
as
well.
Thank
you.
Bye.