Before anybody processes what you said, they read how you said it, and from that they infer what kind of event they are in.
A written notice on letterhead means one thing. The same content delivered leaning against a doorframe means something entirely different. Neither is more honest. They are different signals, and the signal is frequently doing more work than the words.
What formality actually conveys
Formal register communicates four things, none of which is the content.
That this is on the record and will be referred to later. That it applies generally rather than to the person in front of you. That the institution is speaking rather than an individual. And that a process is operating, with steps that follow.
Plain register communicates the opposite set: that this is between us, that it is current rather than permanent, that a person is talking, and that the matter can still be shaped by the conversation.
Both are legitimate. The failure is using one while intending the other, because people will trust the register over your stated intention every time.
Formal where plain belonged
A supervisor is late twice. The leader, wanting to be fair and consistent, sends a written note referencing the attendance policy.
What the supervisor receives is not a reminder. It is the opening of a file. He will read it as the first step in a documented process leading somewhere, because that is what formal register means, and he will respond to the process rather than to the lateness. Something that a thirty-second conversation would have resolved has become a matter with a paper trail, and the relationship has changed in a way that is difficult to reverse.
Escalating register is the most common form of this error, and it is nearly always driven by discomfort. Writing is easier than speaking, and formality provides cover. The leader experiences their own choice as professionalism and the recipient experiences it as a threat.
Plain where formal belonged
The reverse failure is less frequent and produces different damage.
A policy change delivered as an aside in a corridor conversation has been announced in a register that says this is provisional and negotiable. People will treat it accordingly, and the leader will later be puzzled that nobody complied with something they clearly stated.
The same applies to consequences. Telling somebody informally that their performance has to improve, in a tone that keeps the conversation comfortable, communicates that the matter is not yet serious. If it is in fact the last conversation before a formal process, the register has actively misled them, and any later claim that they were warned will be technically true and substantively false.
Where something is genuinely serious, the register has to carry that, even at the cost of an uncomfortable meeting. Softening it is a kindness to the leader rather than to the person.
Idaho complicates this
Professional culture in much of the state runs plain by default, and formality carries more weight here than it would in a larger market.
A leader who reaches for written formality in a setting where business is ordinarily done face to face has signalled distance, and often distrust, without intending either. Among people who have dealt with each other for years, the letter is read as an escalation regardless of its contents.
The corollary is that formality retains real force when it is needed, precisely because it is unusual. A leader who operates plainly and then writes a formal letter has communicated seriousness with an economy unavailable to someone who writes formally about everything.
None of which changes the situations where writing is required rather than chosen. Anything with legal exposure, anything that must survive personnel turnover, and anything a public body does under open records obligations belongs in writing whatever the local custom.
Say which register you are in
Where the signal might be misread, name it directly and the ambiguity disappears.
This is not a formal warning, it is me asking you to sort it out. Or: I am putting this in writing because it needs to be on the record, and I want you to know that is the only reason. Or: this one is a decision rather than a discussion.
The second example is worth particular attention. A great deal of unnecessary alarm is caused by leaders who must document something for institutional reasons and do not explain that the documentation is not a judgment. Thirty seconds of explanation prevents weeks of a capable person assuming they are in trouble.
The one-way ratchet
Register moves up easily and comes down slowly, which is the practical reason to be conservative about escalating it.
Once a matter has been put in writing, subsequent informal conversations about it are read as informal conversations about a documented matter. The file exists and everybody knows it exists. A leader who formalises early has spent an instrument they cannot recover for that particular subject, and they will need it later if things genuinely deteriorate.
Which suggests a working rule. Start at the lowest register the situation permits, and reserve the higher ones for the point at which the lower ones have demonstrably not worked.
Edited by Patrick J. Wolf, PhD