Sun Tzu and Micromanagement: Executive Autonomy with Oversight

Delegating responsibility while continuing to decide each step leaves unclear who is directing the work. The relationship between sovereign and general makes it possible to examine that contradiction, as long as executive autonomy is paired with boundaries and accountability.

The relationship between Sun Tzu and micromanagement begins with a problem: giving orders without knowing the conditions under which they must be carried out. Within Sun Tzu Applied to Leadership, the comparison makes it possible to examine how decisions are divided between the board of directors and executive management, not to place the CEO above all oversight.

The sovereign and the general: what the passage challenges

In chapter 3, sections 12 to 15 of Lionel Giles's translation, the sovereign may harm the army by ordering movements it cannot carry out, managing it without understanding its conditions, or employing its officers without regard to the circumstances. Section 17 links the general's ability to the sovereign's lack of interference.

The commentary on the hierarchy of attack in chapter 3 places those warnings within the work. The difficulty described is intervention disconnected from the situation. Transferring it to business does not prove that every board question is interference, or that every executive decision must be accepted.

The analogy does not establish legal authority, either. An ancient sovereign is not equivalent to a board, a board of directors, or a group of investors. Here, the goal is to analyze decisions within an already established division of responsibilities, without replacing it or deriving legal obligations from the treatise.

For this reading, we will call micromanagement the repeated replacement of delegated judgment through instructions about details, without clarifying who retains responsibility. Reviewing a deviation is different: it asks about its causes and the options available before deciding whether intervention is appropriate.

Agree on what is decided, what is consulted, and what is reviewed

A clear delegation should describe the expected outcome and the latitude allowed to reach it. “Improve service” leaves questions open. A more precise formulation identifies which problem must be solved, what resources are authorized, and which conditions cannot be changed without a new decision.

As an organizational proposal, it is worth separating the team's day-to-day decisions from those that change the commitment that was made. Ordering tasks within an approved scope can be delegated; changing that scope requires the agreed procedure. Boundaries should be known in advance, not appear later when a solution displeases the person overseeing it.

Informing, consulting, and requesting authorization are not synonyms, either. A manager may communicate a decision they were empowered to make. Turning every communication into a pending approval effectively removes that room to act. Conversely, presenting a change as mere information does not make it a previously delegated decision.

Review needs data that is proportionate to the question. To understand the status of a delivery, it may be relevant to check what is done, what remains, and what is blocking progress. Reviewing every exchanged message does not necessarily answer those questions better, and it adds work that also has to be justified.

The executive has to explain difficulties, including those that challenge their plan. The five virtues of the business leader offer questions about that behavior. Invoking autonomy to conceal a deviation is incompatible with delegation that depends on shared information.

The agreement must also explain what happens when there is a significant change. It may establish that a blocked dependency is reported when it is detected, without waiting for the next review. That distinguishes a necessary alert from a routine consultation about every step. The goal is to resolve the exception, not to return every decision to the board.

An example of oversight that does not replace the team

Imagine a fictional company that decides to renew its customer service system. The board approves the goal and the available resources. Executive management takes on coordination, while the team organizes testing and the transition. It is agreed that the existing service will remain operational until the new one is shown to handle the expected inquiries.

During the work, a board member directly asks a developer to add a feature for a demonstration. Another asks the project lead not to change the scope. The developer receives incompatible instructions, and the schedule no longer matches the work that was actually requested.

The problem is not solved by asking the team for more initiative. First, it has to be clarified whether that request changes the assignment. In the example, the proposals are forwarded to the person in charge, who explains what they would require and which delivery would be displaced. If the change is approved, the commitment is updated and communicated to those who must carry it out.

The board can continue asking about results. The difference is that it stops introducing tasks through parallel channels while holding the executive accountable for a plan it has already altered. Management, in turn, cannot dismiss every proposal by claiming it belongs to technical detail: it must explain its effect on the agreed objective.

Suppose the tests reveal a limitation that delays the transition. The review compares the new evidence with the acceptance conditions and decides what must be checked before continuing. Changing the sequence for that reason is not the same as capriciously failing to follow an order; it requires showing which assumption is no longer being met.

Attention to context connects with the six terrains of chapter 10. In this adaptation, the relevant question is what information the decision-maker needs. That question does not authorize the executive to blame all problems on the environment or to avoid reviewing their own choices.

If repeated delays appear without explanation, decisions fall outside the agreed scope, or information is incomplete, it is appropriate to review how delegation is working. That review may request clarification, check results, and redefine boundaries. Temporarily reducing room to act needs an identifiable reason, not a personal preference for controlling every action.

The same criterion applies between the executive and their managers. Care and discipline in talent management addresses how to maintain clear expectations without turning supervision into constant surveillance. Demanding autonomy from the board and then denying it to the team repeats the contradiction at another level.

Check whether each person in charge can explain what they decide on their own, what they must consult about, and how they report the result. If the answers differ, the division of responsibilities needs to be clarified before demanding more autonomy.

View all articles in Leadership with Sun Tzu: How to Review a Team’s Direction