Frequently asked questions about thinking, epistemology, and cognitive tools. 300 answers
Map the decision flow in your organization for one week. For every decision you encounter — whether you make it, request it, or wait for it — record: (1) What was the decision? (2) Who made it? (3) Who had the information needed to make it? (4) Were the decision-maker and the information-holder.
Confusing self-direction with absence of structure. The most common failure is removing hierarchy without building infrastructure — eliminating managers without creating the decision frameworks, information systems, and feedback mechanisms that managers provided. The result is not self-direction.
With the right infrastructure, organizations can govern themselves without constant top-down control. Self-direction is not the absence of structure — it is the presence of a different kind of structure. Hierarchical organizations coordinate through command: a small number of people at the top.
Audit one week of decisions in your team or organization. For each decision, record: (1) Who made the decision? (2) Who had the most relevant information? (3) How long did the decision take from request to resolution? (4) How much of that time was active analysis versus waiting in queues? (5) Was.
Distributing decisions without distributing information. The most common failure in distributed decision-making is giving people authority without giving them the information, context, and criteria they need to exercise it well. A product manager authorized to set prices without access to margin.
Moving decisions to the people closest to the information improves both speed and quality. Centralized decision-making creates a fundamental information problem: the person with the authority to decide is not the person with the best information about the situation. Every level of hierarchy that a.
Run a one-week self-organization experiment with your team. For one sprint or work week, give the team full authority over three decisions that are currently made by management: (1) task allocation — let the team decide who works on what, (2) process design — let the team design their own daily.
Self-organization without boundaries. Teams given unlimited self-organization authority with no strategic context, no resource constraints, and no coordination requirements will optimize for their own comfort rather than organizational outcomes. A team might choose to work only on technically.
Teams that organize their own work outperform teams that are organized from above. Self-organizing teams determine their own task allocation, workflow design, role assignments, and coordination patterns — within boundaries set by the organization's purpose and strategic direction. They outperform.
Test your organization's purpose as a coordination mechanism using three scenarios. For each, ask: does our stated purpose help resolve this decision, or is the purpose too vague to guide the choice? Scenario 1: Two projects compete for the same engineering resources. Project A is more profitable;.
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.
A clear shared purpose coordinates behavior without requiring detailed instructions. Purpose is the highest-leverage coordination mechanism available to organizations — it aligns decisions, filters priorities, and resolves conflicts without centralized control. When every member of an organization.
Conduct an information accessibility audit for your team. List the ten most important decisions your team makes in a typical month. For each decision, identify: (1) What information is needed to make this decision well? (2) Who currently has access to that information? (3) How does the.
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.
When information flows freely, coordination happens naturally. Transparency is not a virtue — it is an infrastructure. In hierarchical organizations, information is a source of power: managers control information flow and use their information advantage to justify their decision-making authority..
Map your organization's current feedback systems at four frequencies. For each frequency, identify: (1) Real-time — what automated or immediate signals does the organization generate about its performance? Are they visible to the people who can act on them? (2) Weekly — what regular information.
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.
Built-in mechanisms for the organization to learn from its own performance. Organizational feedback systems are the sensing and correction mechanisms that enable an organization to detect deviation, learn from experience, and adjust behavior without management intervention. In hierarchical.
Design and run a lightweight organizational retrospective with three to five representatives from different teams. Use this structure: (1) Individual brainstorm (5 minutes): each participant writes answers to three questions — 'What is working well across the organization?' 'What is frustrating or.
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.
Regular collective reflection at the organizational level drives continuous improvement. A retrospective is a structured practice of looking backward to move forward — examining what happened, why it happened, and what should change. At the team level, retrospectives are well-established in agile.
Select one governance mechanism in your organization — an approval process, a meeting cadence, a reporting structure, a resource allocation method — and evaluate it using four questions: (1) What purpose does this mechanism serve? What organizational need does it address? (2) Is it still serving.
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.
Governance structures that can evolve as the organization grows and changes. Most organizational governance is static — designed once and changed only through major reorganization efforts. Adaptive governance is governance that includes its own mechanisms for evolution: regular review,.