Skip to content
How to ThinkIn the Age of AI

Rituals and ceremonies encode culture

~6 min read

Core Primitive

Rituals are the heartbeat of cultural infrastructure — recurring shared experiences that reinforce what the organization values, how it makes sense of its work, and who its members are as a collective.

Unlike one-time events or written policies, rituals operate through repetition: each recurrence strengthens the cultural schema it encodes. The daily standup, the weekly retrospective, the quarterly offsite, the annual celebration — each ritual is a cultural maintenance mechanism, ensuring that the shared schemas remain active, current, and collectively held.

The rhythm of culture

Every organization has a rhythm — a pattern of recurring events that structure its collective experience. Daily standups. Weekly team meetings. Monthly all-hands. Quarterly planning. Annual reviews. These recurring events are not just scheduling artifacts. They are rituals — shared experiences that encode and reinforce the cultural schemas the organization holds.

The anthropologist Victor Turner distinguished between "liminal" and "liminoid" rituals. Liminal rituals are mandatory transformative experiences (rites of passage). Liminoid rituals are voluntary, recurrent practices that reinforce group identity and shared values. Organizational rituals are primarily liminoid: they do not transform members but they continuously reinforce what the group values, how it makes sense of its work, and what it means to belong (Turner, 1969).

The power of rituals comes from three properties that distinguish them from other cultural mechanisms.

Regularity. Rituals recur at predictable intervals. This regularity ensures that cultural reinforcement is not episodic but continuous. A value that is reinforced once a year (at the annual retreat) fades between reinforcements. A value that is reinforced weekly (at the retrospective) remains active in the organization's collective consciousness.

Participation. Rituals involve collective participation — members experience the ritual together, which builds shared schemas through shared experience. Reading a values document is individual. Participating in a ritual that enacts a value is collective. The collective experience creates social accountability: members who participated in the ritual hold each other to the schema it encodes.

Structure. Rituals have defined formats — specific sequences of activities, roles, and norms that distinguish the ritual from ordinary interaction. The structure creates a container within which the cultural schema can be enacted safely. A retrospective has a format (what went well, what could improve, what will we do differently) that makes it safe to discuss failures. Without the format, the same conversation might feel threatening.

Types of organizational rituals

Organizational rituals operate at different frequencies and serve different cultural functions.

Daily rituals

Daily rituals encode the schemas that need the most frequent reinforcement — typically operational schemas about how the team coordinates its work.

The daily standup is the most common daily ritual. When done well, it encodes transparency ("We share what we're working on"), accountability ("We commit to what we'll accomplish"), and mutual support ("We identify blockers so others can help"). When done poorly, it encodes status reporting ("We tell the manager what we did") or compliance ("We attend because we're told to").

Harrison Owen's concept of "opening space" suggests that the purpose of daily rituals is not information exchange but energy alignment — bringing the group into shared awareness of its current state and shared intention for its next actions (Owen, 2008). The informational content is secondary to the ritual function.

Weekly rituals

Weekly rituals encode learning and reflection schemas — the patterns through which the team improves its practices over time.

The retrospective is the most powerful weekly ritual when practiced genuinely. It encodes the schema that continuous improvement is part of the work, not an addition to it. Esther Derby and Diana Larsen's framework for effective retrospectives identifies five phases: setting the stage, gathering data, generating insights, deciding what to do, and closing the retrospective. Each phase serves a ritual function: the structure creates safety, the data-gathering normalizes honesty, and the action commitment prevents the ritual from becoming merely reflective (Derby & Larsen, 2006).

Monthly and quarterly rituals

Monthly and quarterly rituals encode strategic and identity schemas — the longer-arc narratives about who the organization is and where it is going.

The quarterly planning ritual encodes the schema that the organization is intentional about its direction — that its trajectory is chosen, not accidental. The all-hands meeting, when done well, encodes the schema that the organization is a unified entity with shared purpose — that individual and team efforts connect to something larger.

Annual rituals

Annual rituals encode identity and belonging schemas — the deepest cultural layers that define what it means to be a member of this organization.

The annual celebration (whatever form it takes) encodes the schema that membership matters — that the organization values the collective, not just the individual contributions. The annual planning ritual encodes the schema that the organization is self-directing — that it chooses its future rather than being buffeted by circumstances.

