How to get data retention right
Teams tend to reach for this after something has already gone wrong. The short answer to data retention is that it is mostly a sequence of small decisions, not one big one.
Numbers get quoted in meetings long after anyone remembers how they were calculated. The teams that stay on top of it are the ones who put it on a calendar rather than a wish list.
What it costs to ignore
Keeping everything forever is a liability, not an asset. There is a version of this that is over-engineered, and it is worth avoiding. Most teams find the first pass takes an afternoon and the maintenance takes minutes a month.
The steps
- Establish what you have today before changing anything
- Retention rules should be written down and enforced automatically
- Deletion has to work across backups too
- Write down the decision so the next person does not re-litigate it
Deletion has to work across backups too. The teams that handle this well are rarely the ones with the biggest budgets. The version that survives contact with a real deadline is the simple one.
Turning this into a decision
How to tell if yours is fine
Data outlives the applications built on top of it, which is why the model deserves more thought than the screens. 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
If you want a second opinion on how yours is set up, ask.