Skip to content
How to ThinkIn the Age of AI

Culture change starts with behavior change

~6 min read

Core Primitive

You cannot think your way to a new culture — you must act your way there.

The conventional approach to culture change starts with beliefs (communicate the new values) and hopes that behavior follows. The effective approach starts with behavior (change what people do) and lets beliefs follow. When people act in new ways and experience positive results, their beliefs update to explain and justify the new behavior. Behavior change precedes belief change, not the other way around.

The belief-behavior inversion

The conventional model of culture change follows a logical sequence: change beliefs first, and behavior will follow. Communicate the new values. Explain why they matter. Train people in the new mindset. Then wait for behavior to align with the new beliefs.

This model is intuitive, logical, and wrong.

Leon Festinger's cognitive dissonance theory — one of the most replicated findings in social psychology — demonstrates the opposite causal direction. When people behave in ways that conflict with their existing beliefs, they experience cognitive dissonance — an uncomfortable tension between behavior and belief. To resolve the dissonance, they update their beliefs to be consistent with their behavior, not the other way around. The classic experiment: participants paid a small amount to tell someone a boring task was interesting subsequently came to believe the task was more interesting — because their behavior (saying it was interesting) created dissonance with their belief (it was boring), and the belief shifted to resolve the dissonance (Festinger & Carlsmith, 1959).

Applied to culture change: when organizational systems require new behaviors and members perform those behaviors, the members experience dissonance between the old belief ("individual excellence is what matters") and the new behavior ("I just collaborated successfully on a proposal"). The dissonance resolves in favor of the behavior — the member begins to believe that collaboration is valuable. The behavior created the belief, not the other way around.

Behavioral architecture

If behavior change precedes belief change, then culture change is fundamentally a design problem — designing the organizational systems that shape behavior so that the desired behaviors become the default.

Richard Thaler and Cass Sunstein's concept of "choice architecture" applies directly. Choice architecture is the design of the environments in which people make decisions. Small changes in the environment — the default option, the ordering of choices, the visibility of information — produce large changes in behavior without requiring anyone to change their beliefs first. The same principle applies to organizational culture: behavioral architecture is the design of the organizational environment so that the desired cultural behaviors are the easiest, most natural, most rewarded options (Thaler & Sunstein, 2008).

Default behaviors. The most powerful behavioral lever is the default — the behavior that happens when no one makes a deliberate choice. If the default meeting format includes a round-robin where every attendee speaks, the default behavior is inclusive participation. If the default meeting format is open discussion, the default behavior is domination by the most assertive voices. Changing the default changes the behavior without requiring anyone to change their beliefs about inclusion.

Friction reduction. Make the desired behavior easier. If you want knowledge sharing, put the sharing tool in the workflow where work is already happening — not in a separate system that requires extra steps. If you want cross-functional collaboration, co-locate the functions or create shared channels — do not rely on people seeking each other out across organizational boundaries. Every step of friction between the current behavior and the desired behavior is an opportunity for reversion to the old pattern.

Friction addition. Make the undesired behavior harder. If you want to reduce information silos, require that all significant decisions be documented in a shared space — not to create bureaucracy but to add a small friction to the silo pattern. If you want to reduce hero culture, require that every project have a documented succession plan — making it structurally harder for critical knowledge to remain in a single person's head.

The behavior-belief cycle

The relationship between behavior and belief is not one-directional — it is a cycle. Behavior influences belief (through cognitive dissonance), and belief influences behavior (through motivation and intention). The cycle can be virtuous or vicious.

Virtuous cycle: New systems require new behavior → new behavior produces positive results → positive results update beliefs → updated beliefs motivate more of the new behavior → the behavior becomes self-sustaining.

Vicious cycle: New behavior is required but produces no positive results (because supporting systems are not yet aligned) → the absence of results reinforces old beliefs → old beliefs motivate reversion to old behavior → the culture change stalls.

