►
From YouTube: Compliance UX: adherence report
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
Oh
hi,
everyone
I,
want
to
quickly
talk
about
the
design
of
adherence
report
and
I
just
want
to
remind
everyone
that
I'm
designing
for
the
future
reading,
instead
of
just
for
MVC.
So
in
that
way,
like
even
we're
doing
MSC,
we
know
that
we're
which
direction
we
are
going
to
and
things
we
designed
all
the
features
that
are
potentially
use
for
the
user.
A
A
This
is
fault
and
when
user,
however,
on
the
file,
they
will
see
a
fail
reason
and
when
user
click
on
this
role,
they
will
see
more
details
and
we'll
talk
more
the
details
later
and
for
this
table
like
there's
several
columns,
the
status
is
very
important
for
the
user
to
know
what
it
is
and
the
check
names
is
basically
like
if
user
familiar
with
the
checks,
they
only
look
at
this
and
they
know
what
it
is
and
the
standard
we
only
use
Sasa
for
now,
but
they
have
different
levels,
and
this
is
a
requirement.
A
A
It
will
be
list
two
product
instead,
like
now,
for
example,
this
potential
file
like
the
same
access
name
and
for
two
different
projectable
lists
separately,
and
we
can
talk
about
downside
and
like
good
sets
like
in
detail
synchronously
to
see
which
one
benefit
user.
Of
course,
I
think
this
thing
we
should
test
with
you
and
ask
for
their
opinion
and
for
the
fixed
suggestion.
Currently,
there
are
two
things
here:
information
and
action
available
and
If
user
click
on
the
row
or
the
button
like
we'll
show
the
drawer.
A
A
So
now
go
back
to
the
report.
Besides
the
general
information
here
we
have
a
filter
session.
On
top
like
the
filters
I
set
up
is
about
status,
standard
and
project.
I
think
this
is
the
quick
way
to
let
user
like
find
out
what
they
need
they
can
based
on
the
status.
Of
course,
it's
important
if
you
only
want
to
see,
fell
or
potential
failed
one,
and
if
you
only
want
to
see
certain
projects,
they
can
do
it
and
the
first
standard.
A
So
far,
we
only
have
Sasa
and
I
do
it
by
requirements
thing
we
can
also
like
have
another
filter,
says
level
I
think
yeah,
probably
like
I,
would
just
to
add
another
one.
Just
called
standard
level.
I
think
I
think
compared
to
the
standard.
A
This
is
less
useful,
but
maybe
for
users
it's
useful.
We
can
test
it
out,
like
I,
didn't
do
it
at
the
beginning,
because
yeah
a
lot
of
them
have
one
two
three
four
levels
so
I
was
thinking,
maybe
they're
not
useful,
but
yeah.
A
Since
we
have
a
space
and
like
for
some
users,
it
might
be
useful
I
only
care
about
certain
level,
so
I
think
that's
copy
thing.
I
will
add
a
drop
down
there
like
after
this
call-
and
those
are
the
two
tips
like
for
each
category,
my
computer
new.
A
They
can
just
quickly
hover
on
it
to
know
the
details
and
if
you
either
click
on
like
either
the
blue
one
or
like
on
the
row,
and
they
will
see
the
drawer
and
make
the
blue
is
just
more
indication
to
tell
you
there
that
this
is
clickable
here.
User
can
directly
go
to
the
project
and
see
the
status
and
the
requirement
file
written
at
least
here
like
more
in
detail
and
how
to
fix,
like
I,
said,
I
think
each
column
at
least.
A
A
So
the
best
way
I
think
is
like
yeah
information
available
when
there
is
information
to
tell
you
that,
hey
you
can
use
the
system.
Log
kitlab
provided
to
just
go
over
and
use
it
and
learn.
More
is
like
go
to
the
documentation,
so
the
blue
button
is
like,
for
example,
when
users-
or
this
is
a
premium
feature
when
user
is
a
premium,
they
can
directly
go
there.
If
not.
This
is
disabled.
A
A
Think
it's
quite
useful
for
the
user
to
turn
on
or
turn
off
certain
standards
even
more
like
quickly
if
his
office
collapsed,
if
it's
on,
we
open
it
by
default,
but
if
user
like
collapse,
it
we
should
remember,
is
collapsed
and
the
user
can
turn
on
and
off
for
each
text
and
to
have
like
on
and
off
for
each
like
project.
So
this
is
not
the
horror
effect
for
the
this
is
figma.
Just
don't
miss
I,
just
realized
I,
don't
think
it
works
for
okay.
A
It
worked
for
ignore
all
the
blue
thing
is
like
not
part
of
the
design.
So
when
you
use
a
hover
on
the
one
column,
it
will
like
have
a
button
show
up
apply
this
to
all.
Like,
for
example,
our
product,
just
I,
think
maybe
this
should
be
near
to
this
one
yeah
I
will
think
about
it
now,
I
think
about.
Maybe
this
is
not
clear
when
it's
here
I
was
thinking
some
quick
action,
for
example,
users
are
like
only
three
projects.
They
want
to
apply
all
the
three
project
to
all.
A
A
I
didn't
think
much
about
it
because,
like
I,
don't
know
how
you,
how
we
add
a
new
like
standard
thing.
I
was
thinking
like
to
be
add
a
new
file
or
if
you
certainly
support
different
like
standards,
that's
like
we
have
a
list
when
users
search
it
or
like
a
drop
down.
It
depends
on
how
much
we
support.
So
this
is
just
a
draft
I.
Don't
think
this
will
be
for
MVC,
because
that's
like
a
require
support,
different,
like
standard
on
the
internet.
A
We
need
to
research
on
a
lot
of
them
and
like
import,
a
new
one
and
like
which
format
is
a
CSV
file.
Yamo
file,
how
to
define
it
I
think
that's
a
lot
of
thing.
It
will
be
like
for
the
future
version,
but
I
want
to
list
out
here
that
potentially
we
can
go
there
to
support
multiple
standard,
not
only
salsa.
A
I
think
that's
kind
of
everything
for
the
future
region
and
then
I
have
some
other
exploration
here.
I
also
think
there
are
my
it's
not
be
in
the
MVC
and
need
more
thinking,
so
I
put
it
there,
so
we
can
have
like
some
kind
of
status
on
the
top
of
the
the
form,
but
I'm
not
sure
is
really
that
useful.
There
could
be
a
like
a
widget
in
the
dashboard
and
on
the
report.
A
Since
we
have
only
three
status,
it
depends
on
how
many
projects
they
have
like
how
many
things
we
can
show
them,
and
another
thing
is
like
either
way.
Group
the
project
by.
A
Status
and
checks-
or
we
separate
them
like,
for
example,
this
is
one
line
or
it
should
be
four
lines,
four
rows,
so
that's
also
something
they
can
discuss
like
personally,
so
far,
I
think
have
a
different
line
is
more
clear
also
when
it
felt
it's
literally
more
strong
to
tell
you
that
you
have
four
things
felt
in
the
form
for
that,
but
might
be
user
have
100
product,
the
ones
100
of
them.
They
want
to
group
them.
So
that's
on
possibility.
It
depends
like,
in
the
most
cases
how
users
want
to
manage
them.
A
So
that's
also
could
be
part
of
the
setting
management
view
or
something
user
can
say:
hey
group
back
project
and
best
status
or
like
just
expand.
Everything
and
now
I
also
have
a
MVC
proposal,
so
I
think
what
I
removed
is
like
the
settings
and
new
standard.
The
managed
standards
there
and
the
manage
standard
feature.
I
think
at
least
turned
on
and
off
would
be
like
all
there
and
select
project
should
be
there
and
yeah
the
the
copy
to
all.
We
can
wait
it
for
later
for
the
fixed
suggestion.
A
I
was
thinking
like
maybe
for
the
MVC,
but
only
up
like
have
information
there
and
later
on.
We
can
link
it
to
like
gitlab
features
and
patterns
suggestions,
and
we
can
check
use
our
premium
ultimate
and
the
pattern
should
be
enabled
disabled
that
could
be
for
the
future,
but
the
rest
of
things
I
think
they
could
be
like
for
the
MVC
and
for
the
filter.
A
I
would
strongly
suggest
to
have
like
at
least
like
status
and
projects
there
so
to
help
user
to
narrow
it
down,
because
they
might
have
really
have
a
lot
of
product
and
status
is
what
they
carries
more
and
for
the
standard.
If,
like
a
lot
of
effort,
we
can
just
remove
it.
A
So
I
think
that's
it
and
everything
will
be
uploaded
so
here
in
the
design
area
feel
free
to
comment
on
it.
So
let's
just
start
the
conversation
like,
of
course,
this
is
not
the
final
design.
It's
my
first
proposal
we'll
also
talk
to
the
users
and
yeah.
Just
let
me
know
what
you
think.
Thank
you
so
much.