... | ... | @@ -13,7 +13,7 @@ |
|
|
|
|
|
* Determine around three key results per objective.
|
|
|
* Key results express measurable milestones which, if achieved, will directly advance the objective.
|
|
|
* Key results should describe outcomes, not activities. If the KRs include words like “consult,” “help,” “analyze,” “participate,” they’re describing activities. Instead, describe the impact of these activities, e.g., “publish customer service satisfaction levels by March 7th” rather than “assess customer service satisfaction.”
|
|
|
* **Key results should describe outcomes, not activities**. If the KRs include words like “consult,” “help,” “analyze,” “participate,” they’re describing activities. Instead, describe the impact of these activities, e.g., “publish customer service satisfaction levels by March 7th” rather than “assess customer service satisfaction.”
|
|
|
* Measurable milestones should include evidence of completion and this evidence should be available, credible, and easily discoverable.
|
|
|
|
|
|
|
... | ... | @@ -30,17 +30,13 @@ |
|
|
* Key Result 2
|
|
|
|
|
|
|
|
|
### Goals at the Tor Project
|
|
|
### OKRs at The Tor Project
|
|
|
|
|
|
* coverage (list of goals for every team lead or area lead)
|
|
|
* document work attached to each goals
|
|
|
* implement a routine to review goals and work associated:
|
|
|
* teams do it every 3 months
|
|
|
* team leads or area leads have goals per semester
|
|
|
* Each team lead define objectives for their area.
|
|
|
* We update OKRs every 6 months
|
|
|
* We document the work done for every OKR in issues in Gitlab with milestones and labels to help track them.
|
|
|
|
|
|
----------------------------------------------------------------------------
|
|
|
|
|
|
### Objectives per team and area
|
|
|
|
|
|
|
|
|
[Previous OKRs](previous-okrs) |
|
|
\ No newline at end of file |