►
From YouTube: UX Weekly Call - Feb 9, 2021
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
A
A
A
B
She
is
yeah,
I'm
also
here
yeah,
sorry
to
interrupt
you,
but
you
definitely
welcome
to
the
team
and
you
want
to
introduce
yourself
answering
those
questions
that
we
have
in
the
agenda.
C
Yeah
well
hi
everyone.
My
name
is
emily
and
I'm
a
product
designer
from
toronto,
and
I
just
joined
the
team
yesterday
before
gitlab
I
was
at
capital
one,
so
I
was
working
in
banking
for
a
little
bit
and
then
before
that
I
was
at
ibm,
so
that's
kind
of
where
I
grew
as
a
designer.
C
I
wanted
to
join
gitlab
really
for
what
I've
read
about
the
amazing
culture
here
and
really
hasn't.
Let
me
down
so
far,
so
I'm
really
excited
to
kind
of
get
to
work
with
all
of
you
and
yeah.
I
wanted
to
join
the
growth
team
in
particular,
because
my
background
was
in
acquisitions
and
like
customer
acquisitions
before
too
so
excited
to
kind
of
work
on
that
yeah.
C
So
and
what
I
like
to
do
outside
of
work
is
I
just
like
to
do
everything
outside,
so
I
used
to
before
kind
of
the
world
shut
down
was
traveled
a
lot
got
into
camping
a
lot
over
the
last
summer
and
then
just
to
relax.
I
have
my
two
cats
at
home,
so
I
just
hang
out
with
them
or
do
art
I'm
a
big
into
like
painting.
I
got
back
into
painting
and
yeah.
Well,
it's
really
nice
to
meet
everyone
and
excited
to
join
the.
A
Yes,
welcome
very
excited
to
have
you
on
our
team
all
right.
We
have
a
short
agenda
today,
but
this
conversation
may
take
a
little
while
so
that's,
okay,
our
q1
sus
okr,
so
super
excited
about
this.
For
anyone
who
missed
it.
The
two
themes
that
we'll
be
focusing
on
during
q1
are
ui
polish
and
system
performance.
A
We
did
vote
the
pms
voted
and
long
story
short.
It
was
effectively
a
tie,
but
the
votes
that
came
in
really
aligned
pretty
well
along
sections.
So
the
dev
and
ops
sections
really
wanted
to
focus
on
ui
polish,
and
so
that's
what
they
will
do.
The
secure
and
enablement
sections
really
wanted
to
focus
on
system
performance.
So
that's
what
they
will
do.
Every
body
on
this
team
can
contribute
to
this
okr
and
I'm
excited
to
see
you
do
it.
A
D
Thank
you
christy,
so
I
am,
I
think
I
just
clicked
wrong
button
here.
I'm
thrilled
to
be
able
to
sit
here
and
talk
a
little
bit
about
this,
because,
after
working
on
all
these
documents,
spreadsheets
things
like
that
we're
at
a
point
now
where
we
can
actually
work
together
as
a
team
on
these
things.
So
for
me
this
is
very
exciting.
I
put
a
link
in
there
to
a
deck
that
talks
about
a
lot
of
the
big
themes
that
were
identified.
D
This
shouldn't,
or
you
should
probably
all
know
a
little
bit
about
this,
but
there
are
six
major
themes
that
appeared
after
looking
through
lots
of
lots
of
data
not
only
with
sus
but
looking
beyond
that,
and
when
we
talk
about
ui
polish
I'll
start
with
that
one
first.
D
Admittedly,
we
are
looking
at
how
we
define
that
today.
I
know
that
hayana
and
marcel
were
like
literally
in
an
mr
talking
about
that
now,
so
we
may
see
that
change
a
little
bit
or
we
may
not.
But
what
showed
up
in
a
lot
of
the
data
were
these
sub
themes
and
there
was
a
there
was
a
major
sub
theme
in
ui
polish,
and
that
was
really
around
letting
users
know
what's
happening,
so
these
are
actually
some
of
them
are
verbatim.
D
Some
of
them
are
taken
from
issues
that
fall
within
the
ui
polish
theme,
and
when
we
look
at
this,
it's
really
about
plain
and
simple.
Just
letting
people
know
if
there's
a
status,
and
these
are
things
that
you
can
all
do
through
ui.
So
that's
how
this
sub
theme
landed
here.
There's
lots
of
there's
lots
of
areas
across
the
whole
product,
so
the
best
way
to
approach
this
one
is.
D
I
would
advise
you
strongly
not
to
just
think
about
ui
polish
in
general,
because
that
probably
means
things
like
alignment
on
pixels
or
colors,
or
things
like
that.
It
does
yes,
but
we're
looking
at
it
from
the
perspective
of
usability
and
with
that
in
mind,
there's
this
sub
theme
that
has
surfaced
up
as
being
a
paint
point
with
our
sus
score.
B
D
E
Well,
one
of
the
usability
heuristics,
I
know
is
providing
system
feedback.
So
I
guess
I'm
trying
to
make
the
connection
between
what
we're
saying
is
polish
and
and
that
concept,
but
a
recent
example
that
came
to
mind
for
me
was
we,
I
think,
actually
have
an
issue
about
this.
But
we
are
in
the
process
of
moving
a
feature.
The
move
project
feature
to
a
different
menu
and
we
had
a
discussion
about
how
we
provide
feedback
to
the
user
that
we're
moving
it.
E
Do
we
leave
the
current
link
where
it
is
and
then
duplicate
it
for
a
period
of
time
and
kind
of
track,
the
usage
of
it
in
the
original
location,
or
do
we
move
it
and
then
communicate
it
somewhere
in
the
ui?
So
there's
been
a
lot
of
discussion
around
that,
but
I
guess
I'm
trying
to
better
understand
what
polish
is
and
I
know
it's
being
defined
still,
but
it
seems
like
it's
feedback
to
me.
D
It
it
definitely
can
be
yeah.
Your
example
is
a
little
tricky
because
it's
like,
if,
if
we
do
that,
all
the
time,
what
would
our
ui
look
like?
So
I
would
probably
I
would
think
a
little
bit
more
about
that
one,
I'm
happy
to
follow
up
with
you
on
that
specific
example.
But
yeah
I
mean
if
I
were
to
say
at
a
high
level.
Is
it
around
feedback
on
some
things?
I
think
status
definitely
falls
into
that
so
yeah.
D
D
Great,
the
other
one
is
around
system
performance.
So,
as
I
mentioned
with
our
process
of
theming,
we
found
four
sub-themes
within
here
and
this
one.
When
you
look
at
this
title,
you
may
think.
Oh,
this
isn't
me.
This
is
probably
back
end
type
work
and
that's
not
necessarily
true
when
let
me
go
here:
okay,
so
within
system
performance
there's
these
four
so
lack
of
real-time,
accurate
updates,
because
there
are
some
updates
that
are
happening,
but
there
may
not
be
that
up
to
date
or
accurate
and
people
have
to
sometimes
refresh
their
browser.
D
We
we
all
know
about
that.
I
think
there's
instances
when
we're
not
remembering
information,
the
system's
slow
and
the
general
weirdness
one.
D
This
is
where
I
think
ux
can
probably
help
the
most,
because
these
are
things
that
are
like.
Are
they
bugs?
Is
it
designed
that
way
and
when
we,
when
we
sub
theme
this,
we
didn't
want
to
just
say
these
are
bugs,
because
I
don't
think
they're
all
bugs.
I
think
some
just
weirdness
around
this
is
happening.
Does
this
meet
users
expectations
what's
their
mental
model
around
some
things?
D
So
this
is
a
great
opportunity
for
some
research
to
happen
so
within
your
areas,
think
about
these
four
sub-themes
and
even
even
helping
identify
those
for
your
teams.
That
would
be
incredibly
helpful.
The
verbatims
that
we
have
here
please
for
all
these
slides.
Don't
look
at
this
as
just
this
is
this:
is
it
the
entire
list?
There
are
a
lot
more
within
the
spreadsheets.
Those
are
all
linked
here
and
even
with
those
go
beyond
that
like
just
because
that's
not
all
inclusive
either.
D
So
I
view
all
of
you
as
experts
in
your
area,
your
stage
groups
that
you
spend
all
your
time
in
and
just
look
at
those
experiences
very
detailed
with
these
lenses
and
I'm
I'm
calling
these
sub
themes
lenses.
So
if
you
think
that
something
is
slow,
call,
it
out,
create
an
issue,
put
put
the
proper
label
on
it
and
we
can
actually
conduct
some
research
as
a
next
step.
D
D
The
last
item
I
want
to
talk
about
is
research,
so
my
team,
we
will
be
helping
as
much
as
we
possibly
can
with
researching
here
around
sus
there's
gonna,
be
I'm
expecting
there
to
be
a
lot
of
research
because,
as
changes
are
proposed,
we
definitely
want
to
have
a
high
degree
of
confidence
that
what
we're
proposing
is
indeed
an
improvement
to
what
is
out
there
now.
D
So,
with
that
being
said,
anna
on
on
the
research
team,
she
has
she's
working
on
an
on
an
okr
actually
to
create
a
a
that
allows
everybody
to
utilize,
quick
turnaround,
testing
and
we'll
be
using
some
usability
related
metrics
very
closely
tied
to
the
sus.
D
That
would
allow
all
of
you
to
test
very
quickly
and,
of
course,
utilizing
user
testing
whenever
possible,
so
we're
able
to
get
quick
results
back
and
move
forward
with
a
bit
more
confidence,
so
we
will
make
that
more
public
once
that
is
finalized,
it's
still
in
it
in
a
draft
mode,
but
we'll
definitely
follow
up,
probably
in
one
of
these
meetings
and
walk
through
what
that
process
is.
D
A
Yeah
I
had
some
stuff,
so
you
mentioned
that
there's
an
mrn
process
around
ui
polish
and
how
we
previously
defined
it
and
how
we're
defining
it
now.
D
Yeah,
so
that's
that's
actually
what
I
just
asked
in
the
mr,
so
I'm
proposing
that
we
expand
it
out.
We
think
about
things
that
fall
under
the
usability
umbrella,
ui
polish
elements
that
impact
usability.
So
that's
that's
a
discussion.
That's
happening
right
now,
christy.
F
I
was
just
commenting
the
yeah
so
mike
mike
long's
comic
kind
of
touches
on
it,
like
maybe
it's
usability
polish
or
something
like
that.
Instead
of
you,
like
the
interface
and
like
the
the
thing,
we're
talking
about,
seems
to
be
more
aligned
with
the
experience
and
improving
the
experience
that
the
user
is
having
and
less
about
the
actual
interface
of
like
the
the
foundations
of
a
spacing
color
things
like
that,
which
is
what
we've
previously
attributed
to
ui
polish,
so
expanding
it.
F
A
Yeah,
if
we
do
make
a
change
to
how
we
want
to
do
this,
for
the
okr,
how
we
want
to
talk
about
it,
we
need
to
make
sure
to
communicate
that
really
clearly
and
broadly
so
that
everyone
is
aware
of
the
change.
This
is
an
interesting
one,
because
our
traditional
definition
of
ui
polish,
that
stuff
is
important
too.
A
I
just
saw
a
comment
from
a
customer
today:
who'd
taken
a
screenshot
and
they'd
given
kind
of
a
broad
range
of
feedback,
but
it
was
a
screenshot
of
ui
text
that
was
butting
up
against
a
button
and
their
feedback
I'm
paraphrasing
but
effectively.
It
was
when
I
see
stuff
like
this,
it
dings
the
credibility
of
your
product.
I
assume
that
if
this
is
happening,
then
other
worse,
things
are
happening.
So
these
are
important
things
to
tackle
too.
G
Yeah
and
in
a
previous
discussion,
we
also
thought
about
completely
getting
rid
of
ui
polish,
because
we
didn't
know
exactly
what
we
needed
it
for
and
when
we
had
the
discussion.
One
of
the
things
that
came
out
of
it
was
that
these
issues
would
often
be
very
good.
First
issues
to
tackle
for
new
team
members
would
often
be
very
good
to
tackle
for
community
contributors
because
they
are
a
bit
away
from
functionality
and
large
things
in
the
code
base
for
more,
like
small
things
that
we
could
easily
fix.
A
Yeah,
I
was
just
thinking
the
same
thing
jared
because
when
you
think
about
it,
a
lot
of
this
stuff-
really
they
are
bugs
they're
minor
bugs
but
they're
bugs
and
bugs
do
get
triaged
differently
than
yeah.
I
I
I
think
it's
I
agree
with
the
with
adam,
as
in
yeah
we
can
polish
the
ui
and
therefore
solve
usability
issues.
So
there's
a
new
one
within
ui
polish.
That
fits
this.
The
conversation
we're
having
about
the
the
shared
okrs
anyways
comment
on
the
issue
it's
coming
in
the
mmr,
so
we
can
continue
the
discussion.
A
J
Had
a
quick
question,
if
I
could
interrupt
just
in
terms
of
ui
polish
versus
what
jarek
just
said
about
bugs
we're
not
going
to
differentiate
in
that
in
this
okr,
for
example,
right
so
I've
in
my
group,
I've
identified
some
ui
polish.
That
I
think,
would
be
really
nice
and
would
also
a
lot
add
a
lot
of
feature
to
the
platform.
But
it's
not
necessarily
a
bug
fix
so
to
speak,
or
it's
not
something
broken
right.
A
A
Yeah
we'll
get
this
tightened
up,
asap,
okay
and
then
adam
answered
my
next
question.
I
asked
how
teams
should
use
the
specific
examples
in
the
slides,
so
I
just
want
to
reiterate:
you've
got
examples
in
the
slides.
You've
got
examples
in
the
spreadsheet,
so
one
your
teams
could
go
and
look
for
things
that
are
relevant
to
your
group
and
address
those
things,
but
you
don't
have
to
do
that
to
adam's
point.
You
are
all
subject
matter
experts,
as
are
your
pms.
A
If
you
think
that
there
are
things
that
are
more
impactful
than
the
things
noted
in
the
slides
in
the
spreadsheet,
then
you
have
the
autonomy
to
make
that
call.
But
if
nothing
else
look
at
what's
in
there,
they'll
give
you
context
for
what
users
are
saying
and
maybe
kind
of
jog
your
imagination
for
things
that
you
might
tackle.
D
D
I
don't
know
the
exact
number
of
hours
we've
been
wallowing
in
this
data,
but
we
know
it
quite
well
and
if
there's
any
questions
or
even
if
your
team
wants
to
have
a
workshop
and
have
one
of
us
there,
we
are
happy
to
jump
in.
A
K
It
has
been
interesting
if
you
ever
have
free
time
that
you
somehow
can't
use
otherwise,
just
read
that
sheet:
you
will,
you
will
get
lost
in
there,
but
I
I
wanted
to
go
back
to
one
point
under
the
ui
polish
topic
in
the
with
the
introduction
of
the
variable
about
ux
bugs.
K
I
don't
know
how
my
question
might
fit
in,
but
I
wondered
if
we
could
discuss
a
few
examples,
because
to
give
you
context
when
I
was
working
with
the
sus
data
and
categorizing
by
ui
polish,
it
was
kind
of
thinking
of
things
like
things
that
are
aesthetic
improvements,
but
also
misalignment
of
text.
Inconsistency
in
one
page
versus
another
page
status
indicators.
So
if
we
could
add
examples
of
how
those
would
be
categorized
into
the
different
things,
so
ui
polish
versus
ui,
ux,
ui
bug
and
things
like
that,
that
would
be
very
helpful.
A
I
think
that's
an
excellent
point
and
it's
interesting
because
you
kind
of
keep
bouncing
back
and
forth
here
between.
No
these
things
should
be
separate
and
wait
a
minute.
No,
this
is
all
like
kind
of
part
of
the
same
general
problem.
Examples,
I
think,
are
a
great
idea,
and
I
love
that
you're
calling
out
that
again,
those
aesthetic
improvements
also
make
a
big
difference.
So
we've
got,
we've
got
a
variety
of
different
things
we
can
tackle
as
part
of
you,
I
polish,
adam
and
valerie.
A
A
A
All
right,
y'all
are
all
the
best,
not
just
valerie
and
adam.
Thank
you
for
everything
that
you
do.
I
hope
you
have
a
wonderful
day.