Your client is "not fond of the tab metaphor"? What kind of argument is that? Maybe they should learn to delegate decisionmaking about UI elements to, you know, the UI designer instead of micromanaging them.
–
Rahul♦Aug 18 '10 at 15:35

3

It would help if you could provide a screenshot of the existing interface or give us some hints about what goes on the tabs.
–
Patrick McElhaneyAug 18 '10 at 18:53

2

@Rahul Good luck finding a client who is not the undisputed master of everything about design. It's a rare bird who actually listens to experience.
–
Michael ToddAug 18 '10 at 19:42

3

My challenge to the client was, "other then some default Windows applets, I challenge you to find an application on your system that doesn't use tabs." Of course, there are some, just not many.
–
SergioLAug 23 '10 at 15:59

Do you know what it is about visualizing tabs they don't like? Since all tabs are is an anchor that shows/hides a container, you could still do it the same way but without actually making it look like folder tabs. You could follow Dan's suggestion (which is really the same thing as using tabs without the visual cues) or maybe you could make a case for why exactly tabs are a good idea (users have an easy time understanding the concept and they are used to using them).

I like this one. Keep the tab concept, but just change the style, and come up with several. Make the tabs on one side look like buttons, and now it isn't really "tabs" anymore.
–
John GardnerAug 24 '10 at 21:18

It might be worth mocking up a couple of versions using the Accordian and Expander (as suggested by Ryan) and showing them to the client. These controls are very similar to tabs and might not pass the "fondness" test.

Let them use them for a while and then ask some questions about which they liked or didn't like and why. Treat it as a mini User Experience test. You might get to the bottom of why they're "not fond" of tabs and come up with a better solution.

I'm curious as to what metaphor your client would be more interested in being used than a tab menu.

Anyone who uses a visual operating system uses a tab menu in some aspect or another. The difference being the visual representation of said menu. Mac has their own, Windows as well has their own. The possibilities are endless.

Mocking up a few possibilities even on paper might serve as a good conversation point for suggesting to stick with a tab menu, but offering different variations of the visual aspect of a tab menu which can easily be changed.

If you are using Silverlight, then you may want to look into a Navigation style interface with paging and 'breadcrumbs' to lead the user through the system. In some interfaces I've designed, we've had success with this style of navigation along with a selection of 'related screens' to help route the user through the application.

I think that when you have too many tabs, things can get a little out of hand.

Did they hire you to do what you're told, or to do the right thing? If "the implementation SCREAMS for tabs", do some usability testing which presumably will back up your argument and convince the client. If five random potential customers all prefer tabs and your client doesn't, perhaps he's willing to admit that he'd rather sell his product than have his own way in the design.