Data retention: what to get right first

The gap between knowing this and actually doing it is where most teams lose ground. If you only fix one thing about data retention this quarter, make it the first item below.

Numbers get quoted in meetings long after anyone remembers how they were calculated. If two people in the business would answer this differently, that gap is the actual problem.

Start here

Keeping everything forever is a liability, not an asset. It is worth being explicit about, because assumptions differ quietly. If it only works because one person remembers to do something, it does not work yet.

Then this

Retention rules should be written down and enforced automatically. In practice this is a scheduling problem more than a technical one. Anything you cannot measure here, you are deciding by taste, which is fine as long as everyone knows it.

Eventually

Deletion has to work across backups too. It is worth being explicit about, because assumptions differ quietly. Budget a little time for it every quarter and it never becomes a project of its own.

How to tell if yours is fine

Most data problems are ownership problems that turned into technical ones. Three things worth confirming about data retention before you move on:

• Someone can say what the current setup is without going to look
• Deletion has to work across backups too — and you know whether that is true here
• There is a way to tell whether the last change to this helped

Most of the value here comes from doing the first two things, not all of them.