Summary
Over the past 10 years, there has been an a ground swell of knowledge systems. Knowledge systems stand on the shoulders of information systems...not only delivering information, but delivering that information in the context of the user's needs. The user experience for these systems has not kept pace with the rapid proliferation of technologies that support knowledge systems (artificial intelligence, machine learning, knowledge graphs). Let's take a survey of these the technology and landscape of knowledge systems, and discover strategies and best practices for implementing knowledge systems. You will: Gain an understanding of the different type and purposes of knowledge systems, and their characteristic advantages and disadvantages Discover the needs of users Methods to implement UX strategies for knowledge systems
Key Insights
-
•
Knowledge systems use graph databases with nodes and relationships modeled after subject-verb-object sentence structures for efficient storage and comprehension.
-
•
Knowledge differs from data and information by being tailored toward human action, not just consumption.
-
•
Graph-based knowledge systems are still immature compared to well-established tabular data systems and lack standardized UX patterns and terminology.
-
•
AI chatbots like ChatGPT provide conversational knowledge access but lack traceability and rich interaction beyond transactional Q&A.
-
•
Knowledge creation interfaces must cater to both creators and consumers, a duality posing UX design challenges uncommon in data or information systems.
-
•
Metadata plays a crucial role in enriching knowledge nodes and managing complex relationships at enterprise scale.
-
•
The abstraction of knowledge makes UX design particularly challenging and necessitates translating conceptual models into concrete, usable experiences.
-
•
Different user groups and industries require context-sensitive language bridging jargon from UX, information architecture, and organizational domains.
-
•
UX professionals have an opportunity to influence vendor product design and internal deployments to improve knowledge system usability from the start.
-
•
A blended approach like the World Economic Forum's transformation maps shows promise for integrating graph-based visualizations with narrative information to enrich knowledge presentation.
Notable Quotes
"Knowledge systems are enterprise level applications that are repositories of a body of knowledge, usually focused on a single topic or related group of topics."
"Knowledge is not only intended for human consumption, it is meant for human action."
"The method of depicting knowledge comes directly from subject verb object sentence diagramming that we learned in school."
"Graph databases use nodes and relationships instead of tables to store information, providing a network of knowledge."
"Many knowledge systems have little ability to create new interfaces, but their experience can be shaped by how they’re used and configured."
"The chatbot method is very transactional: user asks, system responds, and that is pretty much it."
"There needs to be some sort of universal standard for sourcing or mapping how the knowledge was obtained."
"We need to break out of the 30 years of design that has been geared around relational databases."
"Knowledge is very conceptual, very abstract, and you’re trying to make it very concrete to use."
"The best experiences I’ve had are where information architecture and user experience worked hand in hand."
Or choose a question:
More Videos
"We thought she was in great shape and we were thrilled, then found out she didn’t know to BCC 500 customers—this still stresses me years later."
Elizabeth Sklar Jessica ShengCo-creating research enablement with your tech org: a case study
March 10, 2026
"Adoption is the only thing that matters in innovation. If you’re not changing behavior, you haven’t innovated."
Saara Kamppari-Miller Nicole Bergstrom Shashi JainKey Metrics: Comparing Three Letter Acronym Metrics That Include the Word “Key”
November 13, 2024
"Pair design is about two perspectives coming together as peers to quickly try and evaluate ideas."
Gretchen AndersonScaling the Human Center
June 8, 2017
"We track every hour so the team's time is visible and understood as the collective engine of revenue and rest."
Chelsea MauldinLet's Talk About Money
November 17, 2022
"Designers must take responsibility when designing systems that impact millions."
Lada GorlenkoTheme 3: Introduction
June 10, 2021
"What happens when a user customizes the UI? Does the experience break? This is the question to ask."
Craig VillamorResilient Enterprise Design
June 8, 2017
"We had passed through this awkward moment. I felt I had rudely probed into this open wound."
Susan Simon-DanielsWar Stories LIVE! Susan Simon-Daniels
March 30, 2020
"Research is not just delivering insights out there in a transactional model, but in a dialogic model."
Robin BeersBeyond Insights: Researchers as Organizational Change Catalysts
March 25, 2024
"Design requires teams because you can't be expert in everything—from pixels to hardware to databases."
Paul Pangaro, PhDSystems Disciplines: Table Stakes for 21st Century Organizations
June 6, 2023
