Our Take
The medium of bad news matters less than the access to support afterward; a 6 a.m. email is cruel because the recipient is alone, not because it is written.
Why it matters
Remote and distributed teams now outnumber co-located ones. The phone-call default assumes everyone works in the same building. HR practitioners managing geographically dispersed workforces face a genuine design problem: how to deliver hard news fairly when synchronous, in-person contact is not an option.
Do this week
People leaders: audit your termination and layoff notification process this week to ensure employees have immediate access to HR support and your manager within 30 minutes of learning of the cut, regardless of delivery method.
Pochettino's email and the Oracle pattern
U.S. men's national soccer team coach Mauricio Pochettino announced the 26-player roster for the 2026 World Cup by email this week. Players not selected learned the news in writing. Former international Herculez Gomez called the approach "diabolical" and argued Pochettino should "face your players and give them the respect they deserve." Pochettino pushed back, noting that when he was cut from Argentina's national team in 1994 and 1998, he preferred his coach not to call him.
The timing is pointed. Oracle recently drew criticism for delivering layoff notices via email sent at 6 a.m., before employees could reach their manager, HR, or peers. The two incidents have revived an HR debate that defaults to strong opinion: is email cold and disrespectful, or is it a practical tool for geographically distributed teams?
The real problem is not the medium
Expert guidance, including from Laura Hamill (chief people officer at Limeade), favors live, person-to-person communication for terminations and layoffs. The reasoning is emotional: a phone call signals the news is significant enough to warrant personal attention. An email can feel like a checkbox.
But Pochettino's defense has substance. Written messages give recipients time to process without the pressure of responding in real time. In high-volume cuts or geographically distributed teams, a phone call to every affected employee is logistically impossible.
The Oracle case exposes the real failure. A 6 a.m. email isolates the recipient. They learn they have lost their job before their workday starts, with no immediate access to HR, their manager, or colleagues. The problem is not the email; it is the timing and the absence of follow-up support built into the moment.
Pochettino's approach, by contrast, was consistent. Players knew they would be notified in writing. The decision was public and applied equally. A phone call to 23 rejected players would have been theater, not kindness.
What actually matters in bad-news delivery
If your workforce is geographically dispersed, remote-first, or spans time zones, synchronous communication is a constraint. Email is a legitimate channel. But the channel itself is not the test. The test is what happens in the first 30 minutes after the recipient learns the news.
Whether you notify by phone, email, or video call, the person must have immediate access to HR and their manager to ask questions, receive severance details, understand benefits continuation, and discuss logistics. If they are learning the news at 6 a.m. with no one available until 9 a.m., the method does not matter. The system has failed.
Build your process around access, not around the choice between phone and email. Specify the window in which support is available. Prepare FAQs. Have HR and the manager both on standby. If you use email, send it at a time when your support infrastructure is staffed and awake. Dignity is not a word choice; it is a system design problem.