►
From YouTube: UX Group Conversation (Public Stream)
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
Not
yet
so
let
me
just
go
ahead
and
vocalize
this
one,
a
new
says:
I
learn
how
customers
use
our
product
by
going
over
the
ux
showcases
love
the
synthesis
by
pedro
on
making
the
mr
widget
lovable
and
other
ux
showcases.
Thank
you
kai
for
helping
create
room
and
prioritizing
this.
I
look
forward
to
the
improvements
me
too.
I
was
really
excited
about
this
one.
A
A
In
my
job,
I
too
was
thrilled
to
see
pedro
talking
about
how
he
and
kai
collaborated
to
in
parallel,
have
debt
and
bug
fixes
get
addressed,
while
also
giving
pedro
the
space
to
take
a
deeper
look
at
the
mr
widget,
which
is
absolutely
critical
to
our
ex
product
experience
and
then
push
both
things
forward
at
the
same
time,
that
was
amazing,
truly
great
collaboration
between
them
all
right.
Nicole.
B
So
for
slide
11,
you
indicated
the
different
patterns
were
going
to
get
updated
on
the
buttons,
and
I
believe
that
also
is
going
to
help
with
our
accessibility
which,
as
somebody
who
has
to
currently
use
high
contrast,
if
you
can't
tell
by
it,
looks
like
I'm
sitting
in
the
sun
and
super
bright
monitors.
I'm
super
excited
about
that.
C
Yeah,
I
was
just
gonna
say
thanks
for
putting
this
in
nicole
and
yes,
there
was
a
concern
over
distinguishing
between
red
and
orange
buttons,
because
we
were
using
orange
buttons
for
warning
users,
and
so
there
was
just
a
number
of
benefits
to
simplifying
our
bot
invariants,
and
this
was
definitely
one
of
them.
D
A
Yeah,
I'm
super
excited
about
this
too.
This
was
one
of
our
okrs
during
q4
was
to
uncover
these
themes,
so
we
can
go
in
and
feel
confident
that
we're
focused
on
the
right
stuff.
I'm
gonna
turn
this
over
to
adam,
but
also
I'll,
say:
we've
got
an
okr
during
q1,
where
we'll
focus
on
two
of
those
themes
which
are
system,
performance
and
ui
polish
and
wheels
are
already
in
motion.
I'm
super
excited
about
both
but
adam.
Can
you
remind
us
what
the
other
four
themes
are.
E
Within
these
themes
we
actually
identified
sub
themes
also
because
we
just
there's
just
so
many
items,
slash
issues
that
we've
looked
through
across
10
data
sources,
so
we
had
about
800
individual
data
points
that
we
sub
themed
them
into
so
under
general
usability.
There's
things
like
making
things
easier
in
general,
reducing
confusion.
Things
like
that.
E
E
There
we
go
so
yeah,
so
I
linked
this
in
the
question.
Also
sid,
oh
okay,
missed
that!
Thank
you,
oh
yeah,
sure
yep.
E
D
A
Yeah,
what
I'll
say
as
an
addendum
to
that
is
our
system
usability
score
came
in
for
q4
in
q3
it
was
70.9
in
q4.
It
was
70.8.
A
This
is
actually
cause
for
celebration
because
in
q3
it
dropped
by
half
a
point
in
q2.
It
dropped
by
a
full
point.
So
what
we're
seeing
here
is
a
turnaround,
I
hope,
and
the
start
of
moving
in
an
upward
direction,
which
is
obviously
what
we
want.
What's
the
difference,
we've
been
focusing
on
refinement.
We've
done
a
ton
of
work
on
system
performance,
we've
done
work
on
other
things.
We
had
no
kr
around
general
polish
stuff
last
quarter,
so
we're
already.
A
A
A
F
I'll
ask
a
question.
Sorry,
I
was
not
prepared
to
ask
one,
but
I
know
recently
I've
been
thinking
kind
of
about
how
you
like
to
think
about
how
we
design
for
different
audiences
and
make
experiences
consistent
across
the
stages
and
things
like
that.
I
know
we
have
a
lot
of
krs
related
to
that
that
have
been
going
on
and
probably
coming
up.
If
you
have
any
thoughts
on
what
you
think
are
best
practices
for
keeping
us
out
of
silos
and
things
like
that.
A
Yeah,
what
a
great
question
and
it's
it
must
be
the
theme
of
the
day,
because
I
had
a
skip
level
earlier
earlier
today,
where
some
folks
brought
this
up
too.
A
So
all
right,
I'm
gathering
my
thoughts
because
I
wasn't
prepared
for
this
question
a
point
of
differentiation
for
us,
so,
okay,
so
as
a
platform,
we're
doing
something
really
innovative
by
bringing
so
many
disparate
tools
into
one
place,
and
we've
done
a
really
good
job
of
that
one
of
the
ways
I
think
that
we
got
to
where
we
are
as
quickly
as
we
did
was
that
we
really
let
teams
just
kind
of
go
independently
with
no
dependencies
and
just
get
stuff
in
there.
That's
great!
A
That's
wonderful
that
we
did
that
our
differentiator,
I
think,
is
going
to
be
connecting
those
things
and
turning
them
into
a
seamless
experience,
and
that's
that's
where
we're
headed
next.
So
when
you
look
at
the
okr,
we
have
this
quarter,
which
anup
requested
again
having
his
collaboration
on
ux
is
jeff's
kiss
love.
It
love
love
working
with
a
noob.
A
It
is
on
doing
cross
stage
research
to
really
understand
the
beginnings
of.
Where
are
those
points
where
we
need
to
be
connecting
things
in
more
refined
ways
and
figuring
out,
then
how
we
can
work
together
to
make
that
happen?
When
we
look
at
our
user
research,
we
get
comments
about
this
right.
A
We
get
a
lot
of
people
say
very,
very
positive
things
about
our
product
to
be
clear,
but
sometimes
when
we
hear
negative
things
it
is
about,
like
things
are
hard
to
find,
I'm
not
sure
you
know
when
I'm
trying
to
complete
a
task.
I
have
to
go
here
and
then
I
have
to
go
over
there
and
then
maybe
I
have
to
go
over
there.
So
the
point
is
start
to
bring
those
things
together
and
just
smooth
that
out
and
make
it
easier.
So
how
can
we
do
that?
A
That
was
really
the
core
of
your
question,
so
one
we
need
to
have
a
better
understanding.
I
think
we've
got
assumptions
right
now
about
where
those
things
happen,
but
user
research
is
going
to
help
us
understand
like
where
do
you
cut?
Where
do
our
users
care
about
these
things-
and
I
think
part
of
this
also
is
just
culturally
sharing
more
information,
so
the
ux
showcases?
A
A
F
F
G
G
So
we
have
those
negative
themes.
We've
also
have.
We
know
how
gitlab's
ux
is
generally
perceived
and
usually
there's
a
natural
tendency.
G
I
think
that's
human
to
point
out
what
is
not
so
good
instead
of
what
is
great
and
what
are
the
delightful
moments
in
gitlab's
ux,
and
we
see
that
everywhere,
like,
for
example,
when
something
is
posted
on
reddit
regarding
gitlab
the
product,
we
have
more
comments
about
people
complaining
about
the
ux
or
even
people,
thinking
about
transitioning
and
others,
comments,
saying:
hey:
no,
don't
transition
to
gitlab,
because
the
ux
has
this
problem
or
the
ui
is
complex
or
this,
and
that-
and
this
is
also
felt
internally
by
many
members
of
the
ux
team-
that
our
the
the
ux
of
our
product
is
worse
when
we
compare
them
to
the
specific
products
that
we're
competing
with
in
the
specific
stage
groups
right
so,
for
example,
in
source
code.
G
If
we
would
compare
just
the
source
code,
features
of
gitlab
with
the
source
code
features
of
github,
for
example,
many
of
our
team
members
in
ux
think
that
they're
worse,
and
this
is
not
to
say
that
we're
not
doing
a
good
job,
but
we
still
have
a
long
way
to
go.
So
my
question
is,
after
all,
this
preamble.
A
Yeah,
I
love
this
question,
so
I'm
gonna
unpack
two
pieces
of
this
there's
the
external
and
the
internal
okay,
we'll
start
with
the
external
look.
A
There
is
no
scenario
in
which
every
single
user
thinks
that
our
ux
is
perfect.
I
would
love
for
that
to
be
the
case,
but
it's
just
not
real
people
think
in
different
ways.
It's
you
know
it
is
what
it
is.
That
being
said,
pedro,
you
brought
up
a
really
good
point,
which
is
people
don't
verbalize
generally,
when
they're
happy
they
verbalize
when
they
have
something
to
complain
about.
So
we
get
exposure
to
that
on
a
really
regular
basis.
A
I
want
to
say
20
of
those
were
people
saying
your
ux
is
awesome.
Your
product
is
amazing.
I
love
it
I'll,
never
use
anything
else.
It's
changed
my
life,
you
look
at
the
score.
They
give
us
on
sus
67,
68
70..
I
don't
know
where
those
two
things
are
bumping
up
against
each
other.
I
think
that's
an
interesting
thing
for
us
to
take
a
look
at,
but
the
point
being
that
people
do
love
our
product.
A
We
work
on
a
really
good
product
that
helps
people
in
their
day
to
day
they
rely
on
it,
they're
excited
about
it,
and
then
they
have
legitimate
complaints
that
we
need
to
go
address
right
internally.
A
F
A
A
That's
important,
that's
what
we
should
be
doing,
but
it's
also
important
to
take
a
step
back
every
once
in
a
while
and
go
yeah,
but
in
the
greater
scheme
of
things
this
is
a
great
product,
and
so
that's
why
I
committed
to
all
of
you
that
I
would
do
a
better
job
of
when
I
see
these
types
of
really
positive
comments
from
users
and
customers.
I
will
surface
them
to
you
to
remind
you
that
hey
you're
working
on
a
product
that
makes
a
difference
in
the
world
and
that
you
should
feel
really
proud
of.
A
That
is
also
part
of
the
reason
why,
in
the
future,
we're
going
to
do
more
competitive
analysis
work.
So
one
of
our
okrs
this
quarter
is
the
leaders
are
setting
up
a
framework
for
the
designers
to
be
able
to
do
that
with
the
appropriate
scope
and
and
to
do
it
effectively.
A
But
I
don't
think
that
we
get
enough
exposure
to
other
products
that
are
in.
Like
their
competitors
with
our
individual
stage
groups-
and
I
think,
as
we
start
to
look
at
those
products
in
more
depth,
two
things
are
gonna
happen.
So
one
is
we're.
Gonna,
see
some
really
cool
ideas
and
we're
gonna
go.
Oh
we're
not
doing
that.
Maybe
we
should
be.
On
the
other
hand,
we're
gonna
see
some
things
where
we
go.
Oh,
we
do
that
better,
we're
doing
a
really
good
job.
A
So
I
think
my
the
tldr
of
this,
for
me
is
we've.
Got
a
we've
got
a
great
product.
We've
got
a
strong
foundation.
G
Yeah
yeah,
thank
you.
Thank
you!
So
much
chrissy
and
it's
as
you
said,
it's
difficult
to
unpack.
All
of
that,
and
there
are
many
things
that
play.
I
think
the
general
sense
usually
and
I'll
speak
for
myself
because,
as
as
you
also
said,
we're
we're
paid
to
spots
like
what
is
wrong
and
how
we
can
improve
it
right
where
we
have
a
very
clinical
and
critical
eye
to
our
product.
But
I
think
it's
easy
for
people
to
become
more
pessimistic
when
they're
in
this
mode.
G
All
the
time
and,
of
course,
if
we
are
always
bragging
about
how
great
our
ux
is,
it
would
probably
have
the
opposite
effect
and
we
think,
oh
maybe
we
don't
need
to
work
so
hard,
because
everyone
feels
it's
great,
but
I
think,
as
you
said,
like
some
positive
reinforcement
here
and
there.
I
think
it's
good
and
also
just
as
a
catalyst
as
a
way
to
motivate
the
wider
community
to
also
feel
different
and
perceive
our
ux
differently.
G
And
I
want
to
like
the
great
example:
is
certain
designers
in
the
team
have
started
sharing
what
they're
doing
more
on
social
media,
for
example,
and
trying
to
get
more
attention
and
people
are
getting
really
really
excited
about.
Seeing
the
the
works
in
progress,
the
alphas
all
of
those
napkin
sketches,
and
things
like
that.
So
I
wish
we
continue
to
do
that
more
because
we
need
to
turn
the
tithe
basically.
A
Yeah,
I
agree
and
by
the
way
I
read
every
one
of
those
blog
posts
and
I
love
them
and
get
so
excited
when
I
see
them
I'm
putting
one
together
right
now,
that's
gonna
highlight
when
you
look
at
the
slides
and
the
interesting
things
we're
working
on
part
of
the
group
conversation
deck.
It's
gonna
put
those
into
a
public
blog
post
to
make
them
more
visible,
so
yeah,
I
think
more
things
like
that.
We
can
do
the
better
okay,
I
think
sid
is
up
next.
D
Yeah
it
feels
like
I'm
responding.
Much
of
this
was
independent.
I
saw
the
competitive
analysis
by
pedro,
which
I
thought
was
really
well
done.
It's
like
10
seconds
and
you
kind
of
have
a
good
idea
of
how
you
compare.
I
thought
that
was
really
cool
thanks
for
that.
I
think
it's
great
if
we
compare
ourselves
there's
so
many
point,
solutions
we'd
have
which
have
a
lot
of
experience
with
them,
and
we
can
kind
of
learn
from
that.
D
Why
is
that
point
solution
working
like
that,
and
what
can
we
learn
so
really
cool
and
then
chrissy?
When
you
said
look
we
have
people
who
really
love
the
product
who
love
how
it
works
and
they
still
give
us
a
low
score.
I
was
thinking
of
our
kind
of
design
halo.
Are
we
known
for
good
design
practices
and
I
think
sometimes
we
are
a
bit
held
back
by
our
history.
D
I
think
some
of
our
main
competitor
is
known
for
good
design
and,
frankly,
if
I,
if
I
look
at
it,
it's
it's
because
I'm
used
to
it
that
it
looks
okay,
but
I
could
I
could
find
a
lot
of
flaws
with
it.
So
I
think
we're
self-critical
here
and-
and
that's
that's
great-
we
shouldn't
lose
that,
but
I
think
we
can
be
more
positive
kind
of
on
the
blog
and
then
social.
D
We
should
still
be
critical
in
our
the
public
issues
in
which
we
work
and
we're
to
actually
try
to
make
a
change,
but
I
think
it
might
change
perception
of
those
users
giving
a
score
that
they
not
think
about
gitlab
the
crappy
open
source
product
that
we
were
five
years
ago,
but
that
they
think
of
well
gitlab's
full
of
great
designers,
and
I
follow
them
on
dribble
and
all
the
other.
A
I
think
that's
a
great
point.
I
will
say
when
we
look
at
the
results
coming
in
from
sus
and
nps.
We
don't
just
look
at
the
negative
themes.
We
look
at
the
positive
themes
too,
and
ux
is
one
of
those
interesting
things
where
it's
in
both
lists.
So
we
don't
just
get
negative
feedback
about
our
ux.
We
do
get
a
lot
of
really
positive
feedback,
and
this
is
stuff
that
I
get
when
I
think
about
david
desanto
and
how
he
positions
secure.
He
positions
it
in
the
context
of.
A
D
H
E
Yeah
great
question,
so
we
do
use
a
95
confidence
interval
and
with
that
and
our
sample
size,
the
margin
of
error,
this
quarter
plus
or
minus
1.3.
E
So
when
you
compare
against
our
last
quarter,
there
really
isn't
statistical
significance
in
change,
but
when
you
look
further
back
in
that
that
pi
that
I
linked
to
you
can
definitely
see
that
over
time
there
is
statistical
change
in
that
drop
there,
jeff
or
catherine.
Do
I
either
of
you
want
to
add
anything
more
to
that
around
the
statistics
around.
H
Our
country,
no,
I
think,
you're
you're
exactly
right,
like
a
0.1
drop,
we
we
can't
know
if
that's
a
true
drop
or
a
viewpoint,
that's
noise.
But
yes,
when
you
look
back
many
quarters
back,
I
don't
know
exactly
how
far
it's
dropped,
but
it
has
gone
outside
of
the
the
confidence
interval
and
now
that
we've
really
tightened
up
how
we're
deploying
sus
and
we
have
a
really
rigorous
methodology.
I
think
this
is
something
that
we
can
feel
really
confident
in
terms
of.
We
know
who's
answering
sus.
H
We
know
we
have
the
appropriate
quotas,
for
you
know
the
different
types
of
users
that
we
care
about,
and
so
we
can
feel
much
more
confident
tracking
those
scores
both
overall
and
for
those
specific
cohorts
of
users
that
we
care
about
over
time.
So
yeah.
F
Yeah-
and
I
will
also
say
that
before
we
got
to
our
awesome
present
day,
really
tighten
up
method
that
to
try
to
control
for
some
of
these
things,
we
use
the
same
sample
size
for
I
think
about
five
quarters
before,
like
the
past
two
quarters,
so
that
margin
of
error
was
kind
of
staying
the
same
each
quarter
as
well.
That's
what
we
were
seeing.
A
Yeah,
thank
you,
ux
research
team
for
all
of
your
hard
work
on
sus
catherine
you've
been
such
a
trooper
running
it
and
synthesizing
it
every
quarter
and
then
getting
jeff
and
adam's
collaboration
on
tightening
up
the
methodology.
I
think
is
really
really
important
for
us.
You
know
there's
no
point
in
the
future
in
which
our
confidence
is
going
to
be
100,
because
the
trade-off
for
that
is
not
worth
what
we
would
get
from
it.
A
That
would
be
a
very
expensive
thing
to
do,
but
the
the
confidence
level
that
we're
out
right
now
is
good
and
then
I
think
the
point
that
we're
seeing
is
also
look
at
it
in
the
context
of
kind
of
the
larger
trend.
You
know
when
you
see
this
downward
trend
quarter
over
quarter
over
a
quarter.
You
can
look
at
that
and
go
okay.
That's
something
we
need
to
address.
A
A
Okay,
we're
at
time.
This
has
been
a
fantastic
group
conversation
I
have
loved
every
moment
of
it.
Thank
you
all
for
being
here
and
asking
such
amazing.