Making OKRs more playful using hill charts

I think it could've used a real example, or a completed example in the template.

Am I right that you idea is you're mapping the KRs to different points on the chart? Or is it about progress towards KRs?

It seems hard to decide where a KR lies in terms of uncertainty/certainty when it's just a measure

Sure, OKR's can help keep multiple teams aligned on business and product goals. And that's an advantage that's too big to ignore. But the problem with OKR's is too often, they're handed down by well meaning people multiple levels removed from the day to day software development work. There can be a lack of ground truth. But too often they miss the bottom-up intelligence, creativity, and engineering needs that comes from the people who work on the product day to day. It's also important not to load your product roadmap into OKR's and call it a day, or else you'll end up with teams of people who check boxes and software that barely makes it out of the driveway. Personally, I would encourage a reflection period after each series of OKR's. Not to just discuss outcomes amongst the senior leaders, but to collect intelligence on the ground, talk to devs, talk to users, talk to support reps, and decide what really should be the priority. But hey, what do I know I'm just a person who's comment you're reading.

When ive been introduced to okr Ive really liked this concept to the point that i started to use them in my private life

But on the other hand i dont fully like them in my work life

First my job forces OKRs amount and treats them equally

So OKR like completing half day training and sharing the learnings has the same value as multi month engineering effort.

I really don’t understand people who are interested in things like OKRs.