See announcements and guidelines for the Guru Community
- 60 Posts
- 195 Replies
Guru Deep Dive Recap: Automating Guru Workflows
Hey y’all! Today we dove into automated Guru workflows. Shoutout to our speakers for sharing examples! @Mary Houston @Kristin Fretz @Hassan Muhammad and Ewan Farry Common challenges around this topic include: Context-switching between workspaces takes time Process management has gotten a lot more complicated in a remote/hybrid working world It’s hard to find time to unpack insights about how team members are using Guru Tips for automating a workflow: Define your challenge. What am I doing manually, that there could be a workaround for? Is there a way to get notifications to manage tasks in a place I’m already looking on a day-to-day basis? Design your workflow. Start with: The trigger (the first activity) The action (the correlated activity) The end result Automated Guru Workflow Ideas included: Topic: Timestamp: Managing Verification 8:25 Managing Verifying Groups 10:53 Jira Example 13:15 Managing Permissions 13:44 Managing Comments 13:53 Favorite Card
Strategizing for the Future of Hybrid Work
Come join a discussion about the future of hybrid work with @Alicia Agnew (Sr. People Operations Manager at Guru) and Vicky Yang (VP, People Ops at Bonusly) on Tue. 8/17 at 1:30pm ET / 10:30am PT! They’ll share guiding principles that inform their own workplace strategies, and the tactical action items you can take to form an effective hybrid work model for your organization. Learn more and register here!
Feedback needed on next steps for the Slack community
What do you think about this new community platform in comparison to our Slack community?Happy Monday Thanks so much for all of the feedback so far, please keep it coming! To kick off week two of our early access period, I'd love to hear your thoughts on our plan to phase out the Slack community in the near future. Here's some important context:We're on the free version of Slack, and as such message history gets wiped out frequently because we've far exceeded the messaging cap. This means there is no searchable history of all of the rich knowledge sharing that happens over time. Note: this is just one drawback to maintaining our community on Slack; it's an amazing tool for internal collaboration, but even Slack has said very clearly that it's not built for communities like ours. We believe the best experience for Guru Community members is to have one go-to place for asking questions, sharing tips and advice, and connecting with the community and Guru team. That said, we welcome feedb
Guru Deep Dive Recap: Centralizing Knowledge
Yesterday we gathered to hear tips from Martin Theobald, Knowledge Manager at Crisp and Matt Garren, Senior CSM at Guru for centralizing knowledge and structuring content in Guru. Common challenges folks raised around this topic include: Knowledge is all over the place, living in people’s heads and multiple platforms Investing time into knowledge is perceived as difficult Structuring content and keeping it verified within Guru is an initial blocker and ongoing challenge Tips & Tricks for Centralizing Knowledge:Survey team members and review existing technology to evaluate KM landscape Lean on energized teammates to accelerate a culture shift Focus on centralizing the knowledge you need now—don’t try to boil the ocean Walk team members through an activity to help them identify their knowledge needs and break down knowledge creation into manageable sprints When creating information architecture, consider: Access controls Content structure When mapping content
Getting access to the Guru Community
Leave feedback for the new Guru Community
Welcome to Guru’s new community, we’re excited you’re here. Here’s what you can expect during our early access period:You'll be part of a small, VIP group of initial members -- your active participation is greatly appreciated! You'll receive a limited edition "Trailblazer" badge and bragging rights for being an OG community member It's a work in progress, so please share your feedback in the thread below. Specific actions to take: Respond to existing posts, or create a new post Share your feedback in the comments below on how we can improve the experience of the new Guru Community. If you had a magic wand, what would you change? What’s confusing? Upvote a product feedback suggestionPlease note: our Product Feedback area is still under construction, as we tidy up prior posts shared in SlackShare any of your reactions, thoughts, or questions below in the comments.Happy posting!
Big news re: the Guru Template Gallery!
We have big news! The Guru Template Gallery has officially launched on Product Hunt. We have over 97 templates including NEW templates for every role that cover a range of topics from internal communications to employee onboarding to product management. If you like our templates, please give us an upvote on Product Hunt! 🤗
About Product Feedback statuses
What does the status on my feedback mean? First of all, thank you for sharing your thoughts on what changes would be helpful to you! Customer feedback is a major part of our decision-making process for improving Guru so we rely on customers like you to share your thoughts.Now that you’ve submitted a piece of feedback and it has a status, you might be wondering what that status means. Read on to find the answer to that very question! Status What it means Open All new posts will be in this status by default. Accepted We intend to find a solution to this problem, but we don't have a specific plan in mind yet. We may be actively thinking about or researching it. Posts in this status are usually in open discussion. Scheduled We have a specific plan to address this problem, and it is slotted into our backlog or roadmap. It may be something we can solve in the near term, or it may take longer. Either way, we intend to solve this with a change to Guru. Complete A s
Safe Harbor statement
Information shared by Guru employees on the Community is intended to outline our general product direction.It is intended for information purposes only, and may not be incorporated into any contract.It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions.The development, release, and timing of any features or functionality described for Guru's products remains at the sole discretion of Guru.
How to share product feedback
Hello and welcome to the Community!We love hearing about how changes to Guru could improve how well it works for you. The Product Feedback area is the best place to share your thoughts on what could be different. All of us Product Managers spend time in this section of the Community every week reviewing what’s been shared. Posts with many comments and votes (especially from multiple customers) are of particular interest because that activity indicates that the problem described is one many people are facing. In order for us to quickly get to the heart of what you’re sharing, we ask that you keep the following tips in mind when posting feedback.Describe the problem, not the solution Give details, provide examples, and tell us about the problem you’re trying to work through. The most actionable feedback describes the nature and scope of the problem, not just what functionality is needed. Try to answer these questions when posting: What is the problem? Who is it a problem for? How do
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.