The Efficiency Nobody Reports

I read a comment once from a young man who had automated most of his job.

He had built his workflow so well he could finish a full week in fifteen to twenty hours. He said he would never tell his manager. Not because he was lazy — he had done the harder thing, which was engineering the work down. He stayed quiet because he knew exactly what disclosure would buy him: more work, at the same pay.

He had run the math correctly.

That comment stayed with me because I had lived the other side of it. In 2017, twelve years into running my own firm, I took a full-time job out of curiosity. They would hand me a week of work. I would finish it in hours.

For a while I tried to slow down. I stretched a two-hour task across a day so it would land when it was expected. Pacing myself to the rhythm of the building was harder than the work itself. Eventually I stopped performing and just finished everything as fast as I could do it well, and then sat there with nothing.

That is when I knew I was leaving.

Plenty of people can collect a paycheck for looking busy. I cannot. My time and my creative energy are the only real assets I have, and spending them on the appearance of work — inside an organization that had already declined the system change that would have made the work meaningful — was not something I could defend to myself. Idle capacity in a place that has chosen not to improve is not rest. It is decay, and you can feel it happening.

I left. But the thing I took with me was the young man's calculation, and how ordinary it is.

The Incentive Nobody Designed on Purpose

Almost every knowledge-work compensation structure rewards two things: hours present and volume produced.

Notice what is missing. Nowhere in that structure is there a mechanism that rewards doing the same work in less time. Speed converts into volume. Volume converts into more assignments. The compensation stays flat.

So the employee who finds a faster way faces a straightforward choice. Disclose it and receive more work at the same pay, or keep it and convert the savings into breathing room.

Most people keep it. They are responding rationally to the system in front of them.

Nobody designed this deliberately. It emerged from measuring the things that were easy to measure. Hours are countable. Output units are countable. Judgment, insight, and the redesign of a process are not, so they went unmeasured, and unmeasured things do not get paid for.

What This Costs You as a Founder

Here is the part that should concern anyone running a company.

Your best people are hiding the most. Capacity to compress work correlates with capability. The person who automated a week into fifteen hours is likely the sharpest operator you have. The gap between their real output and their reported output is the largest in the building — and it is invisible to you.

The efficiency you are shopping for already exists inside your team. Founders spend serious money on software promising a thirty percent time reduction while sitting on people who have already achieved it privately and have every reason to keep quiet about it.

You are paying for the performance of work rather than the work. Some meaningful fraction of your payroll is funding the appearance of busyness. It does not show up on any statement. It shows up as a ceiling on what your company can do with the people it already has.

And the good ones leave. Not immediately. They stay while the arrangement is comfortable. Then they go somewhere their actual capability gets used and paid for — or, increasingly, they leave to work for themselves. I returned to my existing clientele because I realized I hadn't missed out on any real growth, just bureaucracy and government-like systems.

The Structural Fix

This is solvable, and none of it requires new software.

Stop measuring hours for roles where hours are not the product. If someone is hired for judgment, output quality, and problem-solving, tracking their presence measures the wrong variable and signals what you actually value. Define the outcome, the standard, and the deadline. Then stop watching the clock.

Pay for the improvement, not just the execution. Build a real mechanism — a bonus, a share of the savings, a title change — that triggers when someone permanently reduces the cost of a process. Right now, in most companies, the reward for finding a better way is more work. Change what happens when someone raises their hand and people will start raising their hand.

Make the promotion path run through process design. If advancement comes from handling more volume, you have told your team that volume is the currency and they will optimize for looking busy. If advancement comes from making the operation permanently better, they will optimize for that instead. People chase whatever the ladder is built out of.

Say the quiet part out loud, then follow through. Tell your team directly: if you find a way to do this faster, bring it to me, and the time you free up is yours to spend on higher-value work — not a reason to hand you three more accounts. Then honor it the first time someone tests you. That first instance is the entire policy. Keep your word so your team doesn't lose trust or become afraid of losing their jobs.

Ask the question nobody asks. In your next one-on-one: where in your work do you feel you are moving slower than you could? Don't make it sound like an accusation; more like an invitation. The answers will tell you more about your operation than any audit, because the people doing the work have known where the friction lives the whole time. Nobody ever made it safe to say so.

Why the Structure Matters More Than the People

The young man was not stealing from his employer. He solved a problem his company had not solved, and then made a reasonable decision about what to do with the result — given a structure that offered him nothing for sharing it.

What he did was set his own price. He looked at what his work was actually worth, saw that his employer had no mechanism for paying it, and collected the difference in the only currency available to him: his own time. That is value pricing. He also gave himself the promotion the structure was never going to hand him — from someone who executes a process to someone who redesigns it. He was almost certainly still underpaid.

I was not slacking in 2017. I was fast in a building that had no use for fast.

In both cases the individual behaved sensibly and the organization lost. That is a design problem, and design problems get fixed by changing the design.

Until then, your most capable people will keep converting their efficiency into private breathing room. And you will keep buying software to solve a problem you are already paying salaries to solve — twice.

If you suspect your operation is running well below its real capacity, that gap can be measured. →Book a free 15-min intro call