How to report problems to a head office in Japan or Korea

Why urgent news loses its significance before it reaches the boss

At a Polish plant, a supplier reports a delay in components. The coordinator knows the shipment may be delayed by four days, but first wants to “have all the data”. His boss adds that the situation is “under control”, and head office is told only of a minor risk. Two weeks later the delay is a fact, and the board asks why nobody warned them. Psychology has long recognised a similar mechanism: Rosen and Tesser described the so-called MUM effect, a reluctance to pass on unwelcome information. Elizabeth Morrison, for her part, showed that employee silence also depends on relationships with managers and on the consequences people expect from speaking up. This is not a “typically Asian” phenomenon. It occurs in a Polish company, an American start-up and an international hospital alike. So a good reporting system does not wait for people to stop being afraid. It lets them report a problem early enough, even if they don’t yet have all the data.

There is no single “Asian head office”

Japan and South Korea have different business traditions, and two companies from Tokyo can differ more than their branches in different countries do. In one organisation, the response to an alert will be an immediate conference call; in another, people expect material in advance and a conversation with a specific person. Don’t assume that your manager’s nationality tells you everything about how they work. When you start working together, ask: “Which incidents should we escalate within an hour, and which can go in the daily report?”, “Do you prefer a short phone call before a written report?” and “Who can approve additional costs?” Research on employee behaviour in different cultural contexts reminds us that hierarchy, trust and the quality of relationships matter, but it does not allow us to predict how a particular person will react. You can show respect by carefully preparing the data, being punctual and avoiding assigning blame in public. What you must not do, in the name of “respect for culture”, is keep quiet about a safety problem or a breach of the law.

The four elements of a report: fact, impact, uncertainty, decision

An effective report does not open with a long account of why the situation is complicated. The first sentence reads: “We have confirmed a delay in the delivery of component X. The assembly deadline is at risk.” Then give the fact with its date and source, the expected impact and what you don’t yet know. For example: “The supplier has confirmed shipment no earlier than 18 June. Without the part, we won’t complete testing on 20 June. We expect a delay of two to four days, but we are waiting for the tracking number.” Only now come the options: postpone acceptance, or bring in a substitute supplier at a stated cost. Finally, the question: “Which option shall we go with by 3 p.m.?” The dates and figures in this example are illustrative. What matters is a structure in which nobody has to dig the bad news out of five paragraphs of reassuring statements. It is clear what has not yet been established and what the recipient needs to decide.

Warn your manager in advance, or report the problem straight away?

Sometimes a good solution is to give your manager a brief heads-up before a wider meeting. It allows you to explain the context, prepare the data and avoid unnecessary public embarrassment. It is not, however, an excuse for delaying a formal alert. When the issue involves a threat to life, a safety incident, a breach of the law, data protection or a contractual obligation, you must follow the reporting procedure, regardless of anyone’s preferred conversational style. For an ordinary organisational problem, you might say: “I’d like to give you advance warning of a risk before tomorrow’s review. I’ll send the formal report later today.” On a critical matter: “In line with the procedure, we have raised the alert, and I’m now presenting the latest data.” You show respect by giving your counterpart a clear picture of the situation so that they are not caught off guard at the last minute. Hiding urgency behind a veneer of politeness also makes it harder for them to meet their own obligations.

A polite “we understand” is not approval of a cost

After the problem has been presented, head office replies: “Thank you for the information. Please investigate.” The branch concludes that it can order more expensive transport. In fact, the message is only a request for analysis. To avoid a similar mistake, record three statuses separately: information received, analysis requested, decision approved. If in doubt, ask a single question: “Can you confirm the choice of option B and a budget up to a specified amount, or are we only to compare the options for now?” After the meeting, send a concise summary with the person responsible for the action, the deadline and what was decided. If the other person says nothing, don’t automatically interpret this as either agreement or refusal. Ask when you will receive a decision and who can make it in that person’s absence. This habit is useful in any company where responsibility is divided between a branch and head office.

The manager’s reaction will determine the next report

If the first employee to report a problem hears “Why only now, and whose fault is it?”, next time people may wait longer. It is better to start with: “Thank you for flagging the risk. What do we know, and what support do we need?” This does not mean giving up on assessing the causes. Once the situation has been contained, both the error and the early-warning process need to be examined. It is important to distinguish responsibility for causing a problem from reporting it in time. A good practice is a short meeting once the incident has been closed: what worked in the flow of information, what delayed the decision and how we will recognise a similar risk earlier. A manager can also lead by example by admitting: “I waited too long to escalate, and I’m going to change how we report.” Safe communication does not mean an absence of accountability. It means that the true message reaches the people responsible while there is still time to act.

When reporting to head office, what counts is passing on confirmed facts on time, describing uncertainty honestly and making a clear request for a decision. Learn the habits of the specific organisation, not imagined national traits. Respect for the recipient and rapid escalation can go hand in hand, as long as both sides distinguish between receiving information, requesting analysis and formally approving an action.

How Em helps you rehearse delivering bad news

A plant manager knows that a delay puts a contract at risk, but is worried that his manager at head office will read the message as a sign that he has lost control of the situation. He describes the circumstances to Em, without any confidential data, and asks for help in structuring the message. First, he practises an opening sentence that names the risk straight away. Then he separates the confirmed information from the hypotheses and prepares two options for further action. Em can play a demanding counterpart who asks “Why didn’t we know sooner?” or replies only “Look into it.” He then practises a calm explanation and repeats his request for a decision and a deadline. If he has access to a specific colleague’s communication profile and is permitted to use it, he can tailor the form of the message so that it is clear to that person. After the exercise, he has a ready-made introduction to the report, a list of questions and a clear ending. The safety procedure and the actual decision remain with the organisation.