►
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).
B
First,
post
well
congrats
to
everyone
on
on
slide
number
nine,
like
we
beautified
our
UI,
and
we
did
a
hundred
seventy
things
that
would
bring
something
down
to
zero.
It's
I
think
that's
a
company
first,
so
congrats
on
that
I
can
tell
wait.
How
did
we
get
to
do
something
all
the
way
like
that?
That
doesn't
vary
so
many
times
yeah,
so
he
knew
coming
up
before
you're
done
like
how
did
you
do
that.
A
D
It's
been
an
amazing
team
effort,
I
had
the
most
fun
bringing
all
the
people
together
and
there
have
been
so
many
designers
been
involved.
So
many
in
designers
who
made
the
first
contribution
actually
in
the
code-
and
it's
been
amazing
to
see
all
of
this
so
I'm
very
happy
to
see
how
that
went
down
and
yeah.
B
D
You
mentioned
perfectly,
it
was
definitely
a
combination
and
we
really
wanted
to
focus
on
making
it
easy
for
everybody
to
to
contribute
for
the
first
time
in
code.
So
that's
why
Annabelle,
for
example,
did
a
great
job
in
creating
a
small
tutorial
for
designers,
how
to
make
code
changes
and
how
to
put
them
into
the
GDK
and
how
then
to
create
the
merge
request
how
to
pay
people
and
basically
showcasing
the
entire
flow
as
a
designer
from
the
code
perspective,
there
has
also
been
an
amazing
effort
from
people
scoping
down
things.
D
B
Thank
you.
He
you
elaborate
a
bit
on
slide.
Seven,
the
UX
scorecards
for
category
maturity.
How
how
are
we
gonna
determine
what
the
category
maturity
is
and
if
the
answer
is
you
just
have
to
UX
designer
give
a
statement
what
they
think
I'm
fine
with
that
you
might
ask
a
follow-up
question,
but
first
of
all
kind
of
want
to
hear
what
the
idea
is.
A
B
I
think
that's
that's
great
and
I
think
we
should.
We
should
probably
it
might
be
linked
already,
but
I
think
we
should
have
a
link
from
the
category
maturity
pace,
kind
of
like
how
we,
how
we
do
that
and
a
proposal
I
have
what
I
wonder
what
people
think
is.
We
got
to
make
sure
we
talk
food
like
if
we
don't
use
it
ourselves,
we're
not
there
yet
so
I
could
see
a
criteria
in
order
to
get
viable.
B
The
majority
of
the
we
have
to
use
it
for
a
substantial
amount
at
gitlab
and
in
order
to
get
complete,
we
have
to
completely
exclusively
use
this
at
gitlab.
So,
for
example,
service
desk
could
not
be
complete
because
we
still
use
Zendesk,
which
is
awesome
software,
but
we
still
use
Zendesk
at
gate
lab,
so
it
can
never
be
complete
and
it
cannot
and
it
cannot
be
viable
until
at
least
one
significant
team
uses
it
I
think
the
IT
team
is
trying
to
use
it.
B
A
We
can
typing
okay,
I
will,
while
someone's
typing
also
I,
would
point
out,
I
think
it's
worth
pointing
out
and
slide
13
that
there
are
some
new
UX
research
training
materials
available
in
the
handbook,
and
you
know
the
intended
audience
for
these
would
be
product
managers
and
product
designers
to
sort
of
feel
more
confident
during
research
with
users.
But
anybody
in
the
company
who's
interested
in
learning
how
to
better
talk
to
our
customers
about
our
product
would
benefit
from
checking
out
these
research
materials.
B
A
The
best
person
to
talk
to
about
UX
about
da
quitting
will
probably
your
UX
manager
counterparts
for
your
stage
groups
that
you're
working
with
I
would
say,
I.
Think
anybody
on
the
UX
team
should
be
able
to
talk
to
you
about
that.
I
think
Jamie
are
probably
specifically
referring
to
well
I'm,
not
I'm,
not
sure
I'm
making
an
assumption,
but
you
can
definitely
talk
to
me
about
it
and
I
can't
get
you
to
the
right
place.
A
F
As
what
I
like
to
call
back
office,
we
don't
always
understand
how
engineering
is
organized,
especially
if
you
don't
typically
interact
with
product
or
engineering,
and
so
when
we
do
have
a
desire
to
use
the
product
in
new
ways.
Besides
opening
a
feature
request,
how
do
we
provide
that
feedback
and
get
it
reviewed.
F
G
A
A
C
Alright
looks
like
I'm
a
yeah,
and
this
is
legitimately
a
question
for
me
because
I
know
little
about
it.
Although
I
was
really
excited
to
see
it.
Can
you
talk
more
about
the
sketching
session?
That
Gio
did
was
a
cross-functional
sketching
session
as
I
understand
it?
That's
on
slide
38.
Yes,.
A
So
sometimes
we're
in
issues
and
we're
talking
a
lot
in
text
and
we're
going
back
and
forth
and
we're
describing
things
textually.
But
that's
not
always
the
best
way
to
get
the
ideas
of
the
team
out,
because
we
have
different
ways
of
communicating
via
writing.
So
this
skip
session
was
meant
to
allow
all
the
members
of
the
team,
whether
it
was
a
product
manager,
an
engineer
or
a
quality
person
to
share
what
was
in
their
brain
in
terms
of
like
what
might
be
a
better
experience
for
this
particular
part
of
the
geo
and
it's
ongoing.
A
So
there
was
there's
going
to
be
another
step.
That's
going
to
be
a
synchronous
meeting,
I
think
where
the
team
will
get
together
and
they'll
use
a
new
mural
and
they'll
have
kind
of
another
level
where
they
can
kind
of
take
all
of
the
different
ideas
that
were
made
available
and
then
kind
of
you
know
go
through
and
pick
the
best
ones.
G
A
A
That
was
how
it
was
set
up,
so
there
was
a
problem.
If
you
look
in
the
issue,
there
was
like
a
problem
statement
and
then
a
request
for,
like
you
know,
share
your
ideas
on
this
topic
and
then
asynchronously
people
drew
paper
and
took
photos
and
uploaded
the
photos
and
then
left
a
few
comments
and
the
issue
just
to
kind
of
describe
some
of
their
sketches
and
their
ideas.
A
H
A
G
Maybe
this
question
to
Tori,
to
give
us
a
little
bit
more
updates
on
the
pajamas
and
building
reusable
components
as
a
super
important
part
of
like
this
connection
between
front-end
and
new
acts,
collaboration
and
productivity
I
know
that
we
are
working
on
like
bringing
in
more
UX.
Maintainer
is
kind
of
like
curious.
Where
does
this
process
goes?
Maybe
some
important
cocoa
out
there
yeah.
E
So
the
slide
11
shows,
which
highlights
all
of
the
foundational
components
that
still
have
items
left
either
create
the
documentation
or
build
out
the
component
lab
UI
or
style
it
correctly
according
to
the
Jemma
specs.
So
there's
14
left
that
we
have
to
complete.
Most
of
them
are
either
close
to
being
done
or
just
have
a
few
things
to
wrap
up,
which
is
great.
E
Once
we
kind
of
burn
down
all
these
components,
then
we'll
start
shifting
our
focus
more
towards
integrating
them
into
the
product,
and
we
already
have
a
lot
of
the
gun
web
UI
components
in
prod
already,
but
there's
some
complexities
with
the
fact
that
we're
using
Hamill
and
view
within
production,
and
so
there's
some
things.
We
need
to
figure
out
about
how
to
make
that
easier.
Just
to
use
pajama
components,
we
are
adding
more
UX
maintainer
for
pyjamas.
E
Like
you
mentioned,
it's
an
okay
are
that
we
have
just
for
our
team,
and
we
want
to
be
able
to
do
that
so
that
we
have
the
same
ratio.
That
engineer
has
setup
for
the
number
of
maintainer
x'
to
designer,
so
we're
aiming
for
one
to
five
and
hopefully,
by
the
end
of
this
quarter,
we'll
have
that
as
we've
already
identified
four
other
designers
who
are
interested
in
being
maintainer,
so
now
we're
just
kind
of
working
on
helping
them
train
up
so
that
we
can
make
them
in
tears.
Does
that
help
answer
your
question?
F
I
have
a
question
about
the
tool
stack
and
this
can
be
taken
offline
and
answered
later.
Just
looking
at
our
tool
stack
for
UX,
do
we
have
the
right
descriptions?
Do
we
have
all
the
tools
that
UX
is
using
listed
on
the
sheet?
And
yet
this
question
I'd
like
to
know
right
now
does
UX
have
all
the
tools
it
needs.
C
So
the
answer
is:
do
we
today,
literally
this
moment,
have
all
of
the
tools
that
we
need?
No,
do
we
have
a
plan
for
how
to
do
that
over
the
course
of
this
upcoming
year?
Yes,
it's
been
planned
for
in
the
budget,
so
I've
heard
me
some
tools
we'll
be
adding.
It
looks
like
we're,
gonna,
add,
figma
and
actually
replace
sketch
with
Sigma.
I
know
that
sara
is
looking
at
dovetail
for
research,
so
we've
got
some
things
like
that.
C
I
I
Was
a
part
of
that
this
is
Holly
and
the
plan
team
yeah.
Thank
you
I'm,
so
glad
to
hear
that
people
are
enjoying
it.
It
was
definitely
a
really
fun
project
to
work
on
an
exciting
project.
I
think
that
Alexis
believe
also
spent
some
time
on
it.
So
it
was
kind
of
a
team
effort
for
sure,
but
it's
good
to
hear
that
people
are
happy
with
it.
Thanks.
J
B
Like
I
think
I'm
the
next
question,
it's
not
a
question,
but
it's
a
statement.
I
love
the
presentations
and
I
think
that
questions
took
a
while,
because
the
presentation
is
beautiful,
interesting
and
extensive
I
think
people
were
just
checking
that
out
so
well
done.
Looks
amazing
and
very
interesting,
like
Freddie,
for
it's
great
to
see
some
growth
of
experiments
on
comm,
getting
our
users
to
not
just
users
for
version
control,
but
multiple
things
very
excited.
Are
there
any
plans
to
rule
this
out
to
self-manage?
B
A
Sometimes
we
might
want
to
actually
do
a
different
experiment
in
self-managed
only,
and
we
have
to
be
able
to
get
the
data
back
from
from
that
from
that
tool,
and
we
need
to
be
able
to
get
enough
data
that
we
can.
We
don't
have
to
let
the
experiment
run
for
months
and
months
in
order
to
know
if
it
was
successful
or
not.
So
we
are
working
on
all
of
that
and
I
could
potentially
find
later
a
couple
of
other
specific
issues
that
are
self-managed
focused.
B
Cool,
thank
you
for
that
and
the
next
question
to
you,
ICU,
that
we're
working
on
get
lab
spaces
and
I
think
it's
very
valuable
to
do
discovery
there.
It's
just
clearly
a
need
for,
like
better
team
management,
using
my
org
make
sure
instance
of
it.
In
instance,
people
in
New
York
cannot
see,
cannot
accidentally
share
stuff
outside
the
organization,
better
account
management.
B
All
these
things
are
needed,
but
I'm
a
bit
afraid
of
that
we
might
introduce
work,
spaces
or
spaces
or
teams,
and
that
you
can
add
people
both
in
a
group
setting-
and
you
can
have
this
alternative
way
and
we
have
two
ways
to
kind
of
achieve
the
same
thing
and
we
increase
confusion
with
our
customers.
Any
anybody
has
ideas
about
how
to
prevent
that.
C
J
Only
to
the
extent
that
we've
actually
talked
about
the
concern
but
I
know
it's
top
of
mind
for
the
p.m.
and
and
for
Amanda,
so
I
think
that's
part
of
the
work
that
they're
doing
part
of
the
competitive
analysis
to
is
to
understand.
Maybe
how
other
solutions
address
those
types
of
concerns
as
well
trying
to
keep
things
simple,
yeah.
B
I
think
one
one:
it's
a
super
hard
problem,
so
I
don't
know
how
to
fix
it.
My
two
cents
would
be
don't
because
we
call
it
spaces
or
teams.
Don't
think
that
we
have
to
create
another
concept.
Maybe
it's
just
taking
the
existing
concept
of
groups
and
making
sure
that
that
works
even
better
than
it
does
today,
because
two
things
to
do
the
same
thing
is
might
be,
might
be
detrimental,
but
it's
it's
super
tough
and
I
have
solutions.
I,.
A
Completely
agree
with
that
and
I'll
just
add
that
the
growth
team
is
thinking
about
this
quite
a
bit
too,
because
in
our
user
research
we
know
that
as
part
of
sign
up
flows,
trial
flows
and
things
like
that.
People
are
super
confused
about
the
group
concepts.
So
we
plan
to
work
closely
with
the
product
designer
and
the
product
manager
in
the
spaces
so
that
we
could
kind
of
collaborate,
because
we
do
research
in
a
similar
area,
no
nose
but
yeah.
K
Yeah
I
can
just
chime
in
a
little
bit
on
that.
That's
something!
We've
had
a
lot
of
conversations
around
when
it
comes
to
subscriptions
as
well
on
the
on
the
growth
team
and
that's
something
Lucas
p.m.
on
that
spaces
and
we've
had
some
conversations
around
with
self-managed.
You
have
this
sort
of
concept
of
instance,
and
that's
where
your
subscription
is
applied.
K
That's
where
your
that's
sort
of
the
largest,
the
largest
encapsulating
I,
want
to
say
group,
but
I
don't
want
to
use
the
word
group,
the
largest
sort
of
encapsulation,
whereas
uncom
the
largest
like
encapsulation
in
the
place
that
your
subscription
is
applied
to
is
the
group.
So
there
are
some.
There
are
some.
K
There
are
some
areas
where
the
instance
level
on
self-managed
gives
the
gives
the
company
a
little
more
customized
ability
and
control
over
over
their
space
that
they
don't
have
uncom
and
I
think
both
from
a
working
perspective
and
also
from
like
a
subscription
perspective.
I
think
that's
sort
of
the
what
spaces
is
trying
to
solve.
Hey.
B
I
think
you're
on
the
money
and
maybe
in
my
mind,
if
I
had
to
pick
a
name
right
now,
I'd
call
it
a
team.
So
it's
not
teams,
because
teams
is
of
replacing
groups.
It's
one
team,
you
can
add
multiple
groups
to
it
or
something
like
that,
just
a
fault,
but
it's
a
I'm
glad
to
hear
everyone
is
thinking
about
this.
How
to
solve
this
without
introducing
duplication
and
maybe
in
the
end
we
should
have
a
concept
that
works
so
well
that
in
self-managed
we
also
replaced
the
existing
instance
base
things
with
the
same
concept.