Standards without micromanagement

A high standard becomes useful to a team when people can recognize it in the work. If it exists only as the owner’s private sense that something is wrong, everyone else has to wait for the owner to inspect the result.

Two parts of Infinite Upside belong together here. Early in the book, Vijay Sheth describes learning to explain reasoning that initially seemed obvious to him. Later, the company’s ability to operate during his recovery depends on other people having enough information and responsibility to act. In both situations, private competence has to become something another person can use.

Describe a result someone can check

Instructions such as “be professional” or “take care of the customer” communicate an intention. They leave considerable uncertainty about the task. Different people can follow them sincerely and produce different results.

For a hypothetical reservation team, a clearer standard might specify that the customer receives the confirmed location and collection time, knows whom to contact, and is told promptly about any change. Those are observable conditions. The employee can check them before asking a manager to review the reservation.

This does not require documenting every sentence the employee may say. Give the person a view of what the work needs to accomplish, the commitments that must be respected and the decisions they are responsible for making. A useful explanation includes why a requirement matters. That helps someone respond intelligently when the next situation differs from the example.

Make a correction understandable

In the family chapter, Sheth describes the distance between seeing an error and communicating it well. Accuracy alone does not ensure that another person can understand or use the point. Tone, timing and the knowledge you assume can affect whether the explanation reaches them.

One practical implication is to correct the work specifically. What did the person know? What did you expect them to notice? Which part of the instruction would have helped them make a better decision? A general complaint about standards gives them little to try differently.

Separate a mistake from a preference. Perhaps a colleague chose a different sequence, used different wording or resolved an issue by a route you would not have taken. If the decision met the agreed requirements and stayed within their responsibility, replacing it merely to make it yours teaches a costly lesson: independent judgment will be undone.

Let the explanation be questioned

The owner’s first account may also be incomplete. Chapter 2 treats explaining a conclusion as a way to discover whether it is mistaken. Another person’s different view may contain information the owner has missed. That possibility belongs in a discussion of standards, not only in a discussion of courtesy.

Return to the invented reservation team. Suppose a manager insists that every confirmation be made by telephone. An employee points out that the customer requested written directions and cannot take calls during work. A completed call is easy to count, but it may be a poor measure of whether this customer received usable information.

The employee still has to fulfill the promise. The manager needs to decide whether the required method serves it. They might retain a telephone requirement where the situation demands a conversation, while allowing a written confirmation for this reservation. Neither a universal rule against procedures nor a universal rule against exceptions would answer the actual question.

Ask the employee what would be lost if the method changed, then ask yourself the same question. If the answer is only that you have always done it this way, the discussion has found something worth examining.

Review the decision and the role

The recovery chapter examines decisions through the information, authority and support available to the person making them. That prevents a disappointing result from becoming an automatic verdict on somebody’s character. It also prevents a lucky result from proving that the process was sound.

Use a recent, ordinary decision for a short review. Ask the employee to explain what they understood the task to require, which options they considered and where they needed help. Then examine the conditions you supplied. An unavailable record, an unclear permission and a gap in skill call for different repairs.

A manager can keep demanding standards while acknowledging that the role was poorly equipped. Equally, providing support does not mean overlooking a deliberate failure to meet an understood responsibility. The purpose of the review is to locate the problem accurately enough to do something about it.

Let the next decision stay with them

After the review, decide what the person can now handle without returning to you. That may require access to a record, a clearer spending limit or an available manager for larger exceptions. Leave an ordinary decision with them long enough to find out whether the preparation works.

Standards that another person can understand, apply and question give the company a way to improve while you are elsewhere. At the next review, return to the agreed result. Did the customer receive what was promised, and did the team have what it needed to provide it?