Skip to main content

Hey everyone! Carlos from Guru Technical Support here :hand_splayed_tone2:I wanted to talk a little about getting started in Guru. Specifically how to avoid the paralysis that might arise from information living in too many systems.   

Don’t freeze. Make the process a breeze with this three-step process: audit your information, identify the best organizational structure, and start leveraging content when you need it most.

  1. Map out where your knowledge currently lives. Jot down what type of knowledge you currently have, where it currently lives, and who needs it most on your team. Make a copy of our content mapping exercise template to make this easy and simple.

  2. Structure your content in Guru. Read our Different ways to migrate or create content in Guru and  How to scale Groups and Collections articles to learn the best way to setup your new workspace.

  3. Make sure your knowledge appears where you need it most. Install the Guru Extension and practice searching for content by asking questions or submitting keywords. Consider doing user testing to make sure your team members can also find the information they need as well. Use these search tips and tweak titles, Card content, and tag structure depending on your findings. 

Looking for more tips on how to consolidate knowledge and structure content in Guru? Check out our deep dive recap on centralizing knowledge.

After centralizing all of your knowledge into Guru you might be asking yourself how you can increase adoption in Guru. Take a look at the link below to watch a recording of Tori Belkin, Director of Sales at Ceros, talking about her team's firsthand experience in successfully adopting Guru as their knowledge management system:

Trusting your source of truth: How to make Guru your company’s first and final place for knowledge

​What are some ways you’ve combatted information living in too many places and ensured Guru is your central repository of knowledge? 

I look forward to seeing examples from others!

Be the first to reply!

Reply