Earn up to $100 when you refer your friends to Taro Premium. Learn more
Taro Logo

How to write an OKR for something with a lot of risk/uncertainty?

Profile picture
Senior Software Engineer [E5] at DoorDash25 days ago

My team made a ton of changes (e.g., different UI, different SDKs, etc.) when rearchitecting a large feature last year. When metrics were impacted during the rollout, we didn’t know what caused the metrics degradation due to all these changes and had to ramp down the experiment repeatedly last quarter. We’ll likely run into lots of unanticipated issues when ramping back up this quarter as well. Due to this uncertainty, what should we have as an OKR for this feature? Committing to a 100% rollout seems like setting the team up for failure. My team’s also working on another project this quarter, but we want to make some progress on this feature. Since it’s unlikely we can hit an OKR for 100% rollout, would it make sense to have an OKR for, say, committing X% time for feature Y? We’ll likely ramp up, discover some issues, ramp down, resolve the issues, then ramp back up repeatedly. Unfortunately we don't know what issues we'll run into ahead of time.

1 Like
1 Comment


(1 comment)
  • Lee McKeeman
    Staff SWE at Google, ex-Meta, ex-Amazon
    25 days ago
    1 Like
Taro Footer Icon
Taro Footer Logo

Explore by company


Explore by level

Taro iOS appTaro Android app
Copyright © Taro