Actually, every time I have to use the ribbon (my institute's laptop has office 2010) I start imaging an addon which "learns" what are the most used commands an

Actually, every time I have to use the ribbon (my institute's laptop has office 2010) I start imaging an addon which "learns" what are the most used commands and configures the "Home" (or another) ribbon tab showing icons to access those commands. Surely, someone must have already thought of that no? This is similar to what MS did with pulldown menus in the pre-Ribbon days. It sounds like a great idea but it turns out to be a terrible one in practice. During the critical "newbie" phase, as a user begins to work with the program, the UI never seems to look the same twice. Tasks that should become reflexive never lose their dependence on the brain. At the same time, more advanced users are left wondering what interesting features they might be missing. You really, really do not want a UI that changes behind your back, or in ways that aren't explicitly commanded. Resorting to discrete novice / expert modes is a venial sin in UI design, but "personalized menus" is a mortal one. It's about the worst thing you can do, and IMO there's no reason to think it would be any better in a ribbon-oriented model than in a menu-driven one. (Edit: I do agree that restricting the adaptive menu scheme to a specific ribbon tab might be a more promising approach than monkeying with the structure and layout of the standard tabs.)