Sun Tzu in a Business Crisis: the Limits of Mortal Ground

A struggling company needs to understand its options, not eliminate every exit to force a reaction. The mortal ground metaphor can help examine urgency and coordination, but it stops being useful when it replaces diagnosis or justifies extreme pressure.

Linking Sun Tzu to a business crisis requires separating a military situation from an economic and organizational problem. Within Sun Tzu Applied to Business, mortal ground is used here as a metaphor that must be examined critically. This text does not offer financial or insolvency advice, nor a method for avoiding bankruptcy.

What mortal ground describes, and what it does not explain about a company

In Chapter 11, Lionel Giles’s translation describes a situation in which the army must fight without delay to avoid destruction. That context is part of the nine situations in Chapter 11. Bringing it into a company changes both the danger and the options available.

The possible similarity lies in urgency: some decisions cannot be postponed indefinitely. But it does not follow that closing off alternatives improves the situation. In an organization, preserving information, capacity for review, and access to help may be exactly what makes it possible to assess options that had not yet been considered.

It is important to distinguish a work stoppage from a difficulty meeting financial obligations. Both may coincide, but they are not explained in the same way. Resolving an operational issue does not prove the company can remain viable; arranging financial records does not automatically repair a service that has been interrupted.

The phrase “we are on the brink of bankruptcy” does not replace that distinction. A real assessment requires documentation and review by accounting, financial, and legal professionals. The treatise cannot determine a company’s situation or what actions apply in a specific jurisdiction.

Sun Tzu’s vocabulary in business helps to recognise the shift in meaning. “Survival” can express concern about continuity, but it does not permit treating workers as expendable resources or presenting any management decision as inevitable.

A fictional case: blocked deliveries and uncertain receivables

Imagine a digital services company managing projects for several clients. Some deliveries have been delayed, there are unpaid invoices outstanding, and management does not share a common view of the work left to do. Staff are asked to speed everything up at once. The situation allows for an analysis of coordination problems, but it is not enough to diagnose solvency.

The first visible problem is the mixing together of different situations. One project may be awaiting internal review; another, waiting for material from the client; a third, finished but without confirmation of receipt. Grouping them under the label “late work” prevents recognition of what the team can actually do in each case.

In the example, management assembles a shared log of deliveries, owners, and blockers. Each entry distinguishes confirmed information from the estimated date. This change does not generate revenue by itself. It makes it possible to see what information is missing and prevents two people from working with incompatible commitments.

Financial documentation is reviewed separately with professionals. An issued invoice, an expected payment, and money already received do not describe the same fact. Confusing them in an operational meeting could create an impression of availability that does not match what has been confirmed.

For the team, priority is expressed through verifiable tasks: finishing a pending review, obtaining clarification, or resolving an issue that is blocking a delivery. “Saving the company” may describe a shared concern, but it does not say who must do what or what result allows a task to be closed.

Suppose one person receives two urgent requests that cannot be completed at the same time. Coordination requires someone to resolve that conflict and communicate which commitment is changing. Sending both requests back with instructions to try harder does not change the time or resources available.

The information each client receives about their delivery is also reviewed. Communicating an unconfirmed date to reduce immediate pressure would create an additional promise. In the fictional case, the alternative is to distinguish between what is finished, what is pending, and what still has no reliable forecast.

Expense review needs a different kind of verification. This example does not recommend specific cuts. An item with no immediate use for a delivery may support security, maintenance, or continuity. Deciding about it requires examining its function and consequences, not eliminating it simply because it seems unrelated to the urgency of the day.

The assessment must keep different outcomes open. Clearing blockers could improve deliveries and still leave the economic problem unresolved. It could also show that certain promises cannot be met with the resources available. Organizational improvement is an identifiable outcome, not proof of financial recovery.

Coordinating without manufacturing a situation of despair

Communicating urgency requires specifying what is happening, what is known, and what decision must be made. It does not require threatening, hiding alternatives, or attributing any unfavourable result to the staff’s lack of sacrifice. Uncertainty should be communicable without automatically becoming an accusation of disloyalty.

A brief review of the work can focus on changes and blockers, rather than demanding ongoing explanations for every minute. In the case described, the criterion is that an update should allow a dependency to be resolved or a forecast to be corrected. If it only adds reports, it consumes capacity without clarifying any decision.

Management needs to hear data that contradicts its plan. If a delivery requires a review that has not yet been done, calling it finished does not reduce the work remaining. Cooperation also means making those limits visible before taking on new commitments.

Another temptation would be to seek sales through indiscriminate price cuts. The toll of price wars addresses that issue separately. No commercial policy is proposed here: more activity does not by itself prove that the cause of the crisis has been corrected.

Nor can one simply copy the strategy of a startup facing a giant. Exploring a new need and managing immediate obligations are different problems. A promising experiment does not automatically solve commitments that already exist.

Any concrete decision about financing, payments, contracts, or continuity requires professional review of the situation. The metaphor stops being useful when it delays that consultation or makes perseverance the only acceptable response. Keeping the ability to examine alternatives is different from giving up at the first difficulty.

If you are facing real difficulties meeting obligations, seek professional advice as soon as possible. A strategic reading can help organise questions, but it does not determine whether a business is viable or what financial or legal measures apply.

View all articles in Sun Tzu in Business: Resources, Competition, and Decisions