►
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
So
we
can
go
ahead
and
get
started.
It
looks
like
the
first
question
is
from
Mike
terror.
He
said
he
will
miss
the
call
so
I'm
gonna
vocalize.
His
question
for
him
says,
with
the
focus
being
on
smile
for
different
product
teams
of
stage
monthly
active
users
for
different
product
teams.
Is
there
an
overarching
project
or
effort
to
make
other
stages
more
discoverable?
And
he
says,
for
example,
trying
to
get
grasp
of
a
deployed
application
requires
navigating
around
between
our
defined
silos,
rather
than
allow
showing
them
on
the
project
overview
page.
A
So
let
me
start
by
saying
each
group
is
responsible
for
discoverability
in
their
own
area,
and
that
is
something
we
absolutely
consider
as
part
of
the
design
process,
and
you
can
see
an
example
of
that
is
on
slide
15,
where
we're
looking
at
the
discoverability
of
our
installation
support
so
where
you
can
install
and
then
also
discoverability
of
documentation.
That's
one
example,
and
we
have
done
research
on
overall
gitlab
navigation,
and
we
do
know
some
things
about
that.
A
B
A
So
if
you
look
at
to
a
mic
says
trying
to
get
graphs
of
a
deployed,
application
requires
navigating
around
between
are
defined
silos
rather
than
showing
them
on
the
project
overview
page
as
our
designer
for
analytics
I
know
that
you're
thinking
about
this
very
deeply
so
I
wanted
to
see.
If
you
have
anything
to
add
about
the
work
that
you're
doing
there.
B
Yeah
at
the
moment
we're
doing
a
little
bit
of
information
architecture,
level,
information
architecture,
work
to
understand,
just
the
general
layout
of
gitlab
and
whether
that
that's
that's
effective
or
not
I
think
basically,
what's
required,
is
to
start
mapping
out
a
number
of
user
flows
that
actually
enter
into
analytics
and
then
use
that
as
a
way
to
to
frame
principles
about
how
we
actually
address.
That
challenge.
C
Yeah,
so
in
growth,
the
growth
teams
for
conversion
and
expansion.
They
look
at
this
quite
a
lot.
If
you
look
at
slides,
33
and
36
I
think
it
was
there's
a
couple
of
examples
of
changes
that
we've
made
recently
our
experiments
that
we're
running
that
improve
discoverability
of
features
and
like
the
CI
pipeline,
one
that
I
think
is
slide.
33
is
a
pattern
that
we
can
reuse
in
other
places.
C
So
so
yeah
there's
that
and
then
the
second
part
is
there's
an
epoch
around
onboarding,
it's
based
off
of
one
of
our
onboarding
Hyuk
scorecards,
so
recommendations.
It
has
a
lot
of
ideas
and
kind
of
strategic
approaches
that
we
would
like
to
pursue
or
an
onboarding
users
more
effectively,
which
a
big
part
of
that
is
obviously
like
helping
people
discover,
features
and
how
to
use
them,
and
then
I
would
just
add.
I.
Think
Kristi
already
mentioned
this,
but
you
know
the
growth
team
is
already
we're,
always
open
to
ideas
about
how
to
do
this.
C
Better,
the
product
teams.
They
know
their
users
in
their
products
best.
So
if
you
have
ideas,
bring
them
to
the
growth
team
and
we
would
love
to
design
an
experiment
around
it
or
to
help
you
get
those
implemented
or
to
give
it
a
try
and
see,
see
what
works
yeah.
That's
that's
all
I
wanted
to
add,
but
definitely
you
follow
up
with
with
me
or
any
of
the
other
growth
product
designers.
If
you
have
any
other
feedback
or
questions
Thank.
D
Yes,
Nick
again,
Nick
post
has
worked
on
something
called
object-oriented
design
and
I
was
trying
to
find
the
issue
just
now,
but
I
believe
that
can
actually
help
us
componentize
different
capabilities
throughout
the
application
and
they
present
themselves
at
the
right
moments
rather
than
having
these
sort
of
siloed
experiences
throughout
the
app.
So
I
want
to
add
that
I'll
put
a
link
to
the
issue
in
the
stock.
A
A
F
F
We've
had
a
lot
of
good
async
work
out
of
that,
and
it's
been
a
lot
easier
because
we
can
easily
jump
into
those
components,
we're
not
having
to
pull
files
down,
create
branches,
etc.
Do
pushes
to
see
the
latest
that
anyone
is
working
on.
It's
been
just
streamlining
async
work
for
us
and
I
think
it
makes
it
a
lot
faster
to
have
feedback
one
other
last
note
and
I'll
pass
it
to
Jarek
to
voice
his
is
that
with
figma,
we're
also
able
to
have
more
contextual
design
feedback
so
because
commenting
is
built
right
into
it.
F
We
can
actually
comment
right
into.
You
know
the
the
pixel
that
we're
wanting
to
discuss
and
I
think
that
really
helps
async
as
well,
so
that
we're
not
trying
to
map
a
comment
in
an
issue
or
thread
to
a
design
in
a
separate
document.
We're
able
to
have
a
closer
connection
so
Jarek.
Do
you
want
to
voice
your
answer?
Yeah.
G
I
just
wanted
to
add
something:
this
is
going
to
lead
to
a
simpler
workflow
for
contributing
to
pyjamas
before
we
had
to
commit
sketch
files
and
changes
the
sketch
files
and
get
lab
design
and
then
update
the
documentation
in
pyjamas
and
now
that
were
in
figma,
it's
just
going
to
be
within
one
repository
in
pyjamas.
So
it's
going
to
make
contribution
contributing
much
simpler
and
there's
a
work-in-progress
merge
request
in
there
for
that
issue.
Template.
H
Yeah
I'm
excited
as
well
to
see
the
conversion
to
figma
I.
Think
it's
really
awesome.
I
was
just
curious,
as
the
team
has
been
working
with
it.
Are
there
any
new
processes
around
figma
around
locking
or
approving
the
comps
that
you're
working
on
that
you
may
have
learned
or
process
around
using
figma
with
issues
either
in
beds
or
links
that
the
team
might
want
to
share.
F
Yeah
I'll
post
a
link
in
the
doc
and
I'm
just
pulling
up
really
quick.
We
do
have
new
contribution
guidelines
for
figma
the
deal
with
the
workflow
of
what
it
looks
like
to
make
a
changes
to
get
approval.
We
do
have
a
few
issues
open
right
now,
where
we're
deciding
on
what
maintainer
ship
looks
like
for
those
files
before
those
assets
for
both
pyjamas
UIKit,
as
well
as
different
stage
group
work
just
to
mange.
F
You
know
make
sure
that
we
are
the
individuals
that
are
posting,
updates
and
publishing
these
things
in
our
familiar
with
the
workflow
for
those
files,
as
far
as
it
relates
to
the
product
we're
still
following
our
traditional
workflow
of
updating,
more
static,
comps
and
working
through
the
design
tab
when,
when
applicable,
I
would
like
to
as
we
complete
the
migration
consider
what
we
could
do
to
actually
use.
Figmas
live
embed
feature
and
figma
live
in
bed.
F
Is
you
know
it
essentially
embeds
a
live
iframe
of
real-time
design
and
I
know
we
block
iframes
for
security
reasons
would
be
great
to
take
a
look
at
that
so
that
we
could
actually
embed
live
design
within
issues
so
that
we
don't
fall
back
on
static
comps.
We
actually
have
real-time
design
in
the
issues
and
I
think
that's
something
that
we'll
work
towards.
But
at
the
moment
current
workflow
with
working
in
get
lab
and
design
is
the
same.
Just
a
different
guideline
which
I'll
post
here
for
actually
working
in
Sigma.
H
Thanks
that
would
be
awesome
and
I
have
heard
from
customers
that
live
embed
can
be
a
little
scary
because
it
doesn't
walk
so
you
could
have
it
changed
right,
while
it's
going
through
engineering
without
a
process
there.
So
that
was
the
other
question.
I
was
asking
around
snapshotting
or
getting
some
app
real.
I
F
A
great
question
and
part
of
our
workflow
does
address
that
because
we
we
suggest
that
if
you're
going
to
make
a
change,
you
create
an
your
own
personal
draft.
Aside
from
the
current
approved
state,
and
then
we
review
they're
in
a
draft
state
and
then
before
we
bring
in
any
kind
of
breaking
or
progressive
changes.
A
One
little
thing,
I'll
add
is
that
so
in
the
transition
from
sketch
to
pigna
is
not
done
yet.
The
UX
foundations
team
and
a
lot
of
folks
in
general
have
done
a
lot
of
work
on
this,
but
it's
been
a
small
team
because
we
didn't
yet
have
a
contract
sign,
which
is
still
true
today,
I'm
working
through
the
contract
process.
So
it's
part
of
our
budget
once
everything
is
finalized,
then
we're
gonna
open
it
up
more
broadly,
okay,
Sid.
E
The
PM
SNOTEL
Corley
walked
two
of
their
own
section
and
if
you
watch
those,
you
see
them
very
faithfully
sake.
Oh
and
take
a
note-
and
it's
amazing
like
these-
are
like
very
high-level
walk
throughs.
So
there
should
be
no
surprises,
but
there's
like
five
five
surprises
per
ten
minutes
or
something
like
that
of
things.
That
could
be
better
and
it
kind
of
makes
me
think
that
we're
very
focused
on
the
new
things
we're
adding.
But
we
don't
have
a
lot.
A
E
Not
saying
you
actually
be
involved
with
their
turn,
there
YouTube
you
can
watch
them,
but
maybe
it's
good
that
you
wax
also
does
the
same
thing.
They
do
a
quarterly
walk.
I,
don't
think
it
said
like
involving
it's
like
coordination,
and
you
won't
have
been
an
asynchronous
company
like
we
don't
want
to
coordinate
its
find
out
the
PM's.
Do
it,
but
they're
still
finding
a
ton
and
I'm
not
that
new
Xers
haven't
even
better
eye
for
things
that
can
be
improved.
So
maybe
it's
helpful
to
you.
E
A
C
I
would
say
being
in
the
growth
team,
I've
kind
of
seen
them
happening,
but
not
I
mean
within
the
girls
team
doesn't
really
apply,
but
but
the
team
starting
New
York
scorecards,
which
are
by
definition,
going
back
over
and
looking
at
the
top
tasks
that
people
have
to
do
in
the
products.
I
think
like
I've,
noticed
that
the
York
scorecard
findings
kind
of
overlap
with
the
findings
that
the
PM's
have
when
they
do
a
walk
through,
but
I
think
at
the
very
least
each
each.
You
know
stage.
C
I
Get
it's
similar
it's
similar
in
the
access
idea.
We
I
feel
a
lot
of
this
stuff
is
catching
up
in
the
in
the
scorecards
creation,
but
also
as
we
as
PMS
are
going
through
the
walkthroughs
I.
Think.
A
lot
of
this
information
is
coming
back
in
the
issues
later
or
in
in
the
pna-x
discussions,
but
I
actually
like
this
cut
a
suggestion
of
C
to
have.
J
To
address
the
other
piece
of
that,
how
do
we
prioritize
that
work?
So
it
sounds
like
multiple
people
are
going
through
and
doing.
Walkthrough
scorecards
and
recommendations
are
coming
about,
issues
are
created,
but
how
do
we
prioritize
depth
into
our
product
areas?
I?
Think
that's
where
the
real
challenge
is
right
now.
E
I
think
it's
a
great
question.
I
asked
was
slightly
different
I'd
ask:
how
much
do
we
focus
on
the
periphery
and
on
the
center,
like
all
the
new
features
we're
building
by
default
are
on
the
periphery
of
the
product
they're
a
new
part
of
the
product?
How
much
do
we
focus
on
the
periphery
versus
the
center
I'd
love
to
hear
Chrissie
on
that
yeah.
A
We're
looking
right
now
so
going
back
to
you've
got
the
UX
scorecards
and
many
of
those
did
focus
on
the
center.
The
us
management
team
right
now
is
going
back
and
taking
a
look
at
all
of
the
issues
that
were
created.
How
many
were
created,
how
many
we've
actually
addressed
and
starting
to
get
a
sense
of
did
that
work
that
we
did
to
find
those
usability
issues
and
create
issues
for
them
actually
result
in
changes
to
the
product
and
we're
doing
that
literally
right
now,
this
week,
cool.
E
Yeah,
thanks
for
the
screenshots
on
slide,
11
and
12,
and
maybe
shadows,
and
make
sure
that
the
EC
section
of
the
handbook
says
that,
like
all
presentations
in
get
lab,
most
of
the
content
should
be
screenshot
of
the
handbook
of
issues
of
merge,
request,
review,
ABS
data
and
get
up
insidescience
charge,
but
if
you're
creating
the
content
specifically
for
the
presentation,
you're
doing
it
wrong,
and-
and
this
is
doing
it
right
so
I
want
to
call
it
out.
This
is
awesome
to
see
all
of
the
installation
improvements
on
slide
15.
E
C
C
C
E
So,
to
give
an
idea
of
scope
like
do
issues
but
less
than
1%
of
our
users.
A
hundred
percent
of
our
users
hit
this
page
and
it
recently
changed.
Where
now
the
first
thing
we
go
out
installing
gitlab
on
the
Raspberry
Pi,
or
we
also
say
you
need
at
least
four
gigabytes
of
RAM
and
I-
think
the
most
popular
models
for
sure
of
the
Raspberry
Pi
don't
offer
that
I
wonder
if
any
do
also.
E
This
is
like,
probably
like
less
than
1%
of
the
usage
that
we
see
of
gitlab,
and
this
is
probably
more
than
50%.
So
my
first
impression
is
like
get
lab.
Is
that
made
for
a
raspberry
PI's
like
this?
Is
this?
Is
the
the
worst
experience
you
can
possibly
have
if
you
lab-
and
this
is
what
we're
calling
out
on
our
main
page-
that
100%
of
the
people
installing
get
lab
as
the
first
thing
so
simple
things
like
that
are
just
so
important
to
get
right
and
it
used
to
be
that
it
won't.
E
It
was
the
first
thing
and
then
there
be
a
net
cetera,
so
we've
got
to
make
sure
we
nail
the
basics
instead,
we're
in
the
periphery
we're
nailing
the
installation
experience
of
Geo,
which
is
important,
we're
making
money
there
or
if
customers
like
it,
but
it's
1%.
So
let's
make
sure
we
we
do
stuff
like
this,
because
this
very
important
page
for
us
like
this
is
our
lifeblood.
This
is
insulation.
New
give
up
installations
is
our
lifeblood.
C
K
Yeah,
actually
there
is
one
issue
that
Jackie
mentioned
it's
under
AG
lab
/
comm,
and
that
has
another
like
community
contribution
already.
So
there
will
be
one
merger
class
soon
and
the
first
approach
would
be
repositioning.
Those
like
type
of
insulation
and
I'd
like
to
sort
this
out
like,
for
example,
like
outdated
version
of
a
lab
or
some
meet.
Some
link
is
actually
missing,
so
I'd
like
to
remove
them
for
the
first
iteration
and
then
would
like
to
move
on
for
the
second
iteration
for.
E
Sure
I've
noticed
the
same
thing:
if
you
click
on
the
IBM
one,
it
now
feels
because
they
reorganize
their
website.
This
is
on
our
main
installation
page.
So,
instead
of
creating
issues,
let's
start
creating
my
focus
and
actually
fix
things
and
put
things
in
order.
We,
this
is
not
a
very
complex
page
to
rearrange
I
fixed
it.
Nine
months
nine
months
ago,
I
made
changes
to
it.
We
we
should
be
changing
improving
stuff.
We
should
iterate
no
and
I.
Much
rather
have
a
Mercer
crest,
one
improvement
than
an
issue
with
ten
problems.
Yeah.
E
And
the
point
I'm
making
is
in
this
specific
instance
for
this
specific
page,
you
can
fix
it
yourself,
so
don't
create
an
issue
for
stuff.
You
can
fix
yourself.
I've
made
edits
to
this
page.
Other
people
have
of
removing
that
broken
IBM
tile
is
not
rocket
science.
Our
UX
s
can
do
that
I'm,
100%
convinced
so
don't
create
an
issue
for
something
you
can
fix
in
two
minutes.
A
E
I'm,
sorry
and
dominating
questioning
and
deploy
freezes,
hey.
That
sounds
like
something
people
want
to
see,
but
let's
make
sure,
there's
an
override
I
think
that's
my
point
slide
35.
It
says
by
to
continue,
we
have
great
net
expansion
I,
feel
that
because
we
allow
people
to
kind
of
grow
and
then
true
up
later
on
the
by
to
continue
is
the
opposite
of
that.
Some
I
saw
that
screenshot
and
and
I
was
worried.
L
E
Growing
so
I
just
eat
that
our
self-managed
customers
are
growing.
The
idea
for
most
outcome
services
is
that
you
add
additional
seats
or,
like
you,
add
additional
users
and
you
get
built
at
the
end
of
the
month.
That's
how
most
people
do
it.
What
the
screenshot
says
is
to
continue.
You
will
have
to
purchase
additional
seats,
which
is
the
opposite
of
that
yeah.
M
I
can
I
can
add
to
that,
so
we've
actually,
given
the
work
that
we've
been
doing
for
C
link
and
the
quarterly
Co
term,
we
are
gonna
pause
that
work,
take
a
step
back
and
see
given
what
we're
doing
for
self-manage.
Can
we
leverage
that
so
we
can
get
to
a
model,
that's
similar
for
both,
and
that
would
involve
you
know
letting
them
add
and
then
quarterly
to
start
most
likely
doing
that
code
term.
The
same
way
with
was
we're
doing
with
self
manager.
So
that's
the
plan
there.
That
makes
it's.
E
On
the
sense,
I
mean
the
fact
that
we
went
off
to
another
thing.
Maybe
people
aren't
aware,
like
hey,
it's
super
important
to
the
success
of
this
company
that
it's
easy
to
grow
get
lamp.
If
you
put
roblox,
this
is
a
product
light
company.
If
you
put
roadblocks
on
adopting
the
product,
that's
really
gonna
hurt
the
company
point
taken:
Thank
You,
thanks
I.
N
Yeah
yeah
question
not
only
directly
related
to
the
UX
that
partly
this
is
that
you
know
we
are
seeing
a
number
of
customers
and
RFPs,
and
you
know
asking
around
you
know
a
da
508
compliance
and
some
other
you
know,
regulations
around
how
you
know
compliant
get
lab
is
for
those
who
need
accessibility,
so
I
saw
that
there's
posted
link
in
there,
which
is
great
and
that's
something
that
we
need
there.
But
I
was
just
curious
and
you
know
are
we
what
plans
we
have
to
kind
of
work
towards
more
of
those
standards?
N
I
think
you
know
things
like
that
have
been
asked,
specifically
our
tab
indexes
to
be
able
to
navigate
the
pages
through
tagging,
which
you
can't
do
today,
at
least
not
very
far
past
the
the
navigation
so
just
wondering.
If
there's
there's
plans
to
do
more
around
that
and
appreciate
the
link
there
helpful
yeah.
A
There
are
absolutely
plans
to
do
more.
We
also
think
that
this
is
important.
The
work
that
we're
doing
on
pyjamas
right
now
to
get
pajamas
components
implemented
in
the
get
lab
product
will
do
a
lot
to
improve
these
compliance
issues.
Tab
indexing,
I,
agree
with
you,
I,
don't
know.
If
we
have
a
specific
issue
around
that,
if
we
don't
I
would
love
to,
have
you
create
one
and
Tory
Davis
is
the
manager
of
this
and
she
can
work
with
you
if
you
have
questions
or
even
bully
great.