Crownpeak DQM vs Guru

• Ensures quality and consistency of content implementation across distributed teams and markets.
• Quick and easy content updates across global digital ecosystems.
• Custom checkpoints to identify, highlight and manage business updates across multiple websites (e.g. product detail, terminology, customer messaging, brand updates)

Read full review

• Easily accessible > you can use the extension in any browser you are in. This helps us as we live in Slack and Zendesk
• Easy to read > The cards are easy for the agents to read through and click on videos
• Easy to create cards > We can create a card from the extension, we do not have to log into the website to create a card.

Read full review

• It would be helpful if the Issues page under Website showed the WCAG level for each issue (A, AA, AAA). You currently have to look up the guideline to find the level.
• There is no indicator that a page is currently being scanned. During a website scan, some of the reports are blank or missing information. Having a notification on the main page showing which websites are being scanned would be helpful.
• Some ADA compliance items are left off, such as keyboard navigation, tabbing, etc.
• It doesn't view the websites on mobile devices or if using a screen reader. Some pages or formatting changes depending on resolution. The DQM, from what I have seen, doesn't account for that.

Read full review

• Engagement with engineering teams is still an area for improvement, we are unable to get our engineering team to adopt the tool as a means for their own knowledge management product because it does not offer the same functionally such as hosting and revision control - like that of GitHub.
• Using Guru to replace our current wiki (Confluence), we are in need of some other tools such as templates and better import functionality. Transferring existing content from Confluence to Guru was a very hands on and time consuming process.

Read full review

• When driving Customer Care, it was great to be able to add the Autofix tool to the web estate - a quick-win that really drives the accessibility agenda.
• Building reports off the back of DQM gives senior stakeholders an understanding of the importance of usability and accessibility.
• The gamification of league tables highlights to stakeholders the areas that need focus and budget in order to improve.

Read full review

• Our ticket resolution times went from over 8 hours to just over 2 hours.
• We no longer have a continuous conversation between support and developers allowing developers to focus on developing.
• Having the same information across teams has proven helpful too.

Read full review