I don't mean to say that they're not good - looking at yours, they seem very reasonable. We're introducing a Product team right now, over/with a dev team that's been otherwise self-reliant for the last two years, and there are growing pains with that process. As silly as it is, speaking everyone's language (not talking about KPI's or sending power points to devs, not sending Legal to GitHub to checkout your terms of service, etc) is important for buy-in.
That being said, yours is the first tech person's blog post about KPIs. I'll be sure to check back on it as we get our dashboard off the ground - thanks Ryan.
It reminds me strongly of MVP - people that "get it" love it (I'm among them), and it changes the way that they think of things. However, it's buzz-word-y, and alienates those who don't. My point isn't that KPIs are a bad thing (or even a bad term), but there's an important subset of people who stop listening when you say it.