> For the complete documentation index, see [llms.txt](https://help.dscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.dscout.com/guides/courses/from-usertesting-to-dscout/translating-usertesting-vocabulary-to-dscout.md).

# Translating UserTesting vocabulary to Dscout

Before we cover the specifics of conducting research in Dscout, let’s make sure we’re speaking the same language. If you’re coming from UserTesting, you’re likely familiar with their tool names and vocabulary.

## UserTesting vs. Dscout vocabulary

Dscout emphasizes real-world, longitudinal research through media-rich methods, and the terms we use reflect that. Here’s a breakdown of some of the most commonly-used terms in UserTesting and their Dscout equivalents:

| UserTesting term                                                       | Dscout term                  | Description                                                                                                                                                                                                                                                           |
| ---------------------------------------------------------------------- | ---------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Contributor**, **tester**, or **user**                               | **Participant** or **Scout** | Someone who takes part in a Dscout study. The generic “participant” refers to participants of all types while “Scout” is used to refer to those who come from Dscout’s proprietary panel of on-hand participants.                                                     |
| **Test** or **study**                                                  | **Study** or **mission**     | The core research activity used to collect data and insights. “Study” and “mission” are used interchangeably throughout Dscout to refer to diary studies, media surveys, usability tests, or live interviews.                                                         |
| **Folder**                                                             | **Project**                  | A container that houses studies and screeners. Projects allow you to organize multi-phase research projects under a single umbrella.                                                                                                                                  |
| **Workspace** or **team**                                              | **Workspace**                | The top-level area for organizing projects, collaborators, and permissions. A researcher may be part of one workspace or multiple.                                                                                                                                    |
| **Invite network** or **custom network**                               | **Bring your own (BYO)**     | A recruitment option that allows you to invite your own participants (customers, employees, etc.) via a shareable link. These participants are yours and will remain that way: They will not be added to Dscout’s Scout Panel when you invite them to a Dscout study. |
| **Unmoderated test**, **think-out-loud test**, or **interaction test** | **Usability test**           | A task-based study that offers screen recording, prototype testing, and more.                                                                                                                                                                                         |
| **Live conversation** or **moderated session**                         | **Interview**                | A scheduled, real-time interview between a moderator from your team and a participant. Stakeholders can be invited as observers and guests with restricted functionality, including the option to observe invisibly.                                                  |
| **Video clip** or **highlight reel**                                   | **Playlist**                 | A collection of tagged, clipped participant video responses used to share findings with stakeholders.                                                                                                                                                                 |
| **Video review** or **notes**                                          | **Tags**                     | Labels used during analysis to categorize moments by theme or behavior. For example, **pain-point: checkout**.                                                                                                                                                        |

These are the UserTesting-specific terms for which users most often find themselves seeking the Dscout equivalent. With those out of the way, let’s dig a little deeper into building your research framework within the Dscout platform.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.dscout.com/guides/courses/from-usertesting-to-dscout/translating-usertesting-vocabulary-to-dscout.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.