Properties That Age With the Product
How to choose event properties that still make sense after the next redesign.
- taxonomy
- instrumentation
Properties that encode button colour or layout region die the moment design ships a new surface. Prefer properties that describe intent, plan tier, entry source, and experiment assignment.
Keep UI details in a short allow-list only when a specific experiment needs them, and schedule their retirement. A property without a known consumer after two quarters is debt.
Before a redesign, run a property impact review. Alias what you can, dual-write for one release cycle, and freeze comparable funnel names so historical charts remain readable.
Document the owner beside each property. When the design system changes, that person decides whether the meaning still holds—not a shared chat thread.