```json
{
    "title": "Managing Performance Measurement: Who uses this stuff anyway?",
    "url": "https://performancezen.com/2012/11/20/managing-performance-measurement-who-uses-this-stuff-anyway/",
    "datePublished": "2012-11-20",
    "dateModified": "2022-03-31",
    "language": "en-US",
    "description": "One of the least glamorous parts of managing performance measurement data is the time I have to take every month to wade through my measurements and decide which stay on…",
    "author": "spierzchala",
    "publisher": "Performance Zen"
}
```

# Managing Performance Measurement: Who uses this stuff anyway?

One of the least glamorous parts of managing performance measurement data is the time I have to take every month to wade through my measurements and decide which stay on and which get shut off. Since I'm the only person who uses my measurement account, this process usually takes less than 10 minutes, but can take longer if I've ignored it for too long.

With large organizations that are collecting data on multiple platforms, this process may be more involved. By the time you look at the account, the tests have likely accumulated for months and years, collecting data that no one looks at or cares about. They remain active only because no one *owns* the test and can ask to disable it.

What can you do to prevent this? Adding some measurement management tasks to your calendar will help prevent Performance Cruft from clogging your information pipes.

Managing data collection is not the sexiest part of the web performance world, but admitting you have a data collection cruft problem is the first step along the path of effective measurement management.