Sun Tzu and Micromanagement: Executive Autonomy with Oversight

Delegating responsibility while continuing to decide every step leaves unclear who is directing the work. The relationship between sovereign and general allows this contradiction to be examined, provided that executive autonomy is accompanied by limits and accountability.

The relationship between Sun Tzu and micromanagement begins with a problem: issuing 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 how decisions are divided between the board and the executive team, not to place the CEO beyond all oversight.

The sovereign and the general: what the passage questions

In chapter 3, sections 12 to 15 of Lionel Giles' translation, the sovereign can harm the army by ordering movements it cannot carry out, running 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 detached from the situation. Transferring it to a company does not show that every board question is interference, nor that every executive decision must be accepted.

The analogy does not establish legal powers either. An ancient sovereign is not the same as a board, a board of directors, or a group of investors. Here, the aim 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 the 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 clear delegation should set out the expected outcome and the room available to achieve it. “Improve the service” leaves questions open. A more precise formulation identifies which problem must be solved, which resources are authorised, and which conditions cannot be changed without a new decision.

As an organisational proposal, it is wise to separate the team's day-to-day decisions from those that alter the commitment assumed. Ordering tasks within an approved scope may be delegated; changing that scope requires the agreed procedure. The limits need to be known in advance, not appear afterwards when a solution displeases the person overseeing it.

Informing, consulting and seeking authorisation are not synonyms either. A manager may communicate a decision they were entitled to make. Turning every communication into a pending approval effectively removes that room for manoeuvre. Conversely, presenting a change as mere information does not turn it into a decision that had already been delegated.

Review needs data proportionate to the question. To understand the state 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 any better and adds work that also has to be justified.

The executive must set out the difficulties, including those that challenge the plan. The five virtues of the business leader raises questions about that behaviour. 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. This distinguishes a necessary alert from a routine check on every step. The aim is to resolve the exception, not to return every decision to the board.

An example of oversight that does not replace the team

Let us imagine a fictional company deciding to renew its customer service system. The board approves the objective and the available resources. The executive team 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, 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 brief. In the example, the proposals are passed to the person in charge, 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 the results. The difference is that it stops introducing tasks through parallel channels while holding the executive accountable for a plan it has already altered. The management team, in turn, cannot dismiss every proposal on the grounds that it belongs to the technical detail: it must explain its impact 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 proceeding. Changing the sequence for that reason is not the same as wilfully ignoring an instruction; it requires showing which assumption is no longer being met.

Attention to context links with the six grounds in chapter 10. In this adaptation, the point is to ask what information the decision-maker needs. That question does not authorise the executive to blame all problems on the environment, nor 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 can request clarification, check outcomes, and redefine limits. Temporarily reducing room for manoeuvre 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 oversight into constant surveillance. Demanding 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 for themselves, what they must consult on, and how they report the outcome. If the answers differ, the division of responsibilities needs clarifying before more autonomy is demanded.

View all articles in Leadership with Sun Tzu: how to review a team’s direction