Let's talk UX [part 2]: The team

I'm a Tech Writer and therefore I can't help but get obsessed with content structure: Definitions go first, then, the body and last the examples.
Before diving into more specific aspects of UX it's important to understand what an UX team is composed of, what are the related disciplines, roles involved and what their goals is. In today's chapter I'm gonna tell you how my team is. This doesn't necessarily mean that all teams are or should be like that or that they should do the same type of things or have the same focus. It's just an example.

About the team's structure

In terms of structure and resource allocation, a UX/IX team can work independently from other teams or it can be part of teams especialized in different disciplines.
At Atlassian, each product has an engineering team, and also a group of people dedicated to UX/IX. Depending on the product's size, teams might share more or less resources at some point. The following diagram shows our hierarchy:


                             Design UX  /   Core IX

 Designers - Writers - Analysts - Researchers - UX Developers

Some companies have a different approach and we can find the following structure:



                      IX(Information Architecture)
             Other models are focused on support such as the following:


                             Design - UX - Support

This subject is similar to Agile methodologies: everyone use them, most people apply them wrong and the theorie's pioneers get pissed about it. Thus,each organization does whatever they want, the way they can (sometimes).
Having one structure model or the other depends partially on the size, resources availability and the knowledge and focus of the company.


I'm gonna give you a rough idea of our current formation and the responsabilities of each role.
A bowl of bananas Designers There are different types of designers, some of them are usability experts whereas others are focused on user research. We have a few of each type helping to shape pure awesomeness.

A bowl of bananas Technical Writers

Writers are a key part in the whole team since they're not only creating technical content but also analyzing content targets, users and designing Information Architecture patterns.
One day I'll tell you stories about teams that suffer the lack of writers or teams that have bad writers and suffer equally just to exemplify the relevance of this position.

A bowl of bananas Analysts UX analyst usually come from different fields and most of their work consist of defining and executing user analysis and retention strategies. It's important not to get confused with marketing retention strategies. Analysts play with specific metrics around new designs, documentation systems, and combined solutions. The challenging part for them is trying to make sense out of those numbers in a context as fuzzy and hard to measure as human experience. It's because of this reason they must always use a holistic approach to this type of analysis.
A bowl of bananas


We have different type of researches. Some of them are focused on design testing and others are closer to Information Architecture usability and metrics.