Delegating responsibility and still deciding every step leaves unclear who is directing the work. The relationship between sovereign and general allows us to examine that contradiction, provided executive autonomy is accompanied by limits and accountability.
The relationship between Sun Tzu and micromanagement begins with a problem: giving orders without knowing the conditions in which they must be carried out. Within Sun Tzu Applied to Leadership, the comparison makes it possible to examine the division of decisions between the board and executive management, not to place the CEO above all control.
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 paying attention to the circumstances. Section 17 links the general's ability to 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. Transferring it to the company does not prove that every board question is interference or that every executive decision must be accepted.
The analogy also does not establish legal competences. An ancient sovereign is not the same as a board, a board of directors, or a group of investors. What is proposed 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 through 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.
Agreeing what is decided, what is consulted, and what is reviewed
A comprehensible delegation should describe the expected outcome and the room available to achieve it. "Improve the service" leaves open questions. A more precise formulation identifies what problem must be solved, what resources are authorised, and what conditions cannot be changed without a new decision.
As an organisational proposal, it is advisable to separate the team's day-to-day decisions from those that change the commitment undertaken. Ordering tasks within an approved scope may be delegated; changing that scope requires the agreed procedure. The limits must be known in advance, not appear later when a solution displeases the person supervising.
Informing, consulting, and requesting authorisation are not synonyms either. A manager may communicate a decision they were empowered to make. Turning every communication into a pending approval in practice cancels that room for judgement. Conversely, presenting a change as mere information does not make it a decision that had been delegated beforehand.
Review requires data proportionate to the question. To know the status of a delivery, it may be relevant to check what is finished, what is missing, and what is blocking progress. Reviewing every exchanged message does not necessarily answer those doubts better and adds work that must also be justified.
The executive has to set out the difficulties, including those that challenge their plan. The Five Virtues of the Business Leader offer questions about that conduct. Invoking autonomy to hide a deviation is incompatible with a 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 as soon as it is detected, without waiting for the next review. That 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 fictitious 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 queries.
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 actually requested.
The problem is not solved by asking the team for more initiative. First, it must be clarified whether that request changes the assignment. In the example, the proposals are passed to the person responsible, who explains what they would require and which delivery 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 results. The difference is that it stops introducing tasks through 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 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 wilfully disobeying 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 key question is what information the decision-maker needs. That question does not authorise the executive to blame all problems on the environment or to avoid reviewing their own choices.
If repeated delays appear without explanation, decisions outside the agreed scope, or incomplete information, it is appropriate to review how delegation is working. That review may ask for clarification, check results, and redefine limits. Temporarily reducing a margin 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 keep expectations clear without turning oversight into constant surveillance. Claiming autonomy from the board and then denying it to the team reproduces the contradiction at another level.
Check whether each manager can explain what they decide on their own, what they must consult, 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 Team Direction
