What a Mechanic Knows That Most Sales Managers Don't

Every skilled profession measures causes before treating symptoms. Sales is strangely the exception — and it shows up directly in the results.

The argument in the previous chapter — measure inputs, not just outputs — sounds obvious when written down. It is worth showing why, because every other skilled profession already works this way, and sales is the strange exception.

The mechanic

Your bike stops working. You take it in.

The mechanic does not look up and ask, "Why did your bike stop?" That would be absurd — if you knew, you would have fixed it.

Instead, he checks the engine, the spark plug, the battery, the fuel line, the air filter, the wiring, the clutch, the brakes. He measures every input. Only then does he tell you the cause.

Now imagine a mechanic who simply announced: "Your bike isn't running."

You already know that. You have known it since it stopped. The value he provides is entirely in identifying why.

"Your calls are down" is the sales equivalent of "your bike isn't running." Everyone in the room can already see it. The job is to find out why.

The doctor

You go in with a fever. A competent doctor does not write a prescription on the spot.

He checks temperature, blood pressure, oxygen level. He orders a blood test. He asks about symptoms and history. All of these are inputs. He builds a picture of the cause, and only then treats.

The parallel is exact:

The building

Try constructing a building without a measuring tape, a spirit level, a scale or a blueprint. Just enthusiasm and hard work.

Would the walls be straight? Obviously not — and no amount of effort would fix it, because the problem is not effort. Construction depends on measurement. Not because measurement is virtuous, but because without it you cannot tell whether you are on course until it is far too late to correct.

Management works the same way. If you cannot measure work, you cannot improve work. You can only hope.

The cricket coach

This one may be the closest analogy of all, because it involves human performance rather than machinery.

A good coach does not say, "Why didn't you score a hundred?"

He studies footwork. Bat angle. Shot selection. Timing. Fitness. The quality of bowling faced. He watches the technique, because runs are only the outcome — technique is the cause.

And here is the part that matters for sales: a batsman can play beautifully and get out to a good ball. One innings tells you almost nothing. The technique tells you what will happen across twenty innings.

Exactly the same is true of a telecaller. A caller can do everything right in a month and land in a bad patch of data, or a seasonal slump, or a run of genuinely uninterested prospects. Judge them on the output alone and you will punish good work and reward luck — and your team will notice, quickly.

Judge on outputs alone and you are marking people on their luck. Judge on inputs and you are marking them on their work.

Why sales skipped this step

If the principle is this universal, why is sales management the exception?

Because in sales, the output is unusually easy to measure and the inputs are unusually hard.

Revenue counts itself. It arrives in the bank, appears in a report, requires no instrumentation at all. Meanwhile the inputs — how many dials, how long each conversation ran, whether the promised callback happened, what the customer actually objected to — traditionally required somebody to write them down by hand. And as we covered in Part II, that reporting either does not happen or happens so unreliably that nobody trusts it.

So managers measured the thing that was easy to measure. Not because they were lazy, but because the alternative was a clipboard.

The question to sit with

Take your last review meeting and ask honestly: were you the mechanic checking the spark plug, or were you the person announcing that the bike isn't running?

Most of us have been the second one, more often than we would like. Not through incompetence — through lack of instruments.

A mechanic without diagnostic tools is reduced to guessing too. The difference is that he would never accept working that way.