exposure-redesign-risk

Justify the change by concrete user benefit, communicate 30-90 days in advance, roll out gradually starting at 5% of users, and provide migration guides plus an optional old-layout mode during transition.

Backlash stems from familiarity-based preference, relearning costs, loss aversion, and trust concerns. Users like what they are used to, so even improvements trigger resistance disproportionate to the actual change.

Radical change is justified when the existing design has fundamental problems, the product's purpose has changed, technology constraints shifted, or competitors have moved ahead. Even then, plan extensive communication and transition support.

Yes, a temporary old-layout option reduces forced unlearning and backlash during transition. Keep it available for roughly 3-6 months, then remove it once users have adapted to the new design.

Common mistakes include surprise launches without warning, removing features power users depend on, big-bang releases without gradual rollout, ignoring early feedback, and redesigning for the team's aesthetic rather than user benefit.