How are teams verifying new Cards within Collections?
Hey! Curious how people are approaching verifying new cards within collections, as I wonder if we've over-engineered our approach. Right now, we have 8 verifiers (called guru gurus) split by segment/product who are meant to review new cards as they come in and check against relevancy, recency and make sure it's not duplicative. In reality, there are only a few people on the team, mostly on Ops or senior members, who are adding new content to the collection. Their content doesn't need to go through the "guru guru" check. *Basically - how do you successfully gatekeep new content to your collections?*
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.
We've taken a reverse approach where we don't gate content at all. Instead, we encourage everyone to contribute where they feel comfortable and then assign subject matter experts to areas as verifiers. The SMEs are primarily responsible for the content's accuracy, and I cover down on basic formatting, organization, and other administrative tasks. I've created a tool that allows me to verify content on behalf of others so that I can make small changes to content without bothering anyone with a verification request. This approach isn't for everyone, and it certainly has its pitfalls, but it has allowed us to generate around 500 fairly useful articles in less than 2 years.
Personally, and to your point - I'm very okay with shoddy articles if it means my team(s) are moving closer to something resembling Guru's knowledge philosophy (https://app.getguru.com/card/cxgKkExi) but do you wonder if the capability you've enabled for yourself may have unintended (negative) consequences or accusations?
Also, love that Guru knowledge philosophy card. I didn't know about that. :slightlysmilingface: