An OKR is a one-line objective and 1 to 5 key results. The reading explains how they must be short and memorable. The article further explains how one should only have one OKR a quarter. For the sake of training how to write good OKRs, I propose multiple OKRs that are far out and for different sub teams of the hypothetical start-up that we are in.
If we were going to launch the group scheduling web application, we would need to first take care of the following objectives:
Build a first MVP that makes college students excited.
Users revisited their scheduling process twice.
50 % of users successfully scheduled a meeting with our app.
Number of users doubled.
Make Google calendar integration work seamlessly.
Our access to user calendar data is approved by Google.
Extracting free times works within 2 seconds.
Free times are correctly presented in our app.
Create a user interface that is minimal and efficient.
Customers using calendar integration can provide availability within 10 seconds.
Customers come back to schedule another meeting after first-time use.
No more than 3 erroneous clicks per user per group scheduling.
The user experience is so good that people enjoy scheduling meetings.
50 % provide their availabilities within 1 day.
70 % of schedulers customize the theme with GIFs or private pictures.
Progress bar is expanded twice per user per meeting to check “horserace”.
App is so motivational that everybody provides their times.
90% of all attendees provide times within 2 days.
85% of schedulers did not send out reminder.
Average time for scheduling a meeting is 24 hours.
