►
From YouTube: UX Group Conversation
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
everybody
welcome
to
the
ux
group
conversation
I'm
christy
linville.
Thank
you
for
joining
us
today.
It
looks
like
sid
has
the
first
question.
A
Yes,
it
won't
normally
be,
but
I
realized,
as
I
was
putting
it
together,
that
we
had
screenshots
of
research
participants
their
faces
and
they
hadn't
agreed
to
be
on
youtube.
So
not
the
normal
standard
makes.
B
Total
sense,
thanks
for
the
focus
on
lovability
love
the
progress
there
really
important
for
for
our
success.
B
A
A
So
in
preparation
for
that
during
q2,
we
had
an
okr
where
the
product,
design,
managers
and
leaders,
including
me,
migrated
components
to
see
what
it
was
like.
I
wanted.
A
What
kind
of
problems
people
were
going
to
run
into,
but
that
also
gets
me
in
there
in
the
code
base
and
seeing
how
it's
structured,
how
things
are
put
together
the
types
of
challenges
our
development
team
runs
into
so
yeah.
B
That's
really
cool,
and
it's
also
cool
to
hear
that
the
training
is
like
done
in
a
thing
that
adds
value
like
this
is
otherwise
work.
Someone
else
would
have
to
do
so.
Everyone
can
contribute
taken
to
a
new
height.
Thank
you.
The
posted
just
want
to
call
out
they're
posted
on
a
new
monitoring.
Docs
looks
awesome
like
that.
One
posted
just
explains
how
you're
improving
it
and
how
it's
getting
better,
really
love
the
side
of
that,
and
then
my
last
thing
is
that
the
contributing
to
gitlab
talks
demo
is
on
google
drive.
B
We
try
to
put
stuff
on
youtube
for
a
variety
of
reasons
that
are
linked.
It's
not
coming
through
even
eric
who's
leading
the
engineering
department
is
not
giving
the
right
direction
because
his
how
to
achieve
video
today
was
on
google
drive
as
well.
So
somehow
it's
not
happening.
How
what's
what's
holding
up?
Is
it
too
inconvenient
to
upload,
or
is
it
not
clear
to
everyone,
or
should
we
make
it
part
of
onboarding?
I
I'm
a
I'm
a
bit
of
a
broken
record
on
this,
and
I
want
to
make
sure
I
get
out
of
this
business.
A
It's
not
too
hard,
and
I
do
think
people
generally
know.
I
can't
speak
to
the
larger.
I
think
people
generally
know
to
put
things
on
youtube.
I
think
in
this
case
it's
because
they
recorded
the
video
for
right,
the
docs
portland
and
it
hasn't
gone
live
yet
so
I'm
under
the
impression
that
it
will
be
on
youtube,
it's
just
not
there
yet,
but
someone
from
the
docs
team
can
correct
me
if
that's
wrong.
B
B
B
Any
feelings
about
all
the
ux
people
will
now
get
gmao
or
all
the
product
managers
to
kill
up.
Every
single
group
will
now
get
either
gmail
or
page
email.
So
how
many
users
are
using
the
functionality
you
ship
as
like
their
core
metric,
any
feelings
from
the
ux
side,
how
that's
going
to
influence,
maybe
their
incentives,
how
how
to
measure
it,
what
it
will
change?
What
will
be
good?
What
will
be
bad.
A
Yeah,
I
think
that's
an
interesting
question.
I'm
gonna
answer
this
from
a
purely
ux
perspective,
so
product
manager-
sorry,
that's
where
I'm
coming
from
this
one.
When
I
look
at
feedback
that's
coming
in
on
the
nps
on
sus
on
hacker
news,
we
frequently
get
comments
about
usability
bugs
and
if
this
were
just
easier
to
use,
I
would
use
it
or
really
common
one.
We
get
is
yeah.
A
I
can
use
it
because
I've
been
using
it
for
a
long
time
and
I'm
kind
of
an
expert
in
this,
but
I
worry
about
my
newer
team
members
or
team
members
who
aren't
developers
who
I
need
to
work
with,
and
so
I
think
ideally
it
will
help
influence
us
to
create
better
experiences
across
the
board.
Now
is
it
going
to
impact
other
things
too?
Yeah.
Absolutely
that's
why
I
said
this
is
just
the
ux
perspective,
but
that's
what
I
expect
and
hope
to
see.
B
Great
so
that
it
could
be
driving
the
right
behavior
like
making
things
easier
to
use
and
more
discoverable
one
potential
downfall
I
see,
is
a
pop-up
overload
where
all
of
the
we
know
that,
like
our
source
code
and
verify,
is
heavily
used.
So
you
kind
of
want
to
get
into
that
cycle
and
make
sure
that
people
in
that
flow
get
a
notification,
and
I
know
that
for
companies
that
struggle
with
this
at
a
certain
point,
they
get
kind
of
they
get
like
their
internal
advertising
budget
like
if
we're
gonna
have
this
many
pop-ups.
B
A
Yeah,
I
thought
about
that
a
lot.
Actually,
I
think
that
it
is
a
real
risk
for
us
if
we
don't
keep
our
eye
on
it.
This
is
also
true
with
like
the
in-app
notifications
that
we're
using
to
recruit
participants
for
research,
sometimes
or
just
to
let
people
know
that
something
is
going
on.
I
think
it
comes
down
to
collaboration
within
the
teams,
and
a
lot
of
that
starts
with
the
ux
teams.
A
Actually,
on
today's
ux
leadership
meeting,
we
have
an
agenda
item
to
discuss
collaboration
when
people
are
contributing
to
a
section
of
the
product
that
is
not
a
normally
a
part
of
the
product
that
they
work
on.
So,
for
example,
when
someone
outside
of
the
source
code
team
is
going
to
add
something
to
a
merge
request,
there
really
needs
to
be
a
larger
conversation,
not
to
stop
them
from
doing
it,
but,
like
the
source
code
team
needs
to
be
aware,
they
need
to
be
able
to
conversation
about
it.
B
Yeah
and
I
I
think,
like
contributing
functionality
all
good
but
contributing
a
pop-up
in
someone
else's
stream.
I
think
I
think
that's.
I
think
it
will
just
get
out
of
hand
and
we'll
end
up
with
a
group
kind
of
that
owns
in-app
messaging
and
that
will
have
to
make
these
decisions,
because
otherwise
you
can't
get
the
incentives
to
align
but
we'll
see
for
now.
I
agree
it
should
be
a
conversation
before
you
notify
people
in
someone
else's
group.
C
How
does
that
work
with?
So,
if
you're
talking
about
pop-ups
notifications,
that's
fine,
but
we
also
have
different
workflows
within
the
the
application.
So
we
had
a
recent
example
where
one
feature
was
properly
designed,
but
when
talking
about
the
grander
scope
right
like
how
it
looks
within
a
certain
workflow,
it
was
affecting
others
significantly.
How
do
we
balance
that
without
putting
too
much
stress
on
on
both
sides.
A
Yeah
and
that's
exactly
what
today's
topic
in
the
u.s
leadership
meeting
is
going
to
be
about.
There
is
not
a
perfect
answer.
I
think
it
comes
down
to.
We
still
want
to
move
fast.
We
don't
want
to
stop
people
from
doing
things,
but
at
the
same
time
we
want
people
thinking
in
the
larger
context
and
oftentimes
that
can
just
be
awareness.
It
could
be
an
async
like
hey.
I
know
this
is
the
part
of
the
product.
A
You
normally
work
on
heads
up,
we're
thinking
about
doing
this,
take
a
look,
and
sometimes
it
might
need
to
be
a
short
synchronous
conversation.
So
people
have
more
context.
The
other
thing
that
we
need
to
think
about
is
when
we're
doing
solution,
validation,
validating
solutions
in
the
larger
context
of
the
problem,
not
just
like
my
little
widget
does
this
work.
A
So
I'm
not
saying
that
we're
going
to
get
it
perfect,
the
first
time
every
single
time,
because
if
we
did
again,
we
would
probably
slow
ourselves
down
too
much,
but
we've
got
to
be
aware
of
it.
We've
got
to
be
working
on
it
and
so
the
I
don't
have
an
immediate
answer
other
than
it's
on
our
radar.
We
know
it's,
we
know
it's
a
concern
and
we're
going
to
be
discussing
it
as
a
leadership
team.
C
Is
there
anything
top
of
mind
for
you
that
we
from
the
infrastructure
department
could
do
to
enable
you
to
do
those
experiments
quicker?
Oh.
A
A
A
While
we're
waiting
for
more
questions
I'll
give
a
quick
plug,
because
I
think
this
is
super
duper
interesting
and
I
need
to
check
and
see
real
fast
what
slides
these
are
on.
But
if
you
haven't
yet
look
at
slides,
12
and
13.,
if
you
ever,
if
you
haven't
ever
watched
new
users
use
our
product.
Those
are
really
short
clips.
Where
you
get
to
see
research
participants
do
exactly
that
so
they're,
interacting
with
merge,
requests
and
issues
for
the
first
time.
Super
short
clips
really
really.
D
So
christy
to
kind
of
add
to
the
last
topic:
has
there
been
any
discussions,
or
is
it
currently
part
of
the
process
that
ux
is
involved
in
community
contributions
as
well?
Is
that
the
topic
you're
talking
about
related
back
to
the
merge
request,
page
like
that,
was
a
non-team
making
a
change
to
somebody
else's
future?
That's
inside
of
create's
area,
but
we
have
seen
community
contributions
come
in
and
they've
broken
structure
of
page
because
they
didn't
get
properly
reviewed.
A
And
that
that
is
part
of
a
product
designer's
responsibility
to
take
a
look
at
community
contributions
as
they
come
in
just
to
make
sure
to
your
point
that
they
haven't
inadvertently
broken
something
so
it
you
know
it
doesn't
always
go
exactly
as
intended
every
time.
But
yes
that
should
be
happening.
D
Yeah
cause
like
the
I
guess
I
look
at
it
as
there's
kind
of
a
couple
challenges
for
the
designer
there's
the
work
they're
working
on
with
the
team
they're
part
of
there's
the
work
coming
in
from
another
team
within
git
lab
who's.
Making
changes
like
this
last
example
and
then
there's
the
final
part
which
is
coming
from
the
community.
So
that
seems
like
a
lot
of
load
on
on
the
individual
designer.
A
It's
like
you
read
or
13.2
retro
issue.
Mr
reviews
are
a
an
expected
part
of
a
product,
designer's
job
and
they
do
take
time
and
part
of
what's
hard
about
them.
Is
they
aren't
scheduled
right?
They
just
kind
of
come
in,
so
they
just
have
to
fit
them
into
their
workflow,
along
with
their
other
responsibilities.
A
Generally,
we
have
the
person
who's.
A
part
of
that
stage.
Group
do
the
review
because
they
have
the
most
subject
matter,
expertise.
That
being
said,
people
can
always
ask
for
help.
So
if
product
designer
is
underwater,
if
they've
just
got
too
much
on
their
plate,
they
should
always
raise
a
hand
and
say
hey.
I
need
help
with
this,
and
someone
will
always
help
whether
it's
their.
B
A
A
Ask
well,
I
will
give
one
last
plug
for
this.
Deck
is
full
of
videos
that
are
really
really
really
interesting.
There's
probably
25
videos
in
this
deck
that
people
can
watch
about
different
topics.
So
when
you
have
a
chance
jump
in
there
and
do
that,
you
will
learn
so
much
about
what's
going
on
with
the
product
and
what's
coming
up
soon.
So
and
of
course,
if
you
have
any
questions
after
the
fact,
you're
always
welcome
to
reach
out
and
ask
as
well.