Guru's Verification engine ensures consistency, confidence, and trust in the knowledge your organization shares. Learn more.

Authoring Knowledge - Guru HQ Best Practices

What is this card for?

Use this card as a guide when you're creating and consuming knowledge. We have to live what we’re building, selling, marketing and supporting.

When creating a card, Ask yourself these questions:

  • Who am I creating this knowledge for?

  • How are they going to use it?

  • In what situations will they need this knowledge?

  • How will I know if they get value from the knowledge?

  • How will I gather feedback, metrics, and then iterate?

  • Is my knowledge formatted correctly (based on card type) and tagged correctly?

When creating a net-new card from a #product-questions in Slack:

  1. The human who asked the question creates a Guru card with the answered question

    1. Title = Question Asked

    2. Body = Answer to the Question (probably in a Slack thread)

  2. The card is then added to the Knowledge Submissions Collection, onto a board that intuitively makes sense.

    1. Here is a Loom that walks through this process

Why do it this way? This promotes a culture of collaborative knowledge

WHEN updating AN EXISTING FEATURE BREAKDOWN CARD OR FAQ from #product-questions in Slack:

  1. The human who asked the question comments on the existing Guru card with the answer (this can be text or the Slack thread link)

  2. The SME or card verifier amends the card to answer the question, adding context where applicable

  3. The SME or card verifier deletes comment

You must have Author or Collection Owner permission to create Guru Cards. Contact your team's Guru admins to use this template.