Paired constraints tell the truth.
Single metrics can always be gamed. Paired constraints make the truth visible.
You've seen this before. The team hits their number. The dashboard looks great. But something feels off. The number went up. Did the business actually get better?
“Deliver faster!” So corners get cut. Quality drops. But the delivery numbers look great.
“Get more users!” So you acquire at any cost. Retention tanks, but the growth chart goes up.
“Ship more features!” So the team burns out. Velocity looks great until people quit.
The same thing happens with AI. Vendors love single metrics.
“We automated 80% of tickets!” But what happened to resolution quality? Customers get fast, wrong answers.
“50% faster response time!” But accuracy dropped. The AI answers quickly. Just not correctly.
“Handles 10x the volume!” But satisfaction cratered. More throughput, worse outcomes.
The metric improves.
The system doesn't.
The solution isn't to pick better metrics. It's to pair each metric with its natural counterbalance.
How fast things ship
How well things work
New acquisition
Keeping what you have
Volume of work
Team sustainability
For AI capability, the same principle applies. Pair each impressive metric with what it might be hiding.
When you only measure one side, you can't see the damage.
When you measure both, the truth becomes visible.
The gaming scenario
Measure only speed
Quality silently drops
Speed “improves” — you hit the target
But the system is worse overall
The honest scenario
Measure speed AND quality
Gaming speed drops quality — visible immediately
Only genuine improvement helps both
The system actually gets better
Paired constraints create productive tension.
The only way to win is to genuinely improve.
Fix Perspective
For existing systems, pairing exposes the gaming that's already happening. When you add the counterbalance metric, you'll see exactly where “improvement” was actually damage in disguise.
Enhance Perspective
For new AI capabilities, pairing prevents gaming from ever starting. When you design measurement with both sides visible, the AI can't optimize for looking good at the expense of being good.
You probably already sense when something is being gamed. The numbers look good but the situation doesn't feel good. You just couldn't prove it. Or you're about to invest in something new and you want to measure it honestly from the start.
When speed goes up but quality drops, it's visible immediately. No more hiding problems in the gaps between reports.
When the only way to win is to genuinely improve, people stop looking for loopholes and start solving real problems.
Real improvement in both metrics builds on itself. Instead of paying down hidden debt, you're building real capability.
Fix Perspective
Start with your most suspicious KPI. The one where the number looks good but something feels off. What's the natural counterbalance? Add that measurement and watch what becomes visible.
Enhance Perspective
Start with your most impressive AI promise. Whatever the vendor is claiming. What's the natural counterbalance? Require that measurement before you invest and watch how the conversation changes.
Whether you're fixing existing measurement or designing for something new.
Direct answers to what founders and CEOs ask about KPIs, gaming, and honest measurement.
You're probably seeing Goodhart's Law in action: when a measure becomes a target, it ceases to be a good measure. Your team isn't doing anything wrong. They're doing exactly what you incentivized them to do. The problem is that single metrics can always be gamed. Speed goes up by cutting corners. Growth goes up by acquiring low-quality customers. Output goes up by burning out your team. The number improves, but the system doesn't. The fix isn't better metrics. It's paired metrics. When you measure speed AND quality together, the only way to "win" is to genuinely improve. Cutting corners to hit speed tanks the quality number. Gaming becomes visible.