The Plant Fire, the Weak Email and the WhatsApp Leak

The email fails most of the 7 Cs. It is not concrete: it gives no revised delivery date, no explanation of which line was affected, and no recovery plan. It is not complete: it offers no options, no contact point and no next update. It is not considerate: it does not acknowledge Nexa’s production schedule or the impact on Nexa’s own customers. It is not correct: the subject 'Delay' is too vague for a formal customer record. It is only superficially courteous; 'Sorry for the inconvenience' is generic and does not match the seriousness of a three-week delay. It is concise, but concision has become omission.

On channel choice, email is useful for a written record, but it is a lean channel for bad news of this magnitude. Farah should have telephoned Nexa’s procurement head before or immediately after sending the email, then followed up in writing. The email should have had a specific subject, the facts, the revised date, the mitigation steps, options such as partial shipment, a named contact and a commitment to update by a stated time. A phone call would have allowed Farah to hear Nexa’s concerns and correct misinformation before it spread.

Farah should not send the substantive bad news to the CEO on WhatsApp. WhatsApp is informal, easily forwarded, weak on verification and unsuitable for confidential commercial information. It may be acceptable to use WhatsApp only to ask for a short call, but the message itself should be delivered by phone and confirmed by email.

The message should follow a bad-news structure. First, acknowledge the CEO’s concern and thank him for calling. Second, state the facts clearly: the fire, the affected line, the confirmed three-week delay and the revised date. Third, apologise specifically for the uncertainty and for the way the news reached him. Fourth, explain the remedy: what Precision is doing, what capacity is available, whether a partial shipment is possible, and what compensation or priority treatment it can offer. Fifth, give a single point of contact and a fixed time for the next update. Farah should also correct the WhatsApp rumour directly: the plant is not shut and the order is not cancelled. She should avoid blaming the junior employee in the CEO call; the internal issue is for Precision to handle.

The internal memo should be short, factual and issued quickly. It should state what is known and what is not known, the customer impact, the revised production plan, who is authorised to speak to customers and the media, and when the next update will come. It should tell staff not to speculate or post operational information in external groups. It should avoid blaming individuals in writing and should give supervisors a script for answering questions.

The grapevine thrives in an information vacuum. Precision should fill that vacuum with regular formal updates, correct false information quickly, and use supervisors and team meetings as trusted channels. The junior employee’s WhatsApp post was a confidentiality breach, but a public scapegoating will only drive communication underground. The company should remind staff of confidentiality rules, explain why operational updates can damage customer confidence, and designate a single source of truth. Farah should also monitor the supplier group and ask the group administrator to remove the misleading post where possible.