Abstract Wikipedia team/OKR scoring

Purpose

The goal of OKR scoring on the Abstract Wikipedia team is to reflect on what we set out to accomplish in the previous quarter, and inform our planning for the next quarter. We typically conduct OKR scoring near the end of each quarter, during planning for the next quarter.

Scoring Scale

Each project is scored on a 0-to-1 scale:

• 0.0 - no progress
• 0.3 - made some progress, and didn’t meet success metrics
• 0.5 - mostly complete, but didn’t meet all success metrics
• 0.7 - complete and all success metrics met
• 1.0 - completed more than expected and went way above original success metrics

We consider an average of .7 across all our projects to be a success—it means we planned for the right amount of work

How to Score

It’s tempting to give a high score when we’ve worked hard on a project. It’s especially tempting if we also respect and admire our colleagues who worked on it! However, we are not scoring people, nor effort—we are scoring the completeness of a project.

We would be doing ourselves a disservice if we inflate our scores as a way to celebrate team members and their efforts. For example, let’s say we over-committed on projects one quarter and need to pare things down next quarter. If we score ourselves an average of .7, that would signal that we signed up for the right amount of work and we’d go for the same amount next quarter. This would not be the intended outcome for planning. In a quarter where the work was mostly complete, we should get a .5. This would tell us we committed to too much work and we’ll need to commit to less next quarter.

That said, it is important to celebrate our efforts and accomplishments, and we have time set aside for this purpose at our bi-weekly retrospectives!

Process

1. Create a room on https://hatjitsu.toolforge.org/
2. For each project, have a short discussion about how it should be scored. Are there extreme differences in opinions?
3. Distribute the voting link. Click on it only if you are voting. To abstain, don't click the link
4. Each team member inputs a number from 0-1 based on the above scale
5. Enter the final score (average) on the appropriate tab in our roadmap doc