OKR Application in CS177

  • What are your OKRs for this product, if you were going to launch it for realsies?
  • Feel comfortable making something up when you get to the metric or even just put in X. Your best guess is fine, as you don’t have a baseline for comparison. What matters is that the metrics are a strong signal of success.

Christina’s article, The Art of the OKR, Redux, brought to light a lot of the truths and misuses of OKRs in tech. It seems as though every company, scaling from giants to small startups, interprets their objectives and key results differently. And it’s true, at different stages of the company, there may be different priorities. For example, she mentions that “I had to modify the OKR tracking approach from what I did at Zynga. Young startups have a very low tolerance for any meetings, much less daily deep analysis of tactics and metrics. I trimmed the meetings down to two key meetings a week; one to set intentions and one to celebrate progress. This bookended the week with clear reminders of what the company was trying to accomplish.” It’s interesting how even the people in these different companies have different wants in terms of work life. By having less meetings per week, but also positively reinforcing hard work, people are more likely to put in their best effort. This is the type of work culture that healthily contributes to the objectives and key results of a product. The guidelines that Christian provides is something that I hope to apply to Plates’ product. The following objectives and key results are some points that my group hopes to tackle in the future.

Objectives

  • launch an MVP that is recognized by Stanford students
  • provide a convenient medium for eating food
  • create a platform that sparks social connection in groups

Key Results

  • 2,000 students in user base
  • 15+ restaurant partners
  • 1st iteration of IOS application
Avatar

About the author