Workflow
Here's a guide for all the levels of Collaborator User Researcher and Expert User Researcher.
The breakdown described here offers a way for Experts and Collaborators to keep track of their progress and make sure the quality of the deliverables stays consistently high. It also helps split the work and payment between two people in order to recruit new Experts.
Consider the following when splitting the work and payment with a Collaborator:
  • The recruitment bonus will be issued in accordance with the amount of work you delegate. The more you delegate, the higher will be your bonus.
  • Some tasks will require your full attention (like workshops) where you will need to be present. Discuss with your Collaborator how to split the payment for those tasks.
  • Other tasks are easy to fully delegate, please make sure you have enough time to fix the errors in case the result is not acceptable.
  • You will agree on a split before the project starts and will not be able to change it afterward. Make sure you review your Collaborator's previous work and fully trust them.
For more insights and advice on how to choose a suitable collaborator, read this page:

  • When shadowing (observing) a user interview or user test, make sure your camera and microphone are off. This is to allow the user researcher to have a one-to-one relationship with the participant and to avoid the user being distracted or responding to what you might say or do.
  • But be an active listener! Try not to check messages or do other activities that will draw your attention away from the observation.
  • You may be asked by the researcher at the end of the session if you have any questions you would like to ask, so think about this during the session. If you don’t have any questions, that’s fine too.

To make the deep work for the user researcher easier, they need this board populated with tester names (top row), sections of the app (turquoise row left) and sprint questions (bottom three yellow rows). More details can be found on this Loom.

First find out what it is we want to learn during the user test, from the designers and sprint facilitators.

Take over the responsibility of running a user interview from the Expert after witnessing some for yourself. For a detailed guide into interviews, refer to:

Running 3 interviews, irrespective of their order or whether one of them is the first interview. Please refer to UR6 for details and examples.
Additional information on Interviews

Don't worry, the first time you talk to people is always unusual and a bit more challenging. Especially showing strangers something new and expecting their feedback could make everyone nervous. But that's not a problem - be honest, be nice, there will be results either way and you will have another 4 interviews. For interviewing guidelines, refer to:

Taking notes during a user session is important for the researcher to refer back to later. You can take notes in a plain google doc. It doesn’t need to be neat or fancy. The objective is to capture as accurately as possible what happened in the session. Good note-taking is:
  • Verbatim of what the user says and does (important)
  • Try not to let your own thoughts and biases decide for you what to note down and what to leave out. (important)
  • Include observations or insights if you find them (less important). If you do have personal thoughts/insight to log, make sure it is clear to the researcher/note-reader which are your ideas, and which are raw notes from the session.
  • Use different colours to distinguish the type of feedback visually. This will help later to work through what's really important.

Tidying up the user interview notes helps the interviewer do their job faster. It's basically about arranging them by colours to make them more skimmable. Watch this Loom for more info.
Tidying notes

Gathered data analysis is an essential process of user research. Here is the moment where your knowledge of psychology and human behaviour will come into play to be able to make sense of all the data points gathered from the interviews.

  • By clustering similar feedback you will be able to recognise patterns of current behaviours and perceptions of users and organize those into consistent signals.
  • It will make it easier to relate those signals to the client's research questions (or goals) and certain design decisions which will make recommendations for the next iteration more obvious.
  • Overall it will streamline your process of report writing - after the analysis step, you will have clear insights which could be used in the report.
Good analysis examples: Integral ZigZag Unlock protocol
Analysis board
Analysis process

The presentation file will be used during the final presentation. It should look nice, have screenshots of the product at the related parts of the user research. You can use the following file and make a copy of it. Ask your Expert for access to pitch.com so you can edit it.
Make sure you don't edit the template but create a new presentation.
Please follow the slides of the template precisely and use the format to fill in the content. It should look nice and professional.
On some slides, you will have to create screenshots of the product in Figma, so they visually blend into the style of the presentation.

Open the project prototype in Figma and select the screen you are referring to on your slides by clicking the title of it. Export it as a PNG.
Next, open this Figma file and drop the PNG you just exported inside.
Select Effects and add a Drop Shadow with the color FF0088 and X and Y at 16. Blur and Spread should be 0. Then export the PNG again and you're done.

The Long Term Goal is the key statement decided on during the workshops, which guides the team through the design process. It's a short sentence capturing the vision of the project under optimal circumstances, which you can find on the Miro board for the sprint.
After the notes were arranged by colour or the user feedback clearly written out, you can give a more or less confident prediction, whether the product design is currently in the right direction towards the long term goal. Below are a few examples.
When writing the user research report, you can write a paragraph about whether the user's reactions matched with the expected long-term goal and if not, suggest re-designs to move closer to it.

Writing out the detailed feedback involves very succinct writing skills and diplomatic use of language.

Recommendations serve two purposes:
  1. 1.
    Provide the client with strategic design advice. After listening to your presentation they should feel equipped with enough knowledge to make well-informed decisions regarding product strategy.
  2. 2.
    Give our internal Product Designer feedback on Quick Fixes. These should be shared with the designer after the user research sessions, early enough so they can fix them before the final presentation.
More on Recommendations:
More on Quick Fixes:

The presentation can either be during a single Hypersprint as a conclusion or alternatively as an iteration workshop. Here is a detailed overview of the process:
Copy link
On this page
UR_Shadow — Shadowing or proving domain expert knowledge
UR_Prep — Prepare the Miro board
UR_Guide — Write Interview Guide
UR_LaterInt — Run Later Interview
UR_3Interviews — Run at least 3 Interviews
UR_FirstInt — Run First Interview
UR_Notes — Take Good Notes
UR_Tidy — Tidy up notes
UR_Analysis
UR_Slides — Create a presentation file
Here's how to do it:
UR_LTG — Answer Long Term Goal
UR_SQ — Answer Sprint Questions
UR_Details — Summarise Detailed Feedback
UR_Reccos — Write Analysis Report & Recommendations
UR_Presentation — Present results