Hey guys, I am looking for OKRs masters who could share their knowledge. In our organization, we’re currently facing the limitations of the OKR framework v. our product-long adoption cycle.
What are our constraints
- We’re operating in B2B space where majority of our product improvements need implementation (by the client dev team) on the customer side to work and generate value for the end user (non-technical roles)
- As a result, new functionality has a quite long adoption cycle (ranging from 3 to 6 months) among existing clients and is usually adopted much faster by new clients. The reason is that existing clients are usually occupied with other stuff in their already running projects and they need to plan their resources & budget for implementing the product improvements.
- New customer project build time is roughly 3 months
- Our development cycle length is roughly 2 months (this is now the sweet-spot for us that has the best ratio in overhead vs. value delivered)
What are our challenges?
- Decisions we make today in the product will be visible in the product itself next quarter, and in the product data the quarter after the release (the soonest)
- Evaluation of the objectives (did we solve the customer problem) therefore takes quite some time and makes evaluation of the OKR on bi-weekly basis quite challenging unless we deteriorate into tracking development progress
- We tried to go with some “validation oriented” OKRs, but that gives you only little insights into whether you reached the objective or not
- We don’t want to create non-sense OKRs just for the sake of having some
- This whole situation leads to distrust in the OKR framework as a whole and perception that it’s not suitable for our way of working
Anyone who tackled similar challenges during their career and have some advice how to deal with such situations?