"Roadmaps should have varying resolution - detailed near-term, directional far-term"
Evidence from the Archive
Coda, YouTube, Microsoft
YouTube OKR process: Mehrotra's experience leading YouTube's teams at Google shaped his critique of the 70% guidance
Coda: rejects Google's 70% OKR target in favor of 100% commitments because startups cannot afford to miss 30% of promises
Led YouTube's product, engineering, and design teams at Google for six years and founded Coda -- a product literally built to run team rituals including OKR planning -- giving him both operator experience with OKRs at Google scale and founder experience redesigning OKRs from first principles. Their core argument: OKRs work but you should throw out the 70% target - goal for 100% of commitments.
The evidence is specific: Coda: rejects Google's 70% OKR target in favor of 100% commitments because startups cannot afford to miss 30% of promises. Furthermore, coda Maker Billing: only doc creators pay, removing friction from sharing -- a pricing decision informed by growth loop (Black Loop) thinking. YouTube OKR process: Mehrotra's experience leading YouTube's teams at Google shaped his critique of the 70% guidance.
In Shishir Mehrotra's own words: "We throw out the piece about 70% of hitting your goal being considered success. I believe this is a luxury you have when there is a money-printing machine in your basement (like Google). Instead, we goal around getting to 100% of our commitments." (On rejecting Google's 70% OKR target.)
Coda
Coda's Dory/Pulse ritual: in every meeting and write-up, everyone writes opinions simultaneously (hidden from...
Bing Gordon (EA co-founder) articulated the golden ritual framework: Amazon has six-pagers, Google has OKRs, Salesforce has V2MOM -- each is named, known by the first Friday, and templated
Led YouTube's product, engineering, and design teams at Google, now runs Coda, and has interviewed over 1,000 people for his book 'Rituals of Great Teams' -- giving him a uniquely broad perspective on how the best companies operationalize their roadmap processes. Their core argument: Roadmaps should have varying resolution -- detailed near-term, directional far-term -- and be embedded in team rituals.
The evidence is specific: Coda's Dory/Pulse ritual: in every meeting and write-up, everyone writes opinions simultaneously (hidden from others), then questions are collected and up/downvoted -- new employees regularly cite this as proof of the open culture. Furthermore, bing Gordon (EA co-founder) articulated the golden ritual framework: Amazon has six-pagers, Google has OKRs, Salesforce has V2MOM -- each is named, known by the first Friday, and templated. Shishir interviewed over 1,000 people for his rituals book, from Nike and Disney to startups, finding that the how-we-work rituals are what people most willingly share and most eagerly learn about.
In Shishir Mehrotra's own words: "It's not a committed plan, it gives the team and the broader company a look at the longer arc and helps them contextualize your current quarter's OKRs." (On how Coda balances detail in near-term with direction in far-term roadmaps.)