►
From YouTube: UX Group Conversation - November 8, 2021
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
B
Yeah
hi
chrissy,
thanks
for
the
review
materials
one,
the
question:
is
you
talk
about
learnability
as
a
key
challenge
that
is
impacting
our
system
usability
score.
So
what
are
examples
of
things
that
we've
discovered
that
our
users
are
struggling
with?
Regarding
that
vulnerability,
yeah.
A
This
is
a
great
question.
Thank
you
for
asking
it.
Adam
you've
got
some
stuff
in
there.
I've
got
some
stuff
in
there,
but
I'll.
Let
you
kick
it
off.
C
All
right
thanks
omar
first,
I
want
to
say
thank
you
for
populating
your
questions.
So
early
really
appreciate
that.
So
we
just
completed
a
couple
research
studies
on
this
very
topic,
so
the
timing's
excellent.
C
C
What
I
mean
by
that
is
they
learn
gitlab
by
reading
by
taking
seminars
by
talking
other
people.
C
Structured
learning
is
a
big
one
too,
where
they
have
to
essentially
sign
up
for
step-by-step
courses
that
where
they
build
upon
their
learnings
and
there's
a
lot
that
we
can
do
more
here
us
by
offering
more
learning
material
beyond
the
doc
site,
and
I
will
say
on
a
positive
note,
based
on
my
research
that
that
I've
done
the
doc
site
has
been
doing
a
very
good
job
at
helping
people
learn
so
but
there's
more,
we
can
do
beyond
that
and
chrissy.
A
Yeah,
so
I
just
want
to
clarify
that
that
doesn't
mean
that
these
resources
should
not
be
available
on
the
doc
site.
I
think
what
this
comes
down
to
is
that
there
is
a
lot
of
content
that
users
want.
That
is
not
the
type
of
content
we
currently
have
on
the
docs
site
today.
Today
our
documentation
is
very
feature
focused
and
what
we're
hearing
the
gap
is
is
around
larger,
for
example,
jobs
to
be
done,
more
conceptual
information
and
documentation
is
where
people
will
often
go
to
find
this
type
of
content.
A
This
is
less
about
location
and
more
about
content
type,
and
I
got
a
sneak
preview
this
morning
at
the
decks
that
adam
and
team
are
creating
around
the
learnability
research
that
they've
done
they're
wonderful
and
there
is
a
lot
of
really
great
feedback
for
our
tech
writing
team
in
there.
So
I
know
he'll
be
sharing
that
with
them
as
well.
There
may
be
some
things
that
we
can
go
in
and
just
refine
based
on
what
we've
already
learned
through
qualitative
research.
C
Thanks
for
adding
that
christy
there's
a
couple
other
things,
I
want
to
share
too
around
struggles.
So
another
one
is
that
our
users,
they
have
to
find
the
all
these
resources
that
I
mentioned
earlier
themselves
and
google
is
typically
their
starting
point.
But
today
it's
not
that
easy
and
a
big
downside
to
that
is
it
takes
them
a
lot
of
time,
so
they
have
to
search
for
things.
Sometimes
they
don't
even
know
the
proper
terminology
on
what
they're
searching
for
you
can
imagine
what
a
struggle
that
might
be.
C
And
lastly,
what
I
want
to
talk
about
is
just
learning
gitlab.
It
takes
longer
than
initially
planned
by
users.
It's
and
the
main
reason
for
that
is
because
their
day-to-day
job
gets
in
the
way.
So
they
want
to
learn.
They
want
to
learn
more
about
other
features,
but
they
just
can't
really
find
the
time.
C
This
also
really
applies
to
not
only
new
users
but
experienced
users
too,
because
they
can
they
have
an
idea
of
like
I
have
a
feeling
that
gitlab
can
do
more
for
me,
but
I
just
don't
really
have
the
time
to
allocate
towards
it.
So
there
might
be
things
that
we
can
be
doing
to
service
up
some
of
those
other
features
and
learnings
a
little
bit
easier
for
people,
hey
christy.
You
had
some
comments
too.
A
A
We
also
know
that
learnability
is
a
challenge
for
our
competitors
too,
but
we
want
to
note
it's
an
even
bigger
challenge
for
us
than
it
is
for
our
competitors,
and
we
know
that
as
part
of
that
qualitative
research,
we
do
have
some
guidance
from
users
on
the
types
of
content
that
they
want.
I
put
a
few
examples
in
the
agenda.
That
is
not
a
comprehensive
list,
but
just
to
give
you
a
sense
of
what
we're
talking
about
here.
A
I
also
want
to
note
that
in
q4
that
tech
writing
team
has
a
kr
to
create
a
tutorials
page
on
the
docs
site,
this
is
going
to
be
an
mvc
and
the
plan
is
to
initially
populate
it
with
existing
content.
We
just
want
to
get
a
page
out
there
someplace
for
this
content
to
live
where
we
think
people
will
be
able
to
find
it
and
get
as
much
good
content
on
there
as
we
can.
That
will
not
be
the
end
of
that
project.
A
The
idea,
then,
is
to
get
contributions
from
a
wide
variety
of
sources,
to
flesh
out
that
content,
the
way
that
users
are
asking
us
to
do,
and
then
lastly,
adam,
is
leading
the
ux
research
team
and
creating
an
epic
and
associated
issues
focused
on
learnability,
we'll
also
be
creating
a
video
that
we
will
link
to
from
that
epic.
So
we
can
talk
through
all
of
these
things
that
we've
learned
and
that
we
know-
and
you
know
to
be
documented
in
inside
of
our
products-
everybody
has
access
to
it.
B
Great,
thank
you
so
much
for
the
answer
and
it
seems,
like
you
know,
there's
potentially
quick
wings
in
the
documentation
side,
then
integrating
it
into
their
products.
So
people
don't
have
to
search
on
google
to
find
these
things.
So
that
sounds
really
great.
I
have
a
second
question
as
well,
which
is
how
do
you
see
our
learnability
challenges?
Evolving
as
we
look
to
mature,
more
categories
in
the
product
and
getting
a
wider
range
of
users
on
board.
A
Yeah,
that's
a
really
thoughtful
question,
so
a
complaint
that
we
commonly
hear-
and
we've
heard
for
a
very
long
time-
is
that
our
product
is
already
very
complex.
We
hear
things
like
you,
keep
adding
more
and
more
stuff.
You
know
that's
great,
that
you
have
these
features,
but
it
was
already
complicated
to
begin
with.
A
So
the
more
of
that
that
we
do
the
more
risk
we
run
of
having
a
negative
impact
on
learnability,
I'm
really
glad
so
many
of
our
our
designers
and
researchers
are
here
on
this
call
today,
because
this
is
something
we
haven't
discussed
a
lot
yet
yet
as
a
department
we
will
be,
but
all
of
this
information
is
just
kind
of
coming
together.
Right
now,
so
I'll
say
one
of
the
things
we
have
to
get
better
at
leading
our
our
cross-functional
teams
in
doing
is
considering
learnability
at
every
stage
of
the
process.
C
A
Start
thinking
about
learnability,
if
that
goes
into
development,
make
sure
you
look
and
make
sure
that
we
are
including
that
and
that
it
doesn't
get
d
scoped
from
the
mvc
and
then
lastly,
really
being
thoughtful
about
our
documentation
and
making
sure
that
we
are
putting
learnability.
First,
as
we
are
documenting
new
things
jerick,
you
wanted
to
add
something
there
yeah.
D
Sure,
since
it's
very
closely
related,
if
not
directly
related,
we
recently
shipped
our
first
iteration
to
our
empty
state
docs.
So
up
until
recently,
we've
been
using
a
component
when
there's
an
empty
state,
and
we
say
here's
what
this
feature
does
check
out
the
docs
or
you
know,
go
link
out
somewhere.
So
this
update
really
refocuses
us
to
think
about
on
a
case-by-case
basis.
How
can
we
increase
learnability
and
not
just
link
to
docs,
even
though
they're
incredibly
useful
and
they're
going
to
be
useful
in
a
lot
of
cases?
D
But
you
know
what
can
we
do
to
be
more
creative
to
make
things
more
engaging
to
make
it
easier
to
understand
so
that
they
don't
have
to
be
going
back
and
forth
and
they
can
understand
it
right
when
they
see
it.
So
that's
just
something
that
I
wanted
to
note.
It's
our
first
iteration
and
we'll
be
continuing
to
work
on
that
as
well.
B
E
Hey
christy,
hey
adam
love,
the
deck
that
was
really
informative,
thanks
for
putting
that
together,
kind
of
like
tangentially,
related
buyer
and
user
personas
kind
of
related
to
learnability
they're,
never
perfect,
but
I
was
just
curious
if
you
all
have
plans
to
revisit
update
them.
E
I've
looked
through
the
handbook.
I
found
some
I've
kind
of
I'm
always
suspect
of
personas,
so
I
was
kind
of
trying
to
find
out
like
okay.
Well,
who
made
these?
What
data
were
we
using?
And
the
answer
is,
I
don't
know
we're
not
sure
which
makes
me
be
like
okay?
E
Well,
I'm
not
going
to
use
them,
but
yeah,
it's
kind
of
like
this
buyer
or
potential
customer
to
becoming
a
user,
like
that's
a
really
important
learnability
moment,
and
if
we
had
a
single
source
of
truth
or
just
a
shared
understanding
like
this
is
our
understanding
from
talking
to
real
people.
That
would
be
immensely
helpful
to
me,
and
I
was
just
wondering
if
that
was
on
your
radar.
A
Well,
blind
trust
in
personas
is
a
rookie,
so
good
on
ya
for
being
suspicious
yeah.
This
is
actually
really
good
timing.
We
are,
we
are
thinking
a
lot
about
personas
right
now.
Adam
is
really
been
leading
the
charge
on
this.
Let
me
turn
this
over
to
him.
C
Yeah,
hey
michael
so
researcher
on
my
team
named
michael
oliver,
he's
been
spearheading
the
effort
there
because
we
were
recently
asked
to
create
a
new
persona
and
we
started
to
dig
around
a
little
bit
and
realize.
Oh,
we
don't
really
have
a
process
for
that
which
you
probably
ran
across
yourself,
so
we
have
been
working
to
create
a
process
on
creating
personas
based
on
data,
so
mainly
based
on
ux
research.
So
there's
about,
I
think,
about
a
five
step
process.
C
There's
a
draft
we're
just
putting
together
a
draft
mr
for
it
probably
this
week.
It
will
go
out
and
from
that
point
I
don't
know
if
it's
something
your
team
world
might
borrow
from
the
buyer
personas
perspective,
but
that's
totally
an
option
and
yeah
to
talk
about
whether
we're
going
to
revisit
our
existing
ones.
E
That
sounds
great
I'll,
definitely
definitely
borrow
borrow
or
steal,
because
everything
we've
done
so
far
has
what
we've
taken
from
your
team.
That's
worked
out
great
and
no
rush.
Let's,
let's
do
it
once
and
get
it
right.
So
hopefully
I'm
not
rushing
things
for
you
not
at
all.
A
And
steal
away,
that's
we
want
you
to
that's
the
point,
so
that's
wonderful
that
you
have.
I
do
want
to
call
out
release
explicitly
because
adam
kind
of
inferred
this
in
his
answer,
but
really
clearly
our
ux
research
team
is
focused
on
product
users,
not
buyers.
So
you
know,
if
you
don't
see
us
working
on
buyers.
C
A
E
Definitely
I'll
maybe
for
q
force
we're
focused
on
something
else,
but
yeah.
Let's
talk
about
that
and
cue
that
up
for
q1.
A
My
tolerance
for
silence
is
very
high,
as
my
department
knows,
but
I
want
to
give
everybody
a
chance,
because
I've
been
surprised
before
people
do
come
up
with
things
kind
of
after
a
good
30
seconds
or
so,
but
I
think
it's
been
long
enough.
If
you
do
have
follow-up
questions
that
you
think
of
later,
you
know
how
to
find
us.
Thank
you
for
joining
us
today.
I
hope
you
have
a
wonderful
rest
of
your
day.
Bye.