►
From YouTube: The Process: Personal OKRs experiment
Description
Nadia, the Product Designer at GitLab (Verify:Pipeline Authoring), shares her experience setting personal OKRs for the first time. You will learn:
- What are the benefits of setting personal OKRs
- The process for setting OKRs
- How not to set OKRs :D
What are OKRs: https://about.gitlab.com/company/okrs/
Nadia's Planning Epic for FY21-Q4: https://gitlab.com/groups/gitlab-com/-/epics/1241
Personal Growth Mural exercise: https://app.mural.co/t/gitlab2474/m/gitlab2474/1604064961704/fa0d3ff479468e549c4a0886ead8a67bf5a31596
GitLab UX Department OKRs for FY21-Q4: https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/9303
A
I
conducted
lots
of
different
exercises,
like
brainstorming
exercises,
to
figure
out
what
I
want
to
focus
on,
for
example,
this
is
the
mural
board
that
I've
been
working
with
kind
of
tracking
my
progress
towards
the
senior
product
designer
role,
where
I
track
how
I'm
doing,
in
terms
of
all
of
the
different
responsibilities
that
the
senior
product
designer
has
at
gitlab
and
then
looking
at
the
different
gitlab
values
and
how
I'm
living
those
values.
And
what
can
I
do
to
improve
this?
A
This
board
is
accessible.
I
think
for
all
youtube
members
so
feel
free
to
check
it
out.
If
you
want-
and
my
process
for
setting
okrs
was
mostly
based
on
this
kind
of
exploration,
so
thinking
what
do
I
want
to
focus
on?
What
are
my
personal
interests?
What
what
things
I
should
strengthen
and
what
are
some
things
that
I'm
already
doing.
A
So
this
is
my
epic
for
planning
the
current
quarter,
which
is
ending,
I
think
today
or
tomorrow,
or
something
like
that,
and
here
I
added
issues
that
were
directly
tied
to
current
ux
okrs
ux
department
okr.
So
I
wanted
to
make
sure
that
I
contribute
to
those
and
then
I've
set
some
personal
qrs
for
myself
as
well,
so
one
kr
was
to
conduct
two
solution.
A
A
I
did
really
well
with
this
qr,
where
I
wanted
to
share
my
work:
output,
more
I'll
talk
about
it
in
a
bit
more
detail
in
a
minute.
I
wasn't
able
to
make
as
many
contributions
to
the
pajama
design
system
as
I
wanted
to.
Well,
it's
not
surprising.
This
quarter
was
very
short.
I
took
lots
of
time
off.
I
took
almost
one
month
time
off
because
of
christmas,
and
then
I
took
another
vacation
so
yeah
it
was
not
really
attainable.
A
On
top
of
all
of
the
other
work
that
I'm
doing,
and
I
made
zero
contributions
to
the
pajamas
migrational
qr,
just
because
it
was
very
difficult
for
me
to
accomplish
that
on
top
of
everything
else,
my
gdk
is
still
broken,
and
I
I
decided
that.
Okay,
I'm
just
not
going
to
focus
on
it
and
try
to
do
other
things,
but
yeah,
let's
go
to
the
retrospective
now,
because,
as
you
can
see,
my
experiment
wasn't
very
successful
in
the
traditional
sense.
A
So
I
failed
a
lot
of
my
okrs,
but
I
still
think
this
experiment
was
very
interesting
and
rewarding.
So
first
of
all,
I
didn't
put
it
here,
but
I
have
to
say
that
it
was
great
to
quantify
the
work,
output
and
track
it.
So
I
was
able
to
collect
the
issue,
links
and
just
links
to
whatever
contributions
I
was
making
like
sharing
things
on
slack.
A
So
I
did
really
well
with
this
qr
and
I
think
it
was
a
really
good
qr,
because
it
got
me
into
the
habit
of
thinking.
Okay.
How
can
I
share
the
support?
I'm
doing
so?
It
has
more
impact.
How
can
I
leverage
this
work
that
I've
done
already
to
get
more
value
out
of
it
and
what
is
the
best
way
to
communicate
this
value,
so
other
people
can
easily
access
it
and
find
it
and
quickly
consume
the
content
and
get
that
value
for
themselves.
A
For
example,
so
yeah
I
give
it
a
shot,
but
this
was
really
the
only
truly
successful
of
my
qrs.
So
I
don't
know
if
you
should
trust
me,
but
yeah.
I
did
spend
quite
a
bit
of
time
contributing
to
the
pajamas
figma
ui
kit,
so
I'm
currently
going
through
the
pajamas
maintainer
training,
and
I
I
should
be
contributing
more
honestly.
I
feel
like
I'm
moving
very
slowly,
but
I
was
able
to
make
one
contribution
that
got
merged
and
another
one
is
almost
done.
A
A
Second,
some
of
the
qrs
have
set
up
were
dependent
on
many
other
factors,
so
they
kind
of
weren't
in
my
control,
so
one
of
the
qrs
was
to
conduct
two
solution:
validation
cycles
at
verify,
pipeline
authoring
and
given
the
big
features
that
we've
been
working
on
and
lots
of
back
and
forth
and
lots
of
time
off.
Basically,
we
were
only
able
to
go
through
several
design
iterations.
It
was
needed
and
we
haven't
really
gotten
to
solution
validation.
A
So
I
gathered
feedback
internally
and
I
did
my
best
to
get
as
much
feedback
as
I
could
from
from
within
github,
but
I
wasn't
able
to
run
any
proper
solution,
validation
efforts,
which
is
fine,
but
you
know
in
the
future.
Maybe
I
would
frame
this
differently
so
if
the
goal
is
to
find
usability
issues
with
pipeline
authoring
features,
I
could
also
do
that
in
easier
ways.
You
know
I
don't
have
to
run
to
solution
validation
cycles.
A
I
can
just
do
like
a
ux
scorecard,
perhaps-
and
I'm
sure
out
of
that
I
would
create
some
some
good
issues
for
us
to
work
on
but
yeah.
This
was
one
of
the
learning
points
and
then
I
had
almost
one
month
of
time
off
this
quarter
and
looking
at
my
okrs,
I
really
did
not
account
it
for
it
at
all,
and
I
tried,
but
I
always
tend
to
set
oral
english
goals
and
it's
good
that
ocr
is
really
pointing
it
out.
A
So
I
can
see
now
that
I
really
need
to
scale
down.
I
have
fewer
goals
for
next
quarter,
so
yeah.
If
you
want
to
give
okay
a
shot,
let
me
know
I
can.
I
can
share
my
okrs
issue
with
you.
If
you
want
to
have
a
look,
and
maybe
if
you
have
been
using
okrs
more
successfully
than
I
have
so
far,
please
share
your
feedback
and
advice
as
well
and
yeah.
Hopefully
it
can
help
you
help.
You
quantify
your
work.
A
It
can
push
you
a
little
bit
when
it
comes
to
achieving
your
personal
goals
and
also
it
helps
you
track
your
work.
So
then
you're
able
to
share
it
with
the
ux
team
and
your
manager,
which
is
always
great
when
it
comes
to
working
towards
a
promotion
or
anything
like
that
yeah.
I
hope
you
found
it
interesting,
my
kind
of
failure
story,
and
maybe
it
will
help
you
in
setting
your
own
qrs
thanks.