Frequently asked questions about thinking, epistemology, and cognitive tools. 100 answers
Two symmetric failures. The first is treating processes as sacred — refusing to modify a process because 'it has always been done this way' or because the process was designed by someone with authority. This treats the process as a fixed instruction rather than a living schema, ensuring that the.
Two symmetric failures. The first is value inflation — listing so many values that they provide no guidance. When an organization has eight or ten values, the values cannot function as schemas because they do not resolve tradeoffs. An organization that values 'innovation, quality, speed,.
Trying to change culture directly rather than changing the schemas that produce it. Culture is an emergent property — it arises from the interaction of lower-level components (schemas) and cannot be changed by addressing the emergent property itself. Telling people to 'be more innovative' does not.
Treating schema conflicts as one side being right and the other wrong. When engineering and marketing disagree, the typical organizational response is to decide which team's perspective is correct and force the other to conform. But schema conflicts between functions usually reflect different but.
Assuming that formal onboarding programs are sufficient for schema propagation. Formal onboarding covers policies, tools, and procedures — the explicit layer of organizational knowledge. But the most consequential schemas are implicit: who to go to for real answers, how decisions actually get.
Two failures that are mirror images. The first is schema rigidity — refusing to update schemas until a crisis forces the change. This produces organizations that are perfectly adapted to the past and catastrophically maladapted to the present, which is the pattern described in the example above..
Confusing documented knowledge with operational knowledge. An organization can have extensive documentation — wikis, runbooks, architecture diagrams — and still have a fragile knowledge graph if no one has internalized the documented knowledge well enough to act on it under pressure. Documentation.
Treating knowledge transfer as a departure event rather than an ongoing practice. When an employee gives notice, organizations often schedule a two-week knowledge transfer period. But two weeks is not enough to transfer years of accumulated knowledge — especially the tacit knowledge that cannot be.
Two opposing failures. The first is documentation as archaeology — creating documentation that is so detailed and comprehensive that it becomes impenetrable. A fifty-page document that captures every nuance of a system's history but cannot be navigated or searched effectively preserves knowledge.
Confusing learning by individuals with organizational learning. When a team member learns a better approach through personal experience, the organization has not learned — a person has learned. Organizational learning occurs only when the new knowledge is embedded in the organization's schemas,.
Attempting to pay down all schema debt at once. Organizations that discover their accumulated schema debt often try to update everything simultaneously — new strategy, new processes, new values, new culture. This produces change fatigue, resistance, and the failure of all changes rather than the.
Assuming that vertical schema misalignment is a communication problem that can be solved by more or better communication. When the CEO's strategy schema has not reached the front line, the typical response is more all-hands meetings, more strategy documents, more town halls. But communication.
Expecting one function to adopt another function's schema rather than translating between them. When engineering and marketing disagree, the typical response is to escalate to a leader who picks one side. This forces one function to adopt a schema that does not fit its context. The result is.
Conducting the audit without the authority or commitment to act on the results. A schema audit that produces scores but no interventions is worse than no audit: it creates awareness of problems without addressing them, which produces cynicism. Every schema audit should conclude with a prioritized.
Designing schemas through announcement rather than through reinforcement. A leader who announces 'We now value speed over perfection' has not changed the schema — they have stated an intention. The schema changes only when the organizational systems reinforce the announcement: when speed is.
Concluding that if schemas are sufficient, rules are unnecessary. Healthy schemas do not eliminate the need for rules, processes, and accountability. They reduce the need for excessive rules by making most behavior self-regulating — people who hold the right schemas naturally behave appropriately.
Concluding that because the gap between espoused and enacted culture exists, the solution is to stop having stated values. Stated values serve a legitimate purpose: they articulate the aspiration, provide a reference point for accountability, and give people language to advocate for the behaviors.
Treating culture-as-infrastructure as a call to over-engineer the organization with rigid processes, detailed policies, and comprehensive bureaucracy. Infrastructure does not mean rigidity. Good infrastructure is designed to enable flexibility, not prevent it. The highway system is infrastructure.
Expecting cultural change from a single dramatic gesture rather than from sustained behavioral repetition. The CEO who makes one powerful speech about transparency, then returns to information-hoarding behavior, has made a gesture, not a deposit. Cultural sediment requires repetition — the same.
Swinging from tolerance to zero-tolerance — creating a culture of fear where any deviation is punished harshly. The insight that tolerance sets the floor does not mean the floor should be set at perfection. People make mistakes, have bad days, and occasionally fall short of the organization's.
Hiring exclusively for cultural fit and producing a monoculture — a team of people who think, act, and look alike. Cultural fit does not mean cultural similarity. It means alignment on the core behavioral standards that define the cultural floor and the cultural values that shape the.
Confusing orientation with onboarding. Orientation is an event — a day or week of introductions, paperwork, and presentations. Onboarding is a process — a sustained, multi-month integration that shapes the new member's cultural schema through repeated exposure to the enacted culture. Organizations.
Creating rituals that are empty of meaning — ceremonies that follow a format without serving a cultural purpose. When a retrospective becomes a rote exercise where everyone says 'things went well' and nothing changes, the ritual has become hollow. Hollow rituals are worse than no rituals: they.
Curating stories that glorify the past without serving the present. Some organizational stories encode outdated schemas — the founding-era 'all-nighter hero' story that encodes the schema that overwork is virtuous, the 'cowboy coder' story that encodes the schema that individual brilliance trumps.