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."
Dig deeper—ask the Rosenbot:
More Videos
"The nuance is the enemy of machine learning and AI; they struggle with ambiguity where humans thrive."
Ovetta SampsonResearch in the Automated Future
March 11, 2022
"Starting with positives and acknowledging good work helps break down resistance when sharing findings that reveal weak points."
Joanna Vodopivec Prabhas PokharelOne Research Team for All - Influence Without Authority
March 9, 2022
"Some of the best ideas come from UX, but often they’re hidden from decision makers who need to see them."
Deanna Washington Tim Allen Jeff Courcelle John Maeda Matt Raw Erica TjaderScaling Success: Paving the Path from DesignOps to VP
October 4, 2023
"Research ops is not just about delivering efficiency; it’s about creating a map and a vision of research across the whole organization."
Brigette MetzlerScaling ResearchOps: Helping Researchers do Their Best Work
March 30, 2020
"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
"Workshop content is equivalent to a one-day in-person event spread over 10 virtual hours with coaching and support."
Rachael Dietkus, LCSW Victor Udoewa Jennifer StricklandEverything You Need to Know about the Civic Design 2022 Call for Presentations
May 17, 2022
"Our brains are terrible at operating on only one type of information—object-oriented or context-oriented."
Alëna IouguinaDesigning Systems at Scale
November 7, 2018
"HITS is not a replacement for researchers but an augmentation to scale their expertise across the organization."
Matt DuignanHITS, Microsoft's internal human insight system: From research library to living body of knowledge
July 16, 2019
"When you hand over something to a machine, what is really yours? How does it affect your identity as a professional or your relationship to your work?"
Clara Kliman-SilverUX Futures: The Role of Artificial Intelligence in Design
June 7, 2023
