Prioritizing your work. What you are doing, why you are doing it, what’s going to be the best return on your time, what is your capacity to actually accomplish things and are you overloading yourself so that you have to rush everything constantly.
Naturally, the output is constrained by the available input. If a KR doesn't take into account the available input, then it is prone to be unrealistic.
It’s there for accountability.
But the O should be the North Star.
Same. But, I think it's a symptom of a bigger problem: lack of coherent strategy. And, I think a lot of companies suffer from this.
So OKRs frequently act as a suboptimal stand-in for strategy. This, instead of flowing from sound strategy and concrete tactics.
I'm not sure how well they'd work even if that was in place. But, without it, they don't stand a chance.
That sounds like OKRs by another name to me. Objective 1: increase revenue. Key result 1a: achieve $X revenue this quarter. Objective 2: increase customers. Key result 2a: number of customers exceed Y by this quarter. Objective 3: increase employer retention. Key result 3a: employee attrition stays below Z% this quarter.
E.g. How Measure What Matters and Radical Focus describe OKRs - two of the most popular books on the subject - differ quite a lot.
I think finally there's some consensus that cascading OKRs is a bad practice but unfortunately people keep.doing it because that's how it was described in MWM.
We tended to have goals / OKRs per team and longer term goals they could align to. Flatter the better when possible.
Any high-level goal becomes an O. Then any measurements of that goal become separate KRs under that O. Simple as that.
Formatting goals this way has its value. A vague goal that cannot be measured with have missing KRs; so this discourages writing vague goals.
I think the changes you are suggesting are sensible, but I would still not use OKRs.
"OKRs have helped lead us to 10x growth, many times over." --Larry Page, in his forward to the book "Measure What Matters"
--Me, in the post above.
I think this doesn't happen because explaining why you're going in a certain direction is hard. Most startups don't really know if the direction they are going is correct and are just trying a bunch of things. This doesn't lend itself to management putting themselves out there and as such, try to push some of that work out to normal employees through OKRs and trying to make them more "autonomous". At the end of the day, there's only so much under our control and the OKRs don't help.
My main gripes with them:
- They focus on output, and I believe most organization (especially startups) should focus on input. In that regard, I'd spend more time figuring out your internal playbook rather than measuring the (invariably too many) goals you've set for yourself and your team at the beginning of the quarter.
- The don't reflect reality. As soon as you set measurable outcomes for anything beyond the hard success metrics (e.g. revenue, profit, churn, CAC...), expect people to try and game the system. This leads to either people hitting the numbers but missing the mark, or simply failing to report accurately.
- They're mostly useful for underperformers. I have the same feeling about 1:1s. Your top performers usually don't need OKRs to know what needs to be done or how well they're performing. This ends up being a lot of busywork, especially for those who want to get sh*t done.
I wouldn't "improve" OKRs. I'd drop them:
- Set high level goals for the company (e.g. revenue, customer acquisition and employee retention).
- Have leadership set TODOs for the company and teams, BUT use this mostly as a way to foster debate and alignment on what needs to be done. Expect them to change often.
- Focus on your inputs. And on that topic, I would invest in building a culture of documenting what you do and how you do it (for example through a playbook). You can't build on quicksand.