3 ms·
I agree with the sibling comment: this is just broadly dysfunctional and the presence of a something formally labeled an "OKR" is not the cause. At worst, the O
by nerdponx 2y ago
I agree with the sibling comment: this is just broadly dysfunctional and the presence of a something formally labeled an "OKR" is not the cause. At worst, the OKR enabled or exacerbated it.
- fifilura 2y agoI think the "at worst" was what happened here. Both in terms of taking a shortcut in the priority queue because it was easily measurable, lived on it's own right without complex dependencies and "the platform guys also need an OKR" But also in terms of how it was handled with regards to the OKR deadline, and possibly bonuses/performance reviews connected to how well it was achieved. Yes, it was dysfunctional, but the OKRs enabled it IMO. A huge company like google can swallow this because this fancy CI/CD tool was what they wanted all along, and there will always be another customer/project. But for a smaller company, this kind of shift in priorities can be lethal.