Enterprise UX Design

I was reading a blog article, " 9 do’s and don’ts of UX design ", this evening and found this particular section concerning: "...sometimes too much corporate oversight can limit the design process, as many clients, who obviously aren’t designers themselves, don’t exactly know what looks and functions best on the web. While they surely have the best intentions, sometimes UX design is best left to the designers—they’re the ones with experience in the field after all." Coming from a corporate environment, this was really more of a whine since it didn't contain any constructive suggestions to handle the situation. So I thought I would share some things I've learned through the years about working with business reps. 1. Everybody is visual. Go with it. While you may have a business analyst to elicit business rules and process and to define the problem, when the solution is a UI it's easier for someone to draw out what they're thinking than to

At my company we've been dreaming of being able to localize our UIs since I started working there. While we have localized here and there for the most part it just doesn't happen. There simply aren't the resources or knowledge. Instead our employees in all branches are required to speak English. I have no idea how branches determine whether a person's ability is up to standard to be hired. I've never seen any guidelines for branch management to follow and admittedly our industry is one where you have to learn a lot of jargon, too. I imagine that may other global enterprises are the same way. This means that your users may struggle to understand your UI, especially those newly hired employees. So part of your user research should be pointed at determining at what level your users can understand written English. Here are guidelines you can use based on the European Framework of Reference for Languages . (See Chapter 9 for more information.) I assigned the readi