Enterprises spend 40 to 60 percent of their time managing legacy systems. These systems are not relics waiting for retirement. They are load-bearing infrastructure, often built by external suppliers without usability testing, customized over years, and now deeply embedded in daily operations. The original engineers are gone. The documentation is sparse. The design files reference tools that no longer exist. And every modern product built around them inherits their failures.
This Smashing Magazine piece by Vitaly Friedman lays out the actual cost of ignoring legacy UX: one broken step in a user flow poisons the entire product's perception, regardless of how polished everything else is. The article earns a full read not for its conclusion but for its migration strategy breakdown, specifically the case against big-bang redesigns and the detailed argument for incremental parallel migration, where new and old systems run simultaneously until the replacement is proven stable. The workflow mapping section is also worth the time, particularly the point that legacy systems often integrate other legacy systems that no one has accounted for.
The strategic framework here applies directly to B2B product teams stuck between stakeholder risk aversion and mounting UX debt. Friedman's core argument is precise: you cannot replace what you do not fully understand, and most teams do not understand their legacy dependencies until they try to remove them. The full article includes a prioritization matrix and specific questions to surface hidden dependencies before any migration decision is made.
[READ ORIGINAL →]