Designed the full transition experience for a flagship fintech platform consolidating multiple independent trading tools into one unified product. As the sole UX designer, I owned the UX strategy, communication design, phased rollout framework, and all 16 transition features.
The company's flagship trading platform was consolidating multiple independent products that had previously operated as separate tools. Most of the new platform was already functional, with new features and tools added. The challenge wasn't building the product - it was transitioning users who were deeply accustomed to the old interfaces. Research showed users were generally positive about the upcoming changes, but the platform handled time-critical financial tasks where any disruption could have real consequences.
I was the sole UX designer on this initiative. The product owner presented a three-phase business rollout: Phase I to selected 'friendly customers' for beta feedback, Phase II expanding to a broader audience including introducing brokers, and Phase III - full availability to all remaining customers. My job was to translate this business strategy into a user experience that would make the transition feel safe, gradual, and under the user's control.
Users relied on the platform for daily, time-critical tasks - executing trades, monitoring positions, managing risk. Forcing a sudden switch could mean frustration, workflow interruptions, and resistance. The challenge was designing a transition that felt supportive and optional rather than imposed - while still driving adoption forward. I wanted to educate, not force. Some users needed to execute tasks as fast as possible, and in those moments execution time was everything.
I broke the PO's three business phases into five UX stages, each with distinct goals: pre-launch (build awareness), launch day (enable access), first days (support exploration), stabilization (deepen adoption), and end of support (complete transition). Across these stages, I designed 16 features - each with a specific purpose, appearance window, and removal point. Nothing appeared all at once. Features were sequenced so users received the right information at the right moment, and earlier elements faded as users progressed.
The 16 features included: what's new preview, learn more page, email invitation, version selection at login, version switcher, welcome banner with version selection modal, temporary labels & hints, interactive onboarding guide, feedback widget, help button, in-app notifications, updated what's new panel, release notes, end of support warnings, feedback summary, and final removal of the version switcher.
Instead of a mandatory onboarding flow, I designed a gradual approach that eased users into the new platform over time. Multiple touchpoints across the timeline meant users encountered information about the new features naturally, making the transition feel gentle rather than abrupt.
Each platform area (e.g. Risk Management, Trading) had its own targeted walkthrough. A user interested in risk management could learn about that section without sitting through a tour of the entire platform. This kept users focused and productive while learning.
The switcher was deliberately temporary - a safety net, not a permanent option. Users who needed to execute something quickly could return to the familiar interface, then come back to explore the new one. This removed the fear of being stuck and made people willing to try.
6 user segments were identified based on behavior and platform usage patterns. I assessed the specific risks for each group and tailored messaging accordingly - enterprise clients needed stability guarantees, inactive users needed re-engagement, mobile users needed performance reassurance.
The primary risk was user frustration - especially for traders executing time-sensitive tasks. The version switcher provided an instant escape route, onboarding was accessible on demand (never blocking workflows), and messaging was informative rather than intrusive. The secondary risk was low adoption, addressed through staged exposure, continuous feedback collection, and time-limited availability of the old version - creating gentle urgency without pressure.
I designed phase gates tied to four metrics: adoption rate, legacy return frequency, onboarding engagement, and early adopter feedback. Moving from Phase I to Phase II required a threshold adoption rate among friendly customers, a declining return-to-legacy trend, and no critical usability issues. Each expansion was grounded in evidence, not just timeline.