Lessons Learned from a 4-year Product Re-platforming Journey
Summary
Key Insights
-
•
Legacy enterprise applications often persist due to high risk and complexity despite technology advances.
-
•
Re-platforming on the cloud varies from simple re-hosting to full refactoring and requires tailoring to business goals.
-
•
UX teams need to evolve from embedded roles to centralized, strategic influencers in re-platforming projects.
-
•
Focusing too narrowly on one persona, such as end users, risks neglecting important power users and administrators.
-
•
A blended approach combining visual refreshes and incremental re-platforming can ease transitions but requires careful consistency.
-
•
Designing for change includes not just usability but also product consumability like adoption speed and time to value.
-
•
Robust change management addresses both external customers and internal teams to align rationale and reduce resistance.
-
•
Initial customer resistance to change is natural and may mask genuine pain points, requiring feedback at scale with qualitative and quantitative data.
-
•
Hyper-focus on individual features or modules can cause loss of peripheral vision, leading to fragmented experience and customer frustration.
-
•
Maintaining team morale during long, complex transformations is critical for sustained success and delivering customer value.
Notable Quotes
"Legacy applications linger because changing them is risk-ridden and a major undertaking."
"No two re-platforming journeys are exactly the same, and there isn't one single formula that works every time."
"We did a blended approach with a visual refresh first to minimize differences between old and new and buy time."
"We neglected our power users during the responsive, one-size-fits-all strategy, and it really hurt us."
"Re-platforming is transformative not just for the product but also for the people, teams, and organization."
"There is no solid way to control the course of your re-platforming project; being flexible is essential."
"The curse of hyper-focus means you lose peripheral vision and miss the larger context and customer needs."
"Designing for change means focusing on learnability and product consumability, not just ease of use."
"Managing resistance is mental; customers might resist because they've learned workarounds with legacy systems."
"Keep a pulse on your team morale because re-platforming journeys can either enrich or burn out your people."
Or choose a question:
More Videos
"If you value innovation and design, then you're investing in creativity."
Dr. Karl JeffriesThe Science of Creativity for DesignOps
January 8, 2024
"We use Alexa’s personification for good, fun, and delight, but we don’t advertise, especially because there may be kids listening."
Amy MarquezINVEST: Discussion
June 15, 2018
"Trust is built by showing you’re there to help make them succeed, not just push your agenda."
Steve Portigal Chris Chapo Kelly Goto Christian RohrerDiscussion
May 13, 2015
"How do you organize a design team to work within a changing environment without freaking everybody out."
Alicia MootyDesign Staffing Models
September 30, 2021
"We want to stay in the game no users cursing our name."
Ana Maria Montero Barrantes Aditi Dhar Michelle Kaplan Nate Osborne Matt LaurenceThe Authentic UX Talent Show
January 8, 2024
"We never compromise on the business goals, but how we achieve them can be flexible and pragmatic."
Lada Gorlenko Sharbani Dhar Sébastien Malo Rob Mitzel Ivana Ng Michal Anne RogondinoTheme 1: Discussion
January 8, 2024
"Choosing a research repository is a big battle in your organization; the right decisions can really help you succeed."
Sofia QuinteroThe Product Philosophy Behind EnjoyHQ
March 10, 2021
"Innovation is very much a team sport."
Laura KleinUnique challenges of innovation in enterprises
April 23, 2020
"Without Jim, what we're going to see today would have been a lot worse."
Andrew MichaelBuilding a Product Insights Team
March 10, 2022
