Concept
Do not track personal data without a question or action
Data can create maintenance and cognitive burden without improving a decision.
When it fits
- A dashboard keeps adding metrics because collection is easy.
When to avoid it
- Some records are required for medical, legal, financial or safety reasons even when no immediate action exists; those follow their own retention needs.
The idea
Before adding a personal metric, state the question it answers, the action that could follow and a stop condition. If no plausible decision changes with the data, do not collect it by default. Periodically remove metrics that create attention cost without useful feedback.
An example
Instead of tracking 20 productivity metrics, you keep one measure tied to whether a boundary experiment reduced end-of-day fatigue.
Check your result
Every tracked personal metric has a stated use and review condition.
Keep this limit in mind
- Some records are required for medical, legal, financial or safety reasons even when no immediate action exists; those follow their own retention needs.
Connected ideas
Compare withSave information for a future job, not because it is interesting
Evidence and sources
Supports
A 2025 systematic review of 172 personal-informatics articles documented unintended burdens including cognitive load, emotional stress and practical management problems from personal data systems.
Personal informatics and PKM overlap only partly; the direct implication here is to avoid tracking with no decision or use case.