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
-
•
Legacy modernization failures often stem from neglecting product thinking focusing on outcomes, vision, and experimentation.
-
•
The 'four faces of doom' in legacy modernization are hubris, distraction, timidity, and overcapitalization.
-
•
A balanced discovery approach blending upfront and continuous discovery uncovers legacy complexities and prevents feature parity traps.
-
•
Spending too much upfront discovery delays value delivery and risks locking in wrong assumptions.
-
•
Shared visual knowledge like customer journey maps and ecosystem blueprints is crucial to managing legacy complexity and aligning teams.
-
•
Digital tools like Miro facilitate inclusive visual mapping, replacing physical walls but retaining wider team visibility.
-
•
Partnering with a pragmatic yet innovative product manager ensures a clear vision and allows early value delivery in modernization.
-
•
Flipping strategies prematurely or without referencing vision wastes resources and leads to half-baked products with little value.
-
•
Change management is integral and continuous across discovery, delivery, and adoption phases, not just training or announcements.
-
•
Investing about 30% of analysis and design effort in change management supports adoption by addressing awareness, desire, knowledge, ability, and reinforcement.
Notable Quotes
"Almost all the negative outcomes in legacy modernization trace back to not applying product thinking focused on value, vision, and experimentation."
"Hubris is the belief you know the best approach and that the market will wait for your big bang release."
"We once saw an organization running 52 projects with only 36 teams — a perfect example of distraction."
"Lift and shift or feature parity is the hallmark of timidity, clinging to what is known rather than delivering real value."
"Legacy modernization needs a mix of upfront and continuous discovery because many details are known but hidden."
"If you skip detailed discovery upfront, you'll only get a superficial understanding and may prove critical assumptions wrong."
"Shared visual maps record what has gone before and allow you to explore with more confidence through complexity."
"Strong product managers avoid flip-flopping by referencing back to a clear vision and prototyping changes before pivots."
"Change management is not linear; it cycles through awareness, desire, knowledge, ability, and reinforcement alongside build-measure-learn."
"Allocate about 30% of your analysis and design effort to change management to help people embrace the new systems."
Or choose a question:
More Videos
"Doctors hate using EHRs because it turns them into clerks, interacting more with machines than patients."
Standardizing Product Merits for Leaders, Designers, and Everyone
June 15, 2018
"If I don’t have a map, I can’t see patterns or apply context-specific gameplay."
Simon WardleyMaps and Topographical Intelligence (Videoconference)
January 31, 2019
"Many smartwatch designs assume male hands as default, excluding smaller wrists and diverse body types."
Sandra CamachoCreating More Bias-Proof Designs
January 22, 2025
"Reviewing decision points creates a source of truth and makes it harder to forget or scrap earlier agreements."
Darian DavisLessons from a Toxic Work Relationship
January 8, 2024
"Timely engagement helps stakeholders make faster, more informed decisions that lead to better business and product outcomes."
Fisayo Osilaja[Demo] The AI edge: From researcher to strategist
June 4, 2024
"Temporary, quick, and sometimes rough artifacts have a lifespan just long enough for the conversation they enable."
Uday GajendarThe Wicked Craft of Enterprise UX
May 13, 2015
"Service blueprints would have helped business units understand backend impacts and responsibilities."
Davis Neable Guy SegalHow to Drive a Design Project When you Don’t Have a Design Team
June 10, 2021
"People were very adverse to changes because a small 0.5% conversion increase meant millions in revenue."
Eniola OluwoleLessons From the DesignOps Journey of the World's Largest Travel Site
October 24, 2019
"Product managers feel design is a black box; they want visibility, transparency, and accountability on timelines."
Aurobinda Pradhan Shashank DeshpandeIntroduction to Collaborative DesignOps using Cubyts
September 9, 2022
