The document discusses objectives and key results (OKRs), providing a brief history of OKRs and how they can be used to focus teams on goals, add transparency to work, and align ideas between teams and strategy. It also provides guidance on setting objectives and key results, including that objectives should manifest bold ideas that stretch capabilities and align with company strategy, and that key results should be measurable, quantifiable, and able to be evaluated.

1. Objectives and Key Results
Eduards Salnikovs, Intrum Justitia Software Development Centre

2. What’s OKRs?
A good mix of common sense
/Jurgen Appello/
2

3. One slide OKRs history
Peter
Drucker
1950s-1960s
Andy
Grove
1980s-1990s
John
Doerr
1990s-2000s
Rick
Klau
2013
3

4. With OKRs mindset we would like to
Focus on goals
4
Add transparency
to work
Align ideas between
teams and with strategy
Engage teams

5. How to get there?
If you dont know where you are going any road will get you there
/Native american proverb/
5

6. 6
Strategy Objectives

7. 7
Key Results: Team member self elaborated measurements
Learn new
business
knowledge
domain
Write 5
confluence
posts around
subject matter
Present 2
internal
workshops
Automate
manual test
effort in
project
Cover minimum of
30% frontend
code with
automated tests
Grow amount
of regression
test cases by
25%

8. OKR Hygiene
 Each quarter
 2 or more Objectives
 with several Key Results to be set
 Objectives should
 manifest bold idea
 be reasonably uncomfortable
 stretch capabilities
 align with company and other teams
 Key Results should be possible to
 measure and quantify
 evaluate and score
8

9. Key Result typology
9
Type of Key Result When used Example
Baseline No metric possible, i.e. no
data available previously
Count and report number of invoices received each
month
Positive metric Exists target metric, more is
better
40 new user stories completed and delivered by end of
quarter
Negative metric Exists target metric, less is
better
Decrease weekly amout of reactive incidents to 5 by
introducing automated log event analytics
Treshold metric Set target range in between
two or more metrics (dates,
amounts...)
Cover minimum of 20% with target of 60% system
functionality with automated integration tests
Milestone Event or happening Go-live in production with new product with one pilot client
on dd.mm.yyyy

10. Key Result evaluation
10
• Nearly impossible to achieve1
• Difficult but attainable0.7
• We know we can definitely achieve this0.3
• No progress0No progress
Minimum
Target
Overachievement
Score matters less than learning process itself although four distinct achievement
levels might be reflected. Any value in between 0 and 1 possible.

11. 11