The Army Can Tell a 21-Year-Old Exactly What Good Looks Like. Most Organizations Can't.
In July, my son passed his Army Combat Field Test.
As he crossed the line, his sergeant turned to the soldier who finished right behind him and said, "You just let a guy who hasn't run in two months beat you."
I have been turning that morning over ever since, and not for the reason you would expect. The proud-mom part is easy. The part I keep coming back to is what the Army had done months before he ever showed up that day.
They told him exactly what good looked like.
The Standard
The Combat Field Test is a mandatory annual assessment. Age-neutral, gender-neutral, pass or fail. You complete the whole circuit in 30 minutes or less, in combat uniform and boots.
A 1-mile run. 30 dead-stop pushups. A 100-meter sprint. 16 reps lifting a 40-pound sandbag onto a 65-inch platform. A 50-meter carry with two 40-pound water cans. A 50-meter movement drill, half high crawl and half combat rush. A final 1-mile run.
He finished in 26 minutes and 30 seconds. (A personal best) After weeks of being restricted from training because of an injury.
Now look at that standard again, not as a parent, but as a leader.
Four Things That Standard Does That Almost No Role Definition Does
It is written down. Not carried in a commander's head, not inferred from what got praised last quarter. Not 'stay fit.' It's written, published, identical for everyone. A soldier can read it a year in advance and know precisely what will be asked.
Ask yourself how many people on your team could read the standard for their own role. Not their job description. The standard.
It describes an outcome, not an activity. Nowhere does the CFT measure how many hours he trained. Nobody tracked gym attendance, logged his meals, or scored his effort. The standard is the result: this circuit, this time, this uniform.
Compare that to what most organizations measure. Calls made. Tickets closed. Hours logged. Days in the office. Those are activities. They tell you what someone did. They do not tell you whether it worked.
It is known in advance. He was not evaluated against a criterion introduced on the morning of the test. There was no moment of finding out what he was being judged on while he was being judged on it.
That single fact is the difference between a standard and an ambush, and it is the reason most performance reviews go badly. If the review is the first time anyone clearly describes what good looks like, it is not a review. It is a surprise, and people do not absorb surprises. They defend against them.
It is one signal. Not twelve metrics on a dashboard. One time on a clock, under defined conditions. Simple enough to hold in your head while you are exhausted at the 50-meter carry.
Most measurement systems fail from too many measures, not too few. When everything is tracked, nothing is the standard.
Then The Injury, Which Is The Whole Argument
Here is the part that convinced me this story belonged in a month about measuring performance.
He got hurt. He could not train the way he had planned. Weeks disappeared.
And the standard did not move.
What moved was the method. He could not run, so he worked what he could work. He kept showing up. He paid attention to what he ate. He prepared in the ways still available to him, consistently, while the calendar ran out.
The plan changed. The target did not. And on the day, the clock said 26:30.
Now imagine the Army had measured training hours instead of the result. The injury would have ended him. Not because he wasn’t capable of passing, he clearly was, but because the measure would have been counting something he was physically unable to produce. He would have failed a test of activity while passing a test of outcome.
That is not a hypothetical problem. That is what happens in organizations every quarter.
When you measure activity, any disruption to the method looks like failure. A person who finds a faster way to the same result gets penalized for lower volume. A person who solves the problem in one conversation instead of nine looks less productive than the person who had the nine. And the moment something changes, a client, a market, a diagnosis, an org chart, the measure stops describing reality and starts punishing adaptation.
When you measure the outcome, the method is free to change. Which is the only way anyone gets through a year that does not go according to plan, and no year does.
The Question This Leaves For Leaders
The Army wrote a standard specific enough that a 21-year-old, injured, with every legitimate excuse available to him, could still tell exactly what was being asked and go get it.
Could you write that for one role on your team?
Not a job description. Not a list of responsibilities. A standard. What this role is here to produce. What good looks like when it is happening. The one signal you would watch. And a date.
Most leaders cannot do this on demand, and it is not because they are bad leaders. It is because nobody ever asked them to, and the work is slow, unglamorous, and never urgent. It is also the most fixable gap I see.
Here is what makes it worth the twenty minutes. A defined standard is not a way to be harder on people. It is the thing that lets them be resourceful. Jr. could adapt because he knew what he was adapting toward. Take that away and all anyone can do is guess at what will count, which is exactly what most of your team is doing right now.
Take one role this week. Write the standard. Hand it to the person in it and let them argue with it.
Then get out of the way and let them figure out the method.
He is 21. He passed in 26:30, and he taught his mother something about measurement. So proud of you, Jr.
Find the real problem. Do the real work. Build what lasts.
Comments