►
From YouTube: Engineering Productivity OKR update 2022-04-19
Description
Engineering Productivity team OKR updates on 2022-04-19
A
A
A
So
we've
done
great
progress
through
the
tooling
that
matia
and
the
team
have
worked
on
and
continuing
that
will
help
make
sure
that
we're
able
to
act
on
new
community
contributions
quickly
without
being
without
the
old
stale
community
contributions
being
mixed
in
next.
Reducing
undefined
merge,
merge
requests
to
15.
So
this
is
this.
Kr
is
in
alignment
with
looking
at
our
merge
request.
Output
for
our
is
part
of
product
projects
which
is
being
used
as
input
into
the
next
prioritization
model
for
get
lab
engineering.
A
A
We've
done
a
lot
here
and
the
next
step
that
we're
looking
to
do
is
to
have
danger
fail,
at
least
for
a
subset
of
projects,
to
learn
when
a
merge
request
type,
isn't
there
and
see
how
much
friction
that
that
creates
in
the
merge
request
process,
as
well
as
kind
of
defining
practices
for
teams
to
roll
out
danger
to
the
rest
of
there
is
part
of
product
projects.
I
think,
having
a
baseline
set
of
expectations
for
those
projects,
I
will
help
make
sure
that
our
metrics
around
all
of
them
are
consistent
and
of
sufficient
quality.
A
Lastly,
updating
tooling
for
new
merge
to
request
subtypes.
I
think
this
is
mostly
complete.
I
need
to
go
in
and
do
some
admin
things,
but
it's
set
to
95
right
now:
okay,
jihu,
sas
developer,
tooling,
so
moving
these
to
jihulab.com.
This
has
been
completed
early
on
the
quarter.
Great
work
by
junction
on
this
next
was
time
to
purse
failure.
We
are
currently
around
25
minutes,
which
is
great
from
where
we
started
the
quarter.
A
A
We
do
have,
I
think,
four
candidates
in
late
late
stages
of
the
team
interview
with
three
set
up
or
about
to
be
at
least
two
set
up
for
executive
interview.
I
should
say
I
don't
want
to
show
my
screen
so
that
this
can
be
posted
on
unfiltered,
but
we
are
making
great
progress.
We
may
not
get
two
engineers
this
quarter.
A
We
may
end
up
with
one,
but
we
should
have
enough
momentum
going
into
the
next
quarter
to
hire
one
shortly
after
that,
and
hopefully
one
more
because
we
have
three
openings
on
the
team
right
now.
The
next
kr
I
revised
this
one
as
well.
This
was
updating
team
direction.
The
handbook,
but
as
david
has
joined
the
team,
as
we've
been
talking
more
as
a
team.
A
What
we're
really
lacking
is
a
run
book
for
our
team's
technical
documentation,
so
we
started
a
home
for
that
and
the
team
is
doing
great
on
getting
I'll
say
getting
content.
That's
helpful
for
troubleshooting,
diagnosing
and
investigating
problems
around
master,
broken
review,
app
failures,
maybe
just
general
pipeline
flakiness,
all
in
the
run
book,
to
help
make
sure
that
this
knowledge
has
been
built
up
over
years
of
experience
on
the
team
is
getting
written
down
somewhere
and
not
really
polluting
the
handbook
with
it,
but
linking
from
the
handbook
to
the
run,
bug
and
then
sourcing.
A
No
change
on
that.
For
this
week,
we've
I've
we've
helped
source
more
than
50
candidates.
The
recruiting
team
is
always
back
in
on
this
as
well.
So
just
but
one
of
the
things
that
I'm
finding
is
more
proactive
outreach.
Where
I
do
like
where
I
do
pre-application
screenings,
that's
led
to
a
lot
of
the
late
stage,
candidates
as
well,
that
we
have
right
now,
so
I'm
going
to
look
to
continue
that
as
we're
projected
to
continue
hiring
into
next
quarter
great.
A
So
if
we
look
at
the
overall
progress
where
it's
78
versus
87
expected,
assuming
we
hit
100,
I
think
we're
right
on
track.
We
could
use
some
help
on
hiring
and
I
think
tiff,
but
we've
had
some
interruptive
work,
driven,
that's
taken
our
focus
away
from
tiff
and-
and
I
believe
tiff
is
going
to
be
where
it's
where
it's
at
to
end
the
quarter,
hopefully
hiring
we
get
to
at
least
50,
if
not
100
by
the
end
of
the
month.