►
From YouTube: SUS Results for FY22-Q3
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
Hi
everyone,
I'm
adam
smalinski
and
I'm
here
with
nick
hurts
and
nick,
is
here
to
talk
a
little
bit
about
the
findings
from
the
q3
system.
Usability
scale
analysis
so
we're
both
on
the
research
team.
Every
quarter
nick
looks
at
at
this
and
he's
there
to
share
the
results
so
nick
the
burning
question
that
we
all
have
what's
the
score
from
the
past
quarter.
B
B
So
this
is
a
slight
decrease
from
last
quarter,
which
was
but
it's
kind
of
within
the
within
that
margin
of
error.
So
it's
not
a
statistically
significant
drop,
but
it
is
just
kind
of
an
incremental
drop
visually.
We're
right
in
that
okay,
adjective
space,
so
kind
of
in
line
with
some
of
the
the
other.
A
B
Yeah,
absolutely
so
the
big
the
big
thing
was
again
similar
to
the
overall
score.
We
kind
of
we
saw
a
reduction
in
every
cohort
as
well
again
with
still
within
that
margin
of
error,
but
still
an
incremental
decrease,
the
one
that
is
kind
of
I
want
to
draw
more
attention
to,
and
this
is
pretty
consistent
from
quarter
to
quarter
as
well.
B
A
Got
it
so?
My
last
question
before
I
ask
more
about
themes,
I
know
that
sus
is
made
up
of
10
questions
which
allows
you
to
really
dissect
that
score
and
look
for
things
that
are
that
maybe
we're
doing
really
well
at
maybe
things
we're
doing
not
so
great
at
at
all.
I
was
wondering
if
anything
stands
out
at
the
per
question
level.
B
Yeah,
so
on
on
that
per
question
basis,
again
I'll
go
in
a
little
bit
more
detail
around
some
of
the
more
negative
ones,
but,
as
you
can
kind
of
see,
there's
some
questions
around
complexity,
ease
of
use
and
learnability
that
are
on
the
lower
side,
which
is
that
kind
of
leads
into
some
of
the
conversation
we'll
have
about
themes
and
that
sort
of
thing
and
then
on
the
positive
side.
We
do
have
again
this
nice
question
number
one.
I
think
that
I'd
like
to
use
gitlab
frequently
that's
consistently
been
above
our
target.
B
Let
me
see
if
I
can
quickly
get
to
it.
So
that's
a
really
nice
thing
to
see
as
well.
That's
a
positive
sign
is
that
it's
it's
above
our
target.
It's
the
only
question
to
kind
of
remain
at
that
level,
so
people
are
enjoying
using
gitlab,
but
there
are
also
other
people
that
have
some
constructive
feedback
for
us
to
improve,
improve
gitlab.
B
B
You
know
gitlab
being
cumbersome
to
use
and
that's
kind
of
reflected
as
well
in
the
verbatim.
So
one
is
kind
of
complexity.
Gitlab
is
tough
to
use,
especially
to
newcomers.
You
can
kind
of
see
in
these.
You
know
score
breakdowns.
New
users
are
having
the
highest
drops
and
they're
having
you
know
the
lowest
scores
in
general,
so
it's
complicated
to
use
and
that's
reflected
in
the
verbatims
as
well.
So
some
of
that
complexity
is
comes
from
feature
richness.
There's
a
lot
on
the
screen.
There's
a
lot
of
features
they
can
use.
B
They
don't
know
where
to
find
them
always
and
then
there's
kind
of
a
theme
around
a
perception
that
gitlab
is
for
technical
users.
You
know
and
that's
who
really
succeed
in
using
it
and
then,
if
you're,
not
a
technical
user
or
new
to
kind
of
get
or
the
kind
of
this
technology
space
you're
going
to
struggle,
and
so
that's
kind
of
a
perception.
B
That's
we've
seen
a
couple
of
times
and
that
kind
of
leads
to
another
theme
which
is
which
we've
seen
kind
of
consistently
from
quarter
to
quarter
is
learnability
as
well,
and
just
that
there's
a
perception
that
they
need
to
know
a
lot
of
things
to
get
going
in
gitlab
and
and
that
you
kind
of
have
to
learn
a
lot
to
do.
Much
of
anything
and
then
once
again,
support
supported
pretty
well
in
the
verbatims
again
more
than
20
people
mentioned
a
steep
learning
curve
or
requesting
tools
to
make
gitlab
easier
to
learn.
A
B
It's
like
the
overall
score
is
not
significantly
different
than
last
quarter,
but
it
is
a
visual
decrease
and-
and
you
know,
we're
kind
of
seeing
that,
although
I
do
you
know,
there
may
be
some
stabilization
happening
over
the
last
couple
quarters
which
is
really
good
to
see
and
that
kind
of
holds
true
for
the
per
question.
Basis
too,
is
that
some
incremental
decrease,
but
for
the
most
part,
no
change
really
from
from
at
least
from
last
quarter
to
today.
A
B
Yeah
absolutely
great
question,
so
we
actually
did
start
collecting.
We
collected
a
good
amount
of
self-managed
data,
but
for
a
number
of
reasons
we
ran
into
some
difficulties
with
reliably
sampling
self-managed
users.
So
I
won't
kind
of
go
into
the
details
now,
but
the
data
we
produced
was
unreliable
and
didn't
produce
an
accurate
score.
So
we
didn't
want
to
well
one
post,
something
that
we
couldn't
replicate
in
future
quarters
right,
the
sampling
methodology
and
but
and
also
we
didn't
want
to
post
an
unreliable
and
inaccurate
sus
score
for
self-managed
users.
B
Yeah,
so
I
think
there's
a
lot
that
we're
doing
now.
So
at
the
department
level,
we
have
a
couple
krs
around
increasing
sus.
This
is
kind
of
a
consistent
thing.
From
quarter
to
quarter,
we
always
try
to
tackle
an
aspect
of
sus,
and
then
we
have
some
sub
department
krs
around
improving
how
we
administer
sus
and
and
basically
getting
the
data
out
to
the
teams
to
make
it
more
actionable.
B
So
some
of
that's
around
building
a
database
for
sus
verbatims,
part
of
that's,
adding
some
machine
learning
around
sentiment,
analysis
for
the
those
sus
verbatim
and
then
establishing
a
delivery
process
for
those
findings
to
the
stages
of
interest.
So
really
getting
those
actionable
insights
to
the
teams
that
need
them,
and
so
we
can
kind
of
see
if
we
can
move
those
scores
by
improving
the
product.