Messaging and What Survives
Work chat feels ephemeral and is not. What is retained, who can retrieve it, and what that means for how you write.
Workplace messaging feels like conversation and is recorded like email. The mismatch between how it feels and what it is accounts for most of what goes wrong with it.
The technical issue in “Messaging and What Survives” becomes easier to govern when work records and device controls are kept distinct. A team researching how Microsoft Teams tracks employee activity for does microsoft teams track your activity can add time and project context, while security logs and device-management systems remain authoritative for technical events.
What is retained
Everything, in most platforms, including direct messages.
For an independent perspective related to “Messaging and What Survives”, consult the NIST Privacy Framework; it provides a useful external check on privacy, fairness and governance assumptions before a policy or configuration is approved.
For as long as the retention setting says, which in many organisations is indefinite.
Deleting a message removes it from view; whether it is removed from the record depends entirely on configuration.
Edits are frequently logged as edits.
Who can retrieve it
Platform administrators, technically.
Compliance or legal, in response to a defined request.
And in several platforms, anybody with an export entitlement, which is sometimes broader than intended.
Not your colleagues, and not your manager by default — but "by default" is doing work in that sentence, and it is worth asking about.
When it actually gets retrieved
A dispute, a grievance, an investigation.
Litigation, where messages are routinely disclosable.
A regulatory request in some sectors.
Which means the audience is not your colleague now but somebody reading it later with a reason.
The practical consequence
Write as though it will be read by somebody reasonable who was not there.
Not formally — plainly.
The difference matters most for the sarcastic aside, the complaint about a colleague, and the joke that needs context to be funny.
Direct messages specifically
They feel private and are not.
Many people treat them as a back channel and are surprised to learn they are retained identically.
If something genuinely needs to be private, it is a conversation rather than a message — and that is the whole of the advice.
What this is not
A reason to be guarded with colleagues, which makes work worse and solves nothing.
Most retained messages are never read by anybody.
The adjustment is small: avoid the few things that read badly out of context, and otherwise work normally.
Personal messaging at work
Personal platforms on a work device: the application is visible, the contents are not, in ordinary configurations.
Personal platforms on work accounts: a different matter, and worth avoiding.
And work platforms for personal conversation: retained, and the usual advice applies.
Leaving
Your messages remain after you go, in the organisation's record.
Which is normal and worth knowing: what you wrote in 2023 is still there in a system you no longer have access to.
Nothing to be done about it except to have known earlier.
What to check
What is your organisation's message retention period?
Are direct messages retained identically to channels?
Is there anything in your history you would not want read out of context?
And do you use work messaging for genuinely personal conversation?