►
From YouTube: UX scorecard - User Onboarding
Description
Issue: https://gitlab.com/gitlab-org/growth/product/issues/170
User journey: https://app.mural.co/t/gitlab2474/m/gitlab2474/1572338087202/252b562c2e5e2de2e634109718b055416a967ee0
Grading rubric for UX scorecards: https://about.gitlab.com/handbook/engineering/ux/ux-scorecards/#grading-rubric
A
Hello,
my
name
is
Matteo
senior
product
designer
on
the
growth
group
here
at
gitlab
and
today,
I'm
reviewing
the
user
onboarding
experience
as
a
part
of
the
UX
departments,
initiative
for
more
holistic
and
proactive
approach
to
improving
ticket
lapse
user
experience,
and
this
is
all
part
of
the
UX
scorecard
work
where
we
map
and
analyze
the
current
user
journey.
Great.
The
experience,
video
the
my
document
is
flow
and,
in
the
end,
come
up
with
recommendations
for
improvements.
A
In
this
particular
case,
we
want
to
show
the
value
of
gitlab
to
newly
signed
up
users
that
are
completely
new
to
our
product.
In
fact,
the
job
to
be
done
that
we
put
together
as
part
of
the
implement
this
flow
is
when
I
sign
up
for
a
github
account.
I
want
to
see
what
are
its
main
features
and
benefits
for
my
robe
or
team.
So
I
can
find
out
if
it's
potentially
valuable
to
our
company.
I
have
now
mapped
and
analyzed
the
users
journey
and
graded.
A
The
experience
I
initially
wanted
to
create
this
experience
with
great
see,
but
after
I
gave
it
another
thought.
I
realized
that
it's
actually
between
C
and
T.
So
I
ended
up
creating
it
with
a
sim.
So
what
does
this
actually
mean?
If
we
look
at
our
grading
rubric,
we
can
see
that
C
is
supposed
to
be
like
an
average
experience,
a
workflow
that
needs
improvements
when
d
is
presentable.
A
Work
workflow
has
clear
issues
and
should
have
not
gone
into
production
without
more
thought
and
testing,
and
if
we
look
at
frustration,
levels
between
C
and
D
for
C,
it's
medium
and
D.
It's
high
and
task
completion
for
C
is
supposed
to
be
successful,
but
with
unnecessary
steps
and
for
D
it's
unlikely,
but
there
may
be
a
chance
that
there
is
completion.
A
So
I
feel
this
experience
lies
exactly
between
these
two
grades,
because
it's
sometimes
unlikely
that
a
user
will
sign
up
for
get
lab
and
find
the
exact
value
that
they
are
looking
for
from
this
product,
at
least
in
their
very
first
experience
with
it
lab,
which
is
exactly
what
we're
aiming
for
here
with
this
new
user
onboarding
experience.
Okay,
so
let's
go
to
the
flow
of
signing
up
for
get
lab
and
then
the
onboarding
as
it
is
right
now
and
I'll
start
off
on
the
homepage
and
go
straight
for
register.
A
Okay,
so
this
is
where
I
landed
right
after
the
registration
and
I'm
seeing
a
lot
of
things
on
this
screen.
It's
still
asking
me
to
confirm
my
email
but
I,
guess
it's
not
something
that
I
need
to
do
right
now,
it's
not
urgent!
Then
I'm
presented
with
a
free
trial
of
gitlab
cold
and
an
option
to
start
my
trial,
as
well
as
the
welcome
to
get
lab
Bart
and
four
options
on
the
screen.
A
So
it's
probably
unclear
at
this
point
exactly
what
the
next
step
should
be,
and
we
do
offer
some
explanations,
but
still
there
are
four
main
options
on
this
screen
and
two
of
them
are
actually
two
of
these
bottom
options
are
actually
accessible
to
everyone.
You
don't
need
to
sign
up
or
get
lab
to
explore
our
public
projects
or
learn
more
about
gitlab,
which
is
basically
get
labs
documentation.
A
So
we
should
find
a
better
way
to
introduce
the
new
newly
signed
up
users
to
get
lab.
What
a
group
is,
what
a
project
is,
what's
the
difference
and
what
should
be
their
next
step
in
getting
started
with
it,
based
on
the
data
we
have
so
far,
we
know
that
most
of
the
users
that
sign
up
for
a
get
lab
comm
account
create
a
project
straight
after
that.
So
I
will
go
down
this
route
today
as
well,
and
try
to
simulate
what
the
experience
of
the
kid
Labs
onboarding
is
at
the
moment.
A
Okay,
so
I
created
a
project
and
again
we
have
a
lot
of
alerts
showing
up
in
various
colors.
One
is
orange,
one
is
blue
and
other
one
is
a
different
shade
of
orange
sort
of
yellowish
and
I'm
also
presented
with
a
lot
of
information
on
how
to
get
started
with
an
empty
project,
as
it
seems,
I
can
start
by
adding
new
files
or
at
standard
files
to
a
repository.
A
I
can
even
go
ahead
and
clone
it,
but
it
doesn't
really
make
sense
right
now,
as
it's
empty
and
I
haven't
done
any
setup
on
it
just
yet.
At
this
point
it's
also
becoming
quite
obvious
that
there's
a
general
lack
of
guidance
for
your
users
and
they
need
to
figure
out
how
to
use
github
by
themselves,
and
we
can
also
see
that
there's
a
lack
of
focus
because
flows
are
full
of
distractions.
A
The
alerts
on
this
page
are
just
an
example,
and
in
the
previous
page,
where
we
were
asked
to
create
a
project
or
a
group,
there
were
four
options,
but
of
course
there
must
be
one
main
option
that
we
should
take.
That
would
guide
us
towards
getting
some
value
out
of
kit
lab
and
I.
Also,
while
I
was
signing
up
for
git
lab
I
told
that
I'm
a
product
designer
I
felt
that
information
in
so
I
would
expect
that
that
information
gets
used
somehow
to
shape
a
more
tailored
experience.
A
That
would
tell
me
this
is
what
value
you
can
get
out
of
kit
lab.
But
let's
say
for
a
moment
that
I'm
a
DevOps
engineer
and
wanted
to
see
how
good
laps
CI
works.
I
don't
want
to
go
through
a
complete
project,
setting
up
the
CI
pushing
some
code,
creating
a
merge
request
just
to
see
one
of
the
main
benefits
of
github.
A
It
could
take
me
at
least
an
hour,
if
not
more,
to
do
just
that
and
at
this
point
I'm
just
kind
of
browsing
through
the
product,
I'm,
not
even
sure,
if
it's
something
useful
I,
don't
think
I'm
willing
to
invest
that
much
time
in
a
product
that
I
barely
know,
I
would
expect
to
be
shown.
The
main
benefits
in
just
a
couple
of
minutes,
in
whatever
format
so
yeah
most
users
end
up
creating
a
project.
A
That's
what
we
know
so
far
and
we
can
even
try
to
go
and
set
up
the
CI
CD
and
we
even
have
the
option
to
choose
from
a
template.
Let's
choose
something
basic
for
this.
Even
if
it's
just
plain
HTML,
we
could
go
ahead,
commit
the
changes
and
we
will
have
something
in
place,
but
is
it
enough
for
me
to
see
you
know
what
kind
of
value
I
can
get
out
of
this?
It?
Doesn't
it's
I've
it's
at
this
point.
A
It's
very
unlikely
that
the
users
will
get
to
an
aha
moment,
as
we
call
them
by
themselves,
and
these
are
her
moments.
Are
you
know
that
point
where
they
realize?
Okay?
This
is
what
I
can
get
out
of
using
gitlab
and
how
it
can
benefit
their
work.
Okay,
we
can
see
now
that
the
pipeline
has
now
failed.
A
So
this
is
the
user
onboarding
flow
as
it
is
right
now,
there's
no
guidance
for
the
user
and
that's
exactly
what
we're
trying
to
fix
with
this
work.
I'll
add
links
to
the
relevant
issues
and
handbook
pages
in
the
description,
so
that
you
can
follow
the
progress
of
this
work.
We
intend
to
identify
the
right
approach
and
the
improvements
to
this
flow
in
the
next
month
or
so
and
hope
we'll,
hopefully
we'll
be
able
to
actually
introduce
these
improvements
shortly
after
thanks
for
watching
bye.