What does it mean that the organization's knowledge graph?

Every organization has a knowledge graph — a network of expertise, institutional memory, relationships, and documented information that its schemas operate on. Mapping this graph reveals where knowledge is concentrated, where it is fragile (held by a single person), where it is redundant, and where critical gaps exist. The knowledge graph is to the organization what working memory is to the individual: the substrate that schemas operate on.

Example: A platform engineering team at a healthcare company supported forty microservices. The team lead, Alicia, suspected that the team's knowledge was unevenly distributed but did not know how unevenly. She conducted a knowledge mapping exercise: she listed every service and every critical operational domain (deployment, monitoring, incident response, data migration, compliance), then asked each team member to self-assess their knowledge as 'can teach others,' 'can operate independently,' 'can operate with reference documentation,' or 'no knowledge.' The resulting map was alarming. Three of the forty services had only one person who could operate them independently. The compliance domain — critical in healthcare — had deep expertise in exactly two people, both of whom had been at the company for more than five years. The deployment pipeline was understood deeply by the original architect, who had given notice the previous week. Seven services had no one who could teach others. The knowledge graph was not just uneven — it was fragile. Any departure in the wrong position would create a knowledge gap that could take months to fill. Alicia used the map to create a deliberate knowledge distribution plan: pair programming assignments, documentation sprints, and cross-training rotations targeted at the most fragile knowledge nodes. Within six months, no service had fewer than two people who could operate it independently, and the compliance domain had been documented thoroughly enough that new team members could reach operational competence in weeks rather than months.

Try this: Create a knowledge map for your team. List the five to ten most critical knowledge domains for your team's work. For each domain, list every team member and rate their knowledge level: 'can teach' (4), 'independent' (3), 'with documentation' (2), 'no knowledge' (1). Sum each domain's scores and divide by the number of team members to get an average knowledge density. Flag any domain where only one person scores 3 or above — these are your fragile knowledge nodes, where a single departure would create a critical gap. Flag any domain where no one scores 4 — these are domains where the team lacks deep expertise. Use the map to plan knowledge distribution activities for the next quarter.