Frequently asked questions about thinking, epistemology, and cognitive tools. 100 answers
Walk through your workspace — physical or digital — and inventory the artifacts. For physical spaces: What does the office layout communicate about what the organization values? What do the meeting rooms look like — are they designed for presentation (projectors, podiums) or for collaboration.
Choose one cultural value your organization claims to hold and measure it using all three approaches. (1) Behavioral observation: Identify two or three behaviors that would be present if this value were genuinely enacted. Track those behaviors for one week. How frequently do they occur? (2).
Identify one cultural pattern in your team or organization that has persisted despite explicit attempts to change it. Reconstruct the history of change attempts: What was tried? How long was each attempt sustained? What happened when the attempt ended? Then analyze the persistence through the.
Identify one cultural change you want to make. Instead of communicating the desired belief ('We should value X'), identify three specific behaviors that would constitute the culture you want. For each behavior, design a structural mechanism that makes the behavior the default rather than the.
Think of a recent change initiative in your organization that encountered resistance. Map the resistance across four categories: (1) Social pressure — Did peers discourage the new behavior through informal signals? (2) Institutional inertia — Did existing systems, processes, or tools make the new.
Map the sub-cultures in your organization. Start by identifying the groups: functions (engineering, marketing, sales, support), geographies (if applicable), hierarchical levels (leadership team, middle management, individual contributors), and tenure cohorts (founding team, early hires, recent.
Take your organization's current strategic priority and assess its cultural alignment. List the three to five key behaviors the strategy requires for successful execution. For each required behavior, assess: Does our current culture support this behavior (the cultural infrastructure makes it easy.
Design a cultural feedback loop for your team. Choose one cultural value that matters most and identify: (1) The sensing mechanism — how will you detect when behavior drifts from the desired pattern? This could be a periodic survey, a behavioral metric, a ritual that surfaces cultural health, or a.
Identify one thing your organization does well that competitors struggle to replicate. Ask: Is the source of that advantage a product feature, a technology, a process, or a cultural pattern? If it is a product or technology, it is vulnerable to replication. If it is a process, it is moderately.
Assess your team's or organization's culture along the conformity-sovereignty spectrum. List five areas of organizational life: (1) How work is done (methodology, processes). (2) What problems are worth solving (strategic priorities). (3) How ideas are evaluated (criteria, evidence standards). (4).
Identify one cultural evolution you want to make — a gradual shift from a current cultural pattern to a modified one. Design a 12-month evolution plan: (1) Month 1-3: Identify one context (a single team, project, or process) where the desired cultural pattern can be piloted without disrupting the.
Conduct the 'leader absence test' — a thought experiment (or, if possible, an actual experiment). Ask: If I were completely unreachable for two weeks, what decisions would stall? What conflicts would escalate? What behaviors would degrade? Each answer reveals a point where the cultural.
Identify one recurring organizational outcome that frustrates you — something that keeps happening despite your efforts to change it. Instead of asking 'Who is causing this?', draw the system that produces it. Map the inputs (what triggers the process), the process steps (what happens in.
Take the system map you created in L-1661's exercise (the recurring outcome that frustrates you). For each system element you identified as a strong driver of the outcome, design a specific system change that would shift the outcome. For structural elements, ask: What structural redesign would.
Choose a system you want to change. Before designing any intervention, create a system map with four layers: (1) Boundary map — draw a circle around everything inside the system and list what is outside. Include upstream suppliers (who provides inputs?) and downstream consumers (who receives.
Take the system map you created in L-1663's exercise. For each component and connection, rate its leverage on a three-point scale: (1) Low leverage — changing this element would have minimal impact on the outcome; (2) Medium leverage — changing this element would shift the outcome noticeably but.
Map the feedback loops maintaining one persistent pattern in your organization — either a pattern you want to preserve or one you want to change. Start with the outcome and trace backward: What produces this outcome? What does the outcome produce in turn? Follow the chain until it loops back to.
Before implementing your next system change, conduct a pre-mortem for unintended consequences. Write down the intended change and the intended consequence. Then systematically ask five questions: (1) Who else is affected by this change besides the intended target? What will they do differently?.
For a change you are planning or currently implementing, map the resistance forces using a force field analysis. Draw a vertical line representing the current state. On the left, list the driving forces — the pressures pushing toward the desired change (market demands, leadership commitment, cost.
For a system change you are planning, create a stakeholder map. List every person, role, team, and function that interacts with the part of the system being changed. For each stakeholder, document: (1) Their current benefit from the existing system — what do they gain from the way things work now?.
For a system change you want to implement, build a coalition map. Identify the three layers of coalition you need: (1) Evidence providers — people who have data, experience, or pilot results that demonstrate the change works. Without evidence, the coalition is advocating for theory. (2) Capability.
Design a pilot for a system change you want to make. Define five elements: (1) Scope — what is the bounded context for the pilot? Choose a team, project, or process that is representative of the broader organization but small enough to monitor closely. (2) Duration — how long will the pilot run?.
For a recent change in your organization, assess whether the system actually changed by applying three tests: (1) The attention test — does the improved outcome persist when leadership attention moves to other priorities? If performance reverts when the spotlight moves, the system did not change —.
Identify one behavior in your organization that you have been trying to change through training, motivation, or persuasion. Ask: What structural change would make the desired behavior the default — the easiest path — without requiring individual motivation to sustain it? Consider four types of.