How to spend your first month in a UX research role (and stay friends with your new work colleagues)

David Travis
Sep 10, 2018 · 7 min read

When you start a new job as a user researcher, you need to both charm your work colleagues (so they take action on your future research findings) and challenge them (so they become more user centred). How can you best achieve this in your first 4 weeks in a new job?

Photo by Charlotte Coneybeer on Unsplash

One of my favourite user experience quotations comes from user researcher Harry Brignull, where he writes: “A researcher who is keen to please the design team is useless.”

One reason I like this quotation is that it makes the point that as a user researcher you are like the grit in the oyster. In the same way that the grit irritates the oyster into growing a pearl, the user researcher is continually finding problems. These might be problems with the initial design concept, problems with later designs or even problems with the fundamental purpose of the product. Your role is not to please the development team but to push them to do better work by understanding users.

There’s an obvious risk with this however — the irritation can be taken too far. When you start a new job, it’s important not to appear like a know-it-all smarty pants and be overly critical of what has gone before. After all, you are not yet aware of the constraints the development team is under. Perhaps some of those ‘bad’ decisions were in fact the ‘least worst’ decisions that could be made in the circumstances.

So you’ve started a new job. How can you irritate your colleagues and still stay friends with them after work?

Week 1: Map the territory

As a user researcher you will interact with everyone on the development team and many people beyond. Part of your job is to connect these people and create a shared understanding of users and their goals. Think of yourself as the glue that makes a good user experience happen. A good way to achieve this is to get all of your colleagues involved in user research, both by observing and taking part in research sessions. And if you’ve just started the job, this means spending time getting to know people and allowing them to get to know you.

So an effective way to spend your first week is by mapping the territory. What is the product about? Where does it sit in relation to other products? Who makes decisions and whose opinions matter?

You can get this information through informal interviews and meetings. You may need to schedule some of these, especially with the busier members of your development team. But not all of these need to be formal: conversations over coffee or lunch, water cooler conversations or corridor meetings will all work.

Your aims in this week are to:

  • Understand the constraints the team is under. What can and can’t be done with the technology? What’s driving the timeline?

Week 2: Help your team understand their users

Your most important responsibility as a user researcher is to help your team better understand their users. The team need to appreciate that there are different groups of users, that some of these groups are more important than others, and that one, or maybe two, of these groups will be the design target. Then you need to help the team gain an in-depth understanding of their users’ goals, motivations and abilities.

Your aims in this week are to:

  • Start compiling the research that has been done with users in the past. This could be research done by the team or organisation or by external researchers, such as universities.

Week 3: Help your team understand their users’ tasks

Tasks are the activities that users do with a product in order to achieve their goals. Helping the team think in terms of users’ tasks, rather than system functions, is an important step in getting the team to see the big picture. This is because users’ tasks almost always require the use of several functions to complete, so it prevents siloed thinking.

Your goal this week is to identify the red routes or top tasks that users carry out with your product. This prevents the team from treating every function as equally important and helps prioritise development.

Your aims in this week are to:

  • Speak to team members and create a list of all possible tasks. Then get the team to identify what they think are users’ top 10 tasks.

Week 4: Run a usability test

Running a usability test is always a good early activity to do when you join a new development team because it will help you flush out the influential stakeholders and gauge their attitude to involving users in your work. It will also give you an idea of the budget that’s available: is there a usability lab, or are you allowed you hire one? If not, can you do remote, moderated usability testing? Or are you restricted to guerrilla, ‘pop-up’ usability tests in coffee shops?

In terms of what you should usability test:

  • Test the current product or prototype — or if there’s no product yet, test the top competitor with around 5 users.

Your aims in this week are to:

  • Get the team to observe at least one session, preferably live. If that’s not possible, get each team member to review one of the session videos. And if that’s not possible, create a highlights reel illustrating the main findings and present this in a show and tell.

Parting thoughts

When starting a new UX job, people tend to ask themselves (often implicitly): “How are things done around here?” Then most people, over time, fall into step, or adjust their working practices to fit in — thereby negating the whole point of their being hired in the first place (since you are generally hired for what you can bring to the party — not because you can replicate what the organisation is already doing).

On the other hand, to charge in and try to change things too quickly is a sure fire way to make your team hate you. You need to walk a fine line between irritating your new colleagues and challenging them to become more user centred. Try some of the ideas in this article to see if you can get the development team to create a few pearls.

Originally published at

David Travis

Written by

User Experience Strategist @userfocus. On a mission to create more UX professionals. Get free online user experience lessons at