►
From YouTube: UX scorecard: Buy add-on CI minutes
Description
Issue: https://gitlab.com/gitlab-org/gitlab-design/issues/531
User journey maps (Mural): https://app.mural.co/t/gitlab2474/m/gitlab2474/1580371439854/de1d2f638437e8cc0337d3b344449b532c8bddf1
Slides: https://docs.google.com/presentation/d/1KMFw3ag6VGxCUiaiyqK4XgBj8rrEmH4DFHdsvWUb2nI/edit?usp=sharing
UX scorecard grading rubric: https://about.gitlab.com/handbook/engineering/ux/ux-scorecards/#grading-rubric
A
Hello,
my
name
is
Betty
I'm,
a
senior
product
designer
for
growth
here
at
Kidd
lab
today,
I'm
a
video
documenting
the
experience
of
buying
a
Don
CI
minutes.
This
is
a
part
of
the
UX
work,
hard
work.
That's
now
well
established
at
eat,
lab
to
quickly
summarize
what
a
UX
scorecard
is.
It's
basically
a
way
for
designers
to
take
a
holistic
approach
to
improving
an
experience,
and
we
do
this
by
first
identifying
the
job
to
be
done
so
who
the
user
is
and
what's
their
desired
outcome?
Then
we
mapped
the
users
journey.
A
It
could
be
an
engineering
manager,
eye
development
lead,
I
BP
of
engineering.
It
very
much
depends
on
the
company,
the
size
of
the
company,
the
type
of
the
company,
and
what
is
it?
What
is
their
job
to
be
done
and
I
have
outlined
it
now,
as
when
I
realize
that
we
are
running
out
of
CI
minutes,
I
want
to
quickly
and
easily
buy
more
so
that
our
team
can
continue.
Building
and
delivering
software
uninterrupted
I
have
also
mapped
the
user
journey
and
I
have
to
user
journeys.
A
In
this
case,
and
it's
simply
because
when
I
was
mapping,
this
journey
I
encountered
a
lot
of
authentication
errors
in
one
of
the
tools
that
the
users
need
to
use,
and
it's
not
a
common
error
that
happens,
but
I
still
wanted
to
map
it,
and
then
I
also
mapped
journey
as
it
is.
If
a
user
doesn't
encounter
all
these
errors.
A
So
with
this
being
not
clear
what
your
scorecard
is
and
what
our
current
persona
is,
what
the
job
to
be
done
is
what
the
main
user
journey
is.
Let's
dive
straight
into
the
actual
process
of
buying
additional
CI
minutes
and
where
the
user
can
see
the
current
usage
of
the
CI
minutes
is
on
their
group
settings
page
if
they
go
under
usage
for
us
and
in
this
particular
case,
I
have
used
more
than
my
limit
of
2,000
minutes.
I
actually
use
2009
and
all
my
pipelines
have
now
stopped.
A
So
this
is
where
they
were
to
consider
usage,
but
they're
very
likely
to
be
warned
about
their
CI
pipeline
minutes
running
out
either
by
an
email
message.
So
we
send
an
email
message
when
their
five
point
minutes
are
worth.
There
is
only
30%
of
them
available
the
content
of
this.
These
email
warnings
could
be
better,
because
this
is
quite
what
a
dry
email
and
it's
it
could
be
phrased
differently
to
more
clearly
communicate
the
message,
which
is
basically
saying
hey.
You
only
have
40%
of
your
CI
minutes
left.
A
You
need
to
do
something
about
it,
and
then
we
also
show
these
warning
banners,
but
the
problem
with
this
is:
we
only
show
them
on
project
overview
pages
in
that
group
that
is
running
out
of
CI
minutes.
So
we
don't
show
them
on
the
group
overview
page.
We
don't
even
show
these
these
warnings
on
the
actual
usage
product
page.
A
So
we
should
definitely
improve
that
and
then
the
content
again
it
can.
It
could
be
clearer.
It
could
state
that
this
is
for
this
group,
because
if
I,
don't,
if
I
have
a
lot
of
groups
right,
I
have
20
groups,
managing
I
might
might
not
know
all
the
names
of
this
group.
So
it
might
be
a
lot
clearer
if
you
actually
stated
that
this
is
a
group
name,
its
forms
unit
at
five,
only
5%
of
CIA
minutes
is
still
available,
and
then
it
has
two
CPAs.
A
A
So
if
a
user
was
to
click
on
either
of
these
two
links,
they
would
end
up
in
our
what
we
call
it
lab
customers
portal
and,
depending
on
what
were
they
clicked
if
they
clicked
on
click
here,
they
would
just
land
on
this
home
page.
If
they
clicked
on
the
purchase
more
minutes,
we
would
actually
send
them
down
the
correct
path
of
buying
more
CIA
minutes,
which
is
something
that
they
can
access
from
this
page.
A
But,
as
I
said,
I
need
to
authenticate
with
this
tool
to
complete
these
stats,
and
my
main
problem
with
documenting
this
user
was
that
I
couldn't
authenticate
with
this
tool
because
of
a
very
particular
authentication
error,
which
actually
is
caused
by
a
bug
that
we
now
identified
and
will
be
fixed
separately
separately
from
this
work.
I
couldn't
sign
in
any
just
figuring
out.
What
to
do.
It
took
me
like
an
hour
which
buying
more
CIA
minutes
should
take
just
like
two
or
three
minutes
max,
but
either
way
I
need
to
sign
in
to
get
that.
A
One
thing:
that's
a
bit
confusing,
also
on
this
screen
is
with
that
that
we
actually
state
the
period.
We
have
this
period
information
shown
here,
but
it
actually
says:
January
31st,
2022,
January,
twenty
thirty,
first,
twenty
twenty,
which
is
confusing
and
I,
know
why
that
is
because,
if
you
buy
a
subscription,
it
will
actually
tell
you
when
your
subscription
is
starting
and
when
it
will
basically
end.
A
But
in
this
particular
case
because
we're
buying
three
minutes,
it
doesn't
really
apply
to
it
because
CI
minutes
once
a
user
price
and
if
they
don't
use
all
of
them,
they
will
actually
roll
on
into
the
next
month.
So
this
might
add
to
the
confusion
in
this
in
this
particular
process
and
from
here
on,
the
user
just
needs
to
their
payment
information
except
the
privacy
policy
interns
and
confronted
purchase.
A
I
won't
do
that
right
now,
because
I'm
actually
in
a
production
environment,
and
it
would
charge
my
credit
card,
but
what
we
show
them
after
a
successfully
completed
process
is
a
congratulations
screen.
It
just
purchased
one
thousand
three
minutes
and
we
told
them
to
go
and
check
out
what's
new
in
github,
which
is
a
bit
strange,
because
I
believe
that
users
at
this
stage
would
want
to
see
that
we
would
want
to
be
reassured
that
their
additional
CI
minutes
that
they
just
bought
were
actually
added
to
their
usage,
kora
and
yeah.
A
They
should
show
up
here,
so
we
don't
do
that
at
the
moment,
which
may
add
some
confusion
and
adds
a
bit
of
manual
work
if,
if
a
user
wants
to
look
for
themselves,
just
to
be
reassured
so
if
I
go
on
to
summarize
the
findings
of
this,
your
scorecard
work
I
have
identified
four
main
problems.
The
first
one
is
that
the
experience
is
somewhat
disjointed.
A
The
users
are
sent
to
a
different
tool
or
they
need
to
complete
the
task,
and
we
tend
to
send
them
to
two
different
parts
of
this
tool,
and
some
of
them
are
just
not
right
that
we
send
them
down
the
wrong
path.
Sometimes,
there
are
unnecessary
steps
to
complete
this
task.
I,
don't
think
a
user
should
authenticate
with
a
separate
tool
to
complete
this
task.
It
should
be,
as
I
said,
like
a
two
or
three
minute
process.
Maybe
even
that's
just
a
couple
of
clicks,
our
warnings,
I
would
say,
are
inadequate.
A
The
messaging
in
our
email,
warnings
and
defender
warnings
were
just
not
clear
enough
and
different
City
is
linking
to
different
destinations,
adds
to
the
confusion,
so
there's
a
lot
of
improvements
that
we
can
do
there
and,
of
course,
the
authentication
problems.
So
this
is
not
very
likely
that
it
will
and
to
all
of
the
users,
but
it
may
happen.
As
I
said,
this
bug
will
be
fixed
separately
from
this
world,
but
in
the
long
run
we
should
probably
look
for
ways
to
maybe
even
avoid
this
whole
authentication
process.
A
So,
based
on
all
these
things,
I
decided
to
rate
the
experience
with
a
great
C,
which
is
average
so
steps
to
complete
these
tasks.
To
complete
this
task
is
average
complexity.
Frustration
is
might
be,
medium
depends
on
if
you
encounter
those
authentication
errors
or
not
and
yeah.
If
we
look
at
how
our
C
grade
is
described
in
our
UX
scorecard
grading,
rubric,
workflow
needs
improvement,
but
user
can
still
finish
completing
the
task
it
usually
takes
longer
to
complete
tasks.
A
A
The
next
step
is
action
just
to
brainstorm
and
write
down
all
the
possible
improvements.
How
can
we
improve
this
experience
in
a
separate
issue
and
then
revisit
this
experience
in
the
next
quarter?
To
see?
Have
we
improved
or
not
risk
or
the
experience,
and
it
seems
like
there's
quite
a
lot
of
improvements
that
we
can?
We
can
do
in
this
particular
case.
So
definitely
stay
tuned.