Treating employees as “beloved children” is not a literal model of workplace relations. The image in the treatise makes it possible to ask how care and coordination coexist, but a business adaptation must recognise 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 organise support, responsibilities, and follow-up without infantilising workers or promising that any one practice will be enough to retain them.
What “beloved children” means within 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 responsibilities of command. The relationship described remains military.
A workplace adaptation must expressly change that framework. Employees are adults with their own judgement; receiving support should not create a debt of personal obedience. Nor should a disagreement be interpreted as ingratitude, or leaving the company as a family betrayal.
What is useful in the comparison is a management question: how do you care for people while also making shared work understandable? The answer proposed here uses expectations, resources, and review of agreements. It does not transfer the sacrifice demanded in the ancient passage to the workplace.
Caring, clarifying expectations, and applying fair criteria
Care can begin by checking what is actually being asked for. A task needs a recognisable result, available resources, and a deadline that can be discussed if conditions change. Phrases like “take ownership” or “show more initiative” do not make clear what is missing or how to know whether it has been resolved.
Attention to physical and mental wellbeing should not be limited to asking whether everything is okay. In this approach, the manager reviews workloads, interruptions, and opportunities for rest, and addresses the difficulties that are communicated. They do not need to diagnose anyone or demand intimate explanations in order to listen to an organisational problem.
Support should match the difficulty observed. There may be a missing 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 side.
Here, discipline is understood as coordination through clear agreements. An incident should have someone responsible for it; an unfinished task should not be recorded as complete. When something goes wrong, the facts are reviewed and a correction agreed. There is no need to turn that review into a general judgement of the person or a public humiliation.
Fair treatment does not require identical responses to different circumstances. A person who is learning may need support that another person no longer needs. Consistency lies in explaining the criterion being applied and checking whether it fits the work, without reserving exceptions for those who are closer to management.
The five virtues of the business leader help 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 get the work done. The analysis of how to avoid management micromanagement distinguishes reviewing results from replacing every decision. Asking for autonomy and demanding permission for every step creates contradictory expectations, even when it is 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 replies to customer queries. Their manager reviews the cases and arranges a private conversation. The starting point is the specific replies 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 instructions and that some queries require technical confirmation that is hard to obtain. In addition, the professional handles interruptions that are not included in the schedule. These facts do not remove the need to correct the replies; they clarify what must 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 the learning on top of an unchanged workload. The professional agrees to flag queries that cannot be completed with the information available.
The expectation is made explicit: a query is not closed while the information needed to answer it is missing. If it depends on someone else, that blockage is recorded. This distinguishes unfinished work from non-compliance and avoids making the only way to appear productive be closing incomplete cases.
The later review uses a sample of replies to check whether the criterion has been understood and whether the difficulties continue. It does not publicly rank people or assume that no complaints equals correct work. It also checks whether the instruction is still ambiguous and whether the promised support was available.
If the problem continues, the part of the agreement that is not working needs to be examined rather than repeating the same warning more harshly. The risks of deciding with anger and ego help distinguish the manager’s discomfort from the reasons for a management decision.
The case describes a way of reviewing work, not a guaranteed outcome. Even if the replies improve, that does not prove that the professional will stay with the company. The decision to remain may depend on issues this intervention does not address, and it must be possible to state that without turning the support received into an obligation to stay.
To assess the practice, it is worth asking what changed in the conditions, which expectations became clear, and which difficulties remain open. Team continuity is a broader issue. It is not proven by an anecdote, nor 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. Caring also means correcting organisational decisions, without treating employees as personal dependants.
View all articles in Leadership with Sun Tzu: how to review a team’s direction
