MapKAI

Day 2 of 5

Trust and the Licence to Operate

How should a company finance and protect its future?

Estimated time: 25 minutes

Today you will learn to
  • compare debt and equity constraints
  • identify liquidity pressure before it becomes a crisis
  • separate protection from speculation
  • connect trust with continued access to capital
Start Lesson

Watch the lesson

Subtitles available where provided

Chinese

The All-Green Illusion: Rethinking Compliance and Sustainability

English

Credible Management

Listen to the podcast

The Clean Checklist

01

Opening story or business situation

There was a small restaurant at the corner of an old street. It was called Anan’s Kitchen.

The restaurant was not big. It had only eight tables. At noon, it sold lunch boxes. In the evening, it served simple home-style dishes. The owner, Anan, often said, “Our restaurant depends on reputation. The food must be clean, safe, and served quickly.”

To help the staff remember this, he put a checklist on the kitchen door. The checklist had three sections: fresh ingredients, kitchen hygiene, and customer waiting time below fifteen minutes.

Before closing every day, the staff on duty had to tick each section. If all three sections had checkmarks, Anan believed the restaurant had operated well that day.

At the beginning, the checklist was useful. Someone checked the fridge temperature. Someone cleaned the oil on the floor. During the delivery rush, someone also pushed the kitchen to prepare food faster. Business became better and better. Office workers nearby liked to have lunch there. Later, Anan also won several corporate lunch orders. He then asked the kitchen to prepare three hundred more lunch boxes every day.

That was when the problems began.

One morning, the cook, Zhou, opened the fridge and noticed that the chicken delivered the previous day had a slightly sour smell. He knew that, according to the rule, the chicken should be returned. At least, it should be separated and checked by the owner. But that noon, two hundred chicken rice boxes had to be delivered to a corporate client. If the chicken was returned, the order would not be finished on time.

Zhou hesitated for a moment. He moved the box of chicken to a corner and thought, “We will not use this box now. I will deal with it tonight.” But when the lunch rush started, everyone became too busy to look at the box again. Later, a new kitchen helper did not know the situation and cut part of the chicken into the preparation tray.

When the restaurant closed that night, the “fresh ingredients” section was still ticked. Nobody wanted to write down the problem. Nobody knew whether “putting it aside for later” counted as a real issue.

In the same week, Li, who was responsible for delivery orders, also faced a problem. There were too many lunch orders, and the kitchen floor was covered with oil and water. According to the rule, if the floor became too slippery, the team should stop and clean it. Otherwise, someone could fall. But once the kitchen stopped, food preparation would slow down. Customers would complain, and the platform rating might drop.

Li looked at the floor, then looked at the fifteen-minute serving target on the wall. In the end, he only placed a “Caution: Slippery Floor” sign near the door and continued pushing the kitchen to prepare orders.

That day, a kitchen helper slipped and fell. His arm was scratched. Li asked him to take a rest and said, “It is not serious. Let’s not write an accident report today. Otherwise, the boss may stop the kitchen for another inspection.”

That night, the “kitchen hygiene” section was also ticked. The floor had already been cleaned by closing time. The checklist looked fine.

A few days later, some customers said they had stomach discomfort after eating at the restaurant. Anan’s first reaction was, “Maybe they ate something else.” Two negative reviews also appeared on the delivery platform, saying the food was not fresh. Anan asked Zhou to check the records from that day. Zhou took out the checklist. Every section had a checkmark.

So everyone said, “There is no problem on the checklist.”

But the problem did not disappear. More ingredients were placed in the fridge corner “for later.” The oil and water on the kitchen floor were mentioned every day, but nobody really stopped the work to solve it. The employee injury was not recorded. Customer complaints were not connected to ingredient batches. The restaurant still looked normal from the outside, but more and more risks were being pushed into invisible places.

At the end of the month, Anan saw that revenue was high. He planned to accept an even larger corporate lunch order. He showed the whole month’s checklist to the client and said, “You can see that we are compliant every day. Hygiene, safety, and serving speed are all under control.”

