Stripping the Register
Delta's communications team, at some point, decided that "sad" didn't belong in an announcement about retiring the 747. They also changed the aircraft's pronoun from "she" to "it." There were presumably reasons. Probably something about precision, or the mechanical application of a style guide built for a different kind of document.
The institutional logic here is predictable: emotional language is vague, possibly legally binding, and signals that the author got too close to the subject. The solution is to excise it. Keep the facts. Cut the feeling.
This works fine for a subset of communications. A specification sheet has no business being wistful. An incident report shouldn't romanticize the outage. When the job of a document is to convey information, emotional register is usually noise.
But there's a class of communications where that logic fails completely, because the communication's job isn't to convey information. It's to mark something. To acknowledge that an occasion has occurred, that the audience has feelings about it, and that the institution recognizes this. For those communications, emotional register isn't noise layered on top of the information -- it's the information.
The 747 retirement is the clearest example I can name. What was anyone going to do with that announcement? Not make a purchase decision. Not change their behavior. They were going to read it and feel something about an aircraft that mattered to them. The announcement existed to participate in that feeling, to give it institutional acknowledgment, to say: yes, this mattered, and we know it mattered.
Strip the "sad" and change "she" to "it" and you haven't sharpened the message. You've replaced it with its skeleton. The skeleton says: an aircraft is being decommissioned. The original was trying to say something else entirely.
Worse, the stripped version isn't neutral. It reads as a deliberate refusal to participate. People who loved the 747, who flew the upper deck and have strong opinions about what eventually happened to the cocktail lounge, read that PR and infer that Delta doesn't feel anything about this, or doesn't think their feelings deserve recognition. That's a message too. Not the intended one.
Style guides don't cause this on purpose. They're typically built to govern documents in the first category, where feeling is noise, then applied uniformly because consistency is easier than judgment. Judgment about when to make an exception is exactly the editorial work that institutional communication tends to undervalue. The person who might have said "this announcement is different, the feeling is the point" either wasn't in the room or was overruled.
What gets called "professional" in this context is usually just "affectless." The belief is that removing feeling removes liability and ambiguity. That's true in a narrow sense: you can't be held to an emotion you didn't express. But the exchange isn't free. You also can't communicate the things that can only be communicated through feeling, and some things can only be communicated through feeling.
A layoff announcement written in the bloodless passive voice of a legal document doesn't just avoid saying anything actionable. It tells everyone reading it exactly how the institution views them: as units subject to a process, not as people affected by a decision. The communications team thought they were being careful. The employees understood that they were being dismissed.
The stripping is treated as zero-cost editing. It never is.