Asking the team only for results is the least effort way to manage. It is also the most useless.
Until a result lands, that stretch of time is a blind spot. You do not know how it was produced, how many detours were taken, or whether the quarter was skill or luck. You find out the verdict when it arrives.
That is not management. That is waiting for a verdict.
I paid for this lesson. One unit posted solid profit for two consecutive quarters, so I stopped looking closely. The third quarter fell off a cliff. The first two had been carried by money that should have been spent and was not: maintenance skipped, headcount left unfilled. Two similar results, two entirely different realities underneath.
Had I read the process, I would have seen it in month one. Because I read only results, I was blind for six months.
Results-only management turns management into sampling. Look once a month and twenty-nine days are dark. Look once a quarter and three months are a black box.
You cannot imagine how much hides in a blind spot. Identical results come from completely different causes. A fluke, a bluff, and real capability all look the same on the P&L.
If your sensitivity is too low, everything looks roughly fine. Underneath roughly fine, the business may already be drifting, just not far enough to move the number. Nothing happens this time. Next time it hits you between the eyes.
Follow the process and you see change early. This is a coincidence, and here is the behavior behind it. This is a different path, which means the business is drifting and needs correcting. Only process data produces those judgments. Results never will.
The time lag cannot be eliminated, only compressed. When reporting gets too granular, people start manufacturing the numbers. Match granularity to the rhythm of the business and the blind spot narrows substantially.
On every material metric I now require process data alongside the outcome. For collections, weekly cash receipts and the aging roll-forward. For delivery, completed work orders plus a reason taxonomy for the open ones. For cost, consumption per ticket. Once granularity goes up, anomalies surface on their own.
This is worth repeating because results-only management is so common. It looks strict. In practice it controls nothing that matters, and the management function becomes decorative.
Demand a result and nothing else, and you do not gain control. You increase your risk. Everything before the result is blind, and you are simply waiting for the verdict.
So manage the process. Control the process. Every workflow should be designed around that idea. Over time you have a feel for the business. You know that if the process is right, the output will be roughly right.
Management is strong control. What it controls is the process. What it guarantees is the result.
Many people misread strong control as meddling in everything personally. It is not. It is eliminating information asymmetry, closing blind spots, raising sensitivity, and forcing problems to show up early.
Knowing everything does not mean touching everything. Once a problem is visible, it gets solved down the line. But if you know nothing, what exactly are you controlling?
Control rests on transparent information. Timely. Accurate.
This is why cross-verification between linked steps is worth more than repeated checking. If a step has only one source, nobody can verify it, and that number is questionable. Hiring one group to watch another, and a third to watch the watchers, is not capability.
China adds a layer here that investors underestimate. In founder-led Chinese service businesses, the control environment was one person holding every thread, and basic operational data was never designed to exist. Revenue sits in verbal arrangements and personal supplier relationships. Payroll is tied to people rather than positions. When a professional board asks for results, it is asking for a number the organization has no machinery to produce honestly, and middle management, being rational, supplies the number that ends the discussion.
That is where results-only management gets dangerous in this market. It does not reveal a control gap. It rewards one.
Does standardizing process kill innovation? No. What gets standardized is information granularity and routing, not human motion. Nobody specifies which foot an employee steps with first. Centralize decisions, but collect input from every step, then keep refining.
There is another reason so many companies prefer to assess results alone. Genuinely managing process is tiring. Breaking work down in meetings. Reconciling data step by step. Staring at workflows until they change. Asking for results from the office is far more comfortable.
So operational chaos is usually not a capability problem. It is laziness.
Some work only the person in charge can do. Otherwise, why are you in the seat.
When any capable manager can walk into this process and produce roughly the same result, that is capability. When it falls apart the moment the unit or the person changes, that is not a team problem. That is management that was never done.
Watch results alone and you only ever learn the outcome after the fact. To know early, you have to look inside the process.
Based on firsthand operating experience. Details have been anonymized.