You’re Probably Not Reviewing Your OKRs Enough
30 November, 2018
Most teams only formally review their OKRs once a quarter (I kid you not, this is what most people do). I've found that checking in on the progress of your critical goals every week is an important positive behavior and at the core of how to use goals to set the cadence of your team.
I believe (surprise, surprise) in the value of using a dedicated tool like Koan to run your goals review. However, you can make-do with a Google spreadsheet or the like.
- Each week, collect a "confidence score" for each goal or key result (KR). The score represents the person's confidence that the goal / KR will be achieved by its deadline. Using a red ("at risk"), yellow ("has issues"), green ("on track") scale is simple and effective. The person that's accountable for delivering the key result should be doing the rating, as well as any other team members that are contributing work.
- Along with the confidence score, collect a qualitative assessment as to why the person provided the rating they did. A red, yellow or green rating is far from scientific, and different members of your team will be naturally more optimistic or pessimistic. The trick is that the rating process forces a judgement that, especially when written down, provides critical decision making data.
- Make it ok to be "yellow" or "red". Getting bad news early is a great reason to have the weekly review cadence, but it's easy for team members to fall into the trap of hiding problems in the hope they can fix them privately. Collecting a confidence score from a broader set of the team is one great way to keep everyone honest.
- Use the review process as an opportunity to review and update the quantitative metrics for your key results. Even if you have an easy way to track and update your goal metrics automatically, it's still important to regularly assess and discuss them.
- Collect the data asynchronously and then go over it synchronously. Writing down qualitative feedback ahead of time yields more thoughtful answers and also offers the opportunity to more easily discover alignment issues. Does one team member believe the goal will deliver successfully and another believe there are major problems? Discuss! By collecting data ahead of time you'll be able to easily set the agenda for your meeting. One suggested format: review problem goals that need extra attention, followed by a rotating deeper dive on 1–2 of your KRs.
By doing this behavior every week, you'll find yourself automatically asking some incredibly important questions... Are we working on the most important things? Where are we having problems and who needs help? How do we improve next week? The weekly reviews will also become the living history of your goals and will help you understand over time the patterns around success and failure. If you're not already running a formal weekly goals review, I think you'll be surprised at how effectively it can set the tempo for your team! Source: https://blog.koan.co/the-heartbeat-of-great-teams-39c81717811a
Scale your coaching effort for your engineering and product teams
Develop yourself to become a stronger engineering / product leader
Vineet Puranik, Senior Engineering Manager at DocuSign, discusses the impact of roadmaps, organization, and proper management for your teams to procure growth.
Senior Engineering Manager at DocuSign
Otavio Santana, Distinguished Software Engineer at Zup Innovation, shares his best practices for upskilling without stretching yourself too thin.
Java champion, software engineer, architect, and open-source Contributor at Independent Technical Advisor
Pavel Safarik, Head of Product at ROI Hunter, discusses the frequently overlooked role of product marketing in getting high user adoption rates for your product.
Head of Product at ROI Hunter
Muhammad Hamada, Engineering Manager at HelloFresh, addresses the uncertainties brought on by the pandemic, how these have affected our work environments, and how we can adapt.
Engineering Manager at HelloFresh
Roland Fiala, Senior Vice President of Engineering at Productsup, raises an interesting issue about autonomy in teams: does it hinder collaboration opportunities that lead to better problem-solving? He shares his system for promoting teamwork in engineering departments.
Senior Vice President of Engineering at Productsup