Delegating responsibility while continuing to decide every step leaves it unclear who is directing the work. The relationship between sovereign and general makes it possible to examine that contradiction, provided executive autonomy is paired with limits and accountability.
The relationship between Sun Tzu and micromanagement starts 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 decision-making is 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 questions
In chapter 3, sections 12 to 15 of Lionel Giles’s translation, the sovereign can harm the army by ordering movements it cannot carry out, managing it without understanding its conditions, or employing its officers without regard for the circumstances. Section 17 links the general’s capability with the sovereign’s lack of interference.
The commentary on the attack hierarchy of chapter 3 places those warnings within the work. The difficulty described is intervention detached from the situation. Bringing it into business does not show that every board question is an intrusion or that every executive decision must be accepted.
The analogy also does not establish legal authority. An ancient sovereign is not equivalent to a board, a board of directors, or a group of investors. The aim here is to examine 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 judgement with instructions on 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 result and the latitude to achieve it. “Improve the service” leaves questions open. A more precise formulation identifies which problem must be solved, what resources are authorised, and what conditions cannot be changed without a new decision.
As an organisational proposal, it is best to separate the team’s day-to-day decisions from those that change the commitment already made. Directing tasks within an approved scope may be delegated; changing that scope requires the agreed process. Limits should be known in advance, not appear afterwards when a solution displeases the person overseeing it.
Reporting, consulting, and requesting authorisation are not synonyms either. A person in charge can communicate a decision they were empowered to make. Turning every communication into a pending approval effectively cancels that latitude. Conversely, presenting a change as mere information does not make it a decision that was delegated in advance.
Review needs data proportionate to the question. To know the status of a deliverable, it may be relevant to check what is finished, what is missing, and what is blocking progress. Reviewing every message exchanged does not necessarily answer those questions better and adds work that must also be justified.
The executive has to explain the difficulties, including those that question their plan. The five virtues of the business leader offer questions about that conduct. Invoking autonomy to conceal a deviation is incompatible with a delegation that depends on shared information.
The agreement should also explain what happens when there is a significant change. It may establish that a blocked dependency is reported as soon as it is detected, without waiting for the next review. This distinguishes a necessary alert from a routine consultation about every step. The aim is to resolve the exception, not to return all decisions 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 organises testing and transition. It is agreed that the existing service will remain operational until it is confirmed that the new one can handle the expected enquiries.
During the work, one 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 actually requested.
The problem is not solved by asking the team for more initiative. First, it is necessary to clarify whether that request changes the assignment. In the example, the proposals are passed to the person in charge, who explains what they would require and which deliverable would be pushed back. If the change is approved, the commitment is updated and communicated to those who must carry it out.
The board can continue asking about the results. The difference is that it stops introducing tasks by parallel channels while holding the executive responsible for a plan it has already altered. Management, in turn, cannot dismiss every proposal by saying it belongs to the technical detail: it must explain its impact on the agreed objective.
Suppose testing reveals a limitation that delays the transition. The review compares the new evidence with the acceptance criteria and decides what must be checked before continuing. Changing the sequence for that reason is not the same as wilfully 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 focus is on asking what information the decision-maker needs. That question does not authorise the executive to blame all problems on the environment or avoid reviewing their own choices.
If repeated delays appear without explanation, decisions go beyond the agreed scope, or information is incomplete, it is appropriate to review how delegation is functioning. That review may ask for clarification, check results, and redefine limits. Temporarily reducing latitude 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 reproduces the contradiction at another level.
Check whether each person in charge can explain what they decide on their own, what they must consult on, and how they report the result. If the answers differ, the division of responsibilities needs to be clarified before asking for more autonomy.
View all articles in Leadership with Sun Tzu: how to review a team’s direction
