Less is More: How to Introduce OKR’s
18 January, 2019
Vice President Of Engineering at Zume Inc
An OKR goal we did in the first quarter was aimed at improving customer satisfaction. It was a wordy sentence that really became a fluffy cloud that was neither at the objective level nor the key responses level. We were not able to get down to the ground and establish a clearly articulated action that people could wrap their heads around. In other words, its lack of strategy led to failure.
- We changed the verbiage of the goal to something more direct, simple, and understandable.
- Limited the number of objectives and key responses to a handful, keeping them short and concise.
- Rallied around the OKR's so that the teams could really come together and focus on the same few goals.
- The more simple your OKR's are, the easier they are to achieve.
- OKR's need to be strategic. You have to show what you want to capture and how you are going to do it with key responses.
- Once you start focusing on OKR's, it is very important that the company speaks the same language. This is something that has to be adopted.
- Sometimes you are forced to pick arbitrary numbers and that's okay. The most important part is creating the vision, getting everyone on board, and offering a clear understanding that supports it.
- You can't learn the correct implementation of OKR's from literature. It is more about absorbing information from the experiences of others.
- Ensure that your OKR plan is working by evaluating if it is automatically happening without your help. If you get your team to buy into the OKR's, they should be able to thrive on their own. If not, it is a failure and you can't scale that.
- Do not go back and forth between OKR and KPI, you will lose traction, making it less measurable, and sending mixed signals as to what is important for a manager and director.
- A merging OKR model is counterintuitive. It is better to implement OKR's in a way to have company centralized thoughts about it rather than getting every engineer's light item contribution.
Peter Berg, Founder and CTO at Forward, recounts how he introduced processes for continuous improvement and thus creating a more psychologically safe working environment.
Founder / CTO at Forward
Justin Potts, VP of Engineering at MoneyLion, tackles the ever-intriguing problem of simplifying the architecture and thus reducing the overall complexity of the systems.
Head of Engineering at MoneyLion
Brian Guthrie, VP of Engineering at Meetup, recalls the difficulties he endured due to a lack of cross-departmental cooperation caused by different systemic incentives teams were given to.
VP of Engineering at Meetup
Brian Guthrie, VP of Engineering at Meetup, tells a story of the first project he tackled as a Head of Platform Engineering -- a notification system gone amiss.
VP of Engineering at Meetup
Himanshu Gahlot, Director of Engineering at Lambda School, shares how he used his own learnings to support his direct reports and help them grow in their careers.
Director of Engineering at Lambda School
You're a great engineer.
Become a great engineering leader.
Plato (platohq.com) is the world's biggest mentorship platform for engineering managers & product managers. We've curated a community of mentors who are the tech industry's best engineering & product leaders from companies like Facebook, Lyft, Slack, Airbnb, Gusto, and more.