Choosing a Verifier and Verification Timeline
Roles: Read Only, Authors, Admins
Guru's verification engine allows you to confidently leverage the content on Cards. To ensure that your team trusts the information, it's important to choose the appropriate subject matter expert or Group of experts to approve it. The verification timeline determines how frequently they're asked to update a Card; selecting the appropriate timeline ensures that they'll be asked to update Cards at the appropriate intervals and the information will remain accurate.
How to Choose a Verifier and the Verification Timeline
- When saving a Card, you will be asked to select the verifier and verification timeline. The default verifier is you (the Author) and default timeline is 90 days.
- Your team trusts Guru because they know the content is verified and up to date. With that in mind, it's important to choose as a Card's verifier the subject matter expert who has the best knowledge of topic. For example, if creating content on the API, the lead back-end engineer would be selected as the verifier.
- If information belongs to a group of people, you can select a Group as a verifier. For example, if 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.
- The verification timeline varies greatly based on the content and plans of your team, but it's important to ensure that the timeline you select reflects your internal processes. For instance, 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.
- We recommend that teams average at least a trust score of 80%, as this means that only 1/5th of the information is unverified. 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.