OKRs for project manager, offer many benefits. These include increased focus and productivity as well as better transparency and alignment with your team. But when it comes to setting OKRs, project managers often have a difficult time. There’s a tendency to do what they do best and write project plans instead of OKRs. It’s a common mistake that can be solved with a little know-how and practice.
Remember: OKRs are not projects. Objectives are your big ambitious goals. These should be aspirational, time-bound, and qualitative. Key Results are used to measure the achievement of an Objective. Your Key Results should be measurable, quantitative, and difficult (but not impossible). Your projects, weekly activities, and initiatives (Plans) are what help drive the progress of your Objective forward.
OKRs for project’s manager can be the different parts of the projects he’s working on or the KPIs the project has to meet/things the project has to accomplish.
Here is an Example OKR for a Project Manager>
Objective: Successfully launch version 3 of our main product
- Get over 10000 new signups;
- Get published product reviews in over 15 publications;
- Achieve sign-up to trial ratio of over 25%;
- Achieve trial to paid ratio of over 50%
Using an OKR system like Weekdone can also be quite beneficial for helping keep track of your OKRs especially if you are using a project management system like Jira or Asana. The big difference between project/task management tools is the level of granularity between these items and the enhanced visibility that Weekdone adds.