|
|
|
|
|
|
by ggregoire
2111 days ago
|
|
|
> 3 months later they're already forgotten and out of date. Some managers will try to keep it going for their teams, because that's what they were told to do, but that'll peter out once they realise no-one else in the org is taking it seriously. > 6 - 12 months later there'll be a half-hearted attempt to reset and resurrect the OKR process, but after the first time people take it even less seriously the second time around, and after a few more months OKRs are never mentioned again. At GitLab (I don't work there but it's explained in their public handbook), OKRs are updated/redefined every quarter. Seems a good way to avoid the issues you are describing. https://about.gitlab.com/company/okrs |
|
|