►
From YouTube: OKR for GitLab Office Hours pt. 1 2023-01-26
Description
Project: https://gitlab.com/gitlab-com/gitlab-OKRs/-/blob/main/README.md
Handbook: https://about.gitlab.com/company/okrs/#how-to-use-gitlab-for-okrs
A
A
B
B
I
think
looking
at
whatever
Ali
was
doing
and
if
I
had
to
guess
they
probably
allowed
both
so
or
if
I
initiate
a
roll
up,
then.
Obviously
the
person
who
authored
the
higher
okr
would
have
to
accept
the
roll-up
because
they
may
or
may
not
want
to
see
that
in
their
work,
progress
I.
Think,
though,
an
MVC
approach
is
just
the
ability
to
see
and
Associate
and
not
consider
okrs
always
to
be,
in
fact,
if
they're
done
too
top
down,
they
end
up.
B
Just
being
you
know
a
new
version
of
mbos,
so
any
ability
to
do
this
collaborative
just
you
know,
connecting
an
effort
that
you
might
already
have
in
flight
or
that
you
could
conceive
of
to
do
something.
Really
quick
and
helpful
to
an
okr
would
be
would
be
handy,
so
I
would
leave
it
up
to
mvcing
to
understand
exactly
how
that
relationship
should
work.
I
guess.
A
But
the
higher
level
must
be
an
objective
and
I
think
the
way
that
we've
entered
okrs,
especially
the
CEO
of
okrs,
is
that
there's
an
objective
and
then
several
Pairs
and
you
cannot
add
children
to
a
care.
So
if
there's
a
case
where
you
want
to
contribute,
contribute
progress,
excuse
me,
you
have
to
add
it
to
a
parent
objective
for
just
simple
relationships:
release
relating
to
another
okr
or
relating
to
work
items
like
epics
and
issues.
That's
definitely
on
the
roadmap.
Just
wasn't
part
of
the
MDC.
C
What
behaviors
do
we
need
to
be
paying
attention
to
on
our
end,
in
order
to
make
sure
that
all
of
the
okrs
are
being
measured
equally,
do
we
need
to
be
I
guess?
The
question
is:
what
are
the
formulas
that
are
feeding
that
progress
measurement
so
that
we
are
using
the
correct
tools
and
habits
in
order
to
feed
that
that
calculation,
so
do
we
need
to
be
using
more
check
boxes
or
tasks
or
what
yeah.
A
Good
question
so
I'm
dropping
a
link
to
how
progress
Works
just
so
you
could
see
that
in
live,
so
progress
is
a
very
simple
formula.
At
the
moment
progress
is
a
even
average
of
the
children
cares
so
I'm
going
to
give
an
example
and
I'm
going
to
drop
it
in
the
agenda,
because
this
is
going
to
be
weird
actually
I.
Think
I
have
an
example.
A
So
I
have
an
example
here,
where
I
have
a
parent
objective,
with
a
child
object
with
two
children
objectives
for
two
different
departments,
engineering
and
product
and
I-
should
probably
share
my
screen
shouldn't
I,
because
this
is
gonna
be
weird
for
the
people
on
the
recording.
So
let
me
share
here
we
go,
somebody
is
not
muted.
If
you
don't
mind,
yeah
like
this.
Okay,
so
in
this
example,
I
have
a
parent
which
is
neutral.
A
A
All
you
have
to
do
is
enter
the
progress
at
the
KR
level
and
all
of
the
objective
parents
are
going
to
inherent
using
the
calculation.
So
in
this
case
this
parent
is
going
to
get
the
average
of
50
and
50,
which
is
50.
In
this
case.
It's
going
to
get
the
average
of
10
and
10,
which
is
10,
and
then
the
ultimate
parent
receives
the
average
of
the
two
children
direct
children,
which
is
10
and
50
percent.
D
A
A
A
You
do
not
have
to
enter
this.
This
is
going
to
be
Auto
calculated.
Okay.
This
is
a
division
objective
below
it,
which
is
engineering
some
flavor
of
that
this
is
another
division
objective.
Let's
say
product
some
flavor
of
that
parent.
Each
of
those
divisions
have
their
own
care
that
add
to
the
progress
of
this
particular
flavor
when
they
enter
this.
This
is
where
they
want
to
enter
progress
right.
All
of
these,
these
are
going
to
be
the
only
place
you
enter
progress
everywhere
else
is
going
to
be
Auto
calculated.
A
A
A
B
A
Yeah,
yes,
absolutely.
This
is
something
that
will
be
coming
so
being
able
to
attach
objectives
or
okrs
in
general
to
the
work
output
is
something
that
is
on
the
roadmap,
whether
that
work
output
will
drive.
The
progress
is
still
TBD
because
it
doesn't
always
have
a
one-to-one
relationship.
You
know
you
do
the
thing
that
doesn't
necessarily
move
the
needle.
You
have
to
go
measure
and
see
if
the
needle's
been
moved.
Did
it
did
user
happiness
increase
because
I
ship
this
project?
B
B
A
Yeah
from
a
feature
perspective
that
doesn't
exist
yet
from
a
I'm
just
dropping
a
link
from
a
process
perspective
we're
following
this
concept
of
explicit
alignment
and
I've
dropped
a
link
to
the
handbook
that
talks
about
the
process,
but
you're
basically
replicating
the
higher
level
KR
as
your
parent
objective,
so
you're
creating
kind
of
a
duplicate,
and
then
you
can
go
from
there.
The
problem
is:
the
progress
is
not
going
to
roll
up
to
that
parent
KR.
E
A
Yep,
that's
that's
correct
Marcin!
Thank
you
for
for
that.
It's
only
enabled
in
the
gitlab
okrs
project,
specifically
because
it's
an
internal
dog
fooding
event
at
the
moment,
and
it's
limited,
it
only
works
within
a
single
project
that
you
can't
span
projects
and
collaborate
together.
Just
yet
we
on
the
roadmap.
We
are
looking
to
put
this
at
the
group
level
so
that
it
does
become
more
accessible
across
organizations,
and
that
will
be
something
that
we
ship
before
becomes
generally
available.
F
You
know
obviously
we're
doing
this
to
get
you
some
data
to
continue
to
iterate
on
the
feature,
so
I
just
want
to
make
sure
I
understand
as
we
use
the
tool
and
as
we
use
the
feature
in
our
dog
fooding
efforts.
How
do
we
ensure
that
we
get
you
the
data
that
that
you
need
and
what
you
know?
Can
we
be
more
deliberate
about
making
sure
you
get
it?
You
know
I
I,
know
I
understand,
for
example,
there's
a
feedback
issue
that
we
can
leave
feedback
in.
F
That's
no
problem,
but
I
don't
know
if
there
are
any
other
specific
instructions
for
using
the
the
tool.
For
example,
like
always
use
the
okr
label.
If
you
don't
use
it,
we
won't
be
able
to
see
blah
blah.
You
know
like
guidance
like
that,
just
to
make
sure
that
our
dog
fooding
is
as
effective
as
it
can
be.
For
you
all.
A
That's
I
love
this
question.
Thank
you.
So,
from
a
best
practices
perspective,
how
to
make
the
most
of
this
MBC
I
would
say.
Labels
are
super
important
right
now
we
don't
have
a
lot
of
visibility
in
terms
of
like
we
don't
have
a
dashboard
to
see.
What's
going
on
your
managers
can't
see
you
know
progress
in
a
in
an
easy
to
find
way.
That's
fed
up
for
them,
so
they
have
to
go
to
the
filtered
list,
to
the
issues
list
and
filter
it,
and
so
labels
are
going
to
be
the
thing.
A
Make
sure
that
you
have
the
appropriate
assignees
I
will
say
I'm,
seeing
a
lot
of
assignees
a
lot
of
okrs
with
multiple
assignees
and
that's
against
handbook
guidance,
so
maybe
think
about
why
you're
doing
that
the
handbook
says
if
you
have
multiple
signees,
maybe
you
need
to
be
broken
down,
but
that's
a
process
thing
and
the
other
thing
I'm
I'm
seeing
is
missing.
Milestones
on
objectives
so
make
sure
you're,
adding
your
Milestones.
The
Milestone
at
the
objective
level
is
simply
the
time
box.
A
For
that
okr,
and
so
for
this
round,
it's
fy24-q1,
so
it's
q1
so
make
sure
you're
doing
that
I
think
that's
going
to
set
you
up
for
Success
from
a
reporting
perspective,
maybe
also
I,
might
add,
because
we
don't
have
that
related
functionality.
Yet
ad
related
issues
to
your
description,
so
that
folks,
who
are
not
as
intimate
with
your
Opera
as
you
are
and
can
find
the
related
work
easily.
A
So
that's
from
a
best
practices
from
a
from
a
feedback
and
how
you
can
help
kind
of
the
the
general
availability
I
linked
the
feedback
issue,
but
also
we
really
need
to
know,
there's
a
lot
of
features
right
like
it's.
It's
a
big
green
space
at
the
moment,
so
helping
us
refine,
what's
going
to
be
the
most
bring
the
most
value
helping
us
understand.
A
F
A
Well,
I'll
take
this
moment,
while
we're
just
checking
to
see
if
there's
anything
else
to
thank
everybody.
I've
been
seeing
a
lot
of
activity,
I
think
there's
over
300
okrs
entered
just
this
as
of
this
morning
and
you've
all
been
really
great
at
jumping
in
and
rolling
with
what
we've
released
so
I
I
appreciate
you
and
I
do
appreciate
the
feedback.
No
feedback
is
bad,
so
do
add
it,
even
if
you
think
that
maybe
it
just
applies
to
you,
it
probably
doesn't
so.
Please
add
it.
A
I
want
to
thank
the
team
that
worked
on
this
effort.
This
was
this
effort
was
across
three
different
teams:
two
groups
in
the
plan
stage
and
our
we
have
a
seg,
a
single
engineer,
group
avalash,
working
on
this
as
well,
who
will
be
driving
this
effort
forward,
but
to
get
this
out
in
literally
like
a
milestone
and
a
half
is
seriously
like
moving
a
mountain
and
they
did
an
amazing
job.
A
So
I've
been
doing
a
lot
of
the
communicating,
but
there
is
a
a
ton
of
people
who
actually
did
the
work,
which
is,
is
a
lot
harder
than
doing
communicating
that
I
want
to.
Thank
for
all
their
efforts,
all
right,
any
questions
moving
forward.
Please
there
is
an
office
hours
later
today
as
well,
but
there
is
a
a
slack
Channel
I'll
drop
the
link
to
the
slap
Channel
if
it
isn't
already
here.