►
From YouTube: UX scorecard: Geo installation
Description
This is the walkthrough of the experience of installing Geo.
Issue: https://gitlab.com/gitlab-org/gitlab-design/issues/731
Slides: https://docs.google.com/presentation/d/1VHMQCnFldwz1LzuRQoLwSkpNd-BWS5S7yTwusfCLNa8/edit?usp=sharing
UX scorecard: https://about.gitlab.com/handbook/engineering/ux/ux-scorecards/
A
A
Our
main
target
user
for
the
insulation
is
Sydney
system
administrator,
and
this
task
could
be
described
based
upon
the
job
to
be
done,
framework
that
we
are
using
when
Sydney
is
installing
Geo.
They
want
to
complete
the
installation
as
quickly
as
possible
so
that
they
can
start
using
an
exploring
geo.
A
This
is
a
really
high-level
overview
of
the
user
flow.
As
you
see
here,
there
are
five
different
steps
and
five
different
interfaces,
including
the
geo
instruction
documentation
and
two
primary
and
secondary
CLI
and
two
different
UI
primary
and
also
the
secondary,
and
this
is
a
nice
journey
which
is
really
long
and
complicated.
A
So
I
will
not
go
through
the
detail
of
each
journey
map
in
each
step.
If
someone
interested
in
please
use
this
link,
mural
link
here
as
a
reference
means,
but
I
would
like
to
focus
on
the
instruction
document
first,
because
it
was
really
not
easy
to
follow
up
all
instruction
here.
So
this
is
a
Geo
instruction
document
and
we
have
some
very
nicely
visualized
what
this
geo
doing
and
some
architecture
diagram,
and
it
was
ok.
A
But
the
thing
is:
if
user
wanted
to
install
geo,
it's
really
not
easy
to
find
where
it
is,
and
then
they
still
need
to
scroll
down
here
and
then,
if
they
find
a
set
of
instruction
here-
and
it's
like
this-
making
your
existing
instance
to
the
primary
and
adding
the
notes,
as
secondary
I
mean.
This
is
not
enough
and
another
small
title
here-
using
kill
ab
omnibus,
of
course,
it'll
work.
But
it
could
be
great
if
this
set
of
instruction
is
somewhere
on
the
top
level,
not
under
this
level
and
I
could
see.
A
There
were
several
steps
to
set
up
geo
and
it's
like
okay,
I
have
to
have
to
skill
up.
Enterprise,
Edition
and
I
have
to
set
up
for
the
proper
license,
and
it's
about
the
database
replication
configure
things
it's
still
a
lot,
but
during
the
installation
user
you
need
to
see
this
screen,
so
they
need
to
copy
and
paste
each
comment
line
and
do
the
reconfiguration
and
modify
the
gitlab
dot
RB
file.
A
Here
it
was
okay,
but
after
this
configure
the
secondary
server
and
they
initiate
the
replication
process,
you
feel
like
the
replication
process
is
now
complete,
so
probably
user
thought
that
okay,
this
is
done,
and
in
this
case,
if
user
would
like
to
add
the
note
on
the
UI,
nothing
will
be
work
as
they
expected
and
I
think
it's
a
bit
problematic
because
it
really
sounds
like
it's
completed,
but
it's
actually
not.
There
is
one
more
step
here.
A
I
know
what
kind
of
license
that
we
need
to
use
geo,
but
it's
it's
not
sufficient
information
provided
here.
So
what
user
can
do
is
Google
like
you,
left
your
application
license
or
navigate
through
our
documentation
again
and
then
find
out
that
we
only
provide
this
feature
for
the
Premium
Plus
user,
which
is
a
bit
confusing,
and
another
thing
was
this,
so
this
is
part
of
the
adding
secondary
note
process
and
based
on
the
documentation.
A
I
should
check
the
gillip
dot
RB
file
again
and
I
can
add
the
geo
node
name
with
the
proper
name
of
the
secondary
and
then
I
can
I
should
reconfigure
and
I
thought
it
was
done,
but
it
was
not
so
actually
what
user
should
do
is
after
adding
the
secondary
nodes
in
the
Gillett
RB
file,
they
still
need
to
go
to
the
primary
node
again
in
the
browser,
and
then
they
still
need
to
add
new
node
here
with
the
exactly
same
name.
It
doesn't
allow
like
space
or
any
typos
on
it.
A
I
should
use
exact
same
name,
so
what
I
did
is
I
need
to
reopen
the
CLI
again
and
go
into
distill
that
dot
RB
file
and
then
check
the
name
and
just
copy
and
paste
it,
because
I
saw
some
errors
at
first
time,
so
I
think
it
could.
It
is
not
that
ideal,
it's
kind
of
like
double
work
for
them
and
didn't
succeed.
Three
interactions
in
total
and
as
I
explained,
all
the
air
to
the
required
number
of
interfaces
was
five.
A
A
So,
based
on
the
grading
rubric
that
we
use
I
rated
this
journey
to
d+,
which
is
a
presentable
level,
they
are
the
excessive
number
of
steps
and
unnecessary
back-and-forth
in
the
flow
we
truly
users
to
feel
unsatisfied,
but
considering
Gio's
main
user
group.
They
have
enough
knowledge
and
Linux
and
configuring
the
database
for
sure.
So
in
the
end,
I
know
that
the
task
completion
rate
might
be
I
had
a
successful
level,
but
probably
the
frustration
level
might
be
high.
A
Thank
you
for
listening
and
please
feel
free
to
ping
me
if
you
have
any
feedback
or
opinion
on
insulin
geo
with
the
baseline
grade.
Here,
our
team
and
I
will
work
on
the
proposed
improvements,
and
this
proposed
improvements
points
will
be
written
down
in
a
separate
issue
and
we
will
revisit
this
insulation
scorecard
in
the
next
few
months.