Hi @rajaraman,
That’s a really good question! I’ll be plain honest that we still have room for improvement on our OKRs.
I can however give you an example of how OKRs embody the experimental approach that gets results. The key is to craft OKRs that are entirely focused on the outcome, not the output.
We recently worked on Piktostory.com, and the main OKRs were:
- Increasing activation rate to xx%
- Acquiring xx,000 users who are in the target group
As compared to an output focused OKRs, such as:
- Build features on the roadmap (payment, email system, admin dashboard, Helpscout, editor foundation, and core repurposing needs) by eoQ1 and launch Piktostory by X date
By giving a business metric that the team can focus on, they have tonnes of incentives to thoughtfully experiment and try to hit the numbers.
Hope that answers!