Sun Tzu and Human Resources: Care Without Paternalism

Treating employees as “beloved children” is not a literal model for an employment relationship. The image in the treatise makes it possible to ask how care and coordination coexist, but a business adaptation must recognize people’s autonomy and make expectations explicit.

Applying Sun Tzu to human resources requires distinguishing care for the team from demands for personal loyalty. Within Sun Tzu Applied to Leadership, the question is how to organize support, responsibilities, and follow-up without infantilizing the people who work there or promising that any one practice will be enough to retain them.

What “beloved children” means in the treatise

The image appears in chapter 10, section 25 of Lionel Giles’s English translation. The text compares caring for soldiers with caring for one’s own children and links it to accompanying the general even to death. “Beloved children” refers here to that image; no specific Spanish edition is being cited.

Section 26 adds a warning: affection does not solve the inability to enforce instructions and command the army. The commentary on the six terrains of chapter 10 places these passages alongside the responsibility of command. The relationship described remains military.

A workplace adaptation must explicitly change that framework. Employees are adults with their own judgment; receiving support should not create a debt of personal obedience. Nor should disagreement be interpreted as ingratitude, or leaving the company as a family betrayal.

What is useful in the comparison is a management question: how can people be cared for while shared work remains clear? The approach proposed here uses expectations, resources, and review of agreements. It does not transfer the sacrificial demands of the ancient passage into the workplace.

Care, clarify expectations, and apply fair criteria

Care can begin by checking what is actually being asked. A task needs a recognizable result, available resources, and a deadline that can be discussed if conditions change. Expressions such as “take ownership” or “show more attitude” do not clarify what is missing or how to know whether it has been resolved.

Attention to physical and mental well-being should also not be limited to asking whether everything is fine. In this approach, the manager reviews workloads, interruptions, and opportunities for rest, and addresses the difficulties that are communicated. There is no need to diagnose anyone or demand intimate explanations in order to hear an organizational problem.

Support should match the difficulty observed. What may be missing is an explanation, a tool, access to information, or uninterrupted time. Before attributing an error to lack of interest, it is worth checking those conditions. Listening to the person’s explanation does not mean accepting any conclusion, but it does prevent deciding before hearing their account.

Here, discipline is understood as coordination through clear agreements. An incident should have an owner; an unfinished task should not be recorded as complete. When something fails, the facts are reviewed and a correction is agreed. There is no need to turn that review into a global assessment of the person or a public humiliation.

Fair treatment also does not require identical responses to different circumstances. Someone who is still learning may need support that another person no longer needs. Consistency consists in explaining the criterion used and reviewing whether it fits the work, without reserving exceptions for those who are closer to management.

The five virtues of the business leader make it possible to connect this approach with the decisions of the person in charge. Benevolence does not replace clarity, and discipline does not justify arbitrary harshness. Both should be visible in what the manager does, even when their own actions contributed to the problem.

Agreed follow-up leaves room to execute. The analysis of how to avoid managerial micromanagement distinguishes reviewing results from replacing every decision. Asking for autonomy while demanding approval for every step creates contradictory expectations, even when presented as a way of helping.

An example of correction without punishment or humiliation

Imagine a fictional support team. A professional has sent several incomplete responses to customer inquiries. Their manager reviews the cases and arranges a private conversation. The starting point is the specific responses and the missing information, not the claim that the person lacks commitment.

As they review the procedure together, they discover that there are two different sets of instructions and that some inquiries require a technical confirmation that is hard to obtain. In addition, the professional handles interruptions that are not included in the plan. These facts do not eliminate the need to correct the responses; they make clear what has to change in order to do so.

In the example, they agree on a single current instruction, identify who will resolve the technical question, and set aside time to review the first cases. The manager removes a secondary task instead of adding learning onto an unchanged workload. The professional agrees to flag inquiries they cannot complete with the information available.

The expectation is made explicit: an inquiry is not closed while the necessary information to answer it is still missing. If it depends on someone else, that blockage is recorded. This distinguishes unfinished work from noncompliance and avoids making the only way to appear productive the closing of incomplete cases.

The follow-up review uses a sample of responses to check whether the criterion has been understood and whether difficulties continue. It does not publicly rank people or assume that zero complaints equals correct work. It also checks whether the instruction remains ambiguous and whether the promised support was available.

If the problem continues, what needs examining is which part of the agreement is not working, instead of repeating the same warning with greater severity. The risks of deciding in anger and ego help distinguish the discomfort of the person in charge from the reasons for a management decision.

The case describes a way to review work, not a guaranteed outcome. Even if the responses improve, that does not prove the professional will remain with the company. The decision to stay may depend on issues that this intervention does not address, and it should be possible to express that without turning the support received into an obligation to remain.

To evaluate the practice, it is worth asking what changed in the conditions, which expectations were made clear, and which difficulties remain open. Team continuity is a broader question. It is not demonstrated by an anecdote, nor is it explained solely by the manager’s kindness.

Before asking for more commitment, check whether the expected result is understood and whether there are means to achieve it. Care also requires correcting organizational decisions, without treating employees as personal dependents.

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