Skip to main content
New Participant
August 11, 2021
Question

Classic -> New Experience Nightmare

  • August 11, 2021
  • 41 replies
  • 6754 views

I was losing sleep over this six months ago when I tested things, but had hopes the experience would have improved. After some testing, we're finding that New Experience pages load 5-6 times slower than in Classic. Try to CTRL+ CLICK an open more than one tab at a time and things get even slower. We've all become quite accustomed to pages loading quickly when popping out into new tabs. But speed isn't the only problem. I'm also getting trapped in iFrame hell where the focus of the cursor is constantly grabbed by each report on the dashboards we use. So getting to that last report at the end of the dashboard is quite an interesting ride. We also use the "Allow embedding of Workfront in an Iframe" feature, which still loads Workfront in Classic for some reason. Perhaps things are better for the users with super high-speed fiber internet connections, but a huge part of our work force is remote with varying internet speeds. However, Classic is fine even when in the most remote places with just a single bar on a Verizon MIFI.

So what gives? Now that Workfront is an Adobe product, perhaps it's time to reconsider kicking Classic to the curb. There's not one feature we NEED in New Experience, yet we're seemingly being forced to use it because of all the features customers WANT.

Is anyone else dreading the day they have to move everyone over? For those of you who have already switched, do users simply normalize working at a much slower pace? Is leadership okay with productivity declining? Am I the only one who finds the experience to be a complete disaster?

  • Dashboards ~25 Seconds to Load vs. 5 seconds in classic
  • Dashboards - Every report is an iframe with scroll bars, grabbing the focus of the cursor if there's a pause resulting in endless scrolling.
  • Issue ~30 Seconds to load instead of < 5 seconds in classic.
  • Program ~20 Seconds to load
  • Project ~30 Seconds to load instead of < 5 seconds in classic.
  • Task ~20 Seconds to load overview instead of < 5 seconds in classic
  • iFrame - When loading Workfront in an iFrame, it still loads in Classic... confusing.
  • Custom Forms Report - We're no longer able to edit forms from a report. Once edit is clicked, navigation takes us to Setup, a huge productivity killer for a team of >5 editing forms all day long.
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

41 replies

RandyRoberts
New Participant
October 6, 2021

When I'm in some kind of training session or demo, I just screenshot the Workfront pages and show the images instead of risking the page not loading. Hey, we don't call it WorkAroundFront for nothing!

AileenTa
New Participant
October 14, 2021

I thought we were the only ones who called it that. 😂

kynabaker16
Employee
October 6, 2021

Hi guys!

I just wanted you to know that our team is very invested in hearing your feedback and are actively working on improvements to solve your concerns. In fact, the head of engineering at Workfront just responded a few days ago on this post to give an update as to what they are working on and give an additional way to connect with the product team. I can promise you that they are taking all the customer feedback very seriously.

Thank you,

Kyna

AileenTa
New Participant
October 6, 2021

I just read through this thread and have to agree with every complaint and more regarding the new experience. I had a few users try it out and every single one hated it and switched back. A software update should not take a multiple days of training just to help current users learn it. I frankly doubt that Workfront has any UI/UX testing done at all or that team has no real power to influence the product, the changes Workfront makes all seem to be leadership & developer driven with little to no feedback from real customers. I just dread the migration because my IT keeps beating the drum to get us to move to Jira and the forced change to New Experience will just give them more fuel to set Workfont on fire and remove it completely.

RandyRoberts
New Participant
October 6, 2021

I actually like Jira a lot… for software development, but not so much for standard project management.

I use both Jira and Workfront and they are 2 completely different animals, not competitors at all. One cannot replace the other.

AileenTa
New Participant
October 14, 2021

Hi Randy- Everyone in marketing agree's with you but that does not stop our IT department from beating the drum about moving to "one system". Because Jira works for developers they don't understand why it wouldn't work for everyone.

New Participant
September 27, 2021

Seems to get slighly better for us - anyone with the same experience?

New Participant
August 18, 2021

Hey folx - I have complete empathy by anyone experiencing slow loading speeds whether it is in WF or any page on the internet in general. But, I feel like WF clearly and regularly communicated the upcoming transition to NWE and the pending decommission of Classic well over a year ago. It is just not feasible for any company to support all the previous versions of their product. If so, I know some people who would still be carrying around an iPhone 5 and complaining how slow and incompatible it is with newer apps.

I do wonder if some people are experiencing slower load speeds due to using Classic and NWE at the same time, and I also wonder if a clean sweep of their instance might be needed? Possibly purging unneeded objects could help the situation.

Christina_Jarosz
New Participant
August 18, 2021

Kelly - this was one of the first things we tried - purging the classic from our instance since we are all on NWE and it's no success. The load time is still agonizingly slow.

New Participant
August 17, 2021

After a lot of bad news, a small consolation: our users like the NWE design better…

New Participant
August 17, 2021

Yeah, our users like the design too, though some wish it was a bit more compact and space-efficient vertically.

New Participant
August 17, 2021

The very slow NWE has been discussed several times here in the forum; combined with the numbers provided by @NRYN R - inactive‚ I‚Äòd say we can call it a fact that it is considerably slow and annoying for anyone using Workfront regularly. I resign from creating support tickets here as it’s a waste of time.

Regarding the inconsistency of NWE and Classic: I have the impression we got rid of occasionally seeing the classic one after we entirely and irreversibly switched to the NWE (‚Äî> support ticket). Thus, the issue seems to be a result of the hybrid situation. Please be aware that we didn’t manage to migrate layout templates and created new ones for the NWE.

NRYNRAuthor
New Participant
August 17, 2021

It's a One that needs to be flipped back to a zero. It can be done. it should be done. But will it be done? Ooh the suspense. Tick Tock...Tick Tock...

NRYNRAuthor
New Participant
August 16, 2021

A common suggestion is to reference an existing ticket when there is a larger problem at hand. A ticket has been raised expressing Truist's inability to migrate to New Experience at this time. You can reference the case at https://one.workfront.com/s/case/5004X00001aSAWkQAO/new-experience-migration-plans-failed to help Adobe Workfront Support better understand the scope of the problem.

ChrisBudgen
New Participant
August 16, 2021

Same here, we have roughly 1k users and have started with a POC, the feedback was: better design, super slow (especially if you have more than 100 items in a list and some calculated columns) and there are a lot of inconsistencies within NWE. E.g. the user edit and create modals are still Classic, filter/view/grouping selections have a different UI depending on the object, ...

New Participant
August 12, 2021

We are experiencing the same performance issues since we started using the new experience. Lag times have definitely increased. I agree with Mike. They are intermittent. Lately its been bad.