In Flow Interactive's blog, Phil Barrett offers advice for those who are considering implementing Microsoft's Ribbon in their applications. The Ribbon has received praise from usability folks who see the benefit this offers in terms of ease of use and better, more visible contextual controls. But it has also met with resistance from individuals who find the large menu-heavy approach disruptive.

The ribbon is a decent piece of interface, but like most things in UX, it's hard to design it well. And to design it well you really have to understand your users' needs, behaviours and work practices.

That's because the ribbon tries to show commands grouped together based on what users are most likely to want to do. So in Word 2007, for example, there's a tab for mail-merge, and one for page layout and one for referencing, whereas in Word 2003 those features are pushed lower down in a more generic menu structure. If you get the groupings right, your users will always find the selection of controls they need right there in the ribbon. But if you misunderstand what they need to do, they'll get an irrelevant list and you'll get complaints.