What it costs to forget

"We lose context" sounds like a soft problem, which is why it never makes it onto a business case. It is not soft. It shows up in three places, and all three have numbers attached.

Repeated work

The cheapest version is duplication. Someone writes a proposal that already exists, rebuilds a report someone else built, or re-answers a client question that was answered in a channel they cannot search.

You can measure this. Count the times a week your team asks "did we ever…" in chat. Multiply by the time it takes to redo the thing rather than find it. For a team of forty this was, for us, comfortably more than the licence cost.

Re-litigated decisions

The expensive version is arguing twice. A decision was made, the reasoning was written down somewhere unreachable, and now the same three people are relitigating it with worse information than they had the first time.

This is where retention limits bite hardest, because the decisions worth revisiting are exactly the ones old enough to have expired.

The audit finding

The version with a deadline. If you are regulated, unreliable records are not an inconvenience, they are a finding. Credentials pasted into a private channel are a finding. No audit trail on who could see what is a finding.

Our own worst example was a secrets problem: engineers pasted tokens into channels during incidents because it was faster than the correct route. Policy did not fix it. Making the correct route faster fixed it in a week.

The test

Ask your team one question: what did we decide about pricing last quarter, and where is it written down?

If the answer takes more than a minute, you are paying for this already. You just are not paying for it on the invoice.