Choosing a Verifier and Verification Timeline
Roles: Read Only, Authors, Admins
Your team trusts Guru because they know the content is verified and up to date. Guru's verification engine allows you to ensure your team feels confident to leverage the content on Cards. When saving a Card, you will be asked to select the verifier and verification timeline.
Selecting the Verifier
It's important to choose the subject matter expert or group of experts who have the best knowledge of the Card's topic as the Card's verifier.
The default Verifier is you (the Author)
Subject Matter Expert: If you're creating content on the API, the lead back-end engineer could be selected as the Verifier.
Group of Experts: If the engineering leadership managed the API and all Guru engineering Cards, it would be helpful to choose the Engineering Experts Group when asking an engineering question or creating an engineering Card.
NOTE: Any user or user group who has Author access to the Card can be chosen as the Verifier
Selecting the Verification Timeline
The verification timeline determines how frequently a Verifier is asked to update a Card. This timeline can vary greatly based on the type of content in the Card and how often it needs to be updated, but it's important to ensure that the timeline you select reflects your team's internal processes.
The default Verification timeline is 90 days (3 months).
Project Cadence: if you update your roadmap every three months, the roadmap Card's verification interval should be every three months. Choosing this timeline guarantees that when you update your roadmap, Guru will remind you to update the Card to reflect the freshest content.
Evergreen Content: If you're creating a Card with content that doesn't ever change, set the max timeline, every year, that way you will only need to verify it on an annual basis.
TIP: We recommend that teams average a trust score of at least 80%, as this means that only 1/5th of the information is untrusted. Choosing the correct Verification Timeline and Verifier is essential to maintaining a high trust score, and thus ensuring that your team trusts the content in Guru and does not fall back on old habits, such as shoulder-tapping.
Read more about understanding and improving your trust score here.