Before the client signed the contract, the market inspection officers arrived.

They did not only look at the checklist on the wall. They asked to see purchase records, fridge temperature logs, employee accident records, customer complaints, ingredient handling records, and corrective action records. Only then did Anan realize that many boxes had been ticked, but there was no evidence behind them. Nobody had written whether the chicken was returned. Nobody had recorded when the oil and water on the floor exceeded the limit. Nobody knew who handled the employee injury or whether it had been reviewed.

The inspection officers did not immediately say that the restaurant had a serious problem. They only asked one question:

“If everything was compliant, why is there no record showing what you did after problems happened?”

Anan had no answer.

That evening, the restaurant closed for the first time. A notice was placed at the entrance: Internal remediation, closed for one day.

Some employees were unhappy. Zhou said, “It is only because a few forms were not written clearly. How much money do we lose by closing for one day?” Li also said, “If we stop to clean the floor every time there is oil, we can never finish the lunch rush.”

Anan sat beside an empty table and looked at the clean checklist that had been ticked every day. He suddenly understood the real issue. The problem was not that the restaurant had no rules. The problem was that the rules had become decoration. Everyone cared about whether the restaurant could stay open, serve food on time, and protect revenue. But nobody cared enough about whether exceptions were truly handled after they appeared.

The next day, Anan took down the old checklist and replaced it with a new one.

The new form no longer had only three checkmarks. Every exception had to record five things: where the problem came from; when it was found; who was responsible for handling it; who reviewed the result; and when the next step had to be completed.

If an ingredient had a strange smell, staff could not simply write “noted.” They had to record whether it was separated, returned, or connected to any dishes already sold. If the kitchen floor exceeded the safety limit, the team could not only put up a warning sign. The affected area had to stop working, be cleaned, and then reopen after confirmation. If an employee was injured, the cause had to be recorded, and the team had to check whether the process itself had a problem. If customers complained about stomach discomfort, the complaint had to be traced back to the ingredient batch, the temperature record, and the dishes sold that day.

Anan also added a new rule. If the same type of problem happened three times in one week, the kitchen had to reduce orders. If food safety could not be confirmed, the related dishes had to stop being sold. If corporate lunch orders made safety checks impossible, the restaurant would rather reject the order than use “we were too busy” as an excuse.

During the first week, the new checklist looked bad. There were many red records. Lunch service became slower. The delivery rating also dropped for a short time. Anan lost one large client, and revenue was lower than the previous month.

But from then on, the restaurant’s records were no longer just a page of neat checkmarks. The table finally showed where problems had happened, who handled them, and when they needed to be reviewed.

Ingredients in the fridge had batch records. Employees knew which situations had to be reported. Customer complaints could be traced back to purchase and preparation records from the same day. Oil and water on the kitchen floor were no longer handled only by reminders. Someone had to take responsibility, and someone else had to review the result. A few weeks later, the market inspection officers came again. Anan did not show them a perfect form full of checkmarks. Instead, he showed them a stack of records with red marks, yellow marks, and completed corrective actions.

After reading the records, the inspection officers said, “This record does not look perfect, but it is credible.”

Later, Anan did not remove the sentence “clean, safe, and served quickly” from the kitchen door. He still kept it there. But next to it, he added another sentence:

“Real compliance is not about ticking every box every day. It is about whether the restaurant is willing to stop and handle problems when they appear.”

Anan’s Kitchen slowly recovered its business. Some customers noticed that food was not served as quickly as before, but they felt safer. Corporate clients were also willing to continue working with the restaurant, because Anan could explain where each dish came from, who was responsible when something went wrong, when it was corrected, and who confirmed the correction.

Many years later, when Anan looked back at that remediation, he realized that what he had protected was not a checklist. It was an operating capability. When revenue, speed, and safety were in conflict, the restaurant could not pretend that nothing had happened. It had to make bad news visible, write down responsibility, and handle problems before they became accidents.

