Major feature launches, pricing changes, and seasonal campaigns can age an impact baseline in weeks. Watch for rising “other” crash buckets, support themes that do not appear in your top clusters, and stakeholders inventing unofficial severity labels.
A light refresh cadence—monthly for fast-shipping apps, quarterly for steadier products—keeps product, engineering, and support speaking the same language.
Refresh is not a full rebuild. Confirm which journeys still define severity, prune stale clusters, and only invent new impact rules when a new journey becomes critical.