We have an application that heavily relies on Microsoft Ribbon UI to perform actions etc on say a document. We have a few ribbon groups defined and each have a certain set of actions they can perform on a document.
The problem is, certain set of user base is used to an old technology where they perform ActionA → ActionB → ActionC on a document quickly. (Each followed by the other). Now when we showed them the new ribbon design, we allow for these actions BUT they are defined in separate ribbon groups, so they would have to perform
ActionA → choose ribbon group B → ActionB → choose ribbon group C → ActionC
This they say is heavily not effective in their work process. I have to say that they are a certain set of our user base, the other set of our user base does not care or want these actions specified together.
Are there any alternate design patterns to solve their particular case without having to specifically rewrite the ribbon which may affect other users?