Ritual design principles

Not all rituals are equally effective. Effective rituals share several design principles.

Clear purpose. Every ritual should encode a specific cultural schema. If you cannot articulate what cultural value the ritual reinforces, the ritual is a meeting, not a ritual. The purpose should be understood by all participants — not as a formal statement but as a shared understanding of why this recurring experience matters.

Consistent format. The power of ritual comes from repetition, and repetition requires consistency. When the format changes every time, the experience loses its ritual quality and becomes an ordinary meeting. This does not mean rituals should be rigid — the content changes while the format remains stable. A retrospective always follows the same phases, but the specific discussions within each phase are different every time.

Active participation. Rituals that involve passive listening (the all-hands where the CEO talks for an hour) are weaker cultural encoders than rituals that involve active participation (the retrospective where every member contributes). Active participation creates ownership — participants feel responsible for the ritual's quality, which reinforces the cultural schema more powerfully than observation alone.

Protected time. Rituals that are frequently cancelled or postponed communicate that their cultural function is less important than whatever displaced them. Protecting ritual time — treating it as genuinely non-negotiable — is itself a cultural signal that reinforces the schema the ritual encodes.

Honest content. The ritual's credibility depends on its honesty. A retrospective where people only share positive feedback is a hollow ritual. A standup where people report only successes is a performance, not a practice. The ritual must create space for authentic engagement with both the comfortable and uncomfortable aspects of the cultural schema it encodes.

Ritual decay and renewal

Rituals naturally decay over time. A ritual that was meaningful at founding becomes rote after two years. A ritual designed for a ten-person team does not scale to a hundred-person organization. The format that once created safety now creates boredom.

Ritual decay follows a predictable pattern. First, participation becomes perfunctory — members attend but do not engage. Second, the format becomes shortened — corners are cut to save time. Third, the ritual is occasionally skipped — other priorities take precedence. Fourth, the ritual is abandoned — no one misses it because it had already stopped serving its function.

The antidote to decay is periodic ritual renewal: deliberately redesigning the ritual to maintain its cultural function while refreshing its format. The cultural schema stays the same; the mechanism for encoding it evolves. A retrospective might shift from a round-robin format to a whiteboard clustering format to a silent writing format — each change refreshes the ritual while maintaining its core function of encoding continuous improvement.

The Third Brain

Your AI system can help design and evaluate organizational rituals. Describe the cultural schema you want to reinforce and ask: "Design a ritual that would encode this cultural value. Specify the cadence (daily, weekly, monthly), the format (steps, roles, norms), the duration, and the participation model. How would this ritual encode the intended schema through experience rather than through instruction?"

The AI can also help diagnose ritual decay: "Here is a description of our weekly retrospective ritual — the original design and how it actually runs today. What signs of ritual decay do you see? Where has the ritual lost its cultural encoding power? How could we renew the ritual — refresh the format while maintaining the core cultural function?"

For ritual portfolio management, describe all your recurring rituals and ask: "Map each ritual to the cultural schema it encodes. Are there schemas that are over-reinforced (multiple rituals encoding the same schema) or under-reinforced (important schemas with no corresponding ritual)? Are any rituals encoding schemas that conflict with each other? Propose a rebalanced ritual portfolio that covers the most important schemas without creating ritual fatigue."

From practice to narrative

Rituals encode culture through recurring shared practice. But culture is also transmitted through narrative — the stories organizations tell about themselves, their history, their heroes, and their defining moments.

The next lesson, Stories carry culture, examines how stories carry culture — how organizational narratives encode cultural schemas in ways that persist across generations of membership and shape the organization's identity long after the events they describe.


Sources:

  1. Turner, V. (1969). The Ritual Process: Structure and Anti-Structure. Aldine.
  2. Owen, H. (2008). Open Space Technology: A User's Guide (3rd ed.). Berrett-Koehler.
  3. Derby, E., & Larsen, D. (2006). Agile Retrospectives: Making Good Teams Great. Pragmatic Bookshelf.

Put it into practice

Exercise

