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 ...

I don’t know about you, but I hate design reviews. I finish up a bit of work and then I have to present it to the project team. “Wouldn’t that be better if you moved that down there?” “I don’t like that.”  "It should be just like _______." (Several of us call this JLO or "jello".) And of course we have the occasional business owner who thinks they’re a designer. I have grown a very thick skin. Add on top of it that in Agile, you have very, very little time to get design done. There is no backlog of completed design work. We’re lucky if we have a couple days to get requirements and design before dev is ready to work. So any rework is a major issue. As the sole designer I’m holding up the team or worse the developers will start without me. So getting design right without rework is a major issue. But then once you’re pretty sure about your work, the last thing you want is someone to walk into a design review and blow up your work so that you have to completely sta...