What does it mean that the team cognitive audit?

Example: A reliability engineering team at a cloud provider had grown from four to twelve people over eighteen months. During the growth, several team cognitive systems degraded without anyone noticing. The team's transactive memory had not scaled — new members did not know who held expertise in which subsystems. The retrospective practice had become performative — the same issues appeared every sprint without resolution. Psychological safety had decreased as the team grew — newer members were quieter in meetings than the original four. The team lead, Roberta, conducted the team's first cognitive audit using the framework from this lesson. She assessed ten dimensions, and the results were revealing: the team scored well on decision protocols (4/5) and documentation (4/5) but poorly on transactive memory (2/5), psychological safety (3/5), and cognitive load distribution (2/5). The audit gave Roberta something she had not had before: a prioritized map of where the team's cognitive architecture needed investment. She focused the next quarter on two interventions: rebuilding the expertise map (The team's knowledge graph) and restructuring meetings to ensure all voices were heard (Meeting design as cognitive architecture). The targeted investment produced measurable improvement — the next audit, three months later, showed both dimensions had improved by a full point.

Try this: Conduct a team cognitive audit using this ten-dimension framework. Rate each dimension 1-5 (1 = absent or broken, 3 = functional but inconsistent, 5 = well-designed and maintained). (1) Shared mental models — does the team have aligned understanding of the system, process, and goals? (2) Transactive memory — does the team know who knows what? (3) Psychological safety — do members feel safe to disagree, ask questions, and admit mistakes? (4) Decision protocols — does the team have explicit processes for high-stakes decisions? (5) Information flow — does the right information reach the right people in time? (6) Meeting quality — are meetings designed for their cognitive purpose? (7) Cognitive load distribution — is cognitive demand balanced across team members? (8) Documentation and memory — is institutional knowledge captured, current, and findable? (9) Retrospective effectiveness — does the team learn from its experience and implement changes? (10) Epistemic practices — does the team practice calibration, assumption surfacing, and evidence evaluation? Sum the scores. 40-50 = excellent cognitive architecture. 30-39 = functional with gaps. Below 30 = significant cognitive infrastructure debt. Identify the two lowest-scoring dimensions and create an improvement plan.