Why forcing new UI adoption?

[CIT_BV]

It was cool to revert back…

..until it wasn’t.

Only a few weeks of reverting back and now it’s being taken away to force the new UI down our throats - something that didn’t need change in the first place ?

What’s the reasoning behind that decision because it’s clearly losing on clarity - no need to be a UX designer to see that.

It was okay as long as we could revert back to old UI until the new one was polished. But it isn’t.

Here’s why:

How to revert back to previous UI?

Hi Lisa, Thank you for your answer - I found it. My apologies if that felt a bit rough, allow me to bring clarifications. Old UI: Great overall readability (easy to scan through) One-click status filters Clean scenario modules overview Compact and clean Little icons next to folders Intuitive UI contrasts (grey menu on the left, light-grey scenario pannel) [Capture d'écran 2025-09-25 114619] New UI: Overall feeling of messiness mainly due to changes of UI colors being white everywhere …

[Lisa_Kleinman]

Hi,

Thanks for opening this discussion and I’m happy to talk with the Community about the UI migration.

I completely understand the frustration when something you were comfortable with changes. The old navigation felt familiar and worked well for many of you. Still, we needed to move forward for a few important reasons.

1. With the old navigation, every page in Make was built differently
   What looked consistent on the surface was actually hundreds of individually coded pages and UI elements. The new navigation brings all of that together under a single, unified system. This not only makes the product easier to maintain and improve, but also unlocks new capabilities (eventually) like Dark Mode, which wouldn’t have been possible before.

2. All new features will now be released only in the new interface
   Keeping two versions of the product created extra overhead and more potential for bugs, ultimately slowing down our ability to deliver improvements for everyone. We learned during the “revert” period that splitting focus between two UIs made both experiences worse. By focusing on one, we can fix issues faster and ship updates more reliably.

What data supports that the new navigation is working?

• For the past six weeks, all new customers have been using the new UI exclusively, with positive feedback and no major usability issues reported.

• We’re also tracking feedback scores and customer care tickets closely. While there is a vocal minority who find the new navigation harder to scan or read (especially in the scenario list), we’ve already made several improvements to address clarity and information density — and more are on the way.

Please keep your feedback coming, it directly shapes what we do next.