3 ms·
OKR's are mostly done with things that move the needle with respect to money or user engagement/metrics. That more or less mandates building new products, feat
by kamaal 8y ago
OKR's are mostly done with things that move the needle with respect to money or user engagement/metrics.
That more or less mandates building new products, features and services.
Refactoring, tests etc don't fit anywhere in the OKR model.
- wahnfrieden 8y agoOKR is not a comprehensive planning tool either. It doesn’t have to explain all the work that you do, directly.
- xtracto 8y agoThe way I have factored these and other type of tech debt is to factor it in as development efficiency. Particularly for startups, as they grow, one engineering team objective is to remain efficient as the team is growing. The way to achieve that? By refactoring code and introducing automation (like CI, CD, etc). This gets reflected in the cost of developer time per feature / project. Which can be represented as a KR in the. OKR framework.
- closeparen 8y agoRight, so you do it outside the model. We have a % of engineering capacity reserved for non-customer-facing work. Unfortunately it is mostly spent responding to infrastructure / dependency churn, just treading water rather than getting ahead, but it helps. No one is going to criticize you for refactoring what needs refactoring, as long as you are also making progress on your OKRs.