Create workspace fields to capture metadata
Without a standardized system, every project is its own island. Researchers recreate the same fields over and over, often with slight variations. This makes it impossible to search, compare, or synthesize findings across studies. Your workspace becomes a collection of disconnected files, not a powerful knowledge base. Use Workspace Fields to create a single, standardized set of metadata (likeProduct Area
, Research Method
) that can be applied consistently across all relevant projects.
Workspace fields are housed within workspace field groups. These groups can be linked to multiple projects at once and appear on your data alongside project-level fields.
- To create a workspace field group, go to ⚙️ Settings → Fields.
- From there, you can populate this group with note fields and/or insight fields and select the project/s you wish to link to this group to.
What are some examples of workspace fields should we use?
When creating workspace fields, it’s crucial to distinguish between fields for your raw data and fields for your findings.Here are some examples of fields you can use at a global level:Note fields: Organize your raw data
Use note fields to answer the question: “Who gave us this feedback and under what circumstances?” These fields add context to the source material.Field title | Field type | Field value examples |
---|---|---|
Data | Single select | Interview, Survey, Document |
Region or Market | Single select | APAC, EMEA, AMER |
Interview stage | Single select | Scheduled, Conducted, Analyzed |
Interview round | Single select | Round 1, Round 2, Round 3 |
Insight fields: Organize your findings
Use insight fields to answer the question: “What did we learn and what should we do next?” These fields add business context to your analysis.Field title | Field type | Field value examples |
---|---|---|
Report type | Single select | Final, Atomic finding |
Research method | Single or multi select | Mixed methods, Surveys, Secondary, Exploratory |
Business unit or Product area | Single or multi select | |
Company focus area or initiative | Single select | |
Region or Market | Single select | APAC, EMEA, AMER |
Action required | Single select or check box | |
Priority | Single select | Low, Medium, High |
Prevent changes to a workspace fields
Even with a shared set of fields, a well-meaning team member could accidentally edit or delete a crucial field or option, breaking the consistency for everyone and corrupting your repository’s structure. You can prevent others from making changes to a workspace field group in ⚙️ Settings → Fields or within a linked project by restricting its access.- To do this, open the workspace field group, select Share and assign View only access to the workspace. You will be the only user with Full access to the board.
- From there, you choose to invite other team members to share Full access or Edit access to the board.
Using workspace fields alongside contact fields
Think of workspace fields as the standardized backbone of your research data, ensuring consistency across all projects. Within this framework, contact fields are your dedicated toolkit for capturing crucial demographic and identifying information about your customers. The key to a powerful Dovetail setup is not to view them as separate entities, but to leverage contact fields as a well-defined group within your broader workspace field structure.Feature | Workspace fields | Contact fields |
---|---|---|
Definition | A set of standardized fields that can be used across all projects in your workspace. | A user-defined group of workspace fields specifically for capturing customer contact and demographic data. |
Purpose | To ensure consistent data collection and enable cross-project analysis. | To create a detailed and reusable profile for each research participant or customer. |
Examples | Research Method , Date of Interview , Product Area , Feature Request | Email , Company , Role , Persona , Customer Since , Industry , Plan , Region |
- All feedback from the “Product Manager” persona across all usability tests.
- How feature requests from “Enterprise” customers differ from those from “SMB” customers.
- The most common pain points mentioned by customers in the “EMEA” region.
To put this lesson into practice, create a workspace field group and populate this with data and insight fields for your workspace. Create workspace fields →