When You Say Progress, What Are you Measuring?

Someone on your team just spent three hours testing an approach that did not work.

It is not nothing. They now know something true that will save the project real time later. But there is no field in the update template for that. So they stare at the blank line, trying to figure out how to describe an afternoon that produced no deliverable but real understanding.

Progress is often treated as something you can point to. A finished piece of work. A milestone reached. A number that moved. For many people, that has always been the definition. Work counted once it was done, and the thinking behind it stayed private. Progress meant output.

Others learned something different. Progress was visible through iteration, through what changed from one version to the next, through insight gained along the way. Learning itself counted as forward movement, even before a result fully landed.

A third group learned something quieter, and harder to name. Somewhere along the way, sharing honest uncertainty got read as a lack of competence, or as an excuse. So they learned to translate what they were still figuring out into language that sounds more finished than it is. Not dishonesty, exactly. Self protection, dressed up as a status update.

Same work. Three different ideas of what counts.

This shapes what people choose to make visible. A leader asks for an update expecting something tangible, and someone offers a reflection or a partial insight, genuinely believing that is progress. Or the reverse happens. A leader says learning matters, and the team holds back anyway, unsure whether understanding without a result will actually be taken seriously when it counts.

The cost is not just a mismatch in expectations. It shows up as progress that looks polished but teaches very little, or as real learning that never translates into anything visible enough to build momentum. Sometimes it shows up as a team quietly performing certainty about work that is still, underneath, very much in motion.

This is not about choosing output over learning, or the other way around. Both matter. It is about noticing which one is being made visible in your team, and which one is being quietly sidelined.

A question worth pondering: when progress is shared here, what gets recognized? Completed results, or evolving understanding? And who on your team learned, long before

they ever worked for you, that only one of those was allowed to count?

What shaped your own experience of this?