We are getting ready to implement Guru in a phased approach across our ~350 person remote/distributed company. I’m curious how other folks are helping to define for their users what should and should not go in to their Guru knowledge base? For example, we don’t want users to save meeting minutes in Guru, as meetings and other in-progress work is not authoritative/definitive. What guidance do folk give their users to help make it clear what should and shouldn’t be in Guru? TIA!!!!
Log in to engage in discussions
Use your Guru account credentialsLog in
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Hi Lynn. I’m a Customer Success Manager here at Guru and wanted to give one idea.
I’ve noticed is that some customers do keep meeting records/minutes in Guru. It would typically be just 1 card, with a historical log, with the goal of allowing users to self-serve past meetings that they have missed. We do this at Guru for our Revenue and Company-wide All Hands, and it’s extremely helpful!
I am sure others will chime in with their various governance standards to spark ideas 😄
Hey Lynn! I think about this a lot as I’m going through our collections:
Hope this helps!