List all recurring meetings, events, and shared experiences in your team or organization. For each, identify: (1) What cultural schema does this ritual encode? (A daily standup might encode 'transparency and accountability.' A retrospective might encode 'continuous improvement.' A Friday happy hour might encode 'we are humans, not just workers.') (2) How effectively does the ritual encode that schema? Does the ritual actually reinforce the intended value, or has it become rote — going through the motions without the cultural substance? (3) Is there a cultural schema you want to reinforce that has no corresponding ritual? If so, design a ritual: a recurring, shared experience with a specific format, a regular cadence, and a clear cultural purpose. Start with something small — a 15-minute weekly practice — and let it grow.

More on putting it into practice

See it in action

An infrastructure engineering team at a cloud platform company had a ritual they called 'Failure Fridays.' Every Friday at 3pm, the team gathered for 30 minutes. One team member presented a failure from the week — a deployment that broke, a misconfigured service, a missed alert, an incorrect assumption. The presentation followed a strict format: What happened? What was the root cause? What did we learn? What will we change? The critical rule: no blame, no defensiveness, only curiosity and learning. The ritual had been running for two years when a new VP of Engineering, Chen, joined. Chen was surprised by Failure Fridays — in his previous company, failures were concealed, not celebrated. He observed six sessions before forming his assessment: the ritual was encoding a specific cultural schema — 'failures are data, not shame' — and reinforcing it weekly. The repetition meant that every team member had presented multiple failures and had seen dozens of others presented. The schema was not just stated; it was practiced. When Chen tried to introduce the ritual to other teams, he discovered that the ritual without the cultural foundation felt performative. Teams that did not already have psychological safety could not sustain the vulnerability that Failure Fridays required. The ritual encoded the culture, but the culture had to be seeded first through leadership behavior (Culture is built by repeated behavior) before the ritual could sustain it.

Watch for the failure mode

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 teach the organization that cultural practices are performances rather than genuine expressions of values. The test of a ritual's health is whether it would be missed if it stopped. If the team would not notice the absence, the ritual is already dead — it is just still moving.

Make it stick

This lesson extends the cultural transmission arc from (onboarding transmits culture during entry) to ongoing maintenance: rituals transmit and reinforce culture throughout the member's tenure. The connection to culture is built by repeated behavior is structural — rituals are the organizational mechanism that ensures behavioral repetition happens with regularity. Without rituals, cultural maintenance depends on individual consistency, which is unreliable. With rituals, cultural maintenance is built into the organization's operating rhythm. Look forward to Stories carry culture, which examines a different cultural transmission mechanism — stories, which carry culture through narrative rather than through practice.

Practice

Audit Your Team's Cultural Rituals in Notion

Map all recurring team rituals in a Notion database to identify which cultural schemas they encode, assess their effectiveness, and design new rituals for gaps in your cultural infrastructure.

15 minutesAdvanced
  1. 1Create a new database in Notion titled 'Cultural Rituals Audit' with columns for: Ritual Name, Frequency, Cultural Schema Encoded, Effectiveness Rating (1-5), and Notes. Add a separate table below called 'Missing Rituals' with columns for: Desired Schema, Proposed Ritual, Format, and Cadence.
  2. 2List every recurring team meeting, event, or shared experience in the main database — daily standups, weekly syncs, retrospectives, planning sessions, social events, celebrations. For each entry, write in the 'Cultural Schema Encoded' column what value or belief this ritual reinforces (e.g., 'transparency and coordination' for standup, 'continuous learning' for retrospective, 'we value relationships' for team lunch).
  3. 3Rate each ritual's effectiveness (1-5) in the Effectiveness Rating column by asking: Does this ritual actually reinforce its intended schema, or has it become mechanical? Add specific observations in the Notes column about what makes it effective or ineffective (e.g., 'standup feels rushed, people multitask' or 'retrospective generates real changes').
  4. 4Review your ratings in Notion and identify patterns: Which cultural schemas are well-supported by effective rituals? Which rituals have degraded into empty routines? Use Notion's filter and sort features to group by effectiveness rating and identify your weakest rituals that need redesign or retirement.
  5. 5In the 'Missing Rituals' table, identify 2-3 cultural schemas you want to strengthen that currently have no ritual support. For each, design a specific 15-minute weekly ritual with a clear format and purpose (e.g., 'Weekly Wins Share: 15-min Friday Slack thread where each person posts one accomplishment — encodes recognition and celebration'). Mark one to pilot next week.

Common questions about this lesson

More around this idea