The key to initiating the virtuous cycle is ensuring that the new behaviors produce visible, positive results early. This means selecting the initial behavioral changes carefully — choosing behaviors that are likely to produce quick, observable benefits. A culture change initiative that starts with an easy win (a small collaboration that produces a better outcome than either individual could have achieved alone) builds the evidence that the new behavior works, which begins to shift the beliefs.

The role of narrative

Behavioral change provides the raw material for belief change. But the belief change is accelerated when the behavioral evidence is accompanied by narrative — a story that explains why the new behavior worked and what it means for the organization.

When Apex's consultants collaborated on proposals and won more business, the behavioral evidence was present. But the belief change accelerated when the CEO told the story: "Last quarter, Sarah and Marcus combined their expertise on the Whitfield proposal — Sarah's supply chain knowledge and Marcus's digital transformation experience created a proposal that neither could have written alone. Whitfield chose us specifically because of the integrated perspective. That is what collaboration looks like in practice."

The story does not create the behavioral change — the structural system does. But the story accelerates the belief change by providing a narrative framework for interpreting the behavioral evidence. Without the story, the collaboration might be attributed to luck or to the specific individuals involved. With the story, it is attributed to the cultural value of collaboration — which strengthens the belief that collaboration is how the organization succeeds.

Practical application

The behavior-first approach to culture change follows a specific sequence.

Step 1: Define the target behaviors. Not "we want a culture of innovation" but "we want people to propose experiments, run them with minimal approval, and share the results regardless of outcome." The target behaviors must be specific enough to be observed, measured, and structurally supported.

Step 2: Design the structural supports. For each target behavior, identify the structural change that would make the behavior easier, more rewarded, or more default. Change the process, the metric, the incentive, the meeting format, or the tool.

Step 3: Implement and observe. Make the structural changes and observe whether the target behaviors increase. If they do, the structural design is working. If they do not, the structural design needs adjustment — not more communication about why the behavior matters.

Step 4: Narrate the results. When the new behaviors produce positive results, tell the stories. The stories convert behavioral evidence into belief evidence — they help members construct the narrative framework that explains why the new behavior is working and why it should continue.

Step 5: Sustain and expand. Once the initial behaviors are producing results and the accompanying beliefs are beginning to form, expand to additional behaviors. Each successful behavior change strengthens the credibility of the culture change effort and reduces resistance to subsequent changes.

The Third Brain

Your AI system can help design behavioral architecture for culture change. Describe the cultural change you want to achieve and ask: "Translate this cultural aspiration into three to five specific, observable target behaviors. For each behavior, design a structural intervention — a change to a process, metric, incentive, meeting format, or tool — that would make the behavior the default rather than the exception. Prioritize the interventions by likely impact and ease of implementation."

The AI can also help you diagnose why behavioral changes are not taking hold: "We implemented these structural changes to encourage [target behaviors]. The behaviors have not increased as expected. Here is what we observe. What structural barriers might still be reinforcing the old behaviors? What additional changes might be needed?"

From behavior to resistance

Behavioral change is the lever for culture change — but the existing culture does not accept the lever passively. Established culture actively resists change through social pressure, institutional inertia, and identity defense. Understanding these resistance mechanisms — and designing for them — is essential for any culture change effort to succeed.

The next lesson, Cultural resistance to change, examines cultural resistance to change — the specific mechanisms through which the existing culture pushes back against behavioral change.


Sources:

  1. Festinger, L., & Carlsmith, J. M. (1959). "Cognitive Consequences of Forced Compliance." Journal of Abnormal and Social Psychology, 58(2), 203-210.
  2. Thaler, R. H., & Sunstein, C. R. (2008). Nudge: Improving Decisions About Health, Wealth, and Happiness. Yale University Press.

Put it into practice

Exercise

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 exception: a process change, a metric change, an incentive change, or a meeting format change. Implement one mechanism this week. Do not announce it as a culture initiative — just change the structure. Observe whether the behavioral change occurs. If it does, observe whether the belief change follows over the next several months.

More on putting it into practice

See it in action

