Difference between revisions of "OKR"
(Zeroth version.) |
(→Sources: += Gitlab » Stella Treas » Objectives and Key Results (OKRs)) |
||
(25 intermediate revisions by the same user not shown) | |||
Line 5: | Line 5: | ||
|wish=Keep everyone moving forward as an aligned and autonomous team. | |wish=Keep everyone moving forward as an aligned and autonomous team. | ||
|so=Co-create and publish objectives and key results on all levels in your organization. | |so=Co-create and publish objectives and key results on all levels in your organization. | ||
|image=OKR Best Practices.png{{!}}600px | |||
|prologue=To achieve great things, two things are needed: a plan and not quite enough time. —Leonard Bernstein | |||
|wish full=Keep everyone moving forward as a team in a world where culture, productivity and alignment are all in flux. | |wish full=Keep everyone moving forward as a team in a world where culture, productivity and alignment are all in flux. | ||
|background===Forces== | |background={{quote|The greater danger for most of us lies not in setting our aim too high and falling short, but in setting our aims too low and achieving our mark.|Michelangelo}} | ||
Goals aren’t promises, they’re hypotheses | |||
Not reaching a goal can be just as valuable as reaching it, just as disproving a hypothesis is as valuable as proving it | |||
The purpose of a goal is to '''maximize your learning''', not commit to a predetermined outcome. | |||
# Don’t plan ahead of what you know now, or you’re just spinning fantasies. | |||
# What you know now will likely be wrong in a few weeks. | |||
I’m not saying "don’t plan." I’m saying that the plan is dynamic, constantly changing as you learn, and you’re always learning. | |||
==Forces== | |||
*{{p|metrics drive behavior}} | *{{p|metrics drive behavior}} | ||
*People hate corporate acronyms that mandate work more than just corporate acronyms. | *People hate corporate acronyms that mandate work more than just corporate acronyms. | ||
*Multiple teams often | *Multiple teams often depend on one another to succeed. | ||
*No one person knows everything going on inside the organization. | *No one person knows everything going on inside the organization. | ||
*Personal objectives that are directly and clearly connected to the broader goals of the company are more inspiring and imaginative. | *Personal objectives that are directly and clearly connected to the broader goals of the company are more inspiring and imaginative. | ||
*Public information that everyone can see help make you feel you are toiling in a thriving environment with your manager’s approval. | *Public information that everyone can see help make you feel you are toiling in a thriving environment with your manager’s approval. | ||
*Public goals and clear results | *Public goals and clear results: | ||
** | **encourage people to ask for resources; and | ||
**easily spot where | **easily spot where you can support your colleagues; | ||
** | **force different types of thinking around how people ask for help from others and helps amplifying this type of dialog. | ||
*Airing things out releases anxiety and let’s people get creative—that’s when interesting things happen. | *Airing things out releases anxiety and let’s people get creative—that’s when interesting things happen. | ||
*Stretched goals | *Stretched goals: | ||
**help you to be ambitious enough the push you beyond your limits; and | **help you to be ambitious enough the push you beyond your limits; and | ||
**focuses conversations about what is truly needed to beat expectations; | **focuses conversations about what is truly needed to beat expectations; | ||
Line 31: | Line 46: | ||
*Self-inflicted objectives and goals are much more powerful than top-down goals dictated from higher organizational levels. | *Self-inflicted objectives and goals are much more powerful than top-down goals dictated from higher organizational levels. | ||
{{ | {{okrs}}: | ||
*serve as a layer of communication that holds the company together; | *serve as a layer of communication that holds the company together; | ||
*are designed for accountability; | *are designed for accountability; | ||
Line 43: | Line 58: | ||
*track results on a quantitative basis—key results are not general or subjective actions you plan to take, and should always include numbers to make it clear how much has been achieved. For example, if Mary’s objective is to improve her sales prospecting skills, one key result might be to spend two hours a week shadowing Jennifer, the team member who demonstrates the most prospecting success; | *track results on a quantitative basis—key results are not general or subjective actions you plan to take, and should always include numbers to make it clear how much has been achieved. For example, if Mary’s objective is to improve her sales prospecting skills, one key result might be to spend two hours a week shadowing Jennifer, the team member who demonstrates the most prospecting success; | ||
*are something for people look at, every quarter, every week, every day—consistently setting goals turns goal-setting into a habit and changes how people think about their work and approach their everyday to-dos; it puts in place natural milestones that make you think about what you need to do next and aim high; | *are something for people look at, every quarter, every week, every day—consistently setting goals turns goal-setting into a habit and changes how people think about their work and approach their everyday to-dos; it puts in place natural milestones that make you think about what you need to do next and aim high; | ||
*are stretched goals in order to be effective—achieving 70% of your goals is just about perfect for {{ | *are stretched goals in order to be effective—achieving 70% of your goals is just about perfect for {{okrs}}—if you achieve 100% of your goals, you’re not trying hard enough (cf. Sun Tzu: bow tension); | ||
*are a tool for motivating and aligning people to work together by increasing transparency, accountability and empowerment; | *are a tool for motivating and aligning people to work together by increasing transparency, accountability and empowerment; | ||
*make it easier than ever to keep people focused and collect feedback, inside and outside management meetings; | *make it easier than ever to keep people focused and collect feedback, inside and outside management meetings; | ||
*facilitate continual coaching of yourself and others and develops your whole ecosystem; | *facilitate continual coaching of yourself and others and develops your whole ecosystem; | ||
|therefore full=Encourage people to spend time defining their own {{ | |therefore full=Encourage people to spend time defining their own {{okrs}} and then to meet specifically with their managers to incorporate their feedback. Spend your time defining {{okrs}}, not measuring them. Look at {{okrs}} as a way to communicate so there’s clarity about the {{p|unity of purpose}}. Tweak and tune your {{okrs}} to be more about collaboration and less about action items. Publish them for everyone to see (next to your {{p|flow board}}. Figure out how to put {{okrs}} work best for you. ‘Retroprospect’ your {{okrs}} with a {{p|season beat}} and make it a part of your {{p|operations review}}. Hold people publicly accountable for failing to regularly update their {{okrs}}. Have 60% of your {{okrs}} defined by employees, not leadership. | ||
|new=Consider creating an {{p|impact map}} to discover and express the right {{okrs}}. | |||
|new=Consider creating an {{p|impact map}} to discover and express the right {{ | |||
Grading should be a simple exercise at every {{p|season beat}}, five minutes tops. Score an objective by averaging the individual key result scores underneath it. This is also why it’s so important to make those key results quantitatively measurable. | Grading should be a simple exercise at every {{p|season beat}}, five minutes tops. Score an objective by averaging the individual key result scores underneath it. This is also why it’s so important to make those key results quantitatively measurable. | ||
'''Warning''' | '''Warning''' | ||
*Do not mix {{ | *Do not mix {{okrs}} and performance reviews; do not use it as a weapon against your employees in performance reviews. | ||
}} | }} | ||
==Sharpening Questions== | |||
==Typical Progress Meeting== | ==Typical Progress Meeting== | ||
*Ask people to share their quick wins—one or two notable things they or their team has achieved since last time. | *Ask people to share their quick wins—one or two notable things they or their team has achieved since last time. | ||
*Ask people what progress has been made agains their {{ | *Ask people what progress has been made agains their {{okrs}}: | ||
**What are the areas that are still keeping you up at night? | **What are the areas that are still keeping you up at night? | ||
**Where do you need help?' | **Where do you need help?' | ||
**Everyone shares one or two things that are causing them the biggest concerns about hitting their {{ | **Everyone shares one or two things that are causing them the biggest concerns about hitting their {{okrs}} | ||
*Have the major concerns guides the meeting’s conversation in the right direction—because they’re always focused on removing roadblocks, they always feel like time well spent. | *Have the major concerns guides the meeting’s conversation in the right direction—because they’re always focused on removing roadblocks, they always feel like time well spent. | ||
Smashing Magazine: | |||
:Schedule deadlines as specific tasks, not the ends of phases. Rather than “Content will be completed by 4 April 2010,” state “Review the content over lunch on 4 April 2010.” This ties the deadline to an event at which results must be shown. Mini-deadlines tied to specific events are more powerful than general statements. | |||
==Sources== | |||
{{WebSourceListItem | |||
|url= https://about.gitlab.com/company/okrs/ | |||
|site=Gitlab | |||
|person=Stella Treas | |||
|title= Objectives and Key Results (OKRs) | |||
}} | |||
{{WebSourceListItem | |||
|url=https://www.perdoo.com/resources/get-aligned-strategy-first-okr-second/ | |||
|site=Perdoo | |||
|person=Henrik-Jan van der Pol | |||
|title=Looking to get aligned? Put strategy first, OKR second | |||
}} | |||
{{WebSourceListItem | |||
|url=https://quietstars.com/lax2020/ | |||
|site=Quiet Stars | |||
|person=Adrian Howard | |||
|title=OKRs That Don't Suck | |||
}} | |||
{{WebSourceListItem | |||
|url=https://link.medium.com/uw3MScjdA6 | |||
|site=Medium | |||
|person=Ian Batterbee | |||
|title=Designing for motivation with the goal-gradient effect | |||
}} | |||
{{WebSourceListItem | |||
|url=https://felipecastro.com/en/blog/book-review-measure-what-matters/ | |||
|site=Felipe Castro | |||
|title=Measure What Really Matters | |||
|about=Good, bad and ugly of the book with the same title | |||
}} | |||
{{WebSourceListItem | |||
|url=https://medium.com/@mcleanonline/4-key-lessons-ive-learned-about-okrs-3f4b902ae9f8 | |||
|site=Medium | |||
|person=Richard McLean | |||
|title=4 key lessons I’ve learned about OKRs | |||
}} | |||
{{WebSourceListItem | |||
|url=https://hackernoon.com/beyond-outcomes-over-outputs-6b2677044214 | |||
|site=Medium | |||
|person=John Cutler | |||
|title=Beyond “Outcomes Over Outputs” | |||
}} | |||
{{WebSourceListItem | |||
|url=https://hbr.org/2018/05/how-vc-john-doerr-sets-and-achieves-goals | |||
|site=HBR | |||
|person=Daniel McGinn | |||
|title=How VC John Doerr Sets (and Achieves) Goals | |||
}} | |||
{{WebSourceListItem | |||
|url=https://rework.withgoogle.com/guides/set-goals-with-okrs/steps/introduction/ | |||
|site=re:Work | |||
|title=Guide: Set goals with OKRs | |||
}} | |||
{{WebSourceListItem | |||
|url=http://felipecastro.com/en/okr-tools/ | |||
|site=Filipe Castro | |||
|title=OKR Tools | |||
}} | |||
{{WebSourceListItem | |||
|url=http://eleganthack.com/the-art-of-the-okr/ | |||
|site=Eleganthack | |||
|title=The Art of the OKR | |||
}} | |||
{{WebSourceListItem | |||
|url=https://medium.com/@johnpcutler/untangling-okrs-with-a-big-visual-board-6153afa12213 | |||
|site=Medium | |||
|person=John Cutler | |||
|title=Untangling OKRs with a Big, Visual Board | |||
}} | |||
{{WebSourceListItem | |||
|url=http://okrexamples.co/company-okr-examples | |||
|site=OKR Examples | |||
|title=Company OKR Examples | |||
}} | |||
{{WebSourceListItem | |||
|url=https://medium.com/@johnpcutler/18-things-your-okrs-shouldnt-do-23c8b57a455f | |||
|site=Medium | |||
|person=John Cutler | |||
|title=18 Things Your OKRs Shouldn’t Do… | |||
}} | |||
{{WebSourceListItem | |||
|url=https://dannorth.net/2017/05/01/applying-okrs/ | |||
|site=Dan North & Associates | |||
|person=Dan North | |||
|title=Applying OKRs | |||
}} | |||
{{WebSourceListItem | {{WebSourceListItem | ||
|url=https://medium.com/startup-tools/okrs-5afdc298bc28 | |url=https://medium.com/startup-tools/okrs-5afdc298bc28 | ||
Line 69: | Line 192: | ||
|title=The Fundamentals » OKRs | |title=The Fundamentals » OKRs | ||
}} | }} | ||
{{WebSourceListItem | {{WebSourceListItem | ||
|url=https://docs.google.com/document/d/1OHpQOvZz76_10ebJP2AKvvXUF3H9yd6FC89F5jS4mks | |url=https://docs.google.com/document/d/1OHpQOvZz76_10ebJP2AKvvXUF3H9yd6FC89F5jS4mks | ||
Line 75: | Line 199: | ||
|title=Startup OKRs Template | |title=Startup OKRs Template | ||
}} | }} | ||
{{WebSourceListItem | {{WebSourceListItem | ||
|url=http://firstround.com/review/How-to-Make-OKRs-Actually-Work-at-Your-Startup/ | |url=http://firstround.com/review/How-to-Make-OKRs-Actually-Work-at-Your-Startup/ | ||
Line 80: | Line 205: | ||
|title=How to Make OKRs Actually Work at Your Startup | |title=How to Make OKRs Actually Work at Your Startup | ||
}} | }} | ||
{{WebSourceListItem | {{WebSourceListItem | ||
|url=https://blog.weekdone.com/introduction-okr-objectives-key-results/ | |url=https://blog.weekdone.com/introduction-okr-objectives-key-results/ | ||
Line 85: | Line 211: | ||
|person=Jüri Kaljundi | |person=Jüri Kaljundi | ||
|title=Introduction to OKR – Objectives and Key Results | |title=Introduction to OKR – Objectives and Key Results | ||
}} | |||
{{WebSourceListItem | |||
|url=https://www.perdoo.com/blog/okr-vs-kpi/ | |||
|site=Perdoo | |||
|person=Henrik-Jan van der Pol | |||
|title=OKR vs. KPI: How they compare and how they work together | |||
}} | }} |
Latest revision as of 15:24, 23 July 2023
- To achieve great things, two things are needed: a plan and not quite enough time. —Leonard Bernstein
…culture, productivity and alignment all in flux.
✣ ✣ ✣
Keep everyone moving forward as a team in a world where culture, productivity and alignment are all in flux.
- The greater danger for most of us lies not in setting our aim too high and falling short, but in setting our aims too low and achieving our mark.
Goals aren’t promises, they’re hypotheses
Not reaching a goal can be just as valuable as reaching it, just as disproving a hypothesis is as valuable as proving it
The purpose of a goal is to maximize your learning, not commit to a predetermined outcome.
- Don’t plan ahead of what you know now, or you’re just spinning fantasies.
- What you know now will likely be wrong in a few weeks.
I’m not saying "don’t plan." I’m saying that the plan is dynamic, constantly changing as you learn, and you’re always learning.
Forces
- metrics drive behavior
- People hate corporate acronyms that mandate work more than just corporate acronyms.
- Multiple teams often depend on one another to succeed.
- No one person knows everything going on inside the organization.
- Personal objectives that are directly and clearly connected to the broader goals of the company are more inspiring and imaginative.
- Public information that everyone can see help make you feel you are toiling in a thriving environment with your manager’s approval.
- Public goals and clear results:
- encourage people to ask for resources; and
- easily spot where you can support your colleagues;
- force different types of thinking around how people ask for help from others and helps amplifying this type of dialog.
- Airing things out releases anxiety and let’s people get creative—that’s when interesting things happen.
- Stretched goals:
- help you to be ambitious enough the push you beyond your limits; and
- focuses conversations about what is truly needed to beat expectations;
- encourages to question everything; and
- forces questions that matter like:
- “I’d have to completely solve this hard problem”; or
- “I need to completely rethink how I’m addressing X or Y.”
- Having clear objectives, especially those tied to developing your skills, are a key part of career development.
- People love hitting their marks.
- Key results that are always tied to money block seeing other, diverse objectives in the mix—it will make people play safe rather than being ambitious and entrepreneurial.
- Regular updates and reviews of objectives and key results spur increased dialogue between employees, co-workers, managers, and leadership and allows recognition to be spread out over time, which tends to be more rewarding.
- Self-inflicted objectives and goals are much more powerful than top-down goals dictated from higher organizational levels.
OKRs:
- serve as a layer of communication that holds the company together;
- are designed for accountability;
- are enforced with scores;
- elevates its game;
- can become a part of the culture;
- use the following structure:
- high level objective;
- a more detailed description of why that objective is important—a summary of how the objective aligns with the broader goals of both the person’s team and the company; and
- three to five key results that will help them achieve that goal.
- track results on a quantitative basis—key results are not general or subjective actions you plan to take, and should always include numbers to make it clear how much has been achieved. For example, if Mary’s objective is to improve her sales prospecting skills, one key result might be to spend two hours a week shadowing Jennifer, the team member who demonstrates the most prospecting success;
- are something for people look at, every quarter, every week, every day—consistently setting goals turns goal-setting into a habit and changes how people think about their work and approach their everyday to-dos; it puts in place natural milestones that make you think about what you need to do next and aim high;
- are stretched goals in order to be effective—achieving 70% of your goals is just about perfect for OKRs—if you achieve 100% of your goals, you’re not trying hard enough (cf. Sun Tzu: bow tension);
- are a tool for motivating and aligning people to work together by increasing transparency, accountability and empowerment;
- make it easier than ever to keep people focused and collect feedback, inside and outside management meetings;
- facilitate continual coaching of yourself and others and develops your whole ecosystem;
Therefore:
Encourage people to spend time defining their own OKRs and then to meet specifically with their managers to incorporate their feedback. Spend your time defining OKRs, not measuring them. Look at OKRs as a way to communicate so there’s clarity about the unity of purpose. Tweak and tune your OKRs to be more about collaboration and less about action items. Publish them for everyone to see (next to your flow board. Figure out how to put OKRs work best for you. ‘Retroprospect’ your OKRs with a season beat and make it a part of your operations review. Hold people publicly accountable for failing to regularly update their OKRs. Have 60% of your OKRs defined by employees, not leadership.
✣ ✣ ✣
Consider creating an impact map to discover and express the right OKRs.
Grading should be a simple exercise at every season beat, five minutes tops. Score an objective by averaging the individual key result scores underneath it. This is also why it’s so important to make those key results quantitatively measurable.
Warning
- Do not mix OKRs and performance reviews; do not use it as a weapon against your employees in performance reviews.
✣ ✣ ✣
Sharpening Questions
Typical Progress Meeting
- Ask people to share their quick wins—one or two notable things they or their team has achieved since last time.
- Ask people what progress has been made agains their OKRs:
- What are the areas that are still keeping you up at night?
- Where do you need help?'
- Everyone shares one or two things that are causing them the biggest concerns about hitting their OKRs
- Have the major concerns guides the meeting’s conversation in the right direction—because they’re always focused on removing roadblocks, they always feel like time well spent.
Smashing Magazine:
- Schedule deadlines as specific tasks, not the ends of phases. Rather than “Content will be completed by 4 April 2010,” state “Review the content over lunch on 4 April 2010.” This ties the deadline to an event at which results must be shown. Mini-deadlines tied to specific events are more powerful than general statements.
Sources
- Felipe Castro » Measure What Really Matters, Good, bad and ugly of the book with the same title.