I use Microsoft Edge as my primary browser. Don't judge me. I used to use Firefox but found many websites that would not work properly with it. I switched to a Chromium based browser called Ulaa (from Zoho) that was excellent. Unfortunately, with Edge so embedded in Windows 11, I experienced too much inconsistent behavior, and quite honestly, Ulaa was not keeping up with new and useful browser features. So, I begrudgingly switched to Microsoft Edge.
Edge has a neat feature called Workspaces. This is like a tab group but can be called up with one click. Unlike a tab group, it maintains the current state of the set of tabs. So, if I open a new tab and leave it there when I close the Workspace, it is present when I open the Workspace again. Workspaces are dynamic whereas tab groups are static. Workspaces also open the tabs into a color-coded separate window, visually and spatially separating the tabs into their own space. I use this feature constantly.
What happened recently to Workspaces, provides us with a great example of what is terrible about software today. You see, Microsoft has been retooling Workspaces under the cover, causing the user experience (UX) to change. That can be good, but forcing changes to workflows is disruptive and irritating. In the case of Workspaces, it no longer will maintain a fixed list of Workspaces. Instead, it now insists on what is called Most Recently Used, or MRU, ordering. That means whatever you used most recently goes to the top of your list of Workspaces, even if you only use this Workspace occasionally. I find MRU a silly way to order something. A fixed but adjustable list defines a workflow. Ordering items as Most Frequently Occurring items makes sense in that it highlights something you use a lot. MRU ignores the wishes of the user and frequent usage patterns. It places emphasis on the wrong thing.
This is not a debate about ordering schemes. It's about changing UX without taking into account the end user. It's about not maintaining backward compatibility in workflows. It is about an abrupt forced change in user behavior, without the ability to either ease into it or continue with the old ways. In effect, Microsoft is telling people who use this highly touted feature how they should work.
If a software vendor introduces a new feature, they don't do it just for fun. They are hoping that his new feature will keep you using their product. If you don't use their product, they can't make money from it. That's why I stopped using both Firefox and Ulaa - they didn't keep up with the features that make my work easier. Once lured into using a feature, however, you can't abruptly and capriciously change key elements of it. Once your workflow has adopted this feature, changes to the feature can become changes to your workflow. In this case, instead of enabling my workflow, Workspace changes have altered and disabled parts of my workflow.
For me, the most likely solution will be to abandon Workspaces altogether. The MRU ordering is counterintuitive and counterproductive. I can do something similar with tab groups, though not quite the same. When software companies make changes like this, they sabotage their own features. I can imagine the product manager who made these decisions realizing that use of the feature has dropped dramatically and, instead of admitting that he greenlit a change that was terrible, will say no one uses Workspaces and sunset it. I doubt that anyone will want to admit that they themselves sabotaged their own feature.
This is not just a Microsoft or software problem. For those of you who remember New Coke, you know what I mean. It just happens faster and quieter in software. All of sudden something stops working and everyone is confused. End users think they did something wrong and finally, abandon the new thing in frustration.
Oh, and Copilot lied about it and kept telling me how to "fix" my problem. Sudden changes to my workflow and gaslighting all in one package. Nice!
