Lack of Product Thinking will Doom Your Legacy Modernization
Summary
Scaling an organization or even just a product, inevitably means dealing with your legacy. Through both they and their colleagues' extensive experience with legacy modernization work, Meaghan and Fotina found one consistent theme. View legacy modernization as purely an engineering effort and the outcome won’t be what you want. Legacy modernization needs to be designed. It needs to fit into an overall product strategy and examined through the same lenses of customer, business, and tech impact as anything else. Otherwise you’re just immediately building a new legacy, not something that can scale with you.
Key Insights
-
•
Four common pitfalls of legacy modernization are hubris, distraction, timidity, and over-capitalization.
-
•
A blend of upfront and continuous discovery balances the need to understand existing systems with the agility to adapt plans.
-
•
Visual mapping of features, journeys, and ecosystems is crucial to manage legacy complexity and align stakeholders.
-
•
Strong product management must be both pragmatic and innovative to avoid flip-flopping strategies and deliver early value.
-
•
Change management is a continuous, integral process from research through release, not just announcements or training.
-
•
About 30% additional effort in analysis and design should be budgeted for effective change management.
-
•
Legacy system complexity demands designing at the feature, product, and ecosystem levels simultaneously.
-
•
Avoid big bang releases by slicing modernization into smaller releases for faster learning and value delivery.
-
•
Product managers should actively validate shifts in market needs and avoid merely replicating legacy features.
-
•
Change management cycles should align with the product build-measure-learn process to reinforce adoption.
Notable Quotes
"All negative outcomes in legacy modernization can be traced back to not bringing product thinking to the table."
"Hubris is that belief the market will wait for your big bang release—executives have lost jobs over this."
"We’ve seen organizations try to run 52 projects with only 36 teams—distraction at its worst."
"Lift and shift equals timidity—it’s sticking to what you know rather than delivering real value."
"Avoid too much upfront discovery that delays value and traps you into a fixed plan."
"Maps stop you from getting lost in legacy complexity and keep everyone aligned on what’s important."
"If everyone’s looking at different versions of the plan, you get frustration and confusion."
"A pragmatic product manager decides on strategy and roadmap clarity; flip-flopping kills momentum."
"Change management is not just announcements—it starts with user research and goes through to release and beyond."
"Allocate about 30% of your analysis and design effort to change management for successful adoption."
Or choose a question:
More Videos
"Product telemetry and customer data bring the stories to life in aggregate and help prioritize engineering focus."
Ross SmithBreaking Barriers with Empathy
June 9, 2017
"When product leaders ask for research just to validate ideas, the best response is to say, ‘fuck this group,’ then do real user interviews."
Kevin M. HoffmanTheme 2: Enterprise Team Journey
June 3, 2019
"Your career is a design project. It’s the only one you own, so own it like you would a product."
Ian SwinsonDesigning and Driving UX Careers
June 8, 2016
"VoiceOver gestures like swipe right move the focus through elements; double tap activates them."
Sam ProulxUnderstanding Screen Readers on Mobile: How And Why to Learn from Native Users
October 2, 2023
"The project charter is our best friend for accountability, impact, and timelines."
Briana Thomas Christina RodriguezWhen Design Ops Comes in H.O.T. : A Tale of a Transformed Design Org
September 30, 2021
"Changing the mindset takes time; like a big ship it takes hours to turn direction."
Prerna MakanawalaAchieving Balanced Design Consistency
June 9, 2021
"The components you design in Sketch or XD come with matching coded components in the app builder, so what you design is what you get in code."
George Abraham Stefan IvanovDesign Systems To-Go: Reimagining Developer Handoff, and Introducing App Builder (Part 2)
October 1, 2021
"Attitudinal data alone doesn’t tell us the why behind customer feelings or behaviors, leading to missed improvement opportunities."
Dana Bishop2022: The Year UX Demonstrates its Business Impact
March 11, 2022
"We can’t predict the future; all we can do is make the best guesses based on what we know right now."
Jeff GothelfWho does what by how much?
November 20, 2025
