►
From YouTube: CI/CD By-weekly UX Meeting | 12th August 2020
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
Bi-Weekly
yeah
we
have
couple
of
read-only
items,
of
course,
for
for
checking
in
we
don't
have
any
updates
in
the
your
stage
group
part
just
wanna
again
pause
and
reinforce.
If
anybody
has
anything
interesting
happening
in
the
stage
groups
that
you
wanna
share,
yeah
actually
ian,
you
are
doing
some
interesting
parts
with
that
new
unmoderated
testing.
Maybe
that's
a
good
one
to
share
for
awareness.
C
Yeah,
I
was,
I
will
add
it
to
the
agenda,
but
we
are
doing
unmoderated
testing
to
validate
an
updated
design
to
some
settings
that
we
have
on
the
package
side
of
things,
and
it
was
funny
because
laurie
and
I
were
trying
to
come
up
with
a
way
to
use
zoom
to
make
like
a
makeshift
unmoderated
test
and,
at
the
same
time,
adam,
I
believe,
was
kicking
off
trying
out
some
different
solutions
and
so
we're
going
to
run
it
as
a
pilot
of
usertesting.com
and
see
what
that
experience
is
like.
C
I'm
really
excited,
because
I
think
unmoderated
testing
like
this
could
really
open
up
a
lot
of
doors
for
how
we
do,
especially
in
the
solution.
Validation
stage
of
the
main
question
is:
does
this
help
you?
I
think
it's
a
really
powerful
tool
and
the
it
gives
us
more
space
to
be
able
to
do
quality,
more
qualitative,
moderated
testing
during
the
problem,
validation
stage?
Why
are
you
having
this
problem?
Why
do
you
think
these
things
are
there?
So
it's
exciting
to
get
more
tools.
D
No,
no,
it's
I'm
so
excited
that
you
had
the
the
project
come
up
at
the
same
time,
that
adam
was
looking
at
these
different
tools,
so
it
seems
perfect
based
on
the
ones
that
I've
done
in
the
past.
I
think
what
we're
really
wanting
to
understand
is
the
amount
of
time
it
takes
to
set
it
up.
Of
course,
this
way
I
asked
you
that
the
other
day
and
then
how
robust
their
panel
is
to
recruit.
D
So
if
we
gave
them
because
there's
like
two
different
kinds
of
contracts,
I
guess
you
could
sign
with
them
one
you
do
your
own,
recruiting
with
them
only
or
the
other.
You
could
rely
on
them
and
if
we
rely
on
them,
it's
quite
more
expensive,
but
if
they
have
a
good
group
of
people
to
pull
from,
then
hey
emily
can
be
used
in
other
aspects.
A
Awesome
thanks
for
sharing,
I
think,
that's
an
important
part
because
on
moderating
testing,
that's
like
a
step
to
well,
maybe
I'm
wrong,
but
it
feels
like
a
step
to
a
maturity,
as
in
some
way
so
really
exciting.
I'm
looking
forward
to
see
the
results
of
that
thanks
for
sharing
in
yeah.
I
know
anything
else
that
we
want
to
mention.
E
Here
I'm
very
excited
about
this.
I
I
think
I
talked
with
united
about
this
in
the
past
as
well,
that
I
really
thought
that
the
moderated
testing
was
something
that
we
are
missing
and
that
eventually
it
will
like
help
us
like
in
many
areas
where
it
just
makes
sense
to
just
sometimes
not
be
in
front
of
the
computer
trying
to
guide
the
design,
but
just
let
the
user
like
on
their
own
time
figure
it
out.
I
think
that
there's
something
powerful
about
that.
E
You
know
because
I
think
the
the
problem
is
more
on
how
you
instrument
the
design
or
like
the
artifact
that
they're
gonna
use
while
they
perform
this
in
a
moderated
way,
but
they
think
we
can
figure
out
that
as
we
keep
exploring
this,
but
I'm
very
excited
to
learn
how
yeah,
what's
gonna
be
the
result
of
this.
So
please
sure,
once
you
guys
have
that.
A
Cool,
so
I
now
remember
that
we
talked
with
you
about
that
f1
as
well,
alrighty
then
moving
on.
I
have
an
interesting
thing
kind
of
like
that.
I
wanted
to
a
topic
that
I
wanted
to
bring
up
with
you
all
and
collect
maybe
some
thoughts
or
like
at
least
try
to
figure
out
what
is
happening
here.
This
came
from
the
discussion
with
marcel
about
you
add
that
definition
we've
been
like.
A
I
don't
know
if
you
have
been
seeing
there
is
a
lot
of
discussion
around
that
topic
going
on,
and
actually
this
issue
right
now
is
a
collection
of
all
of
the
discussions
around
what
is
ux
that
what
is
ux
back
and
actually
there
is
another
issue
or
an
mr
connected
to
that-
one
about
defining
the
ui
polish,
but
first
we
kind
of
want
to
figure
out
what
does
ux
that
mean
to
us
today
at
gitlab
and
what's
different
between
the
ux
block
and
that
and
then
we've
been
going
with
marcel
into
investigation.
A
Do
we
because
in
the
ux
handbook
we
say
that
the
ux
depth
is
a
intentional,
like
kind
of
like
pool
user
experience
that
we
dedicate
to
fix
later
and
then
because
it's
intentional,
we
are
not.
We
suppose
we
supposed
to
not
have
a
severity
label
for
that
higher
than
s3,
but
if
we
go
into
the
gitlab
issues
or
if
you
filter
for
ux
depth
and
s
two,
which
is
severity,
two,
we
actually
see
already
five
issues
which
were
before
twelve
or
ten.
A
I
don't
remember
and
like,
unfortunately,
all
of
those
are
coming
from
our
team
cicd,
not
that
I'm
not
throwing
how
to
say
stones
into
anybody's
gardens
for
sure
I'm
just
trying
to
figure
out
like.
Why
do
you
think
this
is
happening?
A
Maybe
this
is
happening
from
like
a
wrong
understanding
of
what
you
asked
that
mean,
or
maybe
like
not
enough
spreading
of
this
yeah
of
this
term
anyway,
just
wanna
throw
it
to
your
to
you
and
see
like
have
you
noticed
this
before
that
we
actually
have
ux
depth
for
s2
and
maybe
you're
familiar
with
some
of
these
issues,
and
you
have
some
ideas
where
why
they're
appearing
and
where
they're
coming
from.
E
Well,
we
talked
about
it
yesterday
you
and
I
on
our
101,
but
I
think
I,
my
my
initial
understanding
of
ux,
that
I
didn't
was
wrong
until
I
read
that
issue,
I
think
I
got
like
it
got
the
meaning
of
you
accept
this
anything
that
was
decided
intentionally
to
and
it
was
decided
that
it
was
going
to
be
addressed
later.
So
that's
the
that
part
right.
E
I
think
many
people
didn't
know
that
or
don't
know
that,
because
they
are
mapping
to
like
the
like
to
the
tech
depth
idea
of
like
others.
You
know,
there's
things
that
feel
like
that,
but
they
are
not
intentional
right,
like
there's
many
things
that
decisions
that
were
made
in
the
past,
not
necessarily
things
that
were
intentionally
made
and
purposefully
like
thought
to
be
addressed
later.
E
So
I
think
that
that
means
many
people
apply
the
ux
that
label
very
in
a
very
liberal
way,
and
I
think
that's
how
you
end
up
with
s2s
plus
ux.
That's
I
don't
think
because
there's
a
relationship
between
both
of
them,
but
that's
just
my
that's
just
a
thought.
I
I
don't
know.
A
Yeah,
but
I
think
you
are
touching
the
right
point
to
be
honest
and
yeah.
I
know
ian
that
there
is
not
much
of
your.
There
is
none
of
package,
so
it's
probably
like
harder
to
judge
I'd,
be
curious
to
hear
what
else
do
you
meet
other?
He
is
also,
but
I,
but
I
think
I
agree
with
your
thoughts
juan,
and
this
is
why
I
think
it's
also
a
really
good
timing
for
discussing
those
the
difference
between
the
two,
no
hey,
dimitri
you're,
joining
at
a
really
good
time.
F
Hey
sorry,
for
being
late
time
flies,
I
was.
I
was
busy.
A
No
worries
hey.
We
are
talking
about
this
point
here
about
the
ux
depth
and
the
severity
two
labels,
and
I
know
that
you've
been
super
active
on
that
discussion
and
I'm
bringing
here
a
point
that
I'm
not
sure
if
I
shared
with
you
earlier
where,
when
looking
when
filtering
for
issues
that
have
you
have
step
and
severity,
two
labels,
so
which
is
like
a
kind
of
like
against
what
we
say
in
the
handbook
that
it
should
not
be
higher
than
severity.
A
Three,
we
come
up
with
a
list
of
five
issues
and
and
quite
a
lo
like
all
of
them-
are
them
rci
cd,
and
there
are
few
in
continuous
integration.
For
example,
I
wanted
to
hear,
like
juan
already
said,
that
he
thinks
that
severity
two
plus
ux
depth
happens
because
we
probably
not
all
on
the
same
page
what
you
asked
that
means
in
gitlab,
because
yeah
there
is
a
lot
of
different
understandings,
but
I
wanted
to
hear
your
thoughts
here.
What
do
you
think
is
the
problem
if
you
have
any
thoughts.
F
Yeah,
that's
that's
a
good
question.
I
think
that
the
the
issue
linked
here
I
highlighted
here
now
actually
really
includes
a
lot
of
useful
feedback
and
how
everybody
perceives
you
know.
Ux
debt
versus
ux
bug
and
my
latest
comment-
and
I've
also
had
some
conversation
with
marcel
about
this.
F
But
my
latest
comment
revolves
around
that.
The
latest
description
offered
by
valerie
she
says.
Basically,
she
wants.
You
accept
label
description
to
be
changed
to
the
following,
which
is
a
follow-up
issue
that
occurs
when
an
intentional
decision
is
made
to
deviate
from
the
mvc
which
sacrifices
the
user
experience.
F
So,
for
example,
if
I
plan
out
an
issue-
and
it
might
be
in
in
a
way
that
an
issue
will
be
implemented
in
in
several
parts
to
become
it
in
its
viable
state-
and
that
is
perfectly
reasonable
to
to
expect,
because
that
is
the
the
reason
we
have
feature
flags
in
a
way
right
like
all
right.
We
don't
ideally
want
such
features
to
be
accessible
to
the
public
and
therefore
we
have
feature
flags.
F
So
we
can,
you
know,
diminish
our
our
risks
there,
but
this
does
mean
that
we
can
introduce
issues
with
high
severity
labels,
because
it
is
part
of
that
road
to
the
actual
viable
minimal
change.
F
So
I
was
wondering
what
your
thoughts
are
on
that
and
how
and
that
that
kind
of,
like
from
my
point
of
view,
that
would
validate
a
reason
for
being
of
of
such
issues
that
you
adapt
or
ux
bug
with
high
severity
labels.
I
think
we're
often
geared
towards
a
single
issue
should
mean
mvc.
Well,
I
don't
think
that
is
actually
the.
E
Case,
can
I
add
a
thought
to
that.
I
think
that
another
another
thing
that
I
that
I
was
thinking
while
dimitri
was
giving
his
his
thought
on.
This
is
very
related
to
what
you
said
about
the
issue
not
being
not
capturing
the
whole
nbc.
I
think
that's
true.
It
also.
E
E
Any
decision,
any
decision
that
you
take
for
the
sake
of
iteration
or
mvc,
it's
going
to
incur
on
ux
that
or
that's
the
feeling
that
I
get
out
of
the
definition
right,
because
many
times
we
decide
on
things
like
okay,
we're
not
going
to
make
these
super
complex
because
we
want
to
be
fast
and
we
want
it
to
rate
them.
We
want
to
get
feedback,
but
that
definition
conflicts
a
little
bit
with
the
idea
of
yeah.
E
If
we
go
by
that
definition,
everything
that
we
create
on
an
mvc
is
gonna
incur
on
that
you
know.
So,
if
that's
how
it's
been
applied,
then,
like
many
people
might
like
be
thinking
that,
like
yeah,
I'm
just
seeing
I'm
just
thinking
that
it's
like
the
liberal
use
of
ux,
that
it's
what
creates
that
situation
of
s2s
or
s3s
with
ux
steps?
It's
not
because
of
the
ux
step.
It's
mostly
because
in
that
sense,
everything
will
be
ux
that
right,
a3.
F
This
is
in
a
way
ux
that
and
like
for
some
of
the
things
I
would
say
even
like
you
know,
coming
from
the
the
discussion
inside
of
the
issue,
there
is
the
clear
difference
between
ux
depth
and
ux
bug
as
it
being
intentional
or
not,
but
for
some
of
the
functionality,
even
still,
we
are
looking
at
legacy
code
or
legacy
ui.
That
hasn't
been
touched
in
a
while.
Nobody
knows
if
it
was
intentional,
yes
or
no
should
it
in
that
case,
be
ux,
bug
or
ux
that
I
I
have
no
idea.
G
Yeah,
hey
kiana,
by
the
way.
A
So
I
make
sure
that
I
think
those
are
great
thoughts
and
actually
what
I
will
encourage
in
order
to
move
on
everybody
who
has
thoughts
in
regard
the
difference
between
ux
depth
and
your
spark
just
please
visit
this
issue.
First
of
all,
read
all
of
the
really
useful
info
there,
but
also
leave
your
thoughts
there
as
well.
So
we
can
carry
this
discussion
to
to
the
issue
and
also
contribute
our
thoughts
and
make
sure
that
they
are
visible
to
ours
to
others.
A
I
think
this
is
super
useful
because
it
is
an
important
topic.
That's
been
up
and
down
for
quite
so
few
times
recently
so
yeah.
A
All
right,
if
are
we
okay
with
moving
on
or
anybody
feels
like?
There
is
an
important
point
still
to
talk
about.
G
A
Yeah
a
little
like
at
an
easy
yeah
all
right.
Moving
on
to
my
next
item.
It's
it's
more
in
fyi.
I
just
wanted
to
give
a
heads
up.
I've
been
talking
with
some
people
on
the
team
and,
like
I
feel
like
we
have
a
lot
of
discussions
about
the
ux
definition
of
done
its
usefulness
or
it's
not
usefulness.
A
I
know
that
we
are
today
running
their
process
in
release
management
and
in
ci,
and
just
an
fyi
heads
up
that
I
want
to
schedule
like
a
retro
or
a
discussion
discussion
in
async
way,
probably
for
us
at
the
end
of
august,
we
can
share
the
learnings
and
yeah,
like
maybe
find
some
tips
for
other
stage
groups
who
would
like
to
adopt
that
in
the
future.
A
A
Yeah
mitika
says
that
she
is
excited
to
share
the
her
experience.
That's
good.
G
Okay,
juan
over
to
you,
oh
sorry,
I
I
thought
this
was
like
a
continuation
of
this
one
topic
on
the
ux
dod.
I
had
my
first
retro
with
the
with
jackie.
Today.
I
think
we
applied
the
ux
dnd
for
four
milestones.
Five,
maybe,
and
we
made
some
decisions
on
how
we
want
to
use
it.
G
I
know
they're
different
from
the
way
that
vitica
is
trying
to
implement
with
the
verify
and
we've
decided
that
we're
gonna
apply
it
only
at
the
epic
level
or
like
the
nbc
levels,
because
there's
too
many
steps
for
small
things,
and
also
that
once
we
are
like
you
know,
validating
things
talking
to
customers
and
we
are
busy
with
actual
work.
G
We
don't
go
back
to
update
it
as
much
so
it
serves
as
a
way
to
guide
us
and
tell
us
where
we
are
in
the
ux
process,
but
it
should
not
constrain.
You
know
what
we
do
and
since
we
want
to
have
some
sort
of
structure
for
the
big
items,
we're
gonna
start
experimenting
as
of
q3
with
ux
dod
for
epics,
slash
nbc's
only
and
that's
pretty
much
it.
So
I'm
happy
to
share
this
next
quarter.
This
quarter,
I'm
not
sure
which
part
we
are
anymore.
A
This
is
an
interesting
learning,
I
think,
yeah,
because
there
were
some
what
struggles
but
like
yeah,
positives
and
negatives
from
vitic
as
well
so
sounds
like
it's
gonna
be
a
great
session.
Thanks
for
a
heads
up,
yeah.
B
E
Yeah
no,
I
just
wanted
to
say
that
we
have
that
kr
through
the
migration
buttons
and
other
things
that
need
to
be
migrated,
not
only
buttons,
but
we
we
started
with
buttons
and
if
anyone
needs
help
with
that,
I
already
migrated
four,
and
I
have
another
couple
that
opened
a
march
for
that.
So
I
think
I
already
got
like
a
good.
Oh
yeah,
like
a
good
idea
how
to
do
it.
E
So
if
anyone
needs
help,
feel
free
to
yeah
reach
out
to
me,
put
some
time
on
my
on
my
calendar
or
schedule
some
time,
yeah
anything
that
you
need.
I'm
happy
to
help.
That
was
just
announcement.
A
Thanks
juan,
you
are
definitely
a
star
there,
hyanna
linking
the
okrs.
There
is
a
main
ux
one
and
I
will
link
this
ui
cd,
one
as
well
yeah,
if
you,
if
you
all,
have
any
questions
reach
out,
because
there
was
quite
some
discussions
laurie
over
to
you.
I
think
in
the
meantime,
juan
if
you
are
done.
D
Yeah
so
andre,
and
I
kicked
off
the
ci
adoption
journey
project
earlier
today.
We'd
already
done
some
stakeholder
interviews
to
kind
of
wrap
our
heads
around
what
this
thing
is.
So
we
uncovered
a
lot
of
inconsistencies
which
actually
helped
us
to
focus
on
our
research
efforts.
So
we've
got
like
four
or
five
different
research
projects
in
this
project
and
we're
gonna
go
all
the
way
through
the
quarter
with
it
it'll,
probably
wrap
up
by
the
end
of
october
there'll
be
some
other.
D
I
don't
call
them
milestones,
that's
usually
what
we
call
them,
but
that's
what
we
call
our
sprints,
so
some
other
end
points
in
there
as
the
different
efforts
wrap
up
and
per
direction
from
our
stakeholders.
D
We
will
be
working
with
jason
and
kenny
to
put
merge
requests
in
to
actually
update
several
pages
on
our
in
our
handbook
and
on
our
website
concerning
the
information
that
we
find
out.
So
our
task
is
to
understand
what
is
adoption.
How
does
that?
How
do
our
customers
define
that?
Where
does
it
start?
Where
does
it
end?
D
But
there
are
a
lot
of
people
who
don't
do
web
apps.
So
we
want
to
understand
if
what
are
the
differences
there
and
if
there
are
any
and
yeah
so
we've
got
lots
of
projects,
and
this
is
all
linked
into
that
epic.
We've
got
children
epics
and
then
issues
so
we're
also
trying
to
dog
food,
the
gantt
chart
as
well
for
project
management,
so
that
was
fun.
A
Cool
and
just
because
we
talked
with
you
a
bit
earlier
about
that,
I
guess
for
now
there
is
no
action
items
for
product
designers
funny
and
I
see
the
clapping
icon
on
your.
So
there
is
no
action
items
from
designers
expected
for
now,
but
I
guess
I
guess
I
expect
a
lot
of
really
really
useful
information
also
for
they
will
probably
influence
jobs
to
be
done
in
in
some
way.
Maybe
for
some
stages,
I
don't
know.
I
expect
a
lot
of
what's
coming.
D
I
think
for
ci
and
see
if
they're,
different
or
the
same
or
how
that
is
going
to
get
looked
at
and
consumed,
but
definitely
we'll
have
that
in
that
as
an
output,
and
I
suspect
that
this
information
will
trickle
down
later
to
all
of
us,
because
runners
are
a
part
of
this
testing's.
A
part
of
this
there's
there's
many
many
facets
that
are
part
of
this,
but
it
won't
be
apparent
immediately,
but
it'll
hopefully
make
it
into
everybody's
road
maps
for
maybe
q4,
maybe
next
fiscal
year
as.
A
G
We
are
talking
to
coutures
about
group
releases.
I
think
I
mentioned
this
in
the
my
last
ux
showcase,
I'm
going
to
add
the
link
here
and
then
we're
doing
using
internal
customer
interviews
and
validating
some
of
the
prototypes
and
some
of
the
assumptions
that
we
have
about
the
workflow
and
it's
great
when
you
get
you
know
very
destructive
feedback,
it's
like
when
the
things
that
you
show
are
not
the
things
that
people
expect.
G
So
it's
been,
it's
been
fun
to
actually
get
that
sense
and
the
perspective
from
users,
because
we
want
to
have
the
ability
to
associate
this
project
releases
at
the
group
level,
but
then
hijacking.
G
But
then
we
also
started
talking
about
what
comes
next,
so
the
ability
to
add
assets
to
release
of
the
group
level-
and
today,
martin
mentioned
something
as
a
specifying
release,
notes
or
description
to
that
group
release.
So
it's
been
interesting
to
get
this
kind
of
feedback
and
jackie
from
them
just
mentioned
that
we're
talking
to
customers
about
group
releases.
We
want
to
add
anything
differently.
H
Yeah
super
excited,
although,
as
I'm
learning
more
about
it,
I
get
more
nervous
about
how
this
will
change
like
the
side
panel
and
what
we
want
to
package
up
for
useful
insights
and
then,
of
course,
I'm
learning
a
lot
of
our
enterprise
customers.
Don't
really
use
groups
and
projects
in
the
same
sort
of
manner
or
architecture.
H
So
group
releases
are
kind
of
great
for
a
micro
services
project
where
you
have
a
bunch
of
projects
that
subgroups
that
feed
into
a
single
customer's
application
or
experience
not
really
the
same
way
if
they
have
like
subgroups
that
are
about
business
operations
or
hr
processes
and
have
nothing
to
do
with
like
a
code
deployment
but
excited
all
together.
A
Well,
it
sounds
like
some
really
important
data
that
can
influence
a
lot
of
things
exciting,
very
close
to
to
being
done
very.
F
A
Like
now
wrapping
up
the
the
the
user
research
to
kind
of
like
what
do
you
say
summarize,
the
data.
H
I
spoke
with
steve
and
spoke
with
tim
fossenberger,
oh
gosh,
I
just
butchered
his
last
name
if
you're
watching
this
recording
later
and
then
we'll
have
hopefully
another
couple
of
people
internally
and
then
externally.
I've
talked
to
two
customers
about
it
and
we're
using
dovetail
to
track
all
this
stuff.
So
eventually
we'll
extract
like
the
10
nuggets
that
will
build
our
feature
from
all
of
the
you
know,
500
insights
that
I
create.
A
Awesome
thanks
for
sharing.
I
see
that
so
many
people
added
some
stuff
about
the
research
immediately
you're
next.
F
Yeah
I'll
keep
it
brief.
I
was
just
talking
with
nadia
about
this
yesterday
and
for
a
b
testing,
I've
gone
a
little
bit
extra.
I've
done
some
some
more
interviews
than
than
what
is
normal,
but
there
was
some
of
it
internal
and
some
of
it
externals.
That's
the
reason
why,
but
it
is
interesting
to
note
that
the
quality
of
the
feedback
from
the
internal
participants
was
way
higher
than
from
the
external
participants,
not
that
that
is
a
given.
F
But
in
this
case
it
was
like
that-
and
I
found
that
an
interesting,
an
interesting
thing
to
share,
and
that
mostly
revolves
around
the
fact
that
I
think
that
the
internal
participants
better
reflected
the
customers
that
we
will
be
developing
for
than
the
external
participants
I
was
interviewing
with.
But
regardless
there
was
still
valuable
input
from
the
external
participants
and
also,
as
a
last
note
to
that,
I
have
been
interviewing
the
external
participants
later
than
the
internal
ones.
F
So
perhaps
I'm
a
little
biased
because
I
knew
most
of
it
already
and
then
there
was
a
lot
of
you
know,
duplicated
feedback,
I'd
say
and
then
some
little
extra
nuggets
of
information
added
to
that.
So
just
for
your
information.
But
if
anybody
has
any
comments,
I
would
love
to
hear.
A
We're
curious
to
hear
your
perspective
on
internal
feedback
more
being
more
valuable
than
external.
D
It
just
depends
on
where
we
are,
I
think,
in
this
stage
of
the
feature
or
the
function,
if
we're
still
kind
of
in
that
dog
fooding
stage,
then
it
makes
sense.
D
But
if
we
move
beyond
that,
it's
more
important
to
get
other
perspectives
like
hayanna
and
jackie
are
finding
out
that,
once
you
talk
to
people
outside
of
our
walls,
they
may
do
things
differently
and
there
may
be
a
good
reason
for
it.
With
my
merge
request
research,
we
don't
like
to
do
large,
merge
requests
right.
D
We
strive
to
do
small,
so
does
everybody
else,
but
they
have
to
deal
with
legacy
code
that
we
don't
necessarily
have
to
deal
with,
so
their
reality
is
a
little
bit
different
than
ours
and
when
we
don't
think
about
those
large
merge
requests
and
we
only
design
and
support
for
small
ones,
merge
requests
can
get
unwieldy,
really
really
fast.
So
it's
important
to
step
outside
of
our
our
walls
every
now
and
then.
F
I
was
I
was
like
moving
my
mouse
towards
the
mute
button.
No,
it
wasn't,
it
wasn't
doing
well,
a
good
job
of
it,
yeah
thanks
thanks
for
that
feedback
or
lori.
That
makes
a
lot
of
sense,
and
I
still
think
we
we
got
some
valuable
feedback
and
perhaps,
as
a
last
note
that
I
think
for
the
internal
participants,
most
of
them
also
could
explain
about
their
experience
from
their
previous
job,
which
makes
it
almost
like
an
external
participant
in
this
case
almost.
D
Yeah,
that
is
helpful.
I
think
it's
more
of
the
situational
aspects
that
might
differ
than
their
inability
to
remember
from
before.
So
it's
funny
like
you
might
have
the
same
job
at
a
different
company.
You
come
here,
you
kind
of
do
the
same
thing,
but
if
you
are
in
a
different
industry
or
a
different
organizational
structure
or
different
tools
that
you
were
dealing
with,
it
could
be
different,
but
I'm
glad
that
you
got
some
feedback,
that's
more
any
feedback's
better
than
no
feedback.
F
A
Cool
thanks
for
sharing
that
ian
over
to
you,
you
have
the
next
point.
C
Yes,
we
wrapped
up
the
interviews
for
the
dependency
proxy
category
vision
test.
It
went
really
well,
we
got
really
consistent
results
and
we
pulled
from
both
the
sales
sam
team
and
from
our
traditional
recruiting.
C
As
you
see
it,
would
it
help
your
team,
the
participants
from
our
traditional
recruiting
their
answers
were
a
little
softer,
a
lot
more.
Like
oh,
be
cool,
or
you
know
it's
a
free
cookie.
Of
course,
I
would
versus
those
that
were
coming
from
the
sales
teams
had
a
very
direct
answer.
Yes,
it
would
work
for
these
reasons
or
no.
F
Yeah,
this
was
just
in
case
there's
some
extra
time
left
in
in
the
handbook.
F
I
created
a
merch
quest
for
progress
delivery
where
I'm
showcasing
the
ux
okrs
there
directly,
so
I
don't
always
have
to
go
and
find
the
epic
and
see
what's
going
on
there
and
also
I
have
introduced
specific
stage
oprs
for
press
delivery,
starting
with
quarter
three
and
the
nice
thing
about
this
is
that
this
is
extendable
for
everyone,
similar
as
the
jobs
to
be
done,
format
that
we
already
had
so
I'll
briefly
share
my
screen
and
I'll
give
you
a
very,
very
two
minute
small
demo
of
it.
F
F
The
ocrs.yaml
file,
if
it
loads-
and
here
you
can
see,
there's
like
this-
this
structure-
you
can
follow,
there's
an
objective.
There
are
the
key
results
you
can
add.
However
many
you
like,
and
if
you
go
back
in
time,
there's
you
know
for
q1
or
q2,
there
will
be
some
progress
reported,
for
example,
for
the
for
the
q2
okrs
of
the
ux.
F
You
can
say:
hey
we,
we
got
100
here
and
of
course,
there
are
some
optimizations
to
be
made
there,
but
the
nice
thing
about
this
is
that
if
you
go,
for
example,
to
your
archive,
got
a
dedicated
archive
section
here,
where
you
can
see
r8
from
past
opr's,
but
if
you
want
to
see
how
this
is
implemented,
that
is
like
a
single
line
of
code
and
just
to
showcase
that,
let
me
see,
there's
the
okr,
so
it's
this
single
line
of
code
that
is
displaying
a
partial
that
has
another
single
line
of
code,
sort
of
that,
but
basically
look
into
it.
F
If
you
want
to
add
the
ux
department
okrs
to
your
handbook
page,
you
are
basically
able
to
copy
this
and
paste
it.
If
you
want
to
create
your
own,
just
add
it
to
the
yaml
file
and
adjust
as
needed
won't
be.
It
won't
be
super
difficult.
I
think
it's
helpful
and
it
might
be
useful
to
you
too,
as
well.
A
A
I
feel
like
we're
going
to
skip
next
week
and
I
know
that
we
are
not
full
and
just
dropped
and
you
guys
know
joining,
but
just
wanted
to
ask
if
there
are
any
like
retro
items
or
issues
that
you
are
encountering,
and
maybe
you
need
some
help
or
maybe
you
have
overcame
something
something
that
could
be
useful
to
others.
A
We
going
to
down
to
the
retrospective
part-
and
I
know
it's
it's
too
early
for
19's,
but
the
next
week
we're
going
to
skip.
So
it's
going
to
be
over
that.
So
I
wanted
to
see
to
hear
if
anybody
is
encountering
any
issues-
or
you
know
like
have
any
interesting
learnings
as
a
retrospective
part,
to
discuss
right
now,
or
we
can
just
finish
this
session
earlier.
G
G
I'm
happy
because
I
wouldn't
do
it.
Otherwise,
if
we
were
in
this
this
intense
and
I
I
definitely
learned
things
that
I
wouldn't
learn
here
on
at
gitlab
more
in
the
sense
of
the
theory
of
research
and
yeah
using
different
software.
G
So
it
was
definitely
a
different
opportunity,
but
I
was
a
student
for
a
month,
a
full-time
student,
so
that
was
very
challenging.
I'm
still
recovering.
I
G
A
Yeah
on
that,
no
some
note
something
that
I
learned
is
that
a
break
is
definitely
needed
and
I'm
talking
about
the
vacation
all
about
the
learning
I
took
a
week
and
a
bit
more
of
vacation
this
month
and
I
feel
great
I
also
like
connecting
with
family
so
for
those
who
have
an
opportunity
to
do
that
right
now,
these
crazy
times
it's
super
mentally
helpful,
so
yeah
those
people
who
did
not
take
a
vacation
in
a
long
time
make
sure
you
do
so
and
especially
enjoy
the
family
and
friends
day,
because
this
is
what
it
is
for.