►
Description
- Rescoring issue: https://gitlab.com/gitlab-org/gitlab-design/issues/516
- Presentation slides: https://docs.google.com/presentation/d/12Ehl-CoelQrYrx-rxgOASENDW7bXJ9X6Snoui91hrtk/edit?usp=sharing
- First scorecard video: https://youtu.be/wCnpEGhS8uk
A
They
work
scorecard
is
a
way
for
designers
to
take
an
elastic
approach
to
improving
experience
in
fixing
usability
challenges
in
our
product.
We
pretty
much
followed
three
main
steps:
the
first
one
being
identifying
the
user
and
the
desired
outcome,
and
today
that
we
define
a
persona
and
a
job
to
be
done
together
with
our
product
managers,
we
map
the
user
journey.
There
are
tivities
desires
and
pain
points
during
your
journey
and,
finally,
using
what
we
learn
with
greatly
experience
establishing
a
baseline
rating.
A
We
later
on,
implement
improvements
based
on
these
recommendations
for
the
shop
to
be
done.
We
are
working
with
multiple
personas
that
share
common
responsibilities
and
steps
in
a
diverse
workflow.
Our
main
persona
is
the
release
manager
or
the
software
DevOps
engineered.
There
is
responsible
for
releases
within
an
organization.
A
Anyone
involved
in
executing
releases
is
considered
from
automation,
engineers,
QAS
users
of
a
project
who
are
necessarily
part
of
the
core
team
and
external
people
who
user
projects
called
a
binary
and
just
want
to
be
aware
of
when
a
new
version
comes
out.
The
job
to
be
done,
recording
is
when
tracking
important
deliverables
in
my
project
I
want
to
easily
create
and
manage
release
entries
in
get
labs.
So
I
can
provide
a
package
softer
notes
and
files
for
people
to
use
the
benchmark,
scored
is
experienced
receive
in
2019.
Q2
was
enough.
A
A
Based
on
the
heuristic
evaluation,
I
focus
on
the
most
painful
areas
of
the
workflow.
These
areas
involves
creating
a
release,
use
the
interface,
making
a
clear
differentiation
between
tags
and
releases,
making
releases
easier
to
find
associated
portant
data
with
such
as
milestones
and
issues
and
general
verification
of
the
workflow
pages.
I
proposed
a
series
of
recommendations
that
once
implemented
will
help
us
improve
the
benchmark
score.
We
had
a
total
of
seven
issues
implemented
from
these.
A
The
first
step
that
is
for
risk
or
news
experience,
was
to
conduct
three
user
interviews.
We
both
internal
and
external
customers
responsible
for
release,
management
and
release
orchestration,
as
it
provides
valuable
insights
and
removes
subjectivity.
Our
intention
was
to
validate
our
hypothesis.
One
of
those
hypothesis
was
that
the
small
solutions
proposed
at
the
recommendations,
part
of
the
experience
baseline
effort,
do
affect
the
experience
in
a
positive
way.
We
wanted
to
learn
from
different
personas
and
understand
how
they
are
created,
religious
with
it
lab.
A
A
One
of
the
improvements
we
did
was
to
add
the
option
to
go
to
releases
right
here
in
the
project
overview
page
during
the
user
interviews.
None
of
the
three
users
spotted
this
new
option.
The
mainly
use
the
releases
menu
here
on
the
side,
navigation
to
go
to
the
releases
clicking
on
it
will
take
me
to
the
releases
page,
and
here
you
can
see
all
the
releases
identical
I
can
see.
Different
people
created
at
different
times
and
I
can
also
see
the
title.
A
This
is
a
commit
tag,
the
tag
which
has
the
same
name
as
title
when
it
was
released
and
by
whom
some
users
during
the
interviews
mentioned
that
will
be
interesting
to
hear
to
not
only
see
the
epitope
but
also
the
full
handle
of
the
user.
So
they
can,
they
can
quickly
identify
who
is
responsible
for
this
release.
A
A
Users
are
able
to
copy
the
comitia
and
click
here
to
see
the
whole
commit.
Here
we
see
some
improvements
in
the
overall
UI.
There
are
differences
from
the
previous
version,
but
they
are
not
very
big,
as
you
cannot
create
a
release
from
this
page
and
that's
a
big
pain
point.
It's
not
very
intuitive
and
the
application
UI
is
not
giving
me
any
hints
on
where
I
have
to
go
to
do
that.
A
Usually
an
it
lab
will
see
a
button
here,
green
or
blue
button
that
allow
users
to
create
new
items,
which
is
not
the
case
for
releases.
This
button
also
does
not
help
and
yeah
I
cannot
do
anything
from
here.
Pardon
see
the
releases
or
editing
an
item.
This
is
a
new
functionality
at
the
tinea
release.
What's
added
a
couple
of
milestones
ago
and
usually
pretty
happy
with
it,
they
could
really
spot
this
very
easily
and
it's
very
intuitive
that
clicking
on
it
will
take
them
to
the
edit
version
of
the
release.
A
A
They
cannot
still
associate
any
data,
such
as
milestones
or
set
a
date
and
date
for
release
or
mark
a
release
as
upcoming
those
are
other
things
that
we
can
do
to
the
API,
but
not
in
user
interface,
which
yeah
can
be
pretty
frustrating
when
editing
release
it
becomes
highlighted,
and
the
page
Scrolls
to
the
latest
item,
which
is
pretty
cool.
This
is
also
known,
was
implemented,
a
few
milestones
back
yeah
and
you
cannot
create
a
release.
A
I
know
that
if
I
go
to
the
text,
page
I
can
create
a
new
tag
and
associate
release
notes
to
it.
This
page,
in
particular,
is
not
very
attractive.
It's
looks
pretty
messy
and
there
are
some
feedback
saying
that
we
should
improve
the
overall
look
and
feel
of
this
page
again,
no
hints
telling
me
where
to
go
or
how
to
create
a
tags
and
how
those
are
associated
with
releases.
A
A
I
can
choose
where
I
want
to
create
from
I
can
choose
from
this
release.
Branch
I
can
add
a
message
and
release
notes.
Messenger
Burleigh's
notes
are
pretty
confusing.
We
also
received
a
lot
of
feedback
from
users
saying
that
they
don't
necessarily
want
to
add
a
message
to
their
tag
and
because
we
are
showing
this
field
as
a
text
area,
it's
confusing
one
of
the
users
say
he
often
has
to
come
back
and
add
it's
the
release
notes
because
he
added
a
description
on
the
messages
field.
So
users
indicated
that
you'll
be
best.
A
This
is
a
test,
so
the
data
here
doesn't
really
matter
and
we're
going
to
add
some
issues,
and
it
should
be
good
to
go
when
I
create
this
tag.
I
expect
that
I'm
going
to
be
taken
to
a
few
of
my
release
page,
and
this
doesn't
really
happen.
This
seems
to
be
the
detail
view
of
attack,
and
these
will
be
their
release
notes.
There
is
no
way
from
here
to
go
to
the
release.
Page
I
can
do
edit
browse
files
commits
or
just
download.
A
That
means
I
have
to
go
back
to
the
main
menu
go
to
releases
and
look
at
my
release.
If
I
try
to
edit
my
release
notes
from
tags
view,
what
happens
is
that
the
form
is
different.
I
no
longer
can
see
the
tag.
Name
and
I
can
no
longer
see
the
release
title.
This
is
very
confusing
by
canceling
it
and
going
back
to
releases.
I
can
now
see
my
new
item
and
yeah.
A
Different
data
to
it,
you
just
mentioned
that
they
would
like
to
see
issues
in
Mouse
time
related
to
this
release.
This
is
possible
through
the
API.
In
the
meantime,
this
is
everything
that
you
just
can
see
and
you
we
also
asked
users
to
subscribe
to
notifications.
We
didn't
release
and
they
expected
to
see
the
notifications
option
on
this
page.
A
They
can
know
on
the
project
overview
subscribe
for
releases.
We
added
this
option,
that's
all
with
our
improvements,
but
as
you
can
see,
it's
really
hidden.
You
have
to
go
to
drop-down,
then
the
model
using
the
mentioned
that
will
be
interesting
to
have
an
option
here
to
subscribe,
to
releases
and
also
on
the
releases
overview
page.
A
So
the
conclusion
is
that
not
all
tasks
can
be
completed
when
users
are
trying
to
create
your
activities
easily
beat
eleven
wise
interface.
There's
still
a
lot
of
friction,
some
of
the
steps
they
need
to
do
through
the
API
and
some
what
they
have
to
do
through
the
UI
tags
and
released
are
still
confusing
for
users.
They
are
not
familiar
with
your
concept
and
there
are
no
signifiers
so
very
little
support
in
the
UI
that
links
to
relevant
information.
That
makes
you
there's
waste
time.
A
These
are
the
insights
that
contributed
to
the
score
of
this
new
step
of
the
scorecard
for
creating
and
releasing
obtaining
it.
The
experience
great
stays,
as
is
its
enough.
There's
a
very
high
chance
of
frustration
and
the
tasks
cannot
be
completed
to
its
fullest.
This
are
steps
missing
and
there's
a
high
risk
of
an
abandonment
users.
We
mostly
like
to
seek
other
methods
to
complete
the
task.
Thank
you
for
watching.
Yes,.