►
From YouTube: Compliance: UX Office Hours (2021-02-12)
A
What's
up
everybody,
my
name
is
austin
I'm
product
designer
at
gitlab.
I'm
going
to
do
a
quick
synthesis
on
this
last
week
to
help
update
the
direction
of
ux
for
compliance.
We're
going
to
keep
this
under
three
minutes.
So
here
we
go.
There
was
an
awesome
discussion
on
merge,
request
approvals,
as
we
continue
to
break
down
this
epic
to
plan
for
work.
A
There
was
a
little
bit
of
discussion
some
confusion,
so
I
posted
a
synthesis
of
how
I
understand
the
proposal
to
be
I'm
going
to
sing
with
matt
on
that
this
coming
week
to
make
sure
we're
on
the
same
page,
jumping
to
next
agenda
item.
I've
been
working
a
lot
with
michael
lee
on
the
vision
for
the
settings
of
ux,
and
there
are
definitely
some
opportunities
that
we
can
use
his
design
patterns
that
he's
establishing
to
go
ahead
and
revamp
some
of
the
areas
of
the
settings
that
we
touch.
A
A
It
will
be
somewhere
down
the
road,
but
for
now
just
wanted
you
to
know
that
I'm
collaborating
with
michael
on
how
that's
going
to
play
out
discovered
this
awesome
page.
By
nicholas
this
week,
he
put
together
a
simple
gitlab
page
that
shows
uipolish
merge,
requests
that
have
been
merged
already
fun
fact.
I
do
get
to
appear
in
here,
because
I
merged
a
change
recently
to
fix
the
border
color
of
the
branches
and
tags.
So
that's
fine,
there's
a
ux,
okay!
A
Well,
there's
a
ux
key
result
specifically
to
improve
our
sus
score
by
affecting
the
visibility
system,
status
or
ui
polish
and
the
system's
performance.
I've
started
aggregating
together
a
few
of
the
issues
that
I
could
see
us
delivering.
I
started
talking
with
dennis
earlier
this
week
about
what's
realistic
that
we're
trying
to
do
this
before
the
end
of
the
quarter.
A
A
We
had
a
great
discussion
on
this
idea
of
monitoring
real-time
activity,
we're
still
trying
to
figure
out
who
will
be
responsible
for
it.
This
would
be
another
item
that
matt
and
I
will
sync
up
on
to
make
sure
whether
or
not
we
want
those
as
compliance
or
if
we
should
put
it
under
the
direction
or
really
it's
group
not
end
tbd.
A
Fun
discussion
going
on
in
the
ux
team
about
adding
an
ellipsis
button
for
non-media
buttons.
You
may
not
have
known
this
because
I
didn't
know
it,
but
adding
ellipsis
at
the
end
of
this
button
or
end
of
this
text
rather
is
indicating
that
there's
an
action
that
you
can
take
before
something
will
actually
happen.
You
may
have
noticed
this
when
you
are
looking
in
windows
like
if
you're
under
the
file
menu
dot
didn't
know
that.
A
All
right,
so
another
great
discussion
we
had
was
around
impersonation
events.
We're
gonna
be
figuring
out
where
exactly
that
should
land,
how
it
should
be
offered
and
just
really
great
thoughts,
and
I
think
this
table
is
awesome.
It's
super
helpful
for
understanding
how
things
are
captured
where
and
who
can
see
those
things.
A
Some
of
those
may
be
updated
soon.
Last
but
not
least,
I
spent
some
time
this
week
continuing
to
refine
my
map
on
our
different
features
that
I
could
discover
between
the
docs
and
our
issues
board.
I
had
mapped
those
to
their
respective
categories
and
then
I
was
trying
to
tie
those
to
jobs.
Still
some
work
to
do.
I
think
in
terms
of
the
job
statements,
but
this
at
least
gives
me.
Hopefully
all
of
you
a
better
understanding
of
maybe
how
our
layout
is
in
terms
of
how
we
affect
the
product.