[romwell]

As someone who shipped a "feature" and had to roll it back because it broke the users' flow (even though it was an improvement by all means):

It can be acceptable to un-ship a feature, breaking users' flows -- as long as there are other means that are left for them to accomplish the same result with just as much effort.

Even then, people having to re-train themselves is not a good thing, but at the very least it should still be possible to get the same result.

In our case, the way the users (ab)used the old implementation allowed them to do something that was not easily done by other means.

So we simply flipped the switch back, enabling the old behavior.

I really hope that the developers elsewhere would do the same in a similar scenario for products that I use.