Feedback loop for overarching design, layout and feature availability for our knowledge base
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
For example, if someone said, it'd be great if instead of a hyperlink to a company org chart site, the knowledge base would host a widget where I could interact with company org site within the knowledge base platform. If we ever did that, we'd mention that this was received as feedback and we deployed it, or it's on our roadmap.
How do you all collect user feedback from end users regarding these types of initiatives?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hello @drosenst2
ServiceNow Continual Improvement Management (CIM) - By treating this as an improvement opportunity, rather than allowing it to remain only as an email, survey feedback or a chat.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
I think it's helpful to distinguish between feedback on individual knowledge articles and feedback on the overall knowledge experience, including navigation, layout, usability, and feature requests.
For the latter, I'd recommend establishing a dedicated feedback channel where users can submit suggestions. This could be as simple as a Service Catalog item or a feedback form linked from your knowledge portal.
The important part is what happens after the feedback is submitted. I'd suggest having a lightweight process to:
-
Categorize suggestions by type (usability, navigation, new functionality, etc.).
-
Evaluate them based on user impact, demand, feasibility, and alignment with your knowledge strategy.
-
Track decisions and implementation status.
-
Communicate outcomes back to users, including suggestions that aren't moving forward.
I especially like your idea of acknowledging when a change originated from user feedback. A simple "You asked, we listened" section or periodic update can help demonstrate that feedback is being considered and acted upon.
I'd also recommend keeping this process separate from article feedback so that content quality issues and broader experience improvements can be evaluated and prioritized appropriately.
Ultimately, the goal is to establish a feedback loop where users know their suggestions are being heard, evaluated, and, when appropriate, incorporated into the knowledge experience.
And, for more info on CIM:
https://www.servicenow.com/docs/r/it-service-management/continual-improvement-management/cim-landing...