Treating employees as ‘beloved children’ is not a literal model for an employment relationship. The image in the treatise lets us 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 those who work there 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 quoted.
Section 26 adds a warning: affection does not solve an 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 family betrayal.
What is useful in the comparison is a management question: how do you look after people while still making shared work understandable? The approach proposed here uses expectations, resources and review of agreements. It does not bring the sacrifice demanded by the ancient passage into 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 outcome, available resources and a deadline that can be discussed if its conditions change. Phrases 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 wellbeing should not be limited to asking whether everything is alright. In this approach, the manager reviews workloads, interruptions and opportunities for rest, and addresses difficulties that are raised. They do not need to diagnose anyone or demand intimate explanations in order to hear about an organisational problem.
Support should match the difficulty observed. There may be a missing explanation, a tool, access to information, or time free from interruptions. Before attributing an error to lack of interest, it is worth checking those conditions. Listening to the person’s explanation does not mean accepting every conclusion, but it avoids deciding before hearing their side.
Discipline here means coordination through clear agreements. An issue should have an owner; an incomplete task should not be recorded as finished. When something goes wrong, the fact is 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 either. Someone who is learning may need support that another person no longer needs. Consistency lies in explaining the criterion applied and checking whether it fits the work, without reserving exceptions for those closest to management.
The five virtues of the business leader allow this approach to be linked 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.
Agreed follow-up leaves room to get on with the work. The analysis of how to avoid managerial micromanagement distinguishes reviewing results from replacing every decision. Asking for autonomy while requiring permission for every step creates contradictory expectations, even if it is presented as a way of helping.
An example of correction without punishment or humiliation
Imagine a fictitious support team. One professional has sent several incomplete replies to customer enquiries. Their manager reviews the cases and arranges a private conversation. The starting point is the specific replies and the missing information, not an assertion that the person lacks commitment.
When they review the process together, they discover that there are two different sets of instructions and that some enquiries require a technical confirmation that is difficult 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 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 to an unchanged workload. The professional agrees to flag enquiries that they cannot complete with the information available.
The expectation is made explicit: an enquiry is not closed while the necessary information to answer it is missing. If it depends on another person, that blockage is recorded. In this way, pending work is distinguished from non-compliance and the only way to seem to make progress is not to close incomplete cases.
The later review uses a sample of replies to check whether the criterion has been understood and whether difficulties continue. It does not publicly rank people or assume that no complaints means the work is correct. 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, rather than repeating the same warning more harshly. The risks of deciding with anger and ego help to distinguish a 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 continue may depend on issues this intervention does not address, and it should 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 made clear and what difficulties remain open. Team continuity is a broader question. It is not shown by an anecdote, nor is it explained solely by the manager’s kindness.
Before asking for more commitment, check whether the expected outcome is understood and whether there are the means to achieve it. Care also requires correcting organisational decisions, without treating employees as personal dependants.
View all articles in Leadership with Sun Tzu: how to review a team’s direction
