I don't know what the rest of the comments are on about but this is a pretty reasonable proposal. In particular, it's heinous to couple customer acquisition to

I don't know what the rest of the comments are on about but this is a pretty reasonable proposal. In particular, it's heinous to couple customer acquisition to engineering projects. Maybe customers don't want what you're selling, or maybe the economy is taking a down turn, or the sales pipeline is broken. OKRs can absolutely be useful, but like so many other things, a system is what it does. If you measure bug rate, then you'll get no bug reports, even if there are bugs. OKRs, when done correctly, aren't about accountability necessarily, but course correcting early and often. It's a tool to combat scope creep and a feedback loop for triggering pivots when progress towards laid plans aren't yielding returns. These are things engineers should love! They keep engineers focused on the right things, aligned with the business and most importantly keep the business aligned with them. Politics and bureaucracy are rampant everywhere, but like everything else, when used in moderation these tools can be really good.