Frequently asked questions about thinking, epistemology, and cognitive tools. 497 answers
Purpose as aspiration rather than infrastructure. Many organizations have inspiring purpose statements that have no operational impact — they appear on the website and in the annual report but are never referenced in actual decisions. The failure is treating purpose as a branding exercise rather.
Transparency without context. Raw information without context is noise, not transparency. Publishing a revenue dashboard without explaining what the numbers mean, what is normal versus alarming, and what actions different scenarios warrant produces anxiety rather than alignment. A team that can.
Feedback without correction mechanisms. Many organizations generate extensive feedback data — metrics dashboards, survey results, performance reports — but lack the mechanisms to convert feedback into action. The data exists, but no one is responsible for responding to it, no process triggers.
Retrospectives that produce insights but not changes. The most common retrospective failure is generating rich discussion and accurate diagnosis without producing concrete action. The team leaves the retrospective feeling heard and understood — but nothing changes. The dysfunction persists, and.
Governance rigidity — treating governance structures as permanent fixtures rather than evolving tools. Organizations often treat their governance structures — meeting cadences, approval processes, reporting lines, decision rights — as immutable features of the organizational landscape. The meeting.
Objection inflation — participants framing preferences as objections to block decisions they personally dislike. Consent-based decision-making requires disciplined distinction between objections (substantiated concerns about specific harm) and preferences (personal opinions about what is best)..
Role ambiguity — defining roles so vaguely that authority overlaps, gaps exist, and conflicts arise about who has the authority to decide. The most common role-based authority failure is poorly defined role boundaries: two roles that both claim authority over the same decision domain, or a.
Knowledge management as documentation — creating documentation repositories that no one reads. The most common knowledge management failure is treating knowledge as a documentation problem: create documents, store them in a wiki, and assume the knowledge is managed. But documentation is only.
Confusing training with learning. The most common organizational learning failure is equating 'learning' with 'training' — sending people to courses, conducting workshops, distributing educational materials. Training is individual knowledge acquisition; organizational learning is systemic behavior.
Emotional suppression — treating emotions as unprofessional, inappropriate, or irrelevant to organizational performance. Many organizations operate on the implicit assumption that emotions have no place at work — that professional behavior means suppressing emotional responses and making decisions.
Confusing efficiency with resilience. Highly efficient organizations often strip out redundancy — every person is fully utilized, every process is optimized, every resource is allocated. This maximizes output in normal conditions but minimizes the capacity to absorb shocks: there is no slack to.
Single-source meaning-making — relying on one leader to interpret all events and communicate meaning to the organization. This creates three problems: (1) the leader's interpretation is limited by their perspective, missing signals visible to other functions; (2) the organization does not develop.
False sovereignty — the appearance of autonomy without the reality. Many organizations claim to value individual sovereignty while structurally undermining it: encouraging 'innovation' while punishing failed experiments, soliciting 'honest feedback' while penalizing dissent, promising 'autonomy'.
Improvement without measurement — making changes without measuring their impact. The self-improvement cycle requires closed-loop feedback: sensing performance, making a change, and then sensing performance again to determine whether the change helped. Organizations that make continuous changes.
Individual epistemic investment without organizational infrastructure. Many organizations invest heavily in individual development — training programs, educational benefits, conference attendance — while neglecting organizational epistemic infrastructure. The result is well-educated individuals.
Scale-blind application — applying mechanisms from one scale directly to another without adapting them. A personal journal does not scale to a team (too private). A team retrospective does not scale to an organization (too many participants). An organizational knowledge management system does not.
Treating sovereignty as a final state rather than an ongoing practice. The word 'sovereignty' can imply a permanent achievement — once you have it, you have it forever. But epistemic sovereignty, at both individual and organizational levels, is a continuous practice that requires continuous.