Why you need a UX team (Part 3)

So what exactly do UX Team members do and what do they deliver?

• Team work session: Working together to transform and shape ideas into a tangible, meaningful and usable products. This is when we focus less on documentation and more on brainstorming ideas, sketching designs and shaping your software product.
• User shadowing and interviews: Perhaps the most important and often overlooked step in designing a great user experience is User Shadowing. There is simply no better way to learn how to design for your users than to spend time with them in their natural work environments.
• Research and analysis: Performing competitive research, design trend research and analyzing usage data helps you make informed design decisions.
• Information design:
  • Conducting card sorting exercises: A very simple exercise that helps you gain valuable insight into exactly how users logically group or categorize content.
  • Designing information architecture site maps: Visualizing the overall navigation structure in an easy-to-follow diagram is an extremely helpful way to get all project team members on the same page with what needs to be built and in what order.
  • Creating task flow diagrams and swimlane diagrams: Taking the time to properly design the step-by-step process that a user will need to follow to accomplish a critical task can mean the difference between increasing or decreasing bounce rates, sales conversions and signups.
  • Defines the visual hierarchies: Documenting all necessary screen elements for key screens and assigning a visual weight to each element based on its relative importance.
• Sketches and wireframes: Quick, easy-to-edit black and white line drawings that capture all necessary screen elements; demonstrate a navigation system and overall layout; and begin to suggest a proper visual hierarchy.
• Visual design: Not only is the look and feel of your product important from a branding standpoint but studies show that a great visual design can also enhance the perceived usability and trust of your product.
• Usability testing: Learn how real people would use your product before it is developed. It doesn’t take much effort to gain a whole lot of valuable knowledge.
• Prototyping, prototyping, prototyping: Sure, you can build a house without blueprints – but you shouldn’t. You can also develop a software product without prototyping it first – but you shouldn’t. Creating a non-functional prototype that the client, users and development team can click through and experience as if it were a live product.
• A/B Multivariate testing: Run simultaneous tests of different variations of a single design that will be shown to an equal split of your total audience to see which design performs the best.
• Conversion Rate Optimization (CRO): There is a definite art & science behind increasing conversion rates on your website.
• Front-end assets: In the end, all the HTML, CSS, JavaScript, jQuery, image assets and prototypes should all be packaged up for the development team to use to build the final product.