►
From YouTube: SUS Results for FY22Q2
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
A
A
A
So
if
we
take
a
deeper
look
into
the
suscor,
the
individual
questions
in
particular,
what
we're
looking
for
is
on
the
individual
questions
scores
that
are
lower
than
the
overall
sus,
so
anything
lower
than
68.3.
Those
questions
if
they
are
lower,
indicate
areas
of
concern
for
us.
So
we
use
those
kind
of
these.
Those
themes,
kind
of
dig
deeper
into
the
questions
and
uncover
other
usability
issues.
So
in
this
case
you
can
kind
of
see
the
ones
highlighted
in
yellow
and
I'll
also
dive
deeper
into
these
as
well
as
I
was
mentioning
earlier.
A
Although
we've
seen
increase
in
both
these
questions
in
this
quarter
compared
to
the
previous
quarter,
these
are
still
two
of
our
lowest
scoring
sus
scores
and
what
is
kind
of
bringing
the
overall
sus
score
down
as
well.
A
So,
just
to
kind
of
look
a
little
bit
deeper
in
this.
I
I
pulled
out
a
couple
of
verbatims,
but
more
than
30
verbatims
mentioned
a
steep
learning
curve
or
or
users
requesting
tools
to
make
gitlab
easier
to
learn.
So
some
examples
are,
you
know:
documentation
wasn't
trivial
to
understand
that
the
learning
curve
was
steep
for
that
particular
feature.
A
It
didn't
feel
intuitive
enough
to
a
new
user,
with
a
lack
of
experience
in
online
repositories
and
the
basics
of
git
labs
are
the
basics
of
gitlab
are
easy
to
learn
and
to
use,
but
after
the
learning
curve,
after
that,
the
learning
curve
gets
very
steep.
So
that
was
a
very
common
kind
of
sentiment
in
that
it's
it's
hard
to
kind
of
get
going.
There's
a
lot
of
features
in
gitlab
and
using
them
to
the
you
know
utmost
potential
for
a
user.
It
was
hard
to
do
and
hard
to
learn.
A
Another
set
of
themes
that
again
was
was
part
of
the
reason
our
overall
sus
was
what
it
was.
Is
users
are
encountering
encountering
complex
and
cumbersome
experiences,
so
the
questions
related
to
complexity
and
cumbersomeness
were
also
relatively
low.
I
think
a
lot
of
this
had
to
do
around
navigation
and
discoverability.
A
A
A
So
one
of
those
okrs
is
helping
drive
category
maturity
forward
by
pre-validating
jobs
to
be
done.
A
As
I
mentioned,
our
another
main
focus
of
of
this
quarter
and
next
quarter
is
learnability,
and
so
this
quarter
we
conducted
a
follow-up
study
with
participants
from
last
year's
sus
to
basically
compare
now
versus
a
year
ago
and
with
the
underlying
theme
they're
pretty
consistent.
Actually
it
was
the
theme
was
that
learnability
was
the
most
common
reason.
A
Gitlab
wasn't
easy
to
use.
What
we
saw
was
a
slight
improvement
in
usability
over
last
year,
but
the
main
reason
why
behind
their
ratings
was
whether
they
were
getting
used
to
it
or
not.
Basically,
were
they
developing
a
cow
path
through
gitlab
learning,
what
they
needed
and
kind
of
ignoring
the
more
complicated
tasks
or
features.
A
This
is
kind
of
key
is
if
we
can
make
git
lab
more
learnable,
we
can
make
gitlab
more
usable
in
particular,
that
we're
we're
planning
to
conduct
a
longitudinal
study
where
we
follow
git
lab
users
from
basically
right
when
they
join,
and
you
know,
have
their
first
experience
with
the
product
and
following
them
for
up
to
eight
weeks
and
seeing
how
they
they
learn,
what
their
obstacles
are,
what
their
pain
points
are
where,
where
can
we
facilitate
learning,
and
how
can
we
make
the
product
more
usable?