information architecture - How to prove a design opposed by the product stakeholders?

We've been working on/off on an account/bar header for a large corporate site for nearly a year now.

We've got so many stakeholders that nobody can ever agree what should go there!

What tools/ways/arguments do UX pros have for sorting this stuff out!

We have quantitave stats on header links useage, but many of those could be false positives (ie, if you put a link in the header, then people are going to click on it!).

BTW - I'm doing some usability testing on the Beta site on Thursday - can I use this to somewhat get some clarity on the situation!

Answer

I think its more about politics and people than about statics and testings. Nevertheless those give substance to your arguments.

In mettings at presenting your design:

• Keep in mind what history and interests your colleagues stand for. Be prepared for it and have arguments for that.



• Identify who is against your arguments and why. Sometimes its best to have a single meeting and presentation with them before. so you can go more into detail. Take their concerns serious, this can work as a dooropener.


• Invite stakeholders to your UX-Testings, so they can see how people struggle with the actual design.


• Invite stakeholders to Design Session and get a Buy-In. Nobody would argue against own ideas - (actually you can spin ideas in right direction during the Session).


• Try to get buddies. Make favours for some and get favours back.

More tactical:

• Step back on some minor points and get your big point win.


• Present minor designs first, so people can get their heads dive into them. Later or last present your most important design - people havent much energy now, got some winning fights and are more likely to wave your design through.


• If nessesary make a special meeting for a very debated/unclear point. So the meeting is going on and not disturbed by just a single tpoic.

Your arguments/points can be supported by:

• UX Testing Outcome


• Interview quotes


• Analytics


• KPI improvements (if numbers matter)


• ROI on new design (if numbers matter)


• Sketches


• Prototypes

And here is a good article about how to manage and prepare this kind of decision-making meetings at Uxmag.com.

Selling UX at UXmatters

Communicating the UX Value Proposition at UXmag

Where's the Value? Return on User Experience (ROUX).