►
Description
Issue: https://gitlab.com/gitlab-org/gitlab-design/-/issues/1666
Slides: https://www.figma.com/file/gVymX9SwTJmscraRxL5sJz/Gina-Runner-FY22-Scorecard-Walkthrough?node-id=105%3A73
Experience map: https://app.mural.co/t/gitlab0631/m/gitlab0631/1629293415498/8b4f7b95d4852709b4b35d884d33b6bc17198c42?sender=u8acaa5f2dd7f92154f687467
UX Scorecard documentation: https://about.gitlab.com/handbook/engineering/ux/ux-scorecards/
UX KR documentation: https://about.gitlab.com/handbook/engineering/ux/#okrs
A
A
The
second
is
to
create
an
experience
map
of
the
process.
This
is
more
of
like
a
storyboard
that
is
related
to
this
scenario
that
you're
going
through
and
we're
using
mural
to
document
that
and
you'll
get
a
little
bit
more
of
an
insight
into
that
as
we
continue
on,
and
I
show
that
the
third
thing
is
to
carry
out
the
evaluation
and
score
the
experience.
A
So,
for
this
part,
there's
a
couple
different
evaluation
types
that
you
can
go
forward
with,
and
one
is
heuristic
evaluation.
The
other
is
observing
internal
or
external
users.
Going
through
the
scenario
for
this
one,
I
am
using
the
heuristic
evaluation
and
then
once
you're
completed
with
that,
then
you
score
it
using
the
grading
rubric.
A
So
for
this
one,
like
I
said,
I
ran
the
scorecard
around
the
runner
enterprise
management
area
of
get
lab
and
the
persona
that
we're
primarily
dealing
with
here
is
priyanka
who's,
the
platform
engineer
and
she
kind
of
acts
more
of
as
an
admin
who
is
overseeing
all
the
runners
that
are
related
to
her
organization.
A
So
there's
a
lot
of
jobs
that
can
be
related
to
that.
But
for
this
one
specifically
we're
focusing
on
when
I
am
managing
the
execution
of
many
ci
jobs
at
scale.
I
want
an
overall
understanding
of
the
job
executors
connected
to
my
organization,
so
I
can
make
effective
decisions
when
we
say
job
executors
here.
A
It
doesn't
just
span
to
the
runner
area
we're
actually
as
a
ux
team,
where
we
are
all
conducting
these
evaluations
and
we're
pairing
up
so
that
one
person
is
evaluating
an
area
that
they
don't
usually
work
on
at
gitlab,
so
they're
acting
almost
as
a
new
user
and
can
therefore
provide
learnability
insights
to
the
other
designer
that
they're
paired
up
with
it
will
also
for
the
runner
group.
It
will
provide
direction
for
us
to
prioritize
issues
in
our
upcoming
epic
focus,
which
is
enterprise
management,
which
is
the
admin
view
of
runners.
A
So
I
have
set
up
my
scorecard
and
I
am
also
evaluating
it
and
that's
because
I'm
new,
I
don't
know
a
ton
about
runner,
so
this
will
be
a
learning
experience
for
me
as
well.
I
have
a
bunch
of
links
here.
If
you
want
to
dive
deeper
into
any
of
that
stuff.
A
So
the
scorecard
details,
there
is
a
scenario
that
is
at
hand,
and
the
main
focus
of
this
is
that
you're
responsible
of
administering
a
large
fleet
of
runners,
like
I
was
saying
with
our
customer
pain
points
right
now.
You
need
to
have
access
to
insights
into
the
status,
availability,
security
and
performance
of
your
runners
in
order
to
make
crucial
decisions
that
impact
your
team
of
developers
and
then
there's
a
bunch
of
tasks
that
I
ended
up
writing
out
to
be
able
to
complete
this
scenario,
since
that's
more
of
like
a
general
scenario.
A
So
what
I'll
do
is
I'll
go
through
each
of
these
tasks
and
give
you
insight
into
how
I
carried
these
out
and
I'll?
This
is
not
my
first
time
completing
them.
So
it's
more
of
like
a
summary
of
how
it
went
so
I'm
going
to
go
into
my
own
instance
of
get
lab
and
I'm
gonna
go
into
the
admin
view,
because
that
is
where
we're
looking
at
this
and
we're
looking
at
runners.
A
Okay,
so
right
from
the
back,
I
can
see
that
I
have
a
ton
of
runners
considering
I
have
up
to
more
than
500,
I'm
assuming
from
that
number
and
the
pagination
is
all
the
way
down
here
and
I
don't
even
see
a
total.
So
I
don't
really
know
how
many
I
have,
but
I
have
a
lot
so
I'm
gonna
jump
over
to
my
scorecard
issue
view
runners
associated
with
an
instance
or
group
and
verify
it
is
running
as
desired.
A
So
here
I
can
see
that
types
are
already
identified
using
these
labels,
so
I'm
assuming
that
I
can
filter
by
type
yep,
so
instance,
okay,
so
it
looks
like
I
have
a
ton
that
are
at
the
instance
level,
which
must
be
the
same
as
shared
and
I'm
guessing
that,
since
these
are
not
contacting,
have
never
contacted,
they
are
not
actually
running
so
the
status
is
probably
inactive.
Although
it's
not
really
clear,
I
wonder
if
I
say
active.
A
No
apparently
they're
active,
they
just
never
have
contacted
okay.
Well,
there's
one!
I
don't
know
how
many
there
are
of
those,
but
there
must
be
a
lot
and
then
the
other
type
is
group.
So
I'll
just
go
to
that.
A
Oh,
I
only
have
two
grouped
runners.
Okay,
so
I
have
one
that
is
pause
right
now
and
one
that
looks
like
it's
running.
Let's
see
what
happens
if
I
say
yeah,
so
this
should
just
give
me
that
one,
that's
positive,
okay,
so
cool.
That
was
pretty
easy.
I'm
really
happy
that
there
were
filters
to
be
able
to
allow
me
to
do
that.
So
that
was
great.
A
A
Okay,
there
we
go
so
maybe
if
I
can
just
search
by
that,
that's
weird
it
doesn't
show
me
any
so.
It
looks
like
I
can't
search
for
the
unique
identifier
which
would
really
suck
if
it
wasn't
on
this
first
page.
But
if
I
use
command
f,
I
can
at
least
get
highlighted
to
it.
Yeah,
that's
pretty
tough.
The
only
other
way
I
can
think
of
using
a
unique
identifier
is
maybe,
by
the
registration
token
that
you
use
to
be
able
to
register
that
runner,
which
I
believe
won't
work
either.
A
For
the
sake
of
this,
I'm
gonna
just
simply
delete
that
yeah
that
doesn't
work
either.
So
I
can't
I
can
complete
that
if
I
know
that
the
name,
if
the
unique
identifier
means
this,
then
I
can
complete
it
but
very
unnecessary
steps
to
be
able
to
do
it,
search
for
an
active
runner
change,
it
state
to
inactive
and
then
edit
its
description.
So,
let's
see
search
for
an
active
runner,
I'm
just
going
to
pick
a
random
one.
A
The
only
thing,
though,
okay
I
did
find
it.
It
would
be
nice
if
I
could
figure
out
which
one
was
just
updated,
because
I
don't
really
remember
the
name:
okay,
but
that's
nice.
So
I
was
able
to
do
that
and
it
was
pretty
easy
cleanup
archive
a
large
number
of
runners
that
haven't
contacted
gitlab
in
30
days.
So
this
is
going
to
be
a
struggle
because
I
already
know
I
don't
have
any
availability
availability
to
filter
by
the
last
contacted
attribute.
A
A
So
that's
gonna
take
forever
and
I'm
not
gonna
do
that
here,
but
that
is
really
tough.
If
I
had
tens
of
thousands,
I
don't
even
know
what
I
would
do
in
that
case,
maybe
write
a
script
manually
to
do
it
determine
how
many
runners
are
out
of
date
by
two
versions
in
order
to
help
with
compliance
enforcement.
So
this
was
a
huge
struggle
for
me.
A
Actually,
when
I
was
first
carrying
this
out
because
I
didn't
know
what
version
was
the
most
updated
and
I
wasn't
linked
to
any
docs
to
be
able
to
see
that
either.
I
would
think
that
maybe,
like
version,
I
don't
know,
would
have
information,
but
then
I
realized
that
most
of
them
are
14.1,
so
I
assumed
that
two
versions
that
would
put
me
at
12.1,
so
I
think
that
I
could
just
go
with
that
assumption.
A
I
did
end
up
verifying
that
in
the
docs,
but
I'm
gonna
see
I
can't
filter
by
version.
This
is
recent
searches.
This
gives
me
create
a
date,
which
means
nothing
for
me.
So
knowing
that
I've
done
this
before,
I
did
end
up
finding
it.
So
if
I
change
this
to
ascending
order,
I
can
find
there's
only
one
that
is
12.1
and
again
I
could
use
command
f,
but
I'd
have
to
be
on
the
right
page
to
be
able
to
find
it.
So
that's
pretty
tough.
A
A
A
Get
web
test
by
the
way
I
wish
it
had
a
link
to
just
get
me
right
to
here,
so
I
would
have
thought
that
runners
would
be
in
ci
cd.
A
And
the
runners
section
here
so
now
I
can
see
I
only
have
one
runner
that
has
ever
been
available
for
this
project
and
it's
interesting
because
the
statuses
are
different.
It's
a
new
runner
has
not
yet
connected,
which
isn't
even
I
think
offline
was
a
status
in
the
last
table,
but
definitely
not
this.
So
that's
interesting
that
it's
different
but
anyways.
This
could
be
a
lot
easier
like
there
was
definitely
some
unnecessary
steps
of
being
able
to
figure
that
out.
A
So
now
that
I've
gone
through
all
of
those
tasks,
I'm
going
to
hop
back
into
the
mural.
So
this
is
the
experience
map
this
kind
of
provides
an
overall
set,
like
visual
display
of
how
I
was
feeling
throughout
the
whole
thing.
A
This
top
area
was
when
I
was
feeling
highlights,
I
guess,
of
the
whole
process
and
then
low
lights
as
the
bottom.
Most
of
the
time
I
was
frustrated.
I
think
I
was
taking
a
lot
of
unnecessary
steps
or
wasn't
able
to
complete
the
things
in
the
way
that
I
wanted
to,
and
so
what
I
did
was
I
broke
it
down
into
each
task
through
these
stages,
so
a
stage
represents
task.
A
So
the
user
thoughts
here
that
I
was
writing
was
related
to
that
experience
and
kind
of
like
what
I
was
thinking,
which
I
kind
of
went
through
as
I
was
walking
through
those
tasks,
pain
points
which
I
definitely
noted,
and
then
opportunities
were
somewhat
based
on
the
pain
points.
So,
for
example,
the
unique
identifier
which
I
wasn't
completely
sure
of
it
would
just
be
so
much
easier
if
there
was
a
filter
type
to
be
able
to
add,
or
just
like
typing
in
the
unique
identifier
and
then
having
it
filter
down.
A
That
would
be
very
easy.
Another
one
is
bulk
deletion
action.
That
would
be
amazing.
That
was
super
super
hard
for
me
and
I
can't
imagine
dealing
with
thousands
of
runners
and
then
also
just
having
a
confirmation
message
that
something
was
deleted
successfully
and
adding
more
context
into
error
messages
and
actions
to
fix.
So
at
one
point
I
had
just
been
clicking
that
x
button
to
delete
them
and
I
had
selected
the
x
button
after
the
runner
hadn't
completely
deleted.