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
"Sometimes it’s reasonable to consider your design as strategy and ship a piece now and other pieces later."
Scott Jensen Sarah Delaney Carmen LiuShort Take #2: UX/Product Lessons from Your Industry Peers
December 6, 2022
"Designing services increasingly span these blurred lines between our digital and public worlds."
Sarah BrooksTheme Three Intro
November 18, 2022
"Order today is change, and the uncertainty that it brings rules us day and night."
Jon FukudaTheme One Intro
October 2, 2023
"Lauren Cantor keeps all those links and other resources so we don’t have to be googling while listening."
Bria AlexanderOpening Remarks
March 29, 2023
"Slowing down speech and asking ‘what’ and ‘how’ questions engages the logical brain and de-escalates tension."
Joshua GravesWe Need To Talk: Navigating Conversations with Your Boss (Part 1 of 3)
April 14, 2025
"Government cannot be the only solution—we needed community groups, nonprofits, and for-profits all involved."
Kyria Stephens Marlon KernerPower to Heal: Civic Design in the Aftermath of Tragedy
November 17, 2022
"At IBM, projects felt like following a recipe, but at Compass, I can promote my ideas and see how they work, which is very satisfying."
Caitlyn Hampton Monica Lee Jina YoonCompass 101: Growing Your Career In A Startup World
June 11, 2021
"Our job as design teams is to teach others what we do, not to feel insecure about sharing."
Louis RosenfeldDiscussion: What Operations can teach DesignOps
November 6, 2017
"Fluid intelligence peaks and then declines; that's when we should lean into crystallized intelligence—organizing, synthesizing, sharing."
Rachel GarbExit Interview #7: Facing a blank slate in retirement when constraints are all you’ve ever known
August 5, 2026
