I believe this was meant as a reply to my comment, and I agree with you entirely.

Often the easiest metrics are the least useful. I worked in an office that wanted "production hours" (the business was largely labor-oriented, where that was actually a semi-useful metric, but it's not a useful metric in software development). It was gamed, as long as people charged directly to a project they were "productive". The costs of training and all were hidden as much as possible so projects and teams could seem productive. This meant that customers were being billed hundreds of dollars an hour for training that may not have even related to their project (bordering on fraud here, certainly abuse of some kind). But it also meant that the training budget (organizational) was slowly being cut, because no one was using it.

Selecting your KPIs carefully may not prevent failure, but choosing them poorly can almost guarantee failure or mediocrity.