What Doesn’t Get Measured Doesn’t Get Done
Why replacing workplace adjectives with simple arithmetic is the only way to fix your actual bottlenecks.
Every department has a throughput. Most have simply never been asked for the number.
Ask a team how the month went, and you will usually get an adjective. Busy. Tough. Promising. Adjectives are comfortable because they cannot be wrong, and they cannot be wrong because they cannot be checked. A number, on the other hand, is a commitment. It can be compared to last month, to the target, and to the team next door. That is precisely why so many departments quietly avoid producing one.

I lead teams across different business divisions, and I have learnt that the single most useful question a leader can ask any of them is the same: what is your throughput? Not how hard did you work, not how full was your calendar, but how many units of finished work actually came out the other end. Qualified leads generated. Deals closed. Support tickets resolved. Invoices collected. Production-ready features shipped. Every department, however creative or technical it believes itself to be, produces something countable. The organisations that grow are the ones that have done the unglamorous work of deciding what that something is.
The old management maxim says that what gets measured gets managed. I put it more bluntly: what isn’t measured doesn’t get done. Not because people are lazy, but because unmeasured work has no edges. It cannot be finished, only continued. A marketing team without a lead count can run campaigns forever and call it momentum. A support desk without resolution times can be permanently occupied without ever getting faster. Activity expands to fill the space that measurement should have occupied.
Measurement accomplishes three operational shifts that no amount of motivational rhetoric can match.
First, it creates a definition of done. The moment sales knows the month is judged on qualified clients closed, every conversation, demo and follow-up is arranged around that outcome. The target does the managing, so the manager doesn’t have to.
Second, it makes performance comparable. In a previous essay, I argued that an organisation is a chain, and growth is governed by its weakest link. Here is the uncomfortable corollary: you cannot find the weakest link in a chain you have never weighed. When every department reports throughput in its own units but on the same rhythm, the bottleneck stops being a matter of opinion. If marketing produced three hundred leads and sales converted twelve, the constraint has named itself. Without those two numbers, the same organisation would be having a very long meeting about whose fault the quarter was.
Third, it turns experience into learning. A month that ends with numbers can be interrogated. What moved? What didn’t? What did we change, and did it matter? A month that ends with adjectives simply evaporates. Teams that measure accumulate knowledge; teams that don’t accumulate anecdotes.
The obvious objection is that measurement breeds gaming, and badly designed measurement certainly does. If you measure volume alone without a quality threshold, you will simply get sloppy output delivered quickly. The fix is not to abandon the ruler, but to point it at acceptable output rather than raw activity. Calls made is activity; ideal clients closed is throughput. Posts published is activity; qualified leads generated is throughput. Hours coded is activity; features shipped without breaking production is throughput.
Resist the dashboard arms race. A department needs three or four numbers it truly owns, reviewed on a fixed rhythm, not forty vanity metrics nobody can influence. The discipline is in the smallness.
There is also a cultural dividend that surprised me. Teams often resist measurement because they expect surveillance. What they discover instead is protection. A salesperson who closed her twenty target clients does not need to perform busyness for anyone. The number has already spoken for her. Measurement, done honestly, replaces politics with arithmetic, and most good people prefer arithmetic.
So run the audit. For each department, ask: what is the unit of finished work, how many did we produce this month, and where is that written down? If any of those questions produce a pause, you have found next month’s project. It costs almost nothing, a definition, a count, and a recurring date in the diary, and it changes everything downstream, because strategy is only as good as the numbers it stands on.
Adjectives are for describing the work. Numbers are for running the business.



Comments