Guru allows your team to quickly leverage the content they need, when they need it, without leaving their daily workflow. The following article provides guidance on creating content in a way that sets you and your team up for success.


ā¯—Important

You must be an Author or Collection Owner to create Card content in Guru.


Tips when Creating Card Content

Add High-value Knowledge First

The first content you add to Guru should be high-value knowledge that your team accesses frequently. When a user sees meaningful, up-to-date content in Guru when they first access it, it shows them that Guru is their single source of truth and can help them respond to customers more quickly. It's also important to have enough content for the team to evaluate Guru's impact.

  • Examples of a high-value knowledge includes Product FAQs, Sales assets, Competitor information, Troubleshooting guides, and key process-oriented information
  • The primary use cases should be added prior to rolling out to the team, so users don't enter an empty account. In addition to yourself, we recommend inviting your subject matter experts to assist with your content curation.

Create Cards with search in mind

Content should be easily searchable and discoverable by your team. The title of a Card should reflect the way a user would typically search for the information it holds.

Avoid Duplicate Information

Avoid duplication of information so you're not having to manage more than one Card covering the same contents.

Note that the same Card can be viewed on multiple Boards (as long as the Boards are in the same Collection), and you can link Guru Cards to each other.

Create easy to consume Cards

Cards should be easily consumable for the user to digest and then relay to customers or other teammates. Unlike docs stored in a shared drive or other repository, Guru's Card design is ideal for surfacing the most relevant content in just a moment. Cards are more likely to be read and consumed if they are less than 1,000 words in length (which equates to a one-page doc).

Break content down by subtopic

If the general topic is Product FAQs, each question and its answer could be its own Card. This allows your team to search and find just the bit of information they're looking for, rather than scrolling within a longer doc.

Did this answer your question?