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 primarily use graph databases, which differ structurally from traditional tabular relational databases.
-
•
Knowledge is distinct from data and information by being designed for human action, not just consumption.
-
•
Graph-based knowledge representation uses subject-verb-object structures, paralleling sentence diagramming.
-
•
User experiences for knowledge creation are as important as experiences for knowledge consumption.
-
•
There is no universal standard for traceability and sourcing in AI-generated knowledge outputs.
-
•
Graph systems currently lack standardized UI elements and terminology, hampering adoption and UX consistency.
-
•
Enterprise knowledge systems must balance vast scales of interconnected subjects, objects, relationships, and metadata.
-
•
The World Economic Forum's transformation maps offer an elegant blend of graph-based and narrative information presentation.
-
•
Successful knowledge system design requires multidisciplinary collaboration, especially between UX and information architecture.
-
•
Effective communication with stakeholders involves adjusting jargon and language to enterprise culture and context.
Notable Quotes
"Knowledge is not only intended for human consumption, it is meant for human action."
"Graph databases use nodes and relationships instead of spreadsheet-like tables."
"The relational structure of knowledge mirrors subject-verb-object sentence diagrams we learned in school."
"Many knowledge systems have little ability to create new interfaces, but their usage can shape user experiences."
"There needs to be some universal standard for sourcing or mapping how the knowledge was obtained."
"The chatbot method is very transactional: user asks, system responds, and that is pretty much it."
"We are at the same place for graph-based systems that tabular systems were in the 1980s."
"If what I call organizational amnesia happens, you may have a knowledge problem."
"User experience and information architecture must work hand in hand from the earliest stages."
"We need to break out of the 30 years of design that has been geared around relational databases."
Or choose a question:
More Videos
"You’re born on third base but think you hit a triple — that’s the enterprise software delusion."
Standardizing Product Merits for Leaders, Designers, and Everyone
June 15, 2018
"You can mine metadata from your platform to spot emerging patterns and commoditize new components."
Simon WardleyMaps and Topographical Intelligence (Videoconference)
January 31, 2019
"Many smartwatch designs assume male hands as default, excluding smaller wrists and diverse body types."
Sandra CamachoCreating More Bias-Proof Designs
January 22, 2025
"I felt on edge around Jeff and physically depleted after our interactions."
Darian DavisLessons from a Toxic Work Relationship
January 8, 2024
"Stakeholder communication is crucial to professional strategy because without it, we run the risk of activity without impact."
Fisayo Osilaja[Demo] The AI edge: From researcher to strategist
June 4, 2024
"Creating tangible artifacts forces reaction and debate, helping break enterprise paralysis and drive decisions."
Uday GajendarThe Wicked Craft of Enterprise UX
May 13, 2015
"Consistency over business unit efficiency was a design principle to ensure unified interface and language."
Davis Neable Guy SegalHow to Drive a Design Project When you Don’t Have a Design Team
June 10, 2021
"Everyone wanted to know what was the official pattern and who was accountable for it."
Eniola OluwoleLessons From the DesignOps Journey of the World's Largest Travel Site
October 24, 2019
"Our two-way Jira integration allows you to link design activities directly with epics, user stories, and tasks."
Aurobinda Pradhan Shashank DeshpandeIntroduction to Collaborative DesignOps using Cubyts
September 9, 2022
