Dovetail Champions Icon

Dovetail Champions

Join the Community

Ensuring Quality Assurance for Insights in Dovetail: Best Practices Needed | Dovetail Champions

Customer Support

Customer Support

Ensuring Quality Assurance for Insights in Dovetail: Best Practices Needed

·

·

Hi all! I am currently working on the quality assurance for all research projects and Insights in Dovetail, while we are rolling out the platform to the organization of +20.000 employees. We are currently experiencing that some users are publishing Insights, without them being actual insights, and as a result, we are seeing a lot of published Insights in our feeds that does not say anything relevant. We have a template that we request users to fill out before publishing an Insight, but these are also not being followed. We want viewers to be able to use the search tool to look for and find new Insights and relevant information across the projects, so we cannot just make people move the insights to a folder when they are done, and then giving viewers rights to view that folder and nothing else. I am therefore looking for inspiration on how others have ensured quality in published Insights and the platform in general? What have you done to utilize the platform agility, while still ensuring relevant content and is there any best-practices for quality assurance in Dovetail? Any help and/or tips is greatly appreciated!

9 comments

armina
·
·
hi Andrea, i don’t have a solution for you, because we’re also struggling with very similar issues of increasing adoption while still maintaining some guardrails in place 😭 i’m more curious to hear if you’ve been able to identify what the main challenges are for your stakeholders? especially re:
We have a template that we request users to fill out before publishing an Insight, but these are also not being followed.
do you know why they’re not following the templates you created for them? that would be my first step — try to conduct some internal usability sessions with your main stakeholders to identify their main pains with your proposed workflow. we’re working with a small group of contributors, and we still have to offer a lot of 1on1 support in addition to the templates, but obviously this is not scalable. so we’re also doing mini interviews or group brainstorming sessions with the contributors to understand: a) what their main issues are with the documentation we’ve already created for them, and b) what improvements to the documentation would make it more usable. that said, i think Karolina Kowalczyk had some good examples of using templates in Dovetail to make it very simple for her stakeholders to be more independent 🤓 but of course, what works for one team doesn’t necessarily work for another.
👍1
Karolina Kowalczyk
·
·
Hi, Andrea B.! Have you tried having an insight template in a project template? I feel like this helped us a lot, because since people forget about insights templates, they always create a project from a template 🤔 At Appfire we invest a lot in documentation on Confluence and internal training, but it is still hard 😞
👍1
Ashley
·
·
We're about to do a roll out as well and this is a big concern. I wish there were an option for approvals before publishing an insight, but in the meantime we have a couple of ideas:
Have insight templates nested in project templates.
Filtering out insights from feeds that don't have values for required insights fields (each insight + template has the same standard fields).
Filtering out insights from feeds with poor/unclean naming conventions, like "Untitled" or "DRAFT" or ".csv"
We're also looking to implement a training for anyone w an analysis license and will have them review that training before allocating a license to them.
Having a "quick insights" insight type that gives folks permission to publish less detailed things, but also reduces its credibility and can be filtered out if you log it as such in an insight field.
🙌5
❤️1
Britt
·
·
Thank you for sharing these ideas Ashley! I'm interested in the "quick insights" type. Is this a workspace field? Is there an associated template?
💚1
Ashley
·
·
Britt Yes, its generally pretty flexible. Its a workspace field and theres a general template that goes w it. Its pretty basic: AI summary up top, Highlight reel in the middle with a header for context, then a search block at the bottom that can display the tags or other notes within the project depending on how they wanna approach it. If they want to do more than that, great! Otherwise this at least gives some kind of minimum expectation for reporting among PWDRs. and if that insight type field is empty, it gives us a basis to filter reports out of our feeds by since its standard for all insights in the workspace
🙌3
armina
·
·
so useful to see this example Ashley thanks so much for sharing! i haven’t seen Live feed or Round up as examples of insight types — could you briefly explain what you use those for?
Andrea B.
·
·
Yes, we have an Insights template that is connected to our project template. I just noticed it was called untitled insight, so I renamed it to Insights template - Please use when publishing. Hope this helps. The Insight type fields seems amazing! I will definitely try that. I also really like the "send to feed" option, as that may help people make sure only the intended insights are published to a feed. Does any of you have any ideas on how to change the "newest insight" space on the frontpage to only take information to the feeds under that "send to feed" option? To ensure it doesn´t just show all published Insights that may not be intended.
Ashley
·
·
No problem! the "live feed" was a half baked idea I'm thinking of removing. basically I had some insights with a persona battlecard and a "live" feed of new interviews across the repo coming in from that persona pulled in from a search block. For the round up, its more for research newsletters and similar types of curated reports. I pasted my logic for my Recent insights feed, as well as for my marketing feed where i have the send to feed logic set up.
❤️1
🙌1
2
Paul P.
·
·
Hi Andrea B. and all 🙂 . A while ago I gave Dovetail feedback on "Easier workspace content maintenance & mandatory fields to publish". Maybe you could take a look at it, because I think from the information you gave, you might be facing similar issues to the ones I mentioned in the feedback: https://feedback.dovetail.com/feedback/p/easier-workspace-content-maintenance-mandatory-fields-to-publish-1
👀3
🙏1