Sandra leads a 55-person R&D department at a 400-employee pharmaceutical company. Promoted eight months ago, she learns in a leadership meeting about a major restructuring: two teams merging, roles redefined, five positions eliminated. Leadership asks her to communicate the news to her team.

Sandra doesn't check with HR on the protocol to follow and doesn't take the time to prepare the conversation. On a Friday evening at 5:15 p.m., she sends a group email with a 12-page institutional document attached, with no context and no personal message. Monday morning, the lab is in shock. Rumors are flying about who's getting laid off. Two researchers reach out to an outside union. Sandra, meanwhile, is at a conference planned long in advance, and has to manage the crisis remotely.

💬 The Eskalon moment

Before sending anything, Sandra could have asked Eskalon: "I have to announce a major restructuring to my team. Where do I start, and how do I make sure I keep my employees' trust?" The answer: a five-step protocol. Check with HR before communicating anything. Prepare a personal cover message, not a raw institutional document. Choose the right time and format — an in-person meeting, never an email, for an announcement of this kind. Set aside at least 30 to 45 minutes for questions right after. Confirm what was communicated in writing, along with next steps.

She would also have gotten prepared answers to her team's most likely questions: "Is my position affected?", "What's changing in my responsibilities?", "What's the next step?"

With this protocol, the same news, delivered in person on a Tuesday instead of by email on a Friday evening, takes on a completely different shape. Uncertainty is named honestly instead of being filled in by rumors. Questions get an immediate answer instead of piling up over an entire weekend. Sandra, instead of weathering a crisis of trust remotely from a conference, leads a difficult but controlled transition, and preserves a credibility that would otherwise have taken her months to rebuild.