Later, Anan called this capability Compliance. Connecting ingredient batches, temperature records, employee accidents, customer complaints, and corrective actions into one evidence chain was called Sustainability Reporting. And when revenue would be affected, but the restaurant still decided to close, reduce orders, and solve the problem first, this was called Financial Leadership.

A truly reliable small restaurant is not a restaurant that never has red lights. It is a restaurant that knows where to stop, what to check, who is responsible, and when it can open again when a red light appears.

02

The decision problem

03

Core concepts

Financing

compare debt and equity constraints

Why it matters

Which promise gives your organisation its licence to operate?

Liquidity

identify liquidity pressure before it becomes a crisis

Why it matters

What evidence shows that this promise is kept when pressure rises?

Risk

separate protection from speculation

Why it matters

Which promise gives your organisation its licence to operate?

Hedging

connect trust with continued access to capital

Why it matters

What evidence shows that this promise is kept when pressure rises?

04

Visual framework

01Begin with a business situation
02Reveal the financial logic
03Connect the idea to a practical framework
04Apply it through reflection and decision questions

Five-step knowledge chain | Taking apart an “all-green” report

Clarify what the company promised → trace how failure formed → test whether controls truly worked → trace every public data point to its source → let bad news change decisions.

01Put promises and non-negotiable boundaries on the table

Law, regulation, and public commitments to customers, employees, communities, or the environment must become observable boundaries. Also examine whether delivery, cost, bonus, or growth pressure pushes people into bypassing them.

02Trace an exception backwards through the behaviour chain

Do not stop at who made a mistake. Trace pressure, behaviour, bypassed controls, delayed or beautified information, and resulting harm. A mature review finds the earliest point where harm could have been stopped.

03Test whether a control exists or operates

A policy, training, or a live system proves only that a control was designed. Design effectiveness asks whether it could detect and handle the problem; operating effectiveness asks whether it is consistently performed and exceptions are recorded, investigated, escalated, and closed.

04Return every ESG claim to its evidence chain

A disclosure must trace to materiality, value-chain location, data definition and baseline, recorder, reviewer, target, and explanation of change. Double materiality asks both how the company affects people and environment, and how those effects return to cash, financing, reputation, and continuity.

05Give bad news the right to change the operating pace

Pausing a high-risk customer, retesting, or fixing harm can hurt short-term results. Credible leadership specifies which threshold escalates, who can stop or slow business, when remediation is due, and who verifies closure. If risk capacity is exhausted, growth speed must be adjustable.

05

Practical example

Business example

Make promises, data sources, customer communication, and AI-use boundaries explicit, so growth is not built on trust you cannot keep.

06

Common misunderstanding

07

Key takeaways

  • compare debt and equity constraints
  • identify liquidity pressure before it becomes a crisis
  • separate protection from speculation
  • connect trust with continued access to capital

08

Knowledge check

How should a company finance and protect its future?

09

Reference notes

  1. COSO (2017). Enterprise Risk Management: Integrating with Strategy and Performance.

    COSO enterprise-risk-management framework.

    Supports the relationship among strategy, performance, culture, information, review, and control operation.

  2. Ewing, Jack (2017). “Engineering a Deception.” The New York Times.

    Volkswagen diesel-scandal case material.

    Supports analysis of impossible targets, engineering authority, upward information, and challenge failure.

  3. ING (2018). Wwft settlement material.

    Dutch anti-money-laundering compliance settlement case.

    Supports customer due diligence, transaction monitoring, alert backlog, investigation, escalation, and management accountability.

  4. De Micco et al. (2021). Estra case.

    Sustainability-reporting case study.

    Supports reporting as a management process for data sources, responsibility, and cross-functional learning.

  5. KPMG (2025). ESRS: learnings to progress.

    Observation of first-wave Dutch CSRD reporting practice.

    Supports DMA, IROs, value-chain boundaries, metrics, targets, and disclosure connectivity; it is implementation observation, not the ESRS standard itself.