Standardizing Team Workflows

·
·

Are you a workspace admin thinking about how you're going to standardize all the work your teams are doing? Here's some advice from our success team resident expert Daniel Smith. How have you seen success with enabling your team(s) in Dovetail? put-the-customer-first

  • Avatar of Miriam Donath
    Miriam Donath
    ·
    ·

    Jeremie Gluckman and Daniel Smith, Can you please elaborate on the difference between Tags and Fields? I feel like I've read everything that Dovetail has on this, but I still don't understand under which circumstance each is used. Are Tags only for specific parts of interviews and Fields apply to individual interviews as a whole? For the sake of argument, let's say that we plan to have all Fields and all Tags be global across all projects.

  • Avatar of Daniel Smith
    Daniel Smith
    ·
    ·

    Hi Miriam, This is a great question. I think of these things in the following way:

    • Tags: these are relevant only to a specific highlight or snippet of an interview. These are containers in which you want to collect very specific snippets of interviews. Examples include:

    • Features

    • Tasks

    • Behaviors

    • Sentiment

    • Next steps

    • Fields (let's distinguish between note and insight fields as well)

    • Note fields: this is information that you want to record with every piece of data (note) that you upload. Generally for an interview I would include demographics like (role, company, industry). In general I think differing these by folder makes sense for a lot of teams.

    • Insight fields: This is information that you want to be captured with insights that are published. Examples here include product area, report type, persona, stage in the customer journey, and so on. I do think that in most cases it makes sense for insight fields to be uniform across an entire workspace. This was you can filter down search results, or build feeds that only show insights related to a product area for example.

    Hope this helps! Dan