Metrics Are Symptoms, Not Levers

In 2006, I was deployed with a unit that set a record for the best AH64 Apache maintenance performance in Army history.

I was a platoon leader. 

If you know the aircraft, you know it's a maintenance pig. It takes relentless, disciplined effort to keep one flyable. 

You don't get reliability by accident. You get it because people believe in the checks they're running and do them right, every time.

That deployment, my battalion set the record for the highest fully mission capable rate of any Apache unit in Army history at our flight hour level. 

But inside the the battalion, there were 2 distinct approaches.

Part of the organization ran on metrics. Leaders pulled up the numbers, brought them to the crew, and demanded the numbers get fixed. It felt like accountability. 

The other part of the organization ran on problems. Leaders sat down with crew chiefs, opened the logbooks together, and asked what was actually in the way. They made sure everyone understood what needed to happen and then went and removed the barriers standing between the crew chief and the fix.

Same aircraft. Same standard. Same deployment. Different result.

The problem-first side is what carried the battalion's numbers... and not by a small margin.

The lesson I carry from that deployment: a metric is a symptom, not a lever. 

You can't berate a number into improving. You can only find and remove what's blocking the people closest to the work. Do that, and the metric takes care of itself.

I've seen the same split play out on plant floors for years since. The leaders who ask, "what's stopping you," outperform the ones who just point at the scoreboard.

Which side of that split have you seen win?