[jbay808]

Sure, but the context is that the message wasn't something that the org permanently documents to refer back to, like... an API or a list of deliverables or something. It's just run-of-the-mill workplace interpersonal communications and announcements, like announcing that there's going to be an earthquake drill, or that you're going to be working from home the first week of August. Not documentation. Until a miscommunication occurs and you're suddenly digging for records to piece together how things went wrong.

What communications tool would people use for announcing an earthquake drill? And what does the messaging tool get used for?

Do you send an email to keep the paper trail (with the downsides of email, like that record only being searchable by the people it was sent to at the time)? Or does somebody update the company wiki with records like "2022-07-30: jbay808 absent today due to doctor's appointment"?

[beAbU]

What would be used in the total absence of an IM tool?

How was this managed 10 years ago? Email?

How was this managed 50 years ago? Physical bulletin board?

What the GP is trying to drive at is that slack should be treated like a passing conversation, and nothing more. It cannot be relied upon as a persistent source of truth or a knowledge base.

We try to apply the same philosphy within my team.