►
From YouTube: Compliance: UX Office Hours (2021-05-21)
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
Hey
everyone:
my
name
is
austin,
I'm
a
senior
product
designer
at
gitlab,
so
I
wanted
to
walk
you
through
a
few
things.
This
week
we'll
say
it
was
more
of
a
depth
rather
than
brep
type
of
situation.
So
we
had
a
nice
handbook.
Change
come
in
to
try
and
work
streamline
the
way
that
ux
collaborates
with
product.
It's
encouraging
us
to
really
bring
what
we're
working
in
each
milestone
into
our
planning
issue.
A
So
how
that
will
manifest?
Is
I've
added
two
things
to
our
planning
issue?
The
first
is
I'm
highlighting
our
ux
board,
which
I'm
doing
a
better
job
of
keeping
up
with,
and
these
are
scoped
specifically
to
an
iteration
which
isn't
perfectly
aligned
with
the
milestone,
but
it
gives
you
more
of
an
idea
of
what
I'm
focusing
on
in
like
a
two
week
frame,
as
opposed
to
like
the
entire
milestone
at
one
time
also
doesn't
really
confuse,
then
what
is
planned
to
deliver
in
that
milestone?
A
A
I
still
plan
on
building
out
some
more
sections
to
it.
So
this
is
a
living
document.
I
wouldn't
call
this
done
for
sure,
but
then
I
also
started
taking
the
features
out
of
our
docs
to
try
and
start
mapping
those
to
our
categories
as
well,
because
that's
not
necessarily
what
users
care
about,
but
that's
how
we
can
perceive
how
we
deliver
value.
A
What's
neat
about
this
is
you
can
see
like
where
you
might
have
a
free
feature,
but
you
need
an
ultimate
license
to
take
advantage
of
more
compliance
needs.
What's
also
cool
about
this
video
is
you
can
see
how
we've
used
a
lot
of
the
main
features
that
are
developed
by
other
groups,
other
stages
and
started
extending
them
for
ourselves
to
make
compliance
an
easier
thing
in
gitlab?
I
want
to
talk
about
more
where,
like
these
things
are
concerns
or
cares
for
cameron.
A
So
this
is
a
great
example
where
map's
wrong
place,
but
enforcing
terms
of
service
is
something
that
ties
directly
to
gdpr.
That's
what
we
want
to
help
highlight
so
that
users
can
connect
their
frameworks
with
our
features.
A
And
lastly,
I
got
to
go
through
some
fun
ideation
with
pithika
on
the
pipeline
pill.
A
So
what
this
could
look
like
is
using
some
dashed
lines
as
well
as
tying
into
the
theme
of
the
color
of
a
compliance
framework
to
help
visually
distinguish
this
compliance
job
in
the
pipeline
from
a
project
job.
This
could
be
a
neat
way
to
really
tie
some
of
the
different
elements
together
and
also
give
clarity
to
users,
so
they're
not
confused
about
it,
and
we
can
continue
to
use
this
badge
throughout
the
ui.