►
From YouTube: UX Group Conversation (Public Livestream)
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
B
First,
the
product
management
product
managers
would
do
it,
but
they
spend
a
lot
of
time
on
that
and
we
think
it
should
be
kind
of
other
people's
opinion
and
we
thought
about
sending
surveys,
but
that
would
be
very
tedious
for
our
customers
and
then
we
thought
we
got
a
great
UX
research
team
and
the
UX
managers
who
have
an
idea
about
how
good
something
is
compared
to
the
rest
of
the
market.
So
let's
do
that
any
any
other
few
things
that
false
about
that.
Since,
since
we
make
that
change,
yeah.
A
Absolutely,
and
so
what
we
are
doing
is
adapting
an
existing
process.
We
call
UX
or
cards
to
fit
to
support
the
product
maturity
and
previously
the
way
that
we've
done
us
score
cards
is
they've
been
heuristic
review.
So
what
that
is,
is
a
designer
going
in
and
based
on
their
own
knowledge
and
experience,
assessing
the
usability
and
the
experience
of
a
specific
what
we
call
job
to
be
done,
the
way
that
we're
adapting
it-
and
this
is
what
we've
always
wanted
to
do
so
this
has
given
us
extra
motivation
to
do
it.
A
This
way
is
we
don't
want
those
to
be
sure
istic
anymore?
We
want
those
to
be
based
on
actual
feedback
from
our
user
community,
and
so
we're
really
excited
about
this
change.
This
is
a
big
change,
though,
and
it's
a
big
initiative,
so
what
I
will
say
is
we
are
right
now
in
the
process
of
figuring
out?
What
does
this
mean?
A
How
do
we
do
this
in
a
meaningful,
but
iterative
way
that
allows
us
to
do
it
quickly
and
reasonably
we're
coming
up
with
some
ideas
within
the
UX
department
now,
but
we're
gonna
really
shortly
start
sharing.
Those
with
products
and
they
have
an
opportunity
to
weigh
in
and
make
sure
that
they
feel
really
bought
into
the
process
as
well,
because
that's
really
important
cool
thanks,
yeah
great
question
and
looks
like
we
have
another
question
but
I'm
not
sure
who
added.
C
I
saw
yeah,
that's
about
I'll
update
that,
but
my
question
is
yeah.
Basically,
one
of
the
biggest
remaining
challenges
for
pajamas.
C
A
That's
a
great
question:
I
was
just
looking
to
see
if
Tory
Davis
was
on
the
call,
because
she
has
really
been
the
one
driving
this
and
frankly
should
give
you
a
better
answer
than
I
will
but
I'll
give
you
an
answer.
I
don't
see
her
at
all,
and
so
the
biggest
remaining
challenges
for
pajamas
right
now
is
so
the
work
that
we're
doing
is
foundational
work.
A
So
it's
definitely
a
collaboration
between
product
designers
and
product
managers
and
engineers
to
make
this
work
well.
So
we've
made
a
lot
of
good
progress
for
at
about
70%
right
now.
That's
after
about
seven
months
worth
of
effort,
we
wanted
it
to
go
more
quickly
than
it
has,
but
we
deeply
appreciate
the
work
that
everyone
has
done
next
year.
We're
gonna
have
some
teams
who
are
gonna,
be
more
more
focused
on
this
and
helping
to
drive
it
forward
and
that'll
make
a
huge
difference
now.
A
That
being
said,
I
want
to
make
sure
that
it's
really
clear
to
everyone
that,
just
because
we
have
teams
who
are
focused
on
driving
this
project
forward
does
not
mean
that
they
own
pajamas
pajamas
is
shared
by
everyone
in
the
company.
So
many
people
have
a
stake
in
it.
It
will
always
be
up
to
designers
and
pm's
and
engineers
from
across
the
company
to
continue
doing
this
work
and
really
making
pajamas
a
wonderful
asset
for
everyone,
but
just
having
people
there
to
push
it
forward,
I
think
will
make
a
big
difference.
C
D
A
You
bet
yet,
and
so
individual
growth
plans
are
Dux,
saying
those
are
a
lab
thing,
and
so
what
we're
doing
is
we're
using
the
template,
that's
provided
by
our
people
operations
team,
because
if
we
think
it's
really
good
and
we've
used
quite
a
bit
throughout
this
year,
my
managers
have
done
a
good
job
at
partnering,
with
their
individual
contributors
to
make
sure
that
everybody
has
an
individual
growth
plan
within
the
first
few
months
after
they
get
started
at
gitlab.
So
I
believe
it's
documented
in
the
handbook.
A
A
They
should
be
so
that
they're
both
about
career
growth
at
gitlab,
but
they're,
also
about
just
building
your
own
skills,
and
that
was
the
part
that
we
felt
like
we
hadn't
put
enough
focus
on
in
the
individual
growth
plans
is
making
sure
that
when
people
want
to
attend
workshops
or
acquire
a
specific
skill
that
may
not
may
not
even
be
directly
related
to
their
role.
So,
for
example,
we
have
designers
who
are
really
interested
in
front-end
development.
B
I
was
looking
at
I
want
to
see
those
UX
use
case.
Showcases,
they're,
really
good,
that
I
had
to
add
the
menu
Lisa
I'm,
maybe
a
pretty
lazy
person.
Is
it
possible
to
create
a
playlist
on
it
and
it's
possible
I
know,
but
is
it
worthwhile
and
I'm
not
sure
whether
I'm
the
only
person
we
shouldn't
do
it
for
me?
So
I
know
what
other
people
think
we
have
one.
That's
a
great
answer:
yeah.
A
B
E
I
had
the
next
one.
Can
you
hear
me:
okay,
okay,
great
yeah,
so
Matteo
recently
conducted
or
completed
a
UX
scorecard
review
that
I
found
really
really
insightful.
I
was
curious
if
we
could
add
those
to
this
deck
so
that
way,
there's
just
them
ongoing
list
of
all
of
the
completed
UX
scorecards
and
then
kind
of
like
what
Sid
just
mentioned
by
just
creating
a
stream
for
all
of
the
UX
scorecard
reviews.
A
So
first
let
me
start
by
agreeing
with
you.
The
work
that
Matei
did
on
that
was
awesome.
I
was
so
very
impressed
and
we
have
a
lot
of
them.
You're
right,
and
so
there
are
two
different
places.
You
can
access
those.
So
we
have
an
epic
that
collects
all
of
the
UX
scorecards
and
we
try
to
do
a
good
job
of
updating
that
by
linking
the
the
relevant
issues
to
it.
Also
in
periscope.
A
There
is
on
the
UX
dashboard
a
chart
for
this,
and
it
also
has
links
out
to
the
the
relevant
issues
which
includes
the
videos
and
recommendations.
Periscope
gets
updated
a
little
less
frequently
than
that
epic
does
so
the
epic
might
be
the
place
you
really
want
to
start.
I
I
will
go.
Look
that
up.
I
will
add
that
to
the
agenda
after
this
call.
Thank.
E
A
A
B
I
am
I'm
going
to
do
something
really
small
I'm,
not
sure,
that's,
okay,
but
it's
a
pet
peeve
of
mine
for
our
security
dashboards.
They
start
looking
really
amazing
and
we
got
timelines
and
sparklines
and
I
love
how
they
look.
But
I
don't
see
on
the
UX.
Examples
is
showing
projects
that
aren't
tested
like
that
is
like
the
worst
thing
where
you
you
have
a
project,
you
haven't
tested
it,
so
there
could
be
like
big
monsters
lurking
in
there.
B
It's
not
it's
not
visible,
but
I
never
see
those
in
the
UX
mock-ups
I,
I
I,
wonder
whether
they're
top
of
mind
for
us.
It's
a
very
detailed
question,
but
now,
in
my
mind,
like
you,
have
like
the
high
priority
and
then
above
that
is
the
untested
which
is
like
even
worse
because
I
don't
know.
What's
lurking
inside
gosh
projects
and.
A
B
So
I
mean
the
mock-ups
of
a
UX
of
a
security
vulnerability
dashboard.
So
all
the
projects
I
look
at
have
undergone,
for
example,
dependency,
vulnerability,
scanning
and
I'm.
Looking
at
like
the
list
of
reports
that
come
out
of
that,
basically,
what
I
want
to
see
is
like
which
projects
haven't
undergone
that
testing
or
which
haven't
undergone
that
recently
and
I.
Think
that
should
almost
be
I'm,
not
sure
it
should
be
mixed
in
I.
Think
it's
a
super
hard.
B
A
G
A
F
H
Wi-Fi
issues,
so
it
just
jumped
on
I,
did
hear
that
question
though
there
is
actually
an
issue
there
that
we
closed,
that
you
had
open
said
that
shows
whether
or
not
projects
are
tested
or
untested.
So
we
put
an
NBC
out
there.
I
think
in
the
mock,
that's
being
showed
it's
the
third
module
down,
and
so
that's
actually
showing
two
things
whether
thing
whether
projects
are
out
of
date,
so
when
the
last
pipeline
ran.
H
So
if
it's
five
or
more
days,
for
example,
we
call
that
out
so
projects
could
some
of
the
information
may
be
outdated
and
then
we
also
call
out
projects
that
are
part
of
a
group
that
have
been
untested.
We'd
like
to
further
this
by
further
specifying
like
what
tests
are
we
talking
about
out
of
the
four
scans
that
we
have,
and
so
what
qualifies
as
untested?
If,
if
none
of
them
have
been
configured,
that's
what's
being
defined
as
untested.
In
this
version.
A
I
So
I
can
help
in
real
quick
I'm
actually
have
been
looking
for
the
issue
since
I
saw
the
question
we
recently
completed
a
scorecard
for
growth
for
onboarding
experiences,
and
maybe
this
is
it
so
we
have
a
recommendation,
epic,
that
lists
a
whole
bunch
of
recommended
solutions
for
helping
people
to
onboard
ticket
lab
and
then,
in
addition
to
that,
we
have
some
other
issues
around
helping
people
discover
features
that
may
help
them
so,
for
example,
I'm
suggesting
pipelines
and
an
MRO,
and
there
are
no
pipelines.
A
A
I'll
speak
for
myself
first,
but
then
I
want
to
open
that
up,
because,
frankly,
I
think
people
in
my
team
will
give
you
even
better
answers
and
then
I
will
so
I'll
say:
I'm
I
am
looking
at
every
digital
tool,
I
used
for
inspiration
and,
and
that
goes
in
both
directions.
So
I'm
looking
at
things
that
are
working
well,
I
think,
oh,
this
is
interesting.
This
is
a
new
pattern.
This
is
something
that
we
might
be
able
to
to
leverage
I'm,
also
using
it.
A
Looking
at
things
that
don't
work,
things
that
annoy
me
personally
and
make
me
go:
oh
gosh,
are
we
doing
that
anywhere
in
our
product
and
the
other
thing
that
I
do
is
I
subscribe
to
a
lot
of
different
UX
newsletters
and
I
keep
an
eye
out
for
articles
about
trends
or
things
that
people
are
learning
through
research,
and
so
that's
really
useful
to
me.
But
let
me
stop.
I
want
to
open
it
up
to
my
team,
y'all
jump
in
sure.
K
L
A
G
Cool
I
think
from
me
also
I,
just
get
inspired
by
talking
with
you
know,
not
only
at
our
company
about
people
in
different
roles
and
different
people
and
understanding
other
problems
that
might
be
fun
to
solve
and
within
my
own
community
and
design,
friends
or
just
designers,
I
know
going
to
meetups
or
just
working
with
people
that
are
looking
at
different
problems
than
I.
Am
it's
it's
interesting
to
get
in
my
space?
Sometimes
so,
if
y'all
ever
want
to
talk
to
designers
reach
out
to
us,
because
we
love
talking
with
everyone.
M
The
one
thing
I'll
add
to
this
is
for
defend.
I,
know
that
and
like
will
often
talk
to
customers.
If
we
do
research
with
them
and
ask
them
what
tools
that
what
tools
they
are
using
and
what
they
like
about.
The
tools
are
what
the
pain
points
are
about
those
tools
and
then
we'll
dig
into
that
platform
and
see
you
know
if
it's
working
really
well
for
them,
maybe
what
they're
doing
in
the
UI
that
might
be
supporting
that
or
if
there's,
if
they're
struggling
with
something
in
that
platform,
looking
into
how?
N
Know
I'll
just
piggyback
on
a
lot
of
those
dribble
and
then
newsletters
resources.
A
lot
of
articles
that
go
into
deep
dives,
also
for
me,
like
I,
follow
like
specific
websites
that
are
kind
of
collections
of
like
UI
patterns
or
DataViz
patterns.
So
I've
got
like
in
Chrome
just
a
series
like
of
collections
of
things
that
are
kind
of
topic
specific,
but
then
otherwise
for
inspiration.
I
like
to
use
different
tools
just
as
to
see
how
I
can
solve
problems
in
different
ways.
N
So,
like
from
a
design
side,
you
might
switch
from
like
illustrator
to
Adobe
XD
to
sketch
and
just
work
through
different
problems
and
see
you
know
different
ways.
You
might
figure
it
out
and
solve
it.
So
that
gives
me
a
lot
of
inspiration
kind
of
like.
If
you
play
an
instrument,
you
know.
Sometimes
you
pick
up
a
different
guitar
and
you
play
differently.
It's
sometimes
with
different
tools.
I
find
that
I'm
just
inspired
differently
by
how
I
create
with
them.
B
Really
liked
going
to
the
presentation:
I
love
that
there's
so
many
like
super
big
screenshots
on
the
slides
and,
of
course
they
also
look
beautiful,
but
I
really
like
how
visual
it
is.
It's
a
lot
of
fun
I
since,
since
my
pet
peeves
insecurities
got
fixed
I
already
and
that's
good
news,
I
want
I'm
going
to
my
second
pet
peeve
insecurity,
which
is
we
show
vulnerabilities
over
time
like
how
many
got
sent
in
and
and
when
they
were
resolved.
B
They
probably
disappear,
but
if
I
would
ask
a
security
team,
how
are
you
doing
I
would
look
at
when
you
got
a
new
security
thing.
How
long
does
it
take
to
resolve
like
how
many
are
more
than
12
days
old,
more
than
30
years
old?
How
many
are
about
to
breach
that's
harder
to
collect
that
data?
It's
harder
to
visualize,
but
I,
wonder
how
we're
thinking
about
that?
Can
we
fit
that
in
the
existing
dashboards?
Is
that
too
hard
to
do
or
the
plans
are
there?
No
plans
is
curious.
H
I
think
the
work
that
we've
done
with
first
class
vulnerabilities,
a
first
class
object-
opens
up
the
doors
to
this,
and
so
that
was
a
great
achievement.
The
security
ask
care
team
just
did
and
our
first
visual
MVC
is
having
a
vulnerability
objects
page,
but
from
here
I
think
things
like
that,
like
vulnerabilities
in
time
when
they
were
imported
new
vulnerabilities.
That's
on
the
list
of
things
that
we
can
start
working
on.
Now
that
it's
the
first
class
object,
yeah.
O
I
mean
to
kind
of
add
to
that
so
yeah.
If
you
christian,
take
a
talk,
I
figure
she's,
probably
okay
with
it.
Yes,
so
is
it
the
long
term
where
we're
trying
to
redo
the
first
class
vulnerabilities
items,
so
we
can
look
at
historical
trending
and
be
able
to
identify
patterns
and
whatnot.
A
C
Looks
like
an
answer
is
actually
getting
typed
in,
but
basically
the
high
level
I
was
curious.
How
the
UX
team
thinks
about
shortcuts
and
slash
commands
and
those
types
of
things
that
really
enable
and
empower
people
to
be
even
more
productive,
I'm
curious
how
the
UX
team
thinks
about
that,
because
obviously
the
UI
is
essentially
the
best
way
to
communicate
that,
like
at
the
the
most
timely,
you
know
progressive
disclosure
kind
of
way
but
I'm
curious.
Oh,
are
you
guys
think
about
that?
Yeah.
A
Me
start
by
saying
I
agree:
I,
think
that
they're
very
important
I
think
that
we
look
at
things
like
this
kind
of
on
a
stage
group
by
stage
group
basis,
often
times
I
did
see
a
conversation
about
exactly
this
thing
in
maybe
an
issue
just
this
week.
So
if
anyone
from
my
team
wants
to
pipe
in
if
or
information.