►
From YouTube: UX Group Conversation (2020-06-25) - Advance Video
Description
This video gives a preview of the 2020-06-25 UX Group Conversation.
A
First
I
want
to
welcome
some
new
people
to
our
team.
Adams
mullinski
has
joined
us
as
the
director
of
UX
research
really
excited
to
have
him
leading
our
research
team.
He
comes
from
a
background
of
those
conducting
and
leaving
teams
that
conduct
research
at
technology
companies
and
then
also
in
fast
iterative
and
actionable
ways,
which
is
how
we
like
to
work
at
get
labs,
so
really
excited
to
have
his
experience
and
input
in
leading
our
research
team
and
then
I
also
want
to
welcome
vesica
and
Austin
as
new
designers
on
our
team.
A
I
also
want
to
point
out
that
we've
written
a
few
blog
articles
over
the
past
months
that
you
might
want
to
check
out
in
particularly
you
might
want
to
look
at
how
we
created
a
dark,
UI
or
get
labs
web
IDE.
And
then,
if
you
work
in
our
front-end,
you
want
to
check
out
the
13
dotto
contributor
experience,
update
and
as
a
reminder.
Every
two
weeks
we
had
a
UX
showcase
for
designers,
share
both
designs
and
research.
Both
work
in
progress
and
things
have
been
finished,
really
good
way
to
see
what's
happening
in
our
product.
A
Now,
when
I
talk
about
our
q2
okay,
ours
and
getting
an
update
on
their
progress,
so
one
of
okay,
our
focuses
on
improving
the
love
ability
of
merge
requests.
This
is
really
important
because
merge
requests
are
a
really
critical
area
and
high
use
area
of
our
product,
and
we
want
to
make
them
best-in-class.
So
you
can
see
that
we
have
many
changes
that
both
have
already
been
implemented
in
the
13.1
milestone
or
in
progress
for
the
13.2
milestone
and
we're
about
53
percent
complete
on
this.
A
Okay,
our
I
want
to
point
out
on
three
of
this
table.
Accept
multiple
merge,
requests
suggestions
at
once.
This
is
a
change
that's
already
in
the
product,
and
it's
one
I'm
particularly
excited
about
merge
requests,
often
have
many
suggestions
associated
with
them,
and
previously
you
had
to
go
through
and
accept
those
one
by
one
but
oftentimes
you
want
to
accept
most,
if
not
all,
of
the
suggestions,
so
this
new
capability
allows
you
to
queue
those
up
and
commit
them
all
at
once
with
one
pipeline.
A
I
also
want
to
point
out
a
change.
That's
coming
in
13.3,
we've
recognized
that
there
is
a
problem
when
you
first
submit
a
merge
request,
there's
a
message
that
displays
on
the
screen
for
a
few
seconds,
but
there
are
a
few
confusing
seconds
that
makes
it
look
as
though
something
has
failed
with
your
merge
request,
and
then
it
resolves
itself,
but
that's
friction
for
our
users
and
it's
a
confusing
amount
of
time
that
they
have
to
just
sit
there
and
think
did
I.
Do
something
wrong.
A
So
that's
something
that
we're
also
gonna
be
fixing
not
hindering
for
this
okay
arm,
just
couldn't
quite
make
it
in
for
that,
but
we'll
be
fixing
thirteen
and
then
we're
also
working
to
improve
the
LOV
ability
of
issues
again,
another
critical
area
of
our
product.
So
we
already
shipped
one
change,
which
is
sticky
issue:
titles
oftentimes
when
we're
working
with
issues
we're
coming
from
a
to-do
or
from
an
email
notification.
A
A
This
is
important
not
just
for
gitlab,
but
our
users
and
it's
better
for
us
to
have
fewer
support,
calls,
but
also
users
don't
want
to
call
support.
They
prefer
self-serve
if
they
can,
and
the
intention
of
this
OKR
is
to
make
it
easier
for
them
to
do
that.
We've
committed
to
updating
30
Docs
pages
as
part
of
this
OKR
and
again
they
are
most
highly
used.
Docs
pages
by
the
support
team.
14
of
those
improvements
have
already
been
merged.
A
We're
also
going
to
surface
those
articles
on
the
copula
documentation
section
of
our
Doc's
home
base,
not
all
30,
but
probably
the
top
10
again,
making
it
easier
for
people
to
find
the
documentation
that
they
want
in
need
and
then
we're
also
working
on
a
project
to
help
self
manage
users
to
scale
better
with
reference
architectures.
Previously
we
didn't
have
reference
architectures
and
now
we'll
have
reference
architectures
that
start
as
small
as
2,000
and
go
up
to
50,000.
A
A
We
migrated
from
sketch
to
figma
which
we've
talked
about
in
the
past.
We
also
know
that
our
team
is
not
the
only
team.
That's
gonna
work
with
Sigma.
So
if
you're
a
new
to
Sigma,
you
wanna
learn
more
about
how
we're
using
Sigma
at
git
lab
we've
got
documentation
available
for
you
also.
We
now
have
a
pyjamas
UI
kit
slack
update
bot,
so
it
updates,
in
slack
in
the
design
system,
slack
Channel
every
time
that
there
is
a
change
to
the
shared
asset
library
for
the
UI
kit.
A
A
really
exciting
thing
is
the
alpha
release
of
dark
mode,
and
this
has
been
the
most
highly
one
of
the
most
highly
requested
issues
at
get
lab.
People
have
really
been
looking
forward
to
this.
This
is
an
LFO
release.
It's
not
even
beta.
We
know
that
there
are
bugs,
but
it's
something
that
we're
really
excited
about
and
we
went
ahead
and
released
it
early
so
that
those
people,
users,
insight,
gitlab
and
then
also
the
members
of
our
wider
get
lab
community
can
help
us
find
those
bugs.
So
we
can
begin
to
resolve
them.
A
And
this
is
a
funny
one.
We
now
have
a
gitlab
if
some
lorem
ipsum
text
generator,
so
if
you're,
tired
of
using
weird
lorem
ipsum
in
your
wireframes
either
the
standard,
lorem,
ipsum
or
bacon
ipsum
or
whatever
you
might
have
been
using
and
now
you
have
a
get
leg
if
some
of
its
based
on
content
from
our
handbook,
issuable,
x'
and
dots.
This
is
a
really
fun
little
side
project.
A
From
a
couple
of
our
members
of
our
git
lab
team,
if
you're
interested,
you
should
give
it
a
try
and
then
some
things
to
notice
about
dots,
our
Ducks
team
just
did
a
content
on
it,
learn
some
really
interesting
things
about
the
size
of
our
documentation
site,
how
frequently
we
are
updating
it
and
the
impact
of
our
documentation
site
to
users.
This
was
the
first
step
in
us
making
some,
hopefully
some
really
nice
changes
to
our
documentation
site.
A
We
also
have
UX
research
underway
to
help
us
learn
more
about
what
users
want
and
need
from
our
documentation
site.
But
if
you're
interested
craigmorris
recorded
a
video
and
talks
about
some
of
the
things
we
learned
just
from
the
data
and
the
content
on
it
and
then
also
I,
think
it's
worth
mentioning
that
we
recently
had
an
effort
to
remove
some
offensive
terms
from
our
documentation.
So
that
includes
changing
black
lists
and
white
lists
to
deny
lists
and
allow
lists
and
also
removing
some
references
to
slave
in
the
context
of
master
slave.