►
Description
Anne joins to give the UXR readout of our round 1 tests on the 6 prototypes.
A
A
Before
I
turn
over
to
ann,
I
also
just
wanted
to
mention
that
we
did
schedule
menu
menu,
which
has
been
an
issue.
That's
been
open
for
a
while.
We
have
a
design
for
that
that
one
is
in
15
4
in
this
release
and
we
are
going
to
be
shipping
that
by
end
of
this
release,
so
it's
really
exciting.
This
is
a
small
update
to
navigation.
That's
a
really
positive
improvement
and
we're
going
to
get
it
out
in
this
release.
A
So
high
level,
that's
kind
of
what's
happened.
The
last
two
weeks,
given
that
we're
investing
on
design
and
uxr
and
is
here
to
go
through
the
early
stage,
concept,
validation
and
the
insights
from
the
tests.
So
the
tests
we've
been
talking
about
of
the
sixth
design
she's
going
to
go
through
right
now
and
say
kind
of
all
of
the
data
around
what
they've
seen
from
users
and
what
are
our
next
steps
from
that,
and
I
just
want
to
reiterate
that
we
it's.
This
is
a
huge
uxr
test,
an
investment
from
from
a
design
side.
A
We
don't
usually
do
this
at
git
lab.
It
is
different
and
we
are
taking
a
quarter
or
two
to
make
sure
that
we
have
the
right
design.
So
having
ann
go
through
these
all
of
the
insights
that
they've
gotten
and
the
rigor
with
which
they've
tested
these
six
designs
is
really
cool,
and
so
I'm
gonna
hand
it
over
to
her
and
let
her
show
kind
of
what
they
discovered
doing.
These
tests.
B
B
What
that
means
is
that
the
design
team
had
basically
six
different
design,
ideas
that
address
no
navigation
challenges
and
the
goal
of
this
research
was
to
narrow
down
the
number
that
we
could
take.
You
know
and
those
narrowed
down
numbers
of
design
concepts.
You
know,
take
them
into
additional
rounds
of
research
and
further
down
the
line
and
why
we
do
this
at
this
point
is,
or
this
concept
validation
basically
helps
to
understand
which
elements
of
these
concepts
resonate
well
with
users
like
what
stands
out
to
them.
B
So
it's
important
to
remember
that,
like
none
of
the
participants
saw
all
of
the
concepts,
they
just
saw
a
selection
of
two
that
were
randomized
like,
but
that
were
shown
to
them
in
a
randomized
way
and
for
each
concept
we
asked
participants
to.
You
know
state
their
general
impressions
on
the
concept.
B
Basically,
and
the
reason
for
that
is
because
we
had
six
different
design
ideas
and
it's
not
very
efficient
to
basically
create
six
interactive
prototypes
and
then
take
these
through
testing,
because
that
generates
a
lot
of
data,
but
instead
it's
better
to
just
use
a
static
image,
because
we
wanted
to
only
get
these
first
impressions
from
people
and
these
first
indicators
on
how
they
would
go
about
certain
tasks.
And
that's
basically
enough
to
you
know,
make
a
decision
on
okay.
B
You
know
more
enhanced
data
and
and
get
more
depth
of
the
data
for
those
that
are
not
very
familiar
with
the
concepts
in
the
slide
deck
I
outlined
them
basically,
and
also
in
the
appendix
you
see
larger
images
of
them
and
a
more
detailed
description
of
what
each
concept
is
about,
but
at
a
high
level
I
want
to
say
that
there
were
three
concepts
that
pretty
much
stuck
with
the
traditional
layout,
so
concept,
one
two
and
also
concept.
Four.
B
What
I
mean
by
that
is
they
had
a
sidebar
and
they
had
a
top
bar
and
but
the
content
and
how
things
were
arranged
in
the
left.
Sidebar
was
different,
but
then
there
were
also
concepts
like
concept,
three,
five
and
six
that
basically
broke
with
that
pattern,
and
they
had,
for
instance,
just
you
know:
everything
moved
basically
to
the
left
side
bar
or
they
may
even
have
two
left
side
bars.
B
So
just
keep
that
in
mind
and
before
I
go
into
the
insights
just
to
you
know
to
remind
everyone
in
that
again
with
this
research
we
cannot
say
which
design
is
the
best
one
or
which
one
to
move
forward
with
or
like
that's
the
new
design
to
take.
Simply
because
again,
it
was
not
an
interactive
prototype,
so
it's
more
a
gut
level
check
of
like
you
know
how
people
feel
about
these
concepts
and
again
not
everyone
saw
all
the
concepts.
So
people
only
saw
a
selection
of
the
concepts.
B
So
we
definitely
need
more
research
to
understand
usability
challenges
better
and
also
how
people
feel
about
these
concepts
over
time.
All
right.
But
let's
talk
a
little
bit
what
we
know
in
terms
of
how
people
feel
about
these
concepts
and
what
I
want
to
start
with
is
that
there
were
elements
in
the
concepts
that
participants
universally
appreciated.
B
Things
like
the
breadcrumb,
for
instance,
really
really
helps
with
orientation.
It
was
something
that
people
continuously
pointed
towards
when
we
asked
them
where
they
were
in
a
concept
or
also
when
they
wanted
to
backtrack.
So
that's
something
super
important
that
any
concept
should
have
search
bar
on
the
top,
and
people
feel
really
strongly
about
that
one
and
that
the
search
belongs
to
the
top
bar
and
not
in
the
left.
Sidebar.
B
You
know
the
verbatim
that
we
heard
is
that
it's
really,
you
know
that's
a
standard,
it's
very
common
to
have
it
there
and
people
didn't
really
feel
like.
We
should
move
away
from
that
also
having
the
option
to
collapse.
The
sidebar
to
increase
the
center
space
is
super
important
for
people
because
they
do
value
the
space
they
have
in
the
center
and
also,
generally
speaking,
people
liked
if
there
were
just
a
few
menu
options
in
the
in
the
left
sidebar.
So
you
know,
making
efforts
to
reduce
the
amount
of
items
in
the
left.
B
One
of
the
concepts
included
a
pinned
section
which
basically
pinned
where
people
could
pin
an
item
that
is
relevant
for
them
or
even
too,
and
that
was
seen
as
a
great
aspect
of
customization
and
putting
things
in
the
sidebar.
That's
that
is
most
relevant
to
a
user,
so
people
that
saw
concept
6.
We
heard
a
couple
of
people
refer
to
it,
saying,
like
add
this
pin
section
to
other
concepts
as
well,
so
it
was
something
that
people
generally
liked.
B
The
other
concept
basically
received
less
votes,
and
you
could
interpret
that
as
they
were
like
less
favored.
You
might
wonder
now
why
that
is
and
for
concept,
breadcrumbs
and
parent
items
only.
They
were
generally
speaking
easier
to
grasp
because
they
were
simpler
in
their
layout
and
they
didn't
really
introduce
any
new
functionality.
B
If
you
wonder
how
I
got
to
these
statements,
we
had
rating
scales
as
part
of
the
test
setup.
So
we
had
these
different
statements
that
address
no
navigation
challenges
and
we
ask
people
to
what
extent
they
agree
or
disagree
with
it.
So,
in
this
case
the
statement
was
all
around
ease
of
use
and
we
can
see
that
basically
concept,
one
and
four
receive
the
highest
agreements
there,
followed
by
concept.
B
In
this
research
we
didn't
really
assess
how
motivated
people
would
be
to
learn
like
that
was
not
the
focus,
but
it's
something
to
keep
in
mind,
because
we
have
heard
this
feedback
in
the
past
that
people
struggle
with
learning
gitlab
and
that
it
takes
time,
and
that
is
not
an
easy
thing
to
do
so.
We
should
be
very
conscientious
about
introducing
new
things
and
asking
users
to
learn
things
and,
and
if
we,
you
know
do
that,
we
should
think
about
how
to
best
support
users
and
learning
like
a
new
nav
or
any
new
content
really.
B
Lastly,
I
want
to
touch
upon
two
things.
A
positive
thing
is
that
we
asked
users,
you
know
how
easy
they
can
orientate
themselves
across
the
platform
platform.
We
had
a
statement
there
as
well
and
what
we
can
actually
see
that
most
concepts
really
allowed
users
to
orientate
themselves
in
a
good
way,
so
they
would
either
point
to
the
breadcrumb
or
to
items
highlighted
in
the
left
sidebar
when
we
asked
them
where
they
are,
and
you
know-
and
they
knew
basically
where
they
are
at
even
the
concepts.
B
Five
and
six
that
were
the
rankings
were
a
little
bit
lower.
They
are
still
leaning
towards
agreement,
so
we
can
generally
say
that
the
concepts
tested
so
far
at
this
level
and
this
fidelity
people
felt
you
know
comfortable
knowing
where
they
are
last
point
I
want
to
touch
upon
are
the
tasks
that
we
asked
people
to
do.
B
These
tasks
were
selected
quickly.
Let
me
jump
here
because
they
are
applicable
to
a
broad
range
of
users,
so
we
didn't
want
to
introduce
at
this
point
any
tasks
that
are
specific
to
developers
only
or
specific
to
product
managers.
So
we
looked
at
tasks
that
are
you
know
that
any
gitlab
users
could
do
or
might
be
doing,
and
what
we
see
that
here
is.
B
There
was
basically
one
task,
finding
an
issue
or
seeing
all
issues
for
the
orange
project,
which
was
pretty
much
easy
to
do
across
all
concepts,
except
for
concept
2,
because
that
was
the
only
concept
where
issues
was
not
a
specific
item
in
the
left
sidebar.
It
was
basically
a
submenu
item
and
people
struggled
to
identify
it
there.
B
The
second
task,
which
was
around
creating
an
epic,
received
mixed
results
across
all
concepts,
and
the
main
challenge
here
was
how
good
were
people
in
understanding
the
difference
between
groups
and
projects
and
basically
knowing
that,
in
order
to
create
an
epic,
they
would
need
to
go
back
to
the
group
level.
If
people
weren't
aware
of
that,
then
they
struggled
with
that
task.
If
they
were
aware
of
it,
then
they
knew
what
they
needed
to
do
and
succeeded
in
it.
B
B
At
this
point,
I
cannot
tell
you
which
concepts
or
which
hybrid
concepts
we'll
look
at,
because
that's
basically
a
decision
to
come
from
design
which,
which
will
come
in
the
next
couple
of
days,
but
from
the
research
side
of
things.
What
we
want
to
do
more
next
time
is
to
have
a
more
structured
approach
to
different
personas,
and
so
in
specific,
you
want
to
look
at
developers,
product
managers
and
security
professionals.
B
I'll
mention
on
these
insights
is
that,
as
you
go
through
the
report,
I
just
talked
about
the
high
level
findings
and
how
these
concepts
compare
against
each
other.
But
in
the
report,
you'll
have
a
section
where
I
talk
about
detailed
insights
per
concept,
so
you
can
basically
consume
at
your
own
time
how
each
concept
resonated
with
users
and
how
they
how
they
felt
about
it.