I am of the opinion that you should allow users to customize their workflows by having the ability to bring back the detail of a hidden column as it was in the previous UI. That means we sometimes do not want to see a whole column just because in within dozens of tasks only one has a special custom Tag. This is annoying.
I propose we, as users, could hide a column and make it appear as an inline tag.
Above all: KISS! This update goes against that design rule.
Also, as a consideration on your change process, I would also suggest you follow a period of adaptation by allowing users (and whole companies) to select legacy UI while testing the new changes.
Rolling surprises like this to whole enterprises that base their workflow on your solution might cause more harm than good. Google is a good example on how this process should work - remember they still have the option for plain text gmail and up until some time ago they were testing a new UI which they decided to not roll out. They way they did it, since it was completely different from the previous UI, was by giving users options (have a look here: Here's how to switch to the new Gmail design | TechRadar ).
There is a huge cost on deciding for one UI: you will need to accommodate two types of users: the ones who want to stay on the old UI and the ones eager to use the new (just because).
- Ask your engineer team to figure out the scroll of the new excel list, it’s wrong.
Hope you figure out how to navigate this turmoil you generated.