A consulting firm, Apex, wanted to shift from a culture of individual expertise (each consultant owns their client relationships and guards their knowledge) to a culture of collaborative knowledge-sharing (consultants pool their expertise and serve clients as a collective). The CEO tried the conventional approach first: a company retreat where the leadership team presented the case for collaboration, shared research on how collaborative firms outperform individual-star firms, and asked everyone to commit to sharing more. Three months later, nothing had changed. Knowledge remained siloed, client relationships remained territorial, and the collaboration tools the firm had purchased sat unused. The CEO then tried the behavioral approach. She identified three specific behaviors and made them structurally unavoidable: (1) Every proposal must include at least two consultants from different practice areas — no single-consultant proposals accepted. (2) Every project debrief must produce a one-page knowledge artifact deposited in the shared repository — no debrief is considered complete without it. (3) Quarterly bonuses include a component based on knowledge contributions rated by peers. Within six months, the behaviors changed — not because consultants suddenly believed in collaboration but because the systems required it. Within twelve months, the beliefs began to change — consultants who had collaborated and experienced better client outcomes began to genuinely value collaboration. The behavior preceded the belief. The belief followed the behavior.

Watch for the failure mode

Attempting to change behavior through exhortation rather than through structural change. Telling people to 'collaborate more' without changing the structures that reward individual work is exhortation — it asks people to behave against their incentives. Changing the structures so that collaboration is the path of least resistance is behavioral architecture — it makes the desired behavior easier than the alternative. Exhortation produces temporary compliance. Structural change produces durable behavioral change. The failure mode is investing in communication and training when the investment should be in system redesign.

Make it stick

This lesson is the actionable counterpart to Culture change is slow and difficult's diagnosis of why culture change is structurally difficult. Where Culture change is slow and difficult explained the resistance, this lesson provides the leverage point: behavior, not belief. The connection to culture is built by repeated behavior is foundational — if culture is deposited by behavior, then culture change requires changing the behaviors that deposit it. The connection to schema design as leadership work is also direct: schema design operates on the same principle — change the cognitive infrastructure (schema) and behavior follows. This lesson applies the same principle at the operational level: change the behavioral infrastructure (systems, processes, incentives) and culture follows. Look forward to Cultural resistance to change, which examines the resistance mechanisms that the existing culture deploys against behavioral change.

Practice

Design a Behavior-First Culture Mechanism in Notion

Map your current process, identify a cultural behavior change, and embed a structural mechanism directly into your team's Notion workspace that makes the new behavior the default.

15 minutesAdvanced
Method: Process MappingTool: Notion
  1. 1Open Notion and navigate to a team workspace where you want to implement cultural change. Create a new page titled 'Behavior Change Mechanism: [Your Target Behavior]' and write one sentence describing the cultural outcome you want (e.g., 'A culture of giving constructive feedback').
  2. 2Create a two-column table in Notion with headers 'Current Process' and 'Desired Behavior'. In the left column, document the exact steps of how work currently flows for a specific process (e.g., code review, project handoff, client onboarding). In the right column, write three specific observable behaviors that would demonstrate your target culture (e.g., 'Every code review includes one specific strength and one specific improvement').
  3. 3Below your table, create a section titled 'Structural Mechanism' and design one process modification that makes your desired behavior automatic. Use Notion's database, template, or automation features to embed this mechanism—for example, create a 'Code Review Template' with mandatory fields for 'One Strength' and 'One Improvement', or add a required checkbox in your project handoff database that says 'Feedback conversation scheduled'.
  4. 4Implement your mechanism immediately in Notion by updating the relevant team page, database template, or workflow documentation. Do not announce this as a 'culture initiative'—simply replace the old process template with your new one, or add the new required field to an existing database. If team members ask about the change, describe it as a process improvement, not a values statement.
  5. 5Create a private page in Notion titled 'Behavior Change Observation Log' with a simple table containing columns for 'Date', 'Behavior Observed', and 'Notes'. Set a recurring reminder to log observations weekly for the next three months, noting whether people are using the new mechanism, whether the behavior is occurring, and any spontaneous comments that suggest belief change (e.g., team members saying 'I really value how we do X now').

Common questions about this lesson

More around this idea