Properties Worth Keeping After a Redesign

Redesigns tempt teams to rename everything. Resist encoding layout into property names. Keep properties that describe intent, outcome, and experiment context; move surface-level UI details into optional fields you can drop later.

Run a keep-or-retire review before the redesign ships. For each property, ask whether a chart or alert depends on it today. If nothing consumes it, schedule deletion instead of carrying dead weight into the new UI.

When a property must change meaning, dual-write for at least two release cycles. Document the cutover date so analysts know which cohorts remain comparable.

Assign an owner next to every retained property. Ownership prevents silent drift when the design system evolves again.