If they can point to a number from a really poorly/quickly done ad hoc study, they’ll never worry about being told they made the wrong decision
> Just reduce all their responsibilities into a few numbers so they don't have to really understand what's going on underneath them.
if thats all there was to it, might as well let an algorithm/software do the job instead....So we need metrics., lest we get swept away in the Trickle-down Incompetence.
I also think that the companies that matter getting bigger and bigger, with no actual failure on the horizon (such as bankruptcy) in case of strategically wrong decisions doesn't help things one bit, because in those cases management failure is in many cases rewarded as there's no immediate and adverse affect on the life of the company itself. We need some return to creative destruction, otherwise we'll be left re-arranging the chairs on the deck of the Titanic (I see this type of discussion on this particular subject as part of that metaphorical re-arrangement) until the proverbial iceberg will strike.
They're not going to be personally responsible for "improving the response time of the FizzBuzz server by 22.3%" or anything like that. No - the product manager tells the team on what they'll be working, the work gets broken down into parts, and they take what's available when they come up for air.
OKRs should never be handled at a level more granular than a scrum team, or equivalent.
You don't, as an individual "unit", which is part of the problem, i.e. modern management's focus in trying to split teams/big companies down to its "elementary" unit, the employee.
> Not having metrics means it all depends on the gut feeling of executives.
And that's why you need good executives, executives who have good guts. You cannot automate your way into being successful, at the end of it all running a company is still pretty much a social endeavour, one that cannot be partitioned down to individual units, neither can its success or failure be explained by those individual units alone.