How do you keep your knowledge base from becoming a cluttered mess as your product evolves?

We realized our support team was ignoring our official documentation because half the articles covered old features or outdated UI. Answering tickets took longer because people had to double-check everything verbally.

We spent time cutting our docs down to just the core essentials and archiving the rest. Trimming the clutter reduced our ticket response time by nearly 40%.

Do you have a scheduled routine for retiring old support docs, or do you just wait until the clutter becomes overwhelming?