We often get contacted by potential customers that know they need some kind of help designing their software product or website – but they aren’t always sure how a UX Team fits in. Sometimes a client may have their own development team that they have been trying to stretch into UX designers. Others have a graphic design team that they have been leaning on to fill the role of a UX Team. The most common tipping point that causes a client to finally reach out for help is when their product is either found to be unusable by its users or their site is not converting visitors into paying customers.
To help provide some guidance on who, what and why you may need a user experience design team, I’ve compiled the following from personal experiences we’ve had with our clients.
A UX Team is typically comprised of one or more information architects, visual designers, usability testers, HTML/CSS designers and front-end developers. Often times, a single UX resource can handle one or more of these roles – but if you do not have any of these types of resources on your software or website development team, you should. The truth is, everyone on your project team should be focused on the User Experience but it’s important that you use people for their strengths and not their weaknesses.
To the users of your software product, the User Experience IS the product. If you don’t place a lot of focus on designing it properly, you are not placing a lot of focus on creating a successful product. So, just as you would not have a UX designer develop your back-end code and database, you should not have your back-end developers designing or developing your front-end user experience. We like to say that if the work involves anything that displays on the screen whether it’s as small as changing a label name or as big as adding a new set of screens, someone from the UX Team should be involved.