►
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
A
B
The
most
exciting
thing
for
me
recently
has
been
adding
more
researchers
to
the
team
and
that's
been
fantastic
and
I'm,
really
pleased
that
Italian
Lhari
are
on
board
and
I'm
excited
about
what
that
means
and
like
we
can
do
moving
forwards.
So
one
of
the
things
that
we're
kind
of
looking
into
doing
at
the
moment
is
creating
training,
videos
and
templates
and
they're
people
across
get
web
to
use,
and
so
we
we're
researchers,
but
we
on
other
people
to
be
able
to
do
research
as
well.
B
So
it's
asking
like
this
series
of
videos
for
doing
user
interviews,
so
these
are
primarily
aimed
at
product
managers
and
designer
just
I
get
well.
But
if
you
perhaps
work
in
marketing-
and
you
feel
that
you
want
to
talk
to
some
users,
then
by
all
means,
come
and
have
a
look
at
the
templates
and
stuff
that
we've
got
and
I'm
feel
free
to
kind
of
go
ahead
and
speak
with
users.
I
think
that's
really
exciting
and
that
more
people
will
be
doing
user
research.
B
A
A
A
A
It
also
meant
that
their
teams
who
they
work
with,
had
to
pick
up
the
slack.
So
a
big
thank
you
to
those
people.
I
mean
this
is
a
really
comprehensive
effort,
and
if
anyone
is
interested,
you
can
see
in
that
blog
article.
Some
examples
of
things
that
got
closed
out
some
of
the
more
interesting
things,
and
then
it
also
talks
about
where
we're
going
next.
C
C
Conversation,
it's
not
on
my
first
Frazer
I
was
confused
as
well
when
they
don't.
C
C
Thanks
for
pointing
that
out,
yeah,
so
I
have
a
question
on.
In
general.
Our
our
notion
is
is
to
have
a
product
that
works
across
different
personas
and
and
so
we
have
a
lot
of
different
pieces
of
different
functionality
across
different
personas
and
different
stages,
and
we
see
like
our
major
competitor,
Microsoft
doing
what
a
lot
of
our
competitors
do,
which
is.
Oh,
we
have
all
these
pieces
they're
just
in
different
apps,
we'll
just
put
them
in
a
menu
and
in
that
obviously
loses
something.
C
Know
against
something
like
that:
the
behemoth
of
Microsoft
but
has
I
call
functionality
just
in
different
places,
is
the
fluidity
and
and
how
it
all
ties
together.
What
do
we?
How
do
we?
What
do
we
think
about?
How
are
we
making
sure
that,
as
we
add
capability,
is
that
it's
not
that
there's
a
a
clean
story
across
all
of
it
across
the
personas
across
the
different
functionalities,
as
opposed
to
just
adding
new
screens
in
different
neo
on
a
menu.
A
Sorry,
my
internet
went
down
couple
of
minutes,
so
I
was
briefly
gone,
but
I
think
what
I
caught
the
end
of
that
question,
which
I
think
was
around
as
we're
adding
additional
functionality
to
the
product
additional
features
to
the
product.
How
do
we
make
sure
that
it's
a
connected
and
seamless
experience
is
that
is
that
right.
A
So,
and
so
it's
not
an
easy
problem
to
solve,
especially
when
you
think
about
how
we
work,
which,
by
the
way,
it's
not
the
wrong
way
to
work.
It
just
adds
additional
challenges
as
we
work
in
stage
groups,
they're
kind
of
siloed
down
to
you
know
pretty
narrow
scopes
of
focus,
but
workflows
may
go
across
those
stage
groups.
So
two
things
that
I
think
will
help
with
this
and
I'd
love
to
have
my
my
other
UX
managers,
chime
in
on
this
but
I.
A
A
So
it's
focused
on
understanding
the
most
critical
workflows
that
are
originating
in
stage
groups,
but
then
seeing
how
those
workflows
play
out
not
just
across
that
stage
group
necessarily
but
across
the
product
in
general,
and
so
those
are
some
of
the
things
that
we're
we're
doing
and
Sarah
I.
Don't
know
if
you'd
like
to
chime
in
or
any
of
my
other
managers
about
the
channel
yeah.
B
Should
it
go
under
settings?
Should
it
go
in
the
sidebar?
Should
we
have
a
global
notification
icon
for
it?
There's
so
many
different
things
you
can
do
with
the
navigation
at
the
moment,
but
the
problem
is:
there's
not
space
for
everything
and
we
need
to
design
vacation
that
works.
You
know,
for
the
majority
of
our
users
and
different
personas.
B
B
And
I
think
just
to
add
to
that,
it's
like
we.
We
don't
want
to
just
keep
chipping
away
and
then
aggregation
research
as
well.
We
don't
want
to
do
these
kind
of
small
studies
that
just
temporarily
tell
us
where
to
place
and
think
we
want
to
do
something
where
we
take
it
back
to
the
basics.
We
look
at
it
holistically
and
work
out.
What
features
need
to
be
where
for
the
like,
all
our
personas
and
what
works
best?
It
needs
a
big
strategic
research
effort.
B
A
A
D
Yeah
I'll
walk
through.
We
have
here
and
answer
any
questions.
So
a
couple
highlights
just
to
pull
out
here.
First,
a
style
audit
of
the
docs.
We
had
recently
instituted
a
number
of
new
styles
or
clarified
styles
in
our
style
guide
around
insuring
the
docs
remain
or
ensuring
we
have
a
single
source
of
truth
for
all
the
content.
So
essentially,
you
know
avoiding
duplication
and
you
know
linking
out
rather
than
repeating.
D
Another
page
ensuring
that
when
you
do
get
to
a
page,
you
know
that
that's
the
that's
the
source
of
the
information
you're.
Looking
for
by
clarifying
introductions,
you
know
we
have.
We
have
a
lot
of
engineers
and
others
who've
worked
on
our
Doc's
over
time,
so
to
go
back
and
do
an
audit
and
that
audit
can
be
for
various
things
and
we
can
do
other
kinds
of
audits.
But
in
this
case
we
picked
a
series
of
what
we
thought
were
important
styles
and
we
did
a
first
first
phase,
we're
in
a
second
phase.
D
Now
we're
gonna
continue
throughout
the
docs,
but
but
as
of
a
few
weeks
ago,
we
completed
this
first
phase
and
we
resolve
some
of
those
issues
there,
including
one
of
our
standards,
is
to
have
all
relevant
information
about
the
feature,
and
that
includes
troubleshooting
information,
or
you
know,
workarounds
things
that
some
folks
may
wonder
should
I
include
this
in
Docs
or
not.
Is
this
too
much
of
an
itch
workaround?
D
Is
it
too
much
of
an
exception?
So
the
answer
from
our
style
standpoint
is:
yes
include
it
there,
because
that's
where
folks
are
looking
for
that.
For
that
feature,
including
adding
a
troubleshooting
section,
we
don't
have
a
whole
bunch
of
empty
troubleshooting
sections
so
we're
we
don't
yet
have
troubleshooting
content.
We
have
now
added
a
placeholder
for
that
information,
so
that
especially
support
who
we've
been
working
with
to
make
sure
that
support
is
adding
more
content,
especially
they
can
now
go,
go
add
trouble,
shooting
information
to
each
dot
page.
D
We
can
think
in
the
future
about
whether
we
want
to
aggregate
that
in
some
way
and
make
it
visible
at
the
top
level
of
a
section
what
the
various
troubleshooting
items
are
within
that
section,
but
for
now
storing
that
actual
content
within
the
most
relevant
page
really
gives
users
the
best
chance
of
finding
the
information
they
need
without
actually
needing
to
create
an
issue
or
contact
support.
So
that
was
some
of
what
we've
we've
done.
There's
an
epic
link
there
for
details,
happy
to
answer
questions
about
that.
D
One
and
the
other
one
we
we
chose
to
highlight
here
is
just
around
the
alignment
of
the
docs
across
code
bases
in
line
with
get
labs
a
broader
single
code
base
effort.
So
we
just
completed
that
the
last
and
one
of
them
are
challenging.
Parts
of
the
docs
were
the
API.
So
that's
now
condensed
where
you
know
when
there
are
separate
responses
to
the
API
or
separate
fields,
depending
on
whether
you're
in
C
E
or
you
now
have
a
single
doc
page.
That
explains
all
that.
So
across
our
Doc's
we
handle
both.
D
We
handle
all
tiers
of
get
lab
on
any
given
doc
page
with
labeling
of
what
is
exclusive
to
a
certainty
or
work
to
your
range.
So
that's
now
complete
and
we
have
a
safeguard
in
place
through
the
pipeline
to
make
sure
that
additional
changes
aren't
introduced
only
into
EE,
as
we
used
to
used
to
do
to
make
it
so
that
you
can
simply
merge
contents
EE.
It
gets
Auto
emergency
EE
and
you
can't
actually
merge
content
exclusively.
It's
a
EE,
so
this
parody
should
should
remain
and
it
will
enable
the
broader
effort.
D
A
Here
we
welcome
some
new
folks
to
the
UX
team
and
Marcel
was
a
huge
contributor,
if
maybe
not,
maybe
even
the
contributor,
to
that
alignment
of
Cee
and
EE
Doc's
he's
been
a
good
lab
contributor
for
quite
a
while
emember
super
thrilled
to
have
him
on
the
team,
and
we've
also
got
Jackie
Bower,
who
is
a
new
UX
manager
for
an
agreement
and
growth
where
he
would
occur,
who's
a
new
UX
senior
us
next
researcher,
so
you
heard
Sarah
talk
about
her
team
growing
and
we're
really
excited
to
have
Laurie
and
then
so
Jeremy
elder
is
our
new
senior
visual
designer
I
mentioned
this
in
our
last
group.
A
Conversation
and
Jeremy
is
really
picking
up
that
UI
beautification
issue.
He
effort
and
he's
already
jumped
in
and
he's
doing
some
amazing
things.
So
we're
excited
to
have
these
folks
on
our
team.
I,
don't
see
any
more
questions,
actually
I'll
jump
to
this
slide,
which
is
around
the
design
system,
push
and
I'm
hoping.
Maybe
Tory
is
right
about
this.
One
yeah.
E
I'm
here
so
this
slide
shows
the
amount
of
components
that
we've
completed
so
far
in
q2
of
fiscal
year
20.
So
we've
closed
out
two
and
we
have
six
that
are
really
close
to
being
closed
and
then
there's
another
14
that
have
been
started
and
the
way
that
this
is
working
currently
is
that
stage
groups
are
responsible
for
completing
a
component
within
our
design
system,
so
it'll
be
introduced
into
Ghaleb
UI
and
then
the
docs
will
be
shown
within
pajamas.
So
I
showed
here
the
merge
requests
over
this
past
quarter.
E
E
Ui
merge
request
that
week
too,
so
you
can
see
that
this
quarter
a
lot
more
work
is
being
done
in
the
pajamas
components
which
is
great
and
we,
the
goal
was
to
close
out
around
32
to
36
I
forget
the
exact
number
components
this
month
or
this
quarter
and
it
looks
like
about
22,
have
been
in
progress
and
we're
on
a
good
track.
There
so
it's
exciting
to
see.
A
Yeah
pajama
is,
is
a
hugely
exciting
project
for
the
UX
team
in
terms
of
raising
the
quality
of
the
product
because
of
consistency
having
a
single
source
of
truth,
components
is
going
to
make
such
a
big
difference
and
writing
consistency
throughout
our
UI
and
also
in
terms
of
productivity
both
for
designers
and
for
front-end
engineers.
It's
just
when
we
can
get
through
this
it'll
be
a
huge
win
for
a
lot
of
people.