If management lays down some metric like "higher velocity by 20%" or "20% more bugs closed", don't be surprised when they get it and it turns out to not really be effective. (From imperceptible Story Point Inflation to 20% more technical debt, or bugs mysteriously skipping the bug tracking system...)
But you're right to an extent, and I skipped over it. There's a class of things (call them skills, behaviours or competencies) which aren't suited for evaluation through measurement: "teamwork", "leadership" etc. These are not goals and it's important to understand the difference. For competencies it's best to evaluate them on a simple scale (say 1-10, we don't even label the exact score) so the discussion naturally becomes a bit fuzzy and less concrete — because the concepts are fuzzy. Let's be honest, you want employees to improve in these competencies but there's really no effective way to evaluate them.
Plans and reviews should be driven by the measurable stuff (goals) and the employee's development is driven by discussions not scoring of their skills/competencies/whatever-you-want-to-call-them