I think the first thing you need to do is get out of the programmer mindset. The problem you are solving may be closer to resolving the anxiety of leadership, or build confidence. In reality, the situation is complex and our responses may undermine confidence and drive anxiety at different rates with different stakeholders If you ask some folks from other fields to read the StackOverflow link you shared, they'd provide some insights that aren't fully explored.

I don't think you can get there with KPIs, but at the same time, you can't completely discard methods like these which have some level of credibility with other stakeholders. As evidenced by many conversations on this topic involving programmers, KPIs get completely thrown out, or worse, undermined. Insufficient time and effort is given to actually making the leap to something that might be useful sustainable. Hence, many places never break away from KPIs and the complaints keep coming.

Measurement without particular targets can be quite useful when the organization is open to sharing data without punitive responses. This gives you different axes to explore with regards performance so that you can shape your messaging around performance provided you can contextualize it.

EDIT: My personal philosophy on how strategy should work and be implemented is closer to that of Mintzberg (https://en.wikipedia.org/wiki/Henry_Mintzberg) than Porter.