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 demanding personal loyalty. Within Sun Tzu Applied to Leadership, the question is how to organise support, responsibilities and follow-up without infantilising the people who work there or promising that a single practice will be enough to retain them.
What does "beloved children" mean 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 with accompanying the general even to death. "Beloved children" refers here to that image; no specific Spanish edition is being quoted.
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 disagreement be read as ingratitude, or leaving the company as a family betrayal.
What is useful in the comparison is a management question: how do you look after 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 by the ancient passage into the workplace.
Care, clarify expectations and apply fair criteria
Care can begin by checking what is actually being asked for. A task needs a recognisable outcome, available means and a deadline that can be discussed if conditions change. Expressions such as "take charge" 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 proposal, the manager reviews workloads, interruptions and opportunities for rest, and addresses difficulties that are reported. 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 disinterest, it is worth checking those conditions. Listening to the person's explanation does not mean accepting any conclusion, but it does avoid deciding before hearing their account.
Here, discipline is understood as coordination through clear agreements. An incident should have someone responsible; an incomplete task should not be recorded as finished. When something fails, the fact is reviewed and a correction is agreed. There is no need to turn that review into a global judgement of the person or a public humiliation.
Fair treatment also does not require identical responses to different circumstances. A person who is learning may need support that another no longer needs. Consistency lies in explaining the criterion applied and checking whether it matches 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 proposal with the decisions of the person in charge. Benevolence does not replace clarity, and discipline does not justify arbitrary harshness. Both should be recognisable in what the manager does, even when their own actions contributed to the problem.
An agreed follow-up leaves room to get the work done. The analysis of how to avoid managerial micromanagement distinguishes reviewing results from replacing every decision. Asking for autonomy and requiring permission for every step produces 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 responses to customer queries. 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.
When they review the procedure together, they discover that there are two different instructions and that some queries require a 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 responses; they specify what must change in order to do so.
In the example, they agree on a single current instruction, identify who will resolve the technical query 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 commits to flagging queries that cannot be completed with the information available.
The expectation is made explicit: a query is not closed while the necessary information to answer it is missing. If it depends on someone else, that blockage is logged. This distinguishes pending work from non-compliance and avoids making the only way to appear to be making progress the closing of incomplete cases.
The later review uses a sample of responses to check whether the criterion has been understood and whether the difficulties continue. It does not publicly rank people, nor does it 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, it is necessary to examine which part of the agreement is not working, instead of repeating the same warning more harshly. The risks of deciding in anger and ego help to distinguish the discomfort of the person in charge from the reasons for a management decision.
The case describes a way of reviewing work, not a guaranteed outcome. Even if the responses improve, that does not prove that the professional will stay with the company. The decision to continue may depend on issues that this intervention does not address, and it must be possible to express that without turning the support received into an obligation to remain.
To assess the practice, it is worth asking what changed in the conditions, what expectations were clarified and what difficulties remain open. Team continuity is a broader issue. It is not proven by an anecdote, nor explained solely by the kindness of the person in charge.
Before asking for more commitment, check whether the expected result is understood and whether the means to achieve it exist. Care also requires correcting organisational decisions, without treating employees as personal dependants.
View all articles in Leadership with Sun Tzu: How to Review Team Direction
