Planning stage matters, dramatically, if you’re truly using them to focus and say no to other things
They should enable you to say no, or at least to ask if this gets me closer or farther from my goal
Cadence matters, quarterly mostly, so you can more quickly pivot if the OKR isn’t the ideal or correct one
Andy Grove’s OKR hygiene
Ruthless intellectual honesty, disregard for self-interest, deep allegiance to the team
Less is more: a few extremely well-chosen objectives, what to say yes to and no to
Set goals from the bottom up: teams and individuals should be encouraged to create roughly half of their own OKRs, in collaboration with managers
No dictating: OKRs are a cooperative social contract to establish priorities and define how progress will be measured
Stay flexible: key results (and objectives) can be modified or discarded mid-cycle
Dare to fail
A tool, not a weapon: built to pace a person, not to measure their performance
Be patient, be resolute: expect trial and error
Raw Notes, by chapter:
Intro
OKRs
Objectives
Key results
“a collaborative goalsetting protocol for companies, teams, and individuals.
Objective
What is to be achieved
Significant
concrete
action oriented
(ideally) inspirational
Key results
Benchmark how we get to the objective
Effective KRs are
specific
time bound
aggressive yet realistic
Measurable and verifiable
Binary, you either meet it or you don’t
At the end of the time period
Value prop: “OKRs surface your primary goals, channel efforts and coordination, link diverse operations, lending purpose and unity to the entire org”
“Systematic innovator of scale. Innovator means new stuff. Scale means big, systematic ways of looking at things done in a way that’s reproducible.”
At Google each quarter starts with a leadership debate on their quarterly objectives
At Google Larry would sit down and scrutinize the employee level OKRs to confirm they cohere across the board
“In November and December, each team and product area will develop its own plans for the coming year and distill them into OKRs”
Grade OKRs from the prior year and dissect failures
OKRs aggregate in a central place so teams can browse and see the objectives of every team in the company
Four OKR Superpowers: focus, align, track, and stretch
Focus and commit to priorities
work on what does matter and not what doesn’t
OKRs force hard choices about priorities
Align and connect for teamwork
OKR transparency
Link individual objectives to company game plan
Identify cross-dependencies
Track for accountability
data driven
periodic check ins
continuous reassessment
Stretch for amazing
Andy Grove and Intel
Gordon, wise; Noyce, invented semiconductors, public facing; Grove, all things operations
At Fairchild “expertise was very much valued, that is why people got hired. That’s why they got promoted. Their effectiveness in translating knowledge into results was kind of shrugged off.”
At Intel, “It almost doesn’t matter what you know. It’s what you can do with whatever you know or can acquire and actually accomplish that tends be valued here.” Intel delivers.
Grove: “Now, the two key phrases are objectives and key result. And they match the two purposes. The objective is the direction: “We want to dominate the mid-range microcomputer component business.” That’s an objective. That’s where we’re going to go. Key results for this quarter: “Win ten new designs for the 8085″ is one key result. It’s a milestone. The two are not the same. The key result has to be measurable. But at the end you can look, and without any arguments: Did I do that or did I not do it? Yes? No? Simple. No judgments in it. Now, did we dominate the mid-range microcomputer business? That’s for us to argue in the years to come, but over the next quarter we’ll know whether we’ve won ten new designs or not.”
Andy Grove borrowed it from Peter Drucker’s earlier Management by Outcomes
How do you distinguish between activity and output?
How can we define and measure output by knowledge workers?
And what can be done to increase it?
Aggressive introverts:
Solve problems quickly, objectively, systematically and permanently without attacking the person.
Set politics aside to make faster, sounder, more collective decisions.
Andy’s OKRs
What and how
Quarterly or monthly
Public and transparent
Bottom-up or Sideways (50/50)
Mostly divorced from compensation
Aggressive and Aspirational
OKRs enable to you to say no
Intel project crush
Objectives as measured by these key results
Superpower 1: Focus and Commit to Priorities
What is most important for the next 3, 6, or 12 months
Force a decision to be made (can learn from bad decisions, can’t learn from no decisions)
Values cannot be transmitted via memo
Structured goal setting can’t take root via fiat
Say this is what we’re doing but then also model it
Key points:
Communicate with clarity
Key results need care and feeding
the levers you pull to hit a goal
What, how, and when
Quarterly, maybe monthly
DS is using a three week review window
Pairing key results – measure both the effect and the counter-effect
If one focuses on output, another should focus on quality
Quantity, and quality – make sure the haste towards quantity isn’t propelled by lowering quality
The perfect vs. the good
OKRs can be modified, so go for good and don’t anguish over perfect
Completing all KRs must by definition fulfill the goal
Less is more
Example of focus
Example of commit
Superpower #2: Align and Connect for Teamwork
Public goals more likely to succeed than private
Once objectives are set, day-to-day activities are tied to the vision
Vertical alignment
Preventing cascading of goals:
Don’t aim to cascade all objectives
Becomes “color by numbers” exercise
loss of agility
lack of flexibility
marginalized contributions
one-dimensional linkages
OKRs must be bottom up and top down
Some goals bubble up from the bottom
Some goals come down from on high
20% time a potential example
Avoid micromanagement and managerial meddling
Cross-functional coordination
Must have transparent OKRs across org
People can become aware how they can help out other LOBs, teams, projects
Awareness between teams within a level in the business
Quickly see what teams are succeeding or failing to devote resources properly
Align example
Connect example
Superpower #3: Track for Accountability
Track and then revise or adapt
Use software to manage the process — not excel
Everyone’s goals more visibile
They drive engagement
They promote internal networking
They save time, money, and frustration
Must be adopted universally, no exceptions
Four zones for assessing OKRs:
Continue — don’t change it
Update — what can be done differently, new timeline, back-burner?
Start — launch a new OKR mid-cycle, if it is needed
Stop — drop a goal wit no progress if dropping it is the right thing to do
Scoring
0.7-1.0 = we delivered
0.4 to 0.6 = we made progress
0.0 to 0.3 = we failed to make real progress
Reflections
Did I accomplish all of my objectives?
If not, why not?
If I were to rewrite the goal, what would I change?
What have I learned that might alter my approach?
Track example
Superpower #4: Stretch for Amazing
Set aspirational goals
Can be extraordinary in themselves
Can be ordinary things done extraordinarily well
Can you 10x the goal
OKRs aim for 70% success
Stretch example
Stretch example
Continuous performance management
CFR
Conversations
Feedback
Recognition
“Give OKRs their human voice”
Annual vs Continuous
annual / continuous
tied to compensation / decoupled from compensation
directing / coaching
outcome / process
weakness / strength
prone to bias / fact driven
Conversations
Goal setting and reflection
Ongoing progress updates
two way coaching
career growth
lightweight performance reviews
Feedback
Positive
Negative
Keep it specific
Recognition
Institute peer-to-peer recognition
Establish clear criteria
Share recognition stories
Make recognition frequent and attainable
Tie recognition to company goals and strategies
Performance review example
Performance review example
Culture
Intel example:
People oriented
Openness
Issue resolution
Results
Discipline
Risk taking
Trust and integrity
Google example:
Structure and clarity
are goals, roles, and execution plans on our team clear?
Psychological safety
Can we take risks on this team without feeling insecure or embarassed
Meaning of work
Are we working on something that is personally important for each of us
Dependability
Can we count on each other to do high quality work on time
Impact of work
Do we fundamentally believe the work we